Shawn Simister @narphorium.com · Apr 7

The CLI is great for a lot of things but reviewing Claude Code plans is not one of them. So much scrolling back and forward just to figure out what the agent changed

17 likes 11 replies

?

Replies

Prasad Chalasani · Apr 7

Anthropic just added an /ultraplan slash command for just this. “When the plan is ready, you open it in your browser to comment on specific sections, ask for revisions, and choose where to execute it.” code.claude.com/docs/en/ultr...

iBRAR 🍉 · Apr 7

I use source tree for this once a project has source control.

Tim Mackey · Apr 7

I made a slash command that tells Claude to give me the plan file path, open the file for me (I work in VSCode), and not to exit plan mode or present the plan until I say I’m ready to proceed. It’s made things a lot easier, can also open the plan in formatted markdown preview if you want.

Stephan Schlecht · Apr 7

That's true. Everyone works a little differently. I have it generate .md files and then use 'git difftool -d'.

sōm ⁂ · Apr 7

planninator might be something you'd like :) github.com/backnotprop/...

Pawel Jozefiak · Apr 8

Same pain. I started dumping plan output to a markdown file and reading it in a separate pane. Works for me, not sure it generalizes.