[Bug]: Auto-restart is documented as `claude -c` (conversation kept) but the default is a fresh session (FW_RESTART_MODE=fresh, T-3166)
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 78/100
- Tipo di issue
- Documentazione
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- shell
- Ambito
- cli, documentation
Direzione di ricerca
Leggi la sezione Auto-Restart in lib/templates/claude-project.md e confronta le sue affermazioni con il valore predefinito in bin/claude-fw:1432; poi controlla i riferimenti elencati in bin/claude-fw, docs/harnesses.md, docs/context-compaction.md e agents/context/post-compact-resume.sh. Aggiorna le descrizioni per spiegare il valore predefinito di una sessione nuova e FW_RESTART_MODE=continue. Il lavoro è terminato quando tutta la documentazione citata corrisponde al comportamento del wrapper e spiega che è prevista una conversazione vuota.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Bug Description
Since T-3166 the budget-critical auto-restart starts a FRESH session by default (bin/claude-fw:1432, ${FW_RESTART_MODE:-fresh}): new transcript, seeded from the handover only, SessionStart source startup. The documents that describe the restart still say claude -c, i.e. the conversation is continued:
lib/templates/claude-project.md:875: "the wrapper detects this signal on exit and auto-restarts withclaude -c. TheSessionStart:resumehook then injects handover context into the fresh session."lib/templates/claude-project.md:877: "Flow: Budget critical → auto-handover → signal file → claude exits → wrapper detects →sleep 3→claude -c→ context injected →/resumeready."bin/claude-fw:6: "If found (and fresh), auto-restarts withclaude -cto continue."docs/harnesses.md:59: "claude-fwrestarts withclaude -cafter a handover signal."docs/context-compaction.md:88: "Same as above —claude -cre-injects via the same truncated path."agents/context/post-compact-resume.sh:8: "After claude -c (session continuation, including auto-restart via T-179)"
The template matters most: it becomes the agent's operating instructions (CLAUDE.md) in every consumer project. FW_RESTART_MODE itself appears only in bin/claude-fw and in one runbook (docs/runbooks/arc-012-continuous-mode-live-fire.md:39), so a consumer cannot learn that the choice exists.
Steps to Reproduce
grep -n 'claude -c' lib/templates/claude-project.md bin/claude-fw docs/harnesses.md docs/context-compaction.md agents/context/post-compact-resume.shgrep -n 'FW_RESTART_MODE' bin/claude-fw- Live: start a session with
claude-fw, noFW_RESTART_MODEset, and let it reach the budget cap.
Steps 1 and 2 were run on 1.8.6 and again on 1.8.11 (e42aa41bf). Step 3 was observed once on 1.8.6.
Expected Behavior
The template and the other documents describe what the wrapper does by default: a new session seeded from the handover, the previous conversation not in context (it can be reopened with claude --resume), and FW_RESTART_MODE=continue as the documented way to keep the transcript at the price of not freeing the context.
Actual Behavior
The operator came back to an empty conversation and asked whether it was a bug. The agent's instructions said the restart used claude -c, so the agent had no reason to expect an empty conversation either. The only place the real mode is named is one banner line ("Restart mode: fresh (new session, seeded from the handover)") printed during the three-second cancel window.
fw doctor output
AI Agent
Claude Code
Operating System
Linux
Additional Context
Version: 1.8.11 (e42aa41bf), vendored consumer. First observed on 1.8.6; every quoted line is still present in 1.8.11 (only line numbers moved). Outside bin/claude-fw, FW_RESTART_MODE is only mentioned in that runbook and in an internal report (docs/reports/T-3181-continuous-run-model-refinement.md).
The restart itself worked as designed; nothing was lost. This report is about the description only.
Suggestions:
- Rewrite the "Auto-Restart" section of the template for the fresh default, and document
FW_RESTART_MODE. - Fix the header of
bin/claude-fw, the header ofpost-compact-resume.sh,docs/harnesses.md:59anddocs/context-compaction.md:88the same way. - Say in the template what the operator sees: an empty conversation is the expected result, not a loss.
- Lingua principale
- Shell
- Stelle
- 16
- Fork
- 6
- Merge medio
- 6h 24m
- PR unite (30g)
- 5
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di DimitriGeelen/agentic-engineering-framework
-
area:doctor bug severity:low status:accepted triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
DimitriGeelen/agentic-engineering-framework#100 · 3 commenti ·
-
area:doctor bug severity:medium status:accepted triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
DimitriGeelen/agentic-engineering-framework#97 · 3 commenti ·
-
area:context bug severity:low status:accepted triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
DimitriGeelen/agentic-engineering-framework#96 · 3 commenti ·
-
area:watchtower bug severity:low status:released triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
DimitriGeelen/agentic-engineering-framework#94 · 4 commenti ·
-
area:watchtower enhancement severity:low status:released triaged
Difficoltà 2/5 Meno di un'ora Idoneità per principianti 75/100
DimitriGeelen/agentic-engineering-framework#91 · 5 commenti ·
Tutte le issue di DimitriGeelen/agentic-engineering-framework
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 2 giorni
-
needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
mattpocock/skills#1307 ·
I maintainer di solito rispondono entro 1 giorno
-
status: ready
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
melodic-software/claude-code-plugins#8537 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
vladmandic/sdnext#5161 ·
I maintainer di solito rispondono entro 1 giorno
-
severity: low
Difficoltà 1/5 1-3 ore Idoneità per principianti 89/100
luainkernel/lunatik#1980 ·
I maintainer di solito rispondono entro 1 giorno