Skip to content

feat(staged): forward tool call raw_input params through ACP driver to DB#495

Draft
matt2e wants to merge 1 commit intomainfrom
tool-request-params
Draft

feat(staged): forward tool call raw_input params through ACP driver to DB#495
matt2e wants to merge 1 commit intomainfrom
tool-request-params

Conversation

@matt2e
Copy link
Contributor

@matt2e matt2e commented Mar 26, 2026

Summary

  • Extends MessageWriter trait methods (record_tool_call, update_tool_call_title) to accept an optional raw_input parameter containing the tool call's input JSON
  • Forwards raw_input from ACP session updates through the notification handler to the writer
  • Stores tool call content as structured JSON {"name": title, "input": raw_input} when raw_input is present, enabling the frontend to display detailed tool call parameters

Test plan

  • Existing tests updated to pass None for raw_input and continue to pass
  • Verify tool calls with raw_input are stored as JSON in the DB
  • Verify tool calls without raw_input fall back to plain title string

🤖 Generated with Claude Code

…o DB

The ACP protocol provides raw_input on ToolCall and ToolCallUpdate, but
it was never extracted or forwarded. This adds raw_input through the full
pipeline: LiveAction enum, MessageWriter trait, and DB writer. When
raw_input is present, tool calls are stored as JSON {"name", "input"}
which the frontend already knows how to parse.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@matt2e matt2e requested review from baxen and wesbillman as code owners March 26, 2026 08:54
@matt2e matt2e marked this pull request as draft March 26, 2026 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant