mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
c5cb7da364
The with-key recording session the RFC deferred. plan-mode is the 'plan' header class's pinning scenario and necessarily carries BOTH header shapes verbatim: the plan-shaped initial snapshot and the widened fallback snapshot the approved exit produces mid-turn — so the suite factory's pin guards relax from exactly-one to at-least-one header (the classmates' uniformity anchor is the pin's FIRST header; transition headers are legal only in the pin, matching the sandbox stack's precedent). plan-mode-reject pins the keep-planning branch: the corrective isError carries the reviewer's free-text feedback verbatim and the session stays in plan mode, one header, uniform with the pin. Recording notes, encoded in the prompts: the model is pinned to RELATIVE paths (a recorded absolute temp path neither replays on another host nor normalizes — the normalizers scrub the run's own cwd, not the recording's), and the recorded model never calls a filtered tool, so the gate's deny path stays pinned at the unit tier — that refusal is the behavior the soft layer exists to produce. The gen-tool-catalog meta-test pins exit_plan_mode in the harvested schema list.
29 lines
865 B
JSON
29 lines
865 B
JSON
{
|
|
"steps": [
|
|
{
|
|
"op": "initialize"
|
|
},
|
|
{
|
|
"op": "newSession"
|
|
},
|
|
{
|
|
"op": "setMode",
|
|
"modeId": "plan"
|
|
},
|
|
{
|
|
"op": "prompt",
|
|
"text": "The typo is on line 2 of notes.txt itself; the workspace contains no other file. Read notes.txt (use the relative path notes.txt exactly), then present a one-step plan titled '# Fix the greeting typo' via exit_plan_mode: the single step is editing line 2 of notes.txt to say hello world. After the review approves, apply exactly that one edit to notes.txt and stop \u2014 do not look for any other file."
|
|
},
|
|
{
|
|
"op": "prompt",
|
|
"text": "Read notes.txt (relative path notes.txt) and reply with the single word DONE if line 2 now says hello world."
|
|
}
|
|
],
|
|
"elicitationAnswers": [
|
|
{
|
|
"action": "accept",
|
|
"choice": "Approve"
|
|
}
|
|
]
|
|
}
|