ai/byre
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 15 Wiki Activity

Show startup as one step checklist and re-check tools on the Server tab

Browse Source
This commit is contained in:
Ian Gulliver
2026-10-23 05:42:30 -07:00
parent 522c903344
commit dfb114ea64
9 changed files with 242 additions and 162 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/clean-install-vm.md
+2 -3
View File
@@ -26,9 +26,8 @@ The app's Tailscale sign-in opens Safari in the VM. To have the human approve it
## Driving the VM's screen
- Click the `tart` window's title bar first: the VM takes clicks and keys only while its window is the key window.
- Keys reach the VM without their modifiers through hands, so Shift, Cmd and symbols typed with `type` or `key` arrive wrong. Type only lowercase text and plain symbols there, and do the rest over SSH.
- Scrolling doesn't reach the VM; drag the scroll bar instead.
- Start each `act` with a click on an empty part of the VM's screen, not its title bar: the VM takes clicks and keys only after a click inside it.
- `tart run` in a terminal runs until the VM stops, and Ctrl-C in that terminal shuts the VM down.
- `screencapture` over SSH fails for lack of Screen Recording in the VM; capture the `tart` window from the host with hands.
- Check `screen_list` before acting: another task's `tart` window can sit exactly on top of yours.
docs/operations.md
+1 -1
View File
@@ -32,7 +32,7 @@ Tailscale identifies the connecting Mac, including requests from a web page open
Loopback access requires the bearer credential in `<data>/loopback-token`, regenerated on service startup. It grants both server status (including the node's sign-in URL) and command execution on connected client Macs. Keep it private: loopback is reachable by other OS accounts, so the address alone provides no protection.
A new node needs signing in: `curl -H "Authorization: Bearer $(cat "$HOME/Library/Application Support/byre/loopback-token")" <loopback>/api/tailnet` (`byre check` prints the loopback address) shows `NeedsLogin` and the `auth_url`, and the app on the same Mac shows it as **Sign in to Tailscale**. The tailnet must have MagicDNS and HTTPS certificates turned on (the DNS page of Tailscale's admin console); without certificates byre logs `tailnet has no https certificates` and serves only the loopback address until it is restarted.
A new node needs signing in: `curl -H "Authorization: Bearer $(cat "$HOME/Library/Application Support/byre/loopback-token")" <loopback>/api/tailnet` (`byre check` prints the loopback address) shows `NeedsLogin` and the `auth_url`, and the app on the same Mac shows it as a "Sign this Mac's server in to Tailscale" step with a **Sign in** button. The tailnet must have MagicDNS and HTTPS certificates turned on (the DNS page of Tailscale's admin console); without certificates byre logs `tailnet has no https certificates` and serves only the loopback address until it is restarted.
Each preview gets its own port on byre's node rather than a path under byre's origin, since path-prefix proxying breaks apps that use absolute paths. Previews use the same user-only tailnet trust boundary as the API; tagged nodes are excluded.