From 8775470fa6d31a65c6c8e9b54a03bc6c5eaac14e Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Mon, 30 Mar 2026 20:14:09 -0700 Subject: [PATCH] =?UTF-8?q?feat:=20plan=20mode=20safe=20operations=20?= =?UTF-8?q?=E2=80=94=20browse,=20design,=20codex=20allowed=20in=20plan=20m?= =?UTF-8?q?ode?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add preamble section declaring $B, $D, codex, and ~/.gstack/ writes as plan-mode-safe. Unblocks design skills during planning. --- scripts/resolvers/preamble.ts | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/scripts/resolvers/preamble.ts b/scripts/resolvers/preamble.ts index 8cd1b557..7b144b2f 100644 --- a/scripts/resolvers/preamble.ts +++ b/scripts/resolvers/preamble.ts @@ -460,6 +460,21 @@ If you cannot determine the outcome, use "unknown". Both local JSONL and remote telemetry only run if telemetry is not off. The remote binary additionally requires the binary to exist. +## Plan Mode Safe Operations + +When in plan mode, these operations are always allowed because they produce +artifacts that inform the plan, not code changes: + +- \`$B\` commands (browse: screenshots, page inspection, navigation, snapshots) +- \`$D\` commands (design: generate mockups, variants, comparison boards, iterate) +- \`codex exec\` / \`codex review\` (outside voice, plan review, adversarial challenge) +- Writing to \`~/.gstack/\` (config, analytics, review logs, design artifacts, learnings) +- Writing to the plan file (already allowed by plan mode) +- \`open\` commands for viewing generated artifacts (comparison boards, HTML previews) + +These are read-only in spirit — they inspect the live site, generate visual artifacts, +or get independent opinions. They do NOT modify project source files. + ## Plan Status Footer When you are in plan mode and about to call ExitPlanMode: