From f3e9bac97e7479c0afa7aab172982fed222ec359 Mon Sep 17 00:00:00 2001 From: Dave Date: Tue, 24 Feb 2026 11:52:41 +0000 Subject: [PATCH] story-kit: accept 86_story_show_live_activity_status_instead_of_static_thinking_indicator_in_chat --- ...ty_status_instead_of_static_thinking_indicator_in_chat.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.story_kit/work/5_archived/86_story_show_live_activity_status_instead_of_static_thinking_indicator_in_chat.md b/.story_kit/work/5_archived/86_story_show_live_activity_status_instead_of_static_thinking_indicator_in_chat.md index aa0b67b..bf57f75 100644 --- a/.story_kit/work/5_archived/86_story_show_live_activity_status_instead_of_static_thinking_indicator_in_chat.md +++ b/.story_kit/work/5_archived/86_story_show_live_activity_status_instead_of_static_thinking_indicator_in_chat.md @@ -15,6 +15,11 @@ As a user chatting with Claude in the web UI, I want to see what the agent is ac - [ ] When the agent is between tool calls (actually thinking), it shows "Thinking..." - [ ] The status text is derived from the streaming events already coming over the WebSocket - [ ] No new server-side changes needed if the stream already contains tool use events; otherwise add a lightweight status event type +- [ ] Activity indicators must work for Claude Code PTY sessions (used by agents), not just API-based LLM providers. The Claude Code provider must parse tool activity from the stream-json output and forward it via the same on_activity callback used by the Anthropic provider. + +## Notes + +Previous implementation (now reverted to upcoming) only wired up activity events for the Anthropic API provider. The Claude Code provider in `claude_code.rs` was left with no `on_activity` callback — it only streams text tokens. Since agents use Claude Code, the web UI showed no activity during agent work. ## Out of Scope