P3: document interactive vs pipeline boundary - #42
Merged
Conversation
Contributors need one place that says which Codex surface to use where: the headless pipeline stays plugin-free for reproducibility, while live sessions can lean on the official Codex plugin for ad-hoc review/rescue/transfer. Also pins the correct API tool type (advisor_20260301) so a future API-driven layer doesn't cargo-cult a wrong header/type pairing from tribal memory. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Phase 3 of the workflow-upgrade plan (plan @ e6db065). Docs-only.
What changed
CLAUDE.md:131-149— new "Interactive vs Pipeline Boundary" section: pipeline (bouncer, dev-review.sh, codex-ps) stays headless and plugin-free; interactive sessions may useopenai/codex-plugin-cc(/codex:adversarial-reviewbefore passing risky plans,codex:codex-rescuesubagent when stuck,/codex:transfer/status/result/cancel), review gate stays off; advisor tool documented as Messages-API-only (advisor-tool-2026-03-01,advisor_20260301type) with the opus-4.8-advisor-for-auditability rule.README.md:182-191— 9-line "Interactive Tooling vs The Pipeline" subsection with install commands.Verification — grep-clean: zero
/codex:*invocations in pipeline code (3 hits are prose/comments);docs-sync-simulation.sh38/38;tests/run-all.sh --quick25/25. No scripts, schemas, orrunners/codex-ps/**touched.Post-merge manual checklist (Alan, interactive session):
/plugin marketplace add openai/codex-plugin-cc→/plugin install codex@openai-codex→ smoke/codex:status→ confirm review gate off (/codex:setup --disable-review-gateif it defaults on). Record the/codex:statusoutput here.🤖 Generated with Claude Code