Repository navigation
Conversation
- Rename the settings group to Workspaces and drop Setup from the sidebar. Setup is reached from the Machines page, where its row is always present, and Set Up Later returns there. - Show the hostname in its own row with a copy button, since it is the name used when none is given, and shorten the row descriptions so a long hostname cannot wrap them. - Show the ID in the copy field once assigned, and as "Not Assigned" until then. - Hold the card's four rows while it loads and wait for the workspace before showing them, so the sections below no longer jump. - The copy field truncates a long value and shows it in full on hover. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Escape on a settings page returned to the app, which also fired when a key press missed the dialog or field it was meant for. Settings is left with Back to App or the close button. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A paired machine's status now carries its label, hostname and version as the machine last reported them, whether it is answering, and when it last did. They are kept in the app database, so they show while the machine is offline, and a change reaches watchers without a manual check. - `servers.label` sets the label stored on the machine, over its paired connection. Pairing is direct access to the machine, so nothing more is asked. - The private per-app name of a paired machine is gone; its label replaces it. A migration clears the old names. - An address nobody answers at now says so in plain words. - `codework service pair` notes on stderr that the code gives full access to the machine. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
A machine has a hostname, which is the computer's own name, and one label, which is stored on the machine. Pairing reaches a machine directly; linking puts it in a workspace. - Application > Paired Machines lists the machines this computer is paired with. Each opens a page of its own with its label, hostname, address and version, pairing again when the machine no longer accepts this computer, and removal. - Pair a Machine is a dialog laid out like Add Provider's, with each error under its own field. - Workspaces > Machines says Label, Linked and Unlink. - The settings sidebar keeps a section highlighted on its sub-pages. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Removing a paired machine only forgot it in the app, so the machine kept listing the computer as a device until the session lapsed. - A paired device can end its own pairing with `device.leave`. It removes that device alone and closes its sockets, the one the call came in on included, so a client takes a reply or the connection ending as done. - The app calls it before removing the row, for at most three seconds, and removes the row whether the machine answers or not. - The empty Paired Machines list has one Pair a Machine button, in the header. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…page Settings has one Machines page under Application. Every machine appears once: This Machine, Paired Machines, Waiting to Join, and the workspace's machines this computer is not paired with. A paired machine's page links it to the selected workspace, or unlinks it. - The app server's machine.connect and machine.disconnect take an optional server id, so they reach a paired machine as well as the default one. - A paired machine's status carries its machine id and the workspaces it is linked to; both are stored and refreshed after a link or an unlink. - Setup moves under the new page. The Workspaces group and the Paired Machines entry leave the settings sidebar. - Settings sections gain a description line and more room between them. Descriptions no longer end with a full stop. - The settings pages that only showed mock data are removed, with the controls only they used. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #175.
The model
Application → Machines
One page replaces Paired Machines and Workspaces → Machines. Every machine appears once, grouped by what this computer can do with it. The workspace is the one selected in the app; without one, only the first two sections show.
codework connect, each with its code to approve.A paired machine's page
Settings as a whole
App server
machine.connectandmachine.disconnecttake an optionalserverId, so they reach a paired machine as well as the default one. A machine that is not paired any more, or does not answer, fails in the app's own words; the machine's own connect error passes through unchanged.label,host,version,online,seenAt,machineIdand the workspaces it is linked to. They are stored, so they show while the machine is offline, and are refreshed after a link or an unlink.servers.labelsets the label on the machine over its paired connection.servers.updaterefuses anameon a paired machine.servers.removetells the machine to end the pairing, best effort.202611200002_labeland202611210001_identityadd the columns.Also
codework service pairnotes on stderr that the code gives full access to the machine. Stdout is still only the code.Verified
vp check,vp run typecheckapps/servernon-live suiteapps/webDriven by hand in the Electron app against a local relay and an OrbStack machine: Link, the row turning Linked, Unlink with its confirmation, and the machine's own error shown in the row when it cannot reach the relay. Earlier on this branch: labels, offline and online, revoke and pair again, pairing through the dialog, changing an address, removing, keyboard only, a narrow window, dark theme.
The
packages/codeworkand live suites last ran before this commit; it changes nothing underpackages/.Known gaps
🤖 Generated with Claude Code