Skip to content

Make rename chat tool non-blocking - #331114

Draft
roblourens wants to merge 2 commits into
mainfrom
roblou/rename-chat-background
Draft

Make rename chat tool non-blocking#331114
roblourens wants to merge 2 commits into
mainfrom
roblou/rename-chat-background

Conversation

@roblourens

Copy link
Copy Markdown
Member

Summary

  • return from rename_chat immediately while applying the rename in the background
  • serialize background renames so repeated calls retain invocation order
  • report background failures and update the tool result/display messaging to reflect asynchronous completion
  • cover immediate return, address forwarding, failure reporting, and queued execution

Validation

  • npm run transpile-client
  • ./scripts/test.sh --run src/vs/platform/agentHost/test/node/sessionServerTools.test.ts (42 passing)
  • npm run typecheck-client (change is clean; command still reports unrelated existing errors in copilotAgentSession.test.ts, copilotToolDisplay.test.ts, and assignmentService.ts)

(Written by Copilot)

Run chat renames in an ordered background queue and report failures after the tool returns.\n\n(Written by Copilot)\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings August 16, 2026 19:50

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Makes rename_chat non-blocking while preserving rename order and surfacing background failures.

Changes:

  • Queues asynchronous renames with Sequencer.
  • Logs failures and updates tool messaging.
  • Adds coverage for immediate return, ordering, forwarding, and failures.
Show a summary per file
File Description
sessionServerTools.ts Implements queued background renames and updated messaging.
agentService.ts Reports background rename failures through logging.
sessionServerTools.test.ts Tests asynchronous rename behavior and sequencing.

Review details

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

  • Files reviewed: 3/3 changed files
  • Comments generated: 0
  • Review effort level: Balanced

Wait for background rename work before asserting persisted state and treat persistence failures as asynchronous.\n\n(Written by Copilot)\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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