[FEATURE]: V2 Plan mode: restore V1 experimental plan mode's persistent session plan file workflow #49879

Activity

1. Dante-dan commented on Sep 19, 2026

   

   Dante-dan

   on Sep 19, 2026

   Contributor

   More actions

   I traced this against the V1 workflow and the current V2 plugin. V2 already made two intentional choices: #43710 allows writes under ~/.opencode/plan, while #46905 keeps planning conversational by default and writes a document only when the user explicitly asks. I think the session-file workflow should preserve both decisions rather than restore V1 wholesale.

   Proposed V2 scope:

   • derive one stable path from the durable session creation timestamp + slug, under the existing global Plan directory;
   • include that exact path in the Plan reminder, while retaining the explicit-user-request condition;
   • enforce that session-specific file in the write/edit/patch hook instead of exposing the whole Plan directory to every Plan session;
   • when switching from Plan to Build, mention the canonical path only if the file exists; keep the normal agent switch instead of reintroducing the V1 plan_exit tool.

   I would cover stable derivation across reminder reconciliation/restart, exact-file permission boundaries, no eager file creation, and the conditional Build handoff. Would this V2-shaped scope be acceptable for implementation?
2. shssoichiro commented on Sep 19, 2026

   

   shssoichiro

   on Sep 19, 2026

   Author

   More actions

   Yes, that would satisfy what I'm looking for.
3. fgbm commented on Sep 25, 2026

   

   fgbm

   on Sep 25, 2026

   More actions

   +1, with a concrete case from v2.0.16 (Linux).

   The opencode.plan plugin hardcodes the plan directory to path.join(home, ".opencode", "plan"), and the Plan reminder tells the model to write plan files only there. That breaks projects that keep plans in the repository (in our case docs/plans/, reviewed and versioned alongside ADRs):

   • the directory is shared by every project on the machine, so plans from different repos end up in one flat folder with no link to the project or session;
   • there is no config key to point it elsewhere, and edit is denied everywhere else in Plan mode, so the plan can't be written where the project expects it even when the user explicitly asks;
   • nothing hands the plan over to Build afterwards, so the file is effectively orphaned.

   What would solve it for us:

   1. a plans_directory config option (per-project config supported) that also extends the Plan agent's edit/external_directory allows — like feat: configurable plans directory and opt-out for plugin dependency installs #49502 does for v1, but applied to the v2 opencode.plan plugin;
   2. a per-session file name (<timestamp>-<slug>.md) injected into the reminder, as in the v1 workflow described above.

   Related: #50241 / #46358 (writes into ~/.opencode/plan are rejected even there), #46189 (v1 cluttering projects).

   👍React with 👍1Reacted by Wolverine
4. log0u7 commented on Oct 10, 2026

   

   log0u7

   on Oct 10, 2026

   More actions

   Adding one data point from the v1 -> v2 diff for whoever picks this up: the plan directory itself is now hardcoded to ~/.opencode/plan in packages/core/src/plugin/plan.ts (path.join(global.home, ".opencode", "plan")), and the plan agent's edit permission is scoped to that single directory.

   If the per-session plan file workflow described here gets restored, a small config knob for the directory (with ~ expansion) would fit naturally alongside the filename generation. The v1 proposals went through #49502 / #46199 / #46191. One trade-off to weigh: the single global directory avoids the per-project duplication complained about in #46189, so a per-worktree configurable path is not necessarily the right default.
5. log0u7 commented on Oct 28, 2026

   

   log0u7

   on Oct 28, 2026

   Last edited by log0u7

   More actions

   Current v2 already covers this. The session plan file persists in ~/.opencode/plan and Plan-mode reminders are re-injected across agent switches (packages/core/src/plugin/plan.ts). The plan_exit tool is gone, agent switching replaces it, so the V1 workflow this request asked to restore is effectively in place. This can be closed.
6. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed write-up, @shssoichiro! You're asking for v2 Plan mode to bring back the v1 experimental workflow: a plan file for each session at a generated <session-timestamp>-<slug>.md path, given to the Plan agent and kept up to date by it, with the handoff to Build pointing at that same file.

   For context, on dev the Plan reminder no longer says "not allowed to edit or create files". It now says not to create plan files unless the user explicitly asks, and to write them only under ~/.opencode/plan/. So writing a plan file is still something the user has to request, and there's no per-session file or handoff to Build yet. That's a design change rather than a bug, so I've marked this as a feature request for the maintainers to consider.

   Related issues and PRs:

   • [FEATURE]: Let custom primary agents participate in plan mode (plan file path + configurable plan_exit handoff target) #31868: plan file path and plan_exit handoff for custom primary agents (closed)
   • feat: Added plan_exit tool via question to switch from Plan to Build. #55123: PR adding a plan_exit tool to switch from Plan to Build
   • plan: write path hardcoded to ~/.opencode/plan and cannot be configured per project #55683: plan write path is hardcoded to ~/.opencode/plan
   • plan: plan agent cannot write to its own plan dir when the session cwd contains it #59838 / plan: Plan-mode guard denies writes to the configured plan directory it names (still present on beta-18721, macOS arm64) #46358: Plan agent unable to write to its own plan directory in some setups
7. macintacos

   added a commit that references this issue on Oct 29, 2026

   docs(opencode): record the real-model v2 check

   ...

   68b6d32