VSCode tools, file uploads, and Builder fixes

Specialists can now read what you have open in the embedded VSCode editor, including the active file, visible tabs, current selection, and a screenshot of the panel. You can attach files in chat, the Specialist Builder picks the same model as everywhere else, and each workspace manages its own billing subscription.

Editor and Sandbox

Specialists can now see your VSCode editor state when they need it. The active-file tool returns the file you are looking at along with its contents and language, the visible-files tool returns every open tab with active and unsaved markers, the selection tool returns the highlighted text and its range, and the screenshot tool returns a PNG of the editor panel. When the code panel is closed these tools return empty results instead of failing, so a specialist can still ask without the editor open.

Specialists

The Specialist Builder now uses the same model selection as everywhere else in the app. Previously, builder generation took a separate path that ignored your workspace and user-level model overrides, which sometimes caused provider sign-in to fail unexpectedly. The Builder now respects the model and provider you have configured for your workspace.

Chat

You can now attach files directly to chat messages — uploads actually send the file, and error messages are clearer when something goes wrong.

The chat message list scroll position is more stable when older history loads. Scrolling to the top of a long conversation no longer flickers or jumps when older messages appear, the viewport stays anchored to where you were reading, and history pagination stops chasing pages that yield no new messages. Specialist responses no longer get clipped at the bottom while streaming, expand and collapse state on long messages now persists, and the right sidebar tab strip scrolls horizontally with proper left and right controls when you have many tabs open.

Settings

Browser tool permission prompts are now reliable. Prompts can no longer race or be skipped silently, and you will see a clear error with diagnostics instead of a quiet failure if something is missing. The “already responded” error you might have seen is gone.

Each workspace now has its own billing subscription. Switching workspaces switches the billing context, owner and admin checks resolve against the workspace you are in, and the billing settings page and upgrade flow read from the active workspace rather than a shared customer.