[Bug] Runtime hangs indefinitely on unhandled `send_feedback` tool_use in `ClientChatBackend`
Assessment
This issue has not been assessed yet.
Description
Description
When running tasks such as failure-brainstorming or document generation, the model invokes the internal send_feedback tool. However, the runtime does not execute or acknowledge this tool call, emitting no corresponding tool_result event back to the session stream. As a result, ClientChatBackend deadlocks waiting for a completion response, causing the UI to display the pending tool call (→ send_feedback: {message}) and freeze indefinitely with blinking dots.
Steps to Reproduce
- Start a session in the desktop app / web client using
ClientChatBackend. - Provide an architecture/solution document in the workspace.
- Prompt the agent to run failure-brainstorming or protocol analysis (e.g., across multiple operational/security perspectives).
- Observe the model invoke
send_feedback.
Expected Behavior
Either:
- The tool invocation should be automatically handled/acknowledged with an emitted
tool_resultevent so the model can continue generating, or - The
send_feedbacktool should not be exposed in the model's available tools during standard analysis turns if no client handler is active.
Actual Behavior
The session deadlocks immediately following the tool_use event. Re-opening or resuming the session (session_resume) fails to advance because the unresolved tool call remains at the tail of the transcript.
Log Extract (transcripts/*.events.jsonl)
{"schema_version":"1","type":"tool_use","timestamp":"2026-09-07T07:52:22.547983Z","tool_use_id":"call_WEp4nEzVAl4Fs2m9pKkhxPPl","name":"send_feedback","input":{"message":"Executing failure brainstorming steps for RA3-to-ScienceClaw VM bridge and asynchronous queuing across Operational, Security, and Human-Factors frames as guided by the Clarity brainstorming protocols. Report follows causal analysis. No issues to flag w/concurrent API risks"}}
{"schema_version":"1","type":"session_resume","timestamp":"2026-09-07T07:53:14.277041Z","backend":"ClientChatBackend","llm_session_id":null}
Environment
- OS: macOS
- Backend: ClientChatBackend
- Client: Clarity Desktop App
- Dominant language
- Python
- Stars
- 266
- Forks
- 33
- Avg merge
- 9d 8h
- Merged PRs (30d)
- 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/clarity-agent
-
microsoft/clarity-agent#150 · 2 comments · 1 reaction · 1 assignee ·
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/clarity-agent#140 ·
-
Consider how clarity architecture can be enhanced to support simultaneous writes and reads to it Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/clarity-agent#139 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
microsoft/clarity-agent#138 · 1 comment ·
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/clarity-agent#137 ·
All issues in microsoft/clarity-agent
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100