From cbfad0347ae1c8b338ffa261bc385d630b5c9403 Mon Sep 17 00:00:00 2001 From: Dave Date: Tue, 24 Feb 2026 14:05:08 +0000 Subject: [PATCH] story-kit: start 147_bug_activity_indicator_still_only_shows_thinking_despite_bug_140_fix --- ...icator_still_only_shows_thinking_despite_bug_140_fix.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.story_kit/work/2_current/147_bug_activity_indicator_still_only_shows_thinking_despite_bug_140_fix.md b/.story_kit/work/2_current/147_bug_activity_indicator_still_only_shows_thinking_despite_bug_140_fix.md index 3b5fad0..0ce5219 100644 --- a/.story_kit/work/2_current/147_bug_activity_indicator_still_only_shows_thinking_despite_bug_140_fix.md +++ b/.story_kit/work/2_current/147_bug_activity_indicator_still_only_shows_thinking_despite_bug_140_fix.md @@ -66,6 +66,13 @@ Indicator always shows "Thinking..." and never changes to tool activity labels l Indicator should cycle through tool activity labels as the agent calls tools +## Hints for the Coder + +- **Check external docs**: The Claude Code CLI `--output-format stream-json` format may be documented at https://docs.anthropic.com or in the Claude Code repo. Search for the actual event schema before guessing. +- **Add logging as an intermediate step**: If unsure about the event format, add a `slog!` or `eprintln!` in `process_json_event` (line 334) to log every `event_type` received. Rebuild, run a web UI chat with tool use, and inspect the output to see exactly what events arrive. +- **Run the CLI directly**: You can run `claude -p "read /etc/hosts" --output-format stream-json` in a terminal to see the raw stream-json output and identify the event types for tool calls. +- **Don't assume the Anthropic API format**: The existing `content_block_start` matching was likely copied from the Anthropic provider. Claude Code's stream-json is a different format. + ## Acceptance Criteria - [ ] Activity indicator shows tool names (e.g. "Reading file...", "Executing command...") when the web UI agent calls tools