chore: apply workspace changes

[notkainoa]

Introduces a helper that automatically scrolls the chat panel back to the top whenever you switch workspaces, so you always see the most recent messages right away.

---

Note

Adds an auto-scroll hook used in chat and multi-agent views to keep terminals at the bottom on workspace/tab switch, and refactors workspace change polling for stability.

• Frontend:
  • Auto-scroll: New useAutoScrollOnWorkspaceSwitch hook; integrated into components/ChatInterface.tsx and components/MultiAgentWorkspace.tsx to scroll terminals to bottom on workspace activation; also scrolls on active tab switches in multi-agent view.
  • TerminalPane: Marks terminal container with data-terminal-container for targeted scrolling.
  • Workspace Changes: Refactors useWorkspaceChanges to memoize fetchChanges, improve error handling, and safely poll via setInterval without stale deps.
• Services:
  • Minor refactors in WorktreeService.removeWorktree (let→const).
  • GitHubService: rename unused params (no behavior change).

^{Written by Cursor Bugbot for commit 4a3fe89. This will update automatically on new commits. Configure here.}

[vercel]

@notkainoa is attempting to deploy a commit to the General Action Team on Vercel.

A member of the Team first needs to authorize it.

[notkainoa]

To see the changes, open 2 workspaces, in 1 have the cli tool do something that will take up a lot of vertical space in the chat, then go to the other workspace and wait for the 1st to finish. When it's done, go back to the 1s,t, and you'll see a nice scrolling animation down to the bottom of the context. Previously, the user would have to manually scroll down.

Keep in mind, this only kicks in when the user switches to a workspace and is at the top of the context, which doesn't always happen. Sometimes they are just by default at the bottom cause of different quirks with emdash.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Error			Dec 9, 2025 1:10am

[arnestrickmann]

thanks for contributing!