Bug Report: Council Skill — Fork Context Not Persisted
Date: 2026-06-15
Priority: Medium — causes silent data loss on substantive Council runs
Summary
When Council spawns forked agent instances to perform work, the full output of those forks is not saved to disk and does not return to the calling context. Only the synthesis summary returns. Any substantive work produced inside the fork — detailed analysis, frameworks, structured outputs — is permanently lost when the fork closes.
Reproduction
- Invoke Council with a complex analytical task requiring multiple agents to build a shared framework
- Council forks agents; agents produce detailed work (in our case: a 7-axis psychological framework with full definitions and cross-references)
- Council synthesizes across agents and returns summary to main context
- Expected: full agent outputs saved to disk OR returned in full to main context
- Actual: only synthesis summary returned; all intermediate agent work gone
Impact
In our session, Council was asked to develop a psychological framework for a creative project. The agents produced a complete 7-axis coordinate system with full definitions, inter-axis relationships, and 18 archetype placements. The synthesis returned a summary.
The complete framework was unrecoverable. Manual reconstruction from memory required approximately 2 hours of subsequent conversation.
This is a silent failure — there is no error, no warning, no indication the work was lost until the user attempts to reference it.
Expected Behavior
One of:
- Fork outputs saved to
MEMORY/WORK/{slug}/council-fork-{n}.md before synthesis
- Fork outputs included in full in the synthesis return (not summarized)
- Council warns before running that fork outputs will not be persisted, allowing user to adjust
Suggested Fix
In the Council fork execution context, before closing each fork, write the fork's full output to disk. The synthesis then references the saved files rather than summarizing from memory. This preserves the work regardless of context window behavior.
Reported after session loss. No crash, no error — just gone.
Bug Report: Council Skill — Fork Context Not Persisted
Date: 2026-06-15
Priority: Medium — causes silent data loss on substantive Council runs
Summary
When Council spawns forked agent instances to perform work, the full output of those forks is not saved to disk and does not return to the calling context. Only the synthesis summary returns. Any substantive work produced inside the fork — detailed analysis, frameworks, structured outputs — is permanently lost when the fork closes.
Reproduction
Impact
In our session, Council was asked to develop a psychological framework for a creative project. The agents produced a complete 7-axis coordinate system with full definitions, inter-axis relationships, and 18 archetype placements. The synthesis returned a summary.
The complete framework was unrecoverable. Manual reconstruction from memory required approximately 2 hours of subsequent conversation.
This is a silent failure — there is no error, no warning, no indication the work was lost until the user attempts to reference it.
Expected Behavior
One of:
MEMORY/WORK/{slug}/council-fork-{n}.mdbefore synthesisSuggested Fix
In the Council fork execution context, before closing each fork, write the fork's full output to disk. The synthesis then references the saved files rather than summarizing from memory. This preserves the work regardless of context window behavior.
Reported after session loss. No crash, no error — just gone.