Repository navigation
Conversation
… another machine Running a quick action from a pull request or issue used to leave the user on the item, with the agent opening in the workspace pane beside it. Since default machines came to every Forge UI (#1924), a quick action on a remote default (a fleet member or a devbox) sends the user to the Workspaces tab instead. Before #1924, a default that named a fleet member was ignored here, so the workspace was created on this machine and opened beside the item. The pane beside an item can show only this machine's workspaces, so it cannot hold the remote one. A quick action does not need it on screen: the server launches the agent and delivers the prompt. Now the user stays on the item, and a message names the machine and offers to open the workspace. A plain Create Workspace on a remote default still opens the workspace in Workspaces, because the user asked to work in it. Phone views and other views without the pane also keep navigating; they have nothing to show beside the item. Quick actions on a local default never navigated. They create, or reuse, the local workspace and open it beside the item, as before. Generated with Claude Code (claude-opus-5-5) Co-authored-by: Claude <noreply@anthropic.com>
roborev: Combined Review (
|
A quick action or Create Workspace on a remote default machine should feel the same as one on this machine: the workspace opens in the pane beside the pull request or issue. The previous commit kept the user on the item but only offered the workspace from a message, so a remote default still behaved differently from a local one. The pane's terminal view could already show another machine's workspace. What it lacked was the machine: the item's link to its workspace held only an ID. The link now carries the machine key and name, the pane's tab says "Workspace on <machine>", and Open Workspace routes to that machine. This Forge's detail response lists only its own workspaces, so a refresh after creation reports none. The pane keeps a remote link through that and drops it when a local workspace appears or the remote one is deleted. After a full page reload the link is gone until the next create or quick action, which reuses the existing remote workspace. Generated with Claude Code (claude-opus-5-5) Co-authored-by: Claude <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
…cal one Review of the previous commit found places where a workspace on another machine still behaved differently from a local one in the pane beside a pull request or issue: - Its quick actions were disabled when this machine lacked the agent, although the agent runs on the workspace's machine. They now skip the local check, as creating on a remote default already did. - The first quick action that created it ignored the session placement setting (tab, left, right) that later actions and local creates honor, including when setup had to be retried first. - After an issue's branch-conflict retry succeeded, the conflict dialog stayed open over the new workspace. It now closes on success, which also fixes the same leftover dialog on the local path. - Deleting it from Workspaces after leaving its item left the item's link behind, so returning reopened a deleted workspace. - Deleting a local workspace and then creating a remote one before the item's detail refreshed let the stale detail, still naming the deleted workspace, erase the remote link. - Before fleet discovery named the machine, the pane said "another machine" for the rest of the visit. It now shows a name taken from the machine's key. The e2e spec now waits for a control that only the loaded remote workspace shows, so it fails if the pane reads the wrong machine. Deferred: when a remote workspace is deleted on its own machine, the pane keeps showing it until something reloads it. That is existing terminal-view behavior for every remote workspace. Generated with Claude Code (claude-opus-5-5) Co-authored-by: Claude <noreply@anthropic.com>
roborev: Combined Review (
|
…its own machine Linking a remote workspace to its pull request or issue left gaps where Forge still treated the workspace as local or trusted a stale status: - A bulk quick action on an item whose workspace this session created on another machine sent the handoff to this Forge, which does not have that workspace. The action failed with "lost contact with Kenn Forge". - The link keeps the status from the create response, because this Forge never lists another machine's workspaces. A quick action on the linked workspace therefore could not see that setup had failed since, and did not set it up again as a create on that machine used to. - The header's agent menu listed this machine's agents, so a remote workspace offered agents its machine lacks and hid ones only it has. - A fleet member with no known name was labeled by its internal node ID. Quick actions on a remote link, from the header or in bulk, now ask that machine for the item's workspace again. The machine returns the same workspace with its current status, so the existing retry and being-deleted handling applies, and it makes a new one if the old one is gone. The header's agent menu uses the agents the pane loaded from the workspace's machine. A remote workspace deleted elsewhere is already handled: the pane loads it from its machine, gets a 404, and drops the link. Generated with Claude Code (claude-opus-5-5) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
roborev: Combined Review (
|
TL;DR
When the default machine is a fleet member or a devbox, a quick action or Create Workspace on a pull request or issue sent you to the Workspaces tab. Now the workspace opens in the pane beside the item, the same as a local one, and the pane's tab names the machine ("Workspace on compute-a (devbox)").
Why
Before #1924, a quick action left you on the item and opened the agent in the pane beside it. #1924 made workspace starts honor the default machine. The pane's link to its workspace held only an ID, so it could only point at this machine's workspaces, and the create path navigated away for remote ones.
How
The pane's terminal view could already show another machine's workspace. The link from an item to its workspace now also carries the machine key and display name. The pane, its tab label, Open Workspace, and delete handling all read the machine from that link.
Reviewer notes
User-facing benefit: starting a workspace on another machine keeps you on the pull request or issue you are reading, with the agent beside it.
Co-authored-by: Claude noreply@anthropic.com
Model used: Opus 5.5