Skip to content

docs(chat): document re-set-on-error semantic for pendingToolUseID field - #141

Merged
mhersson merged 1 commit into
mainfrom
ctxmax-630/follow-up-pendingtooluseid-field-doc-missing-re-se
May 23, 2026
Merged

docs(chat): document re-set-on-error semantic for pendingToolUseID field#141
mhersson merged 1 commit into
mainfrom
ctxmax-630/follow-up-pendingtooluseid-field-doc-missing-re-se

Conversation

@contextmatrix-runner

Copy link
Copy Markdown
Contributor

Summary

  • Appends one sentence to the pendingToolUseID field comment in internal/chat/manager.go
  • Clarifies that the consumed tool_use_id is re-stored when SendChatMessage fails, so a UI retry forwards the same id to the runner
  • Follows up on the AskUserQuestion tool_use_id forwarding work; the field comment was missing this re-set-on-error lifecycle

Test plan

  • Existing TestManager_SendUserMessage_ToolUseID_PreservedOnSendError covers the exact path described — verify it passes: go test ./internal/chat/... -run TestManager_SendUserMessage_ToolUseID_PreservedOnSendError
  • Full chat package tests pass: go test ./internal/chat/...
  • Internal packages build cleanly: go build ./internal/...

- Append one sentence to the pendingToolUseID comment clarifying that
  the consumed id is re-stored when SendChatMessage fails, so a UI
  retry correctly forwards the same tool_use_id to the runner
@mhersson
mhersson merged commit 51804d4 into main May 23, 2026
7 checks passed
@mhersson
mhersson deleted the ctxmax-630/follow-up-pendingtooluseid-field-doc-missing-re-se branch May 23, 2026 17:35
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