feat: add volume mount for ~/.copilot/session-state to persist events.jsonl#1469
Draft
feat: add volume mount for ~/.copilot/session-state to persist events.jsonl#1469
Conversation
Copilot
AI
changed the title
[WIP] Add volume mount for ~/.copilot/session-state to access events.jsonl
feat: add volume mount for ~/.copilot/session-state to persist events.jsonl
Mar 26, 2026
This comment has been minimized.
This comment has been minimized.
Contributor
|
🔮 The ancient spirits stir; the smoke-test oracle has passed through.
Warning
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Copilot CLI writes
events.jsonlto~/.copilot/session-state/inside the container, but AWF had no volume mount for that path — the file was discarded when the container stopped, leavingagent_outputsartifacts without the structured conversation JSONL needed for dashboards and debugging.Changes
generateDockerCompose): addsworkDir/agent-session-state → ~/.copilot/session-statealongside the existingagent-logsmountwriteConfigs): createsworkDir/agent-session-state/before container startagent-session-state/to/tmp/awf-agent-session-state-<timestamp>after the run, matching theagent-logspatterndocs/usage.md): documents the new preserved path and updates the "How it works" volume mapping listAfter a Copilot CLI run,
events.jsonlis available at:⌨️ Start Copilot coding agent tasks without leaving your editor — available in VS Code, Visual Studio, JetBrains IDEs and Eclipse.