Repository navigation
Conversation
Expose native plan mode through public exports, CLI parsing, authentication checks, and non-interactive execution.
- SDK, CLI, and RPC consumers had no supported way to enter plan mode or observe a submitted plan - Profile selection types stay out of the public surface so the export list carries no task profile dependency
Issacboy123
approved these changes
Aug 17, 2026
Issacboy123
left a comment
Contributor
There was a problem hiding this comment.
LGTM! This PR exposes plan mode consistently through CLI startup, slash commands, non-interactive mode, and the package API. The supporting argument, auth, main-mode, and command tests cover those public entry points. I determined there weren't any issues while I was reviewing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Exposes plan mode through the supported surfaces: the
--planCLI flag, the/planslash command, SDK exports, and a non-interactive plan mode entry point.Replaces #70. The accepted-plan harness routing from #69 is deliberately not included; it depends on the task profile stack and belongs to the integration stack.
Reasoning
Plan mode is not usable until a caller can enter it and observe a submitted plan without reaching into internals.
Keeping the public surface to plan concepts only means the export list carries no task profile dependency, which is what allows this stack to merge on its own.
--planis restricted to interactive mode because the non-interactive entry point needs an explicit resolution path rather than an interactive selector.Changes
--planCLI flag and/plan [on|off]slash commandCollaborationMode,PlanArtifact,PlanResolution,PlanContinuation, and the plan session entry typesmodes/non-interactive-plan-mode.tsfor headless plan handlingTesting
npx vitest --run test/main-plan-mode.test.ts test/args.test.ts test/slash-commands.test.ts test/auth-check.test.tstsgo --noEmitreports zero errors