Skip to content

Commit 182fd85

Browse files
committed
fix: replace vague ledger-capture guidance with concrete criteria
- /handoff command: 'if needed' → 'that aligns with the direction above' - handoff promptGuidelines: 'if needed' → 'that the next context will need' Both changes replace the ambiguous 'if needed' with phrases that anchor ledger capture to a specific referent the LLM can reason about: the user's explicit direction (command) or the next clean context (autonomous handoff).
1 parent 7b016b2 commit 182fd85

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

handoff/command.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ export function registerHandoffCommand(pi: ExtensionAPI, state: AgenticodingStat
3737
}
3838

3939
pi.sendUserMessage(
40-
`Handoff direction: ${direction}\n\nPrepare a real handoff in the current session and current context. Before calling the handoff tool, capture any reusable state in the ledger if needed. Then complete the picture in a concise but sufficiently detailed handoff brief and call the handoff tool in this turn. Preserve the important knowledge that is still only present in the current context so the next clean context can start well without re-deriving it. Use any structure that makes the next work unambiguous. Include findings, current state, unresolved questions, failed paths worth avoiding, next steps, refs, constraints, and spawn ideas when useful. Reference ledger entries by name when relevant.`,
40+
`Handoff direction: ${direction}\n\nPrepare a real handoff in the current session and current context. Before calling the handoff tool, capture any reusable state in the ledger that aligns with the direction above. Then complete the picture in a concise but sufficiently detailed handoff brief and call the handoff tool in this turn. Preserve the important knowledge that is still only present in the current context so the next clean context can start well without re-deriving it. Use any structure that makes the next work unambiguous. Include findings, current state, unresolved questions, failed paths worth avoiding, next steps, refs, constraints, and spawn ideas when useful. Reference ledger entries by name when relevant.`,
4141
ctx.isIdle() ? undefined : { deliverAs: "followUp" },
4242
);
4343
},

handoff/tool.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ export function registerHandoffTool(
106106
promptSnippet: "Pivot to a new job via deliberate handoff compaction",
107107
promptGuidelines: [
108108
"Call handoff when the job changes, or when context is past ~30% and noisy. " +
109-
"Capture reusable state in the ledger if needed, then draft a concise but " +
109+
"Capture reusable state in the ledger that the next context will need, then draft a concise but " +
110110
"sufficiently detailed brief that completes the picture for the next clean context.",
111111
],
112112

0 commit comments

Comments
 (0)