From 8b437fbb7d5abc5b3c21150f6250f095fabac7d7 Mon Sep 17 00:00:00 2001 From: Dave Date: Mon, 23 Feb 2026 17:43:05 +0000 Subject: [PATCH] story-kit: create 89_story_persistent_per_session_agent_logs --- ...story_persistent_per_session_agent_logs.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .story_kit/work/1_upcoming/89_story_persistent_per_session_agent_logs.md diff --git a/.story_kit/work/1_upcoming/89_story_persistent_per_session_agent_logs.md b/.story_kit/work/1_upcoming/89_story_persistent_per_session_agent_logs.md new file mode 100644 index 0000000..b9c2c45 --- /dev/null +++ b/.story_kit/work/1_upcoming/89_story_persistent_per_session_agent_logs.md @@ -0,0 +1,22 @@ +--- +name: "Persistent per-session agent logs" +test_plan: pending +--- + +# Story 89: Persistent per-session agent logs + +## User Story + +As a user, I want each agent session to write its output to a persistent log file so I can inspect what an agent did after it completes, even across server restarts. + +## Acceptance Criteria + +- [ ] Each agent session writes output to a log file at .story_kit/logs/{story_id}/{agent_name}-{session_id}.log +- [ ] Log files persist across server restarts and agent completions +- [ ] The get_agent_output MCP tool falls back to reading the log file when the in-memory stream is empty or the agent has completed +- [ ] Log files include timestamps, tool calls, text output, and status events +- [ ] Different sessions for the same agent on the same story produce separate log files (no mixing) + +## Out of Scope + +- TBD