[Feature Request] Plan Mode
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 30
Description
Feature request: Plan Mode
Add a read-only "plan first, execute after approval" mode, like the one in Claude Code, Codex, and Gemini CLI.
What it is
Agent investigates and writes a plan. Can read, search, and run exploration commands but can't edit source. User reviews the plan, then approves and drops into normal execution. Standard hotkeys across all three tools: /plan and Shift+Tab.
Prior art
- Claude Code: one entry in the permission-mode system. Minimal. docs
- Codex:
/plantoggle, recommended for ambiguous/complex tasks. docs - Gemini CLI: most fleshed out. Read-only tool allowlist, plan written to
.mdon disk,Ctrl+Xto edit it in$EDITOR, auto model routing (Pro for planning, Flash for execution), hooks, headless auto-approve. docs
Idea / MVP
/plan [goal]andShift+Tabto enter- Tool allowlist: read-only fs, grep, web search, read-only MCP, memory read,
ask_user. Writes only to the plan file. - Plan written to
~/.jcode/tmp/<project>/<session>/plans/*.md - Approve / iterate / cancel UX at the end
Ctrl+Eopens the plan in$EDITOR, agent picks up edits on save
Why this fits jcode specifically
- Side panel: render the plan there with mermaid diagrams, instead of jamming it into chat scrollback like the others do
- Swarm: plan becomes the dispatch spec; each worker gets its slice
- Self-dev: natural default for self-modification given the README's own warning about weaker models breaking things
- Skills: planning-flavored skills auto-activate via the existing semantic loader
Open questions
- Default on or off? (Gemini: on. Others: off.)
- Hard-block all shell, or allowlist
git status,cargo check, etc.? - Auto-checkpoint on plan approval?
- Adding a "clear context, then execute plan" feature, like
codexandclaudehave?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or existing entry points are named. Start by tracing the current command and hotkey handling, tool permissions, plan storage, and side-panel UI, then define the MVP around /plan, Shift+Tab, read-only tools, plan approval, and $EDITOR editing; done requires a tested end-to-end planning flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai, cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100