This repository was archived by the owner on Apr 14, 2026. It is now read-only.
chore: bump acp-client to 6cb674a (raw_input support) - #122
Merged
Conversation
Bump the acp-client crate from block/builderbot to pick up the raw_input forwarding change (builderbot#495). This updates the MessageWriter trait to accept optional raw_input parameters on record_tool_call and update_tool_call_title. Changes: - src-tauri/Cargo.toml: update acp-client rev to 6cb674a7 - src-tauri/Cargo.lock: updated lockfile - writer.rs: adapt TauriMessageWriter to new trait signatures (raw_input ignored for now — no frontend consumer yet) - dispatcher.rs: forward raw_input from ACP notifications to the writer, and guard update_tool_call_title on title OR raw_input being present
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps the
acp-clientcrate fromblock/builderbotto pick up theraw_inputforwarding change (builderbot#495).Changes
src-tauri/Cargo.toml— updateacp-clientrev fromdbd5bc9c→6cb674a7src-tauri/Cargo.lock— updated lockfilewriter.rs— adaptTauriMessageWriterto the newMessageWritertrait signatures:record_tool_call()now acceptsraw_input: Option<&serde_json::Value>(ignored for now)update_tool_call_title()changestitlefrom&strtoOption<&str>and addsraw_input(ignored for now)dispatcher.rs— forwardraw_inputfrom ACP notifications to the writer; guardupdate_tool_call_titleon title OR raw_input being presentNotes
The
raw_inputvalues are accepted but not yet forwarded to the frontend — no Tauri event payloads were changed. When we want to surface tool call parameters in the UI, we can addraw_inputtoToolCallPayload/ToolTitlePayloadand consume it on the frontend side.The
doctorcrate pin (bfce2926) is unchanged — no new commits to that crate upstream.