Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: bilingual pair for the session-modes RFC

Browse Source 
The zh.md counterpart (section-for-section mirror per the i18n contract:
identical heading structure, byte-identical text fences, same link targets)
plus the recorded i18n.yaml and the language-switcher lines on both sides —
matching the approval / sandbox / env-state RFC practice.
This commit is contained in:
kingwl
2026-07-07 15:55:36 +08:00
parent 1c2d51c9ca
commit 61847183ad
3 changed files with 169 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/rfc/proposed/feature/2026-07-07-session-modes-plan-mode.md
View File

@@ -2,6 +2,8 @@
Status: proposed
English | [中文](2026-07-07-session-modes-plan-mode.zh.md)
## Problem
The harness has no way to put an agent into a reduced-authority working state. The canonical feature that needs one is plan mode — the agent explores and designs under a read-only tool policy, produces a reviewable plan, and crosses back into full authority only through an explicit approval. [The extension cookbook](../../../cookbook/extension-cookbook.md) already reserves the row ("Plan mode — `tools/pre-execute` (deny writes) + a mode prompt section"), and [the ACP feature matrix](../../../../packages/ui/acp/acp-feature-support.md) records session modes as a known gap both reference adapters ship (Claude's plan auto-mode, Codex's read-only / agent / full-access presets). Neither says where the mode STATE lives, how it survives resume and fork, or how its model-visible consequences stay honest with the session log.