DEDICATED SHORTCUT for switching seamlessly from PLAN to EXEC mode alongside "DESIRED MODEL preference for each mode"

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

Es werden keine Repository-Dateien oder Tests genannt. Beginne damit, das bereitgestellte session JSON mit den CLI-Einstiegspunkten für die Tab-Behandlung und die Modellauswahl über Slash-Befehle zu vergleichen. Als erledigt gilt die Aufgabe, wenn Tab zwischen den Modi PLAN und EXECUTION wechselt und dabei das konfigurierte Modell des jeweiligen Modus auswählt, wobei das erwartete Verhalten getrennt von der nicht zusammenhängenden cron-Anfrage geklärt wird.