dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

Add story 39: Persistent Claude Code Sessions in Web UI

Browse Source 
Use --resume <session-id> with claude -p to maintain conversation
context across messages in the web UI claude-code-pty provider.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Dave
2026-02-20 11:16:17 +00:00
parent 94d05c905b
commit a6ea64cca7
1 changed files with 29 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
.story_kit/stories/upcoming/39_persistent_claude_code_sessions_in_web_ui.md Normal file
View File

@@ -0,0 +1,29 @@
---
name: Persistent Claude Code Sessions in Web UI
test_plan: pending
---
# Story 39: Persistent Claude Code Sessions in Web UI
## User Story
As a developer using the web UI with the claude-code-pty provider, I want my conversation context to persist across messages, so that Claude remembers what we've discussed and can build on prior work — just like a normal terminal Claude Code session.
## Background
Currently the `claude-code-pty` provider spawns a fresh `claude -p` process for every message, sending only the last user message. This means Claude has zero memory of prior conversation turns. The fix is to capture the session ID from the first `claude -p` call and pass `--resume <session-id>` on subsequent messages. Claude Code persists conversation transcripts locally as JSONL files, so resumed sessions have full context — identical to a long-running terminal session from the API's perspective.
## Acceptance Criteria
- [ ] First message in a web UI chat spawns `claude -p "<message>" --output-format stream-json --verbose` and captures the session ID from the `system` or `result` JSON event
- [ ] Subsequent messages in the same chat spawn `claude -p "<message>" --resume <session-id> --output-format stream-json --verbose`
- [ ] Conversation context carries across messages (Claude remembers what was said earlier)
- [ ] Starting a new chat in the web UI starts a fresh session (no resume)
- [ ] Session ID is held per web UI chat session (not global)
- [ ] Cancellation still works mid-message
## Out of Scope
- Multi-turn conversation history display in the frontend (already works via existing message state)
- Session persistence across server restarts
- Managing/cleaning up old Claude Code session files on disk