Skip to content

fix(ai-agent): forward model-authored tool description from BackendOutputSink - #945

Open
kylexu88 wants to merge 1 commit into
iOfficeAI:mainfrom
kylexu88:feature/refactor-tool-execution-ui
Open

fix(ai-agent): forward model-authored tool description from BackendOutputSink#945
kylexu88 wants to merge 1 commit into
iOfficeAI:mainfrom
kylexu88:feature/refactor-tool-execution-ui

Conversation

@kylexu88

Copy link
Copy Markdown

Summary

BackendOutputSink hardcoded description: None when forwarding aionrs
tool-call events to the frontend. A model-authored description therefore
never reached the renderer, and the tool-step label always fell back to the
raw command string.

Changes

  • Extract the optional description field from the parsed tool input in
    emit_tool_call and forward it through ToolCallEventData instead of None.
  • Add two unit tests covering the description-present and description-absent
    paths.

Testing

  • New unit tests:
    • emit_tool_call_extracts_description_from_input
    • emit_tool_call_without_description_keeps_none
  • Full workspace gate via just push:
    • cargo nextest run --workspace: 9131 passed, 50 skipped
    • migration check, lint, fmt all green

Related

Companion to the AionUi tool-execution rendering refactor — the frontend
already renders description when present, so this wires the backend side of
the same fix.

…tputSink

The BackendOutputSink hardcoded `description: None` when forwarding aionrs
tool calls, so a model-authored description never reached the frontend and
the step label always fell back to the raw command. Extract the optional
`description` field from the tool input instead.
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.

2 participants