CommandCodeAI / CommandCodeAI/command-code
DEDICATED SHORTCUT for switching seamlessly from PLAN to EXEC mode alongside "DESIRED MODEL preference for each mode"
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Summary
There should be a feature in which when we press the "Tab" key, we auto-switch b/w PLAN mode and EXECUTION mode alongside the desired model of choice for each mode respectively without the need to use the slash '/' command every time then select 'model' when transitioning between PLAN - EXEC modes.
TASTE.md knows the preference of it's user for each but it cannot implement this directly into the CLI cz the harness is hard-wired I guess.
OpenCode can be tweaked to do this instantly by doing edits in it's JSON file.
The cron_create scheduling mechanism is local native on disk, would have been better if it were running on a cloud when the command code team has no limitations to make it happen.
Expected Behavior
Mentioned above
Actual Behavior
Mentioned in summary
Steps to reproduce the issue
read summary
Command Code Version
1.15.1
Operating System
Linux
Terminal/IDE
Unknown
Shell
bash
Session file (optional)
{
"$schema": "https://opencode.ai/config.json",
"model": "openrouter/deepseek/deepseek-v4-flash",
"agent": {
"plan": {
"mode": "primary",
"model": "openrouter/deepseek/deepseek-v4-pro",
"description": "Token-efficient planning & SIGINT/ELINT
vectoring — read-only analysis, robust plan for DS V4 Flash execution"
},
"build": {
"mode": "primary",
"model": "openrouter/deepseek/deepseek-v4-flash",
"description": "Token-efficient execution — builds strictly
from the approved plan"
}
}
}
Default model = Flash (execution). Tab to plan switches to V4 Pro for
planning/analytics.
Fix prompt (optional)
N/A
Additional context
Mentioned in summary already
Contributor guide
No contributing guide indexed for this repository
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 repository files or tests are named. Start by comparing the supplied session JSON with the CLI entry points for Tab handling and the slash-command model selection. Done means Tab switches between PLAN and EXECUTION modes while selecting each mode's configured model, with the expected behavior clarified separately from the unrelated cron request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, json
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100