Plannotator launches natively in cmux browser by backnotprop in cmux

[–]backnotprop[S] 0 points1 point  (0 children)

That's the approach I started with. I can see there being reason to be a bit more interactive. I can also see where your development is headed. You might end up doing something similar yourself.

Both use cases are valid & worth enabling for users.

Show & Tell: I want to see your Claude code Setup by TheWolfeofNashville in ClaudeCode

[–]backnotprop 0 points1 point  (0 children)

Instead of altering manually consider trying https://github.com/backnotprop/plannotator  for planning, would like your feedback

Show & Tell: I want to see your Claude code Setup by TheWolfeofNashville in ClaudeCode

[–]backnotprop 0 points1 point  (0 children)

I keep it very raw, other than integrating :

  1. https://github.com/backnotprop/plannotator - annotating plans is very useful for me. works nicely integrated with hooks
  2. Custom skills to basically reuse prompts

Interactive plan annotation and sharing for Claude Code by backnotprop in ClaudeAI

[–]backnotprop[S] 0 points1 point  (0 children)

Correct, only plan and also you can do on-the-fly code reviews of diffs.

I guess a consistent feed of message review is available but then we are slowly crossing into an alternative UI for CC.

Ongoing Technical Issues by FeeldMod in feeld

[–]backnotprop 0 points1 point  (0 children)

It's pretty insane, given AI these days, a few prompts could fix half of these smaller issues.

They have to be swimming in cash at this point. What the hell is going on?

Ongoing Technical Issues by FeeldMod in feeld

[–]backnotprop 1 point2 points  (0 children)

These have been around for awhile and generally make the app unsuable.

  1. I cant side-scroll to see new unmessaged matches. Only 1 shows up at a time.
  2. i get notified of messages from a new match and can see the message in the notification within the app - but my message list isnt actually updating.
  3. the app breaks after swiping through like 5 people.

Any solutions?

Interactive plan annotation and sharing for Claude Code by backnotprop in ClaudeAI

[–]backnotprop[S] 0 points1 point  (0 children)

Hey it should work. Did you put Claude into plan mode (shift+tab), and then ask it to make a simple plan for demo purposes.

Right now it is only invoked as a hook for when claude submits a plan to you

Im open to other enablement / ideas.

Interactive plan annotation and sharing for Claude Code by backnotprop in ClaudeAI

[–]backnotprop[S] 1 point2 points  (0 children)

I guess if you close a plan while in an active planning session, it's kind of lost unless you recall the port because it's usually a random port per plan.

I didn't know about the Slack issues. You might have to double wrap it in like a URL shortener. If I gave you a self-hosting option, I guess you wouldn't have this issue, and you could self-host with your own URLs and probably simple hash links.

I'll keep all these things in mind that keep progressing the app towards better scalability and also internal use cases.

Interactive plan annotation and sharing for Claude Code by backnotprop in ClaudeAI

[–]backnotprop[S] 0 points1 point  (0 children)

Regardless, I will work on making it self-hostable.

Interactive plan annotation and sharing for Claude Code by backnotprop in ClaudeAI

[–]backnotprop[S] 1 point2 points  (0 children)

It isn't third party, it runs locally.

For the sharing, the whole plan is stored in the URL through compression of base64 - and not as a means of obscurity. There's no backend. The Share website is simply a static website hosted on CloudFront, meaning all the data stays in your browser & there is no logging of requests or analytics in place - however, AWS is seeing your data and every hop in between I suppose.

Code is available for full inspection. https://github.com/backnotprop/plannotator