starred/orca
1
0
Fork 0
mirror of https://github.com/stablyai/orca.git synced 2026-10-30 16:47:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(ssh): say "Orca on <host>" instead of "managed server" in the UI (#31099)

Browse Source 
* fix(ssh): say where Orca runs instead of "managed server" in the UI

Users read "managed server" as hosting run by someone else, so they declined
moving their SSH hosts. Every user-facing string now says "Orca on <host>" or
"this host's Orca server", in all six locales; Settings > "Orca on your SSH
hosts" and the setup line say the code and files stay where they are and only
Orca's list of projects, tabs and terminals moves to the host. CLI command names,
logs and identifiers are unchanged.

Fixes #30880

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(ssh): reassure only when something moves; name the host's label in its row

Review follow-ups: the reassurance shows only while Orca sets itself up or
moves a host, not on every reconnect; the converting line no longer repeats it;
the row names the SSH host's current label; the section description and the
Move anyway dialog stop repeating themselves; translate the Restart dialog's
buttons; drop "managed" from the remaining raw causes and the external
automation refusal.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
Neil
2026-10-20 04:18:08 -07:00
committed by GitHub
co-authored by Claude
parent d9a89dcb0c
commit 0ee13f831d
65 changed files with 528 additions and 338 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/site/content/docs/ssh.mdx
+4 -2
View File
@@ -35,6 +35,8 @@ When creating a worktree, choose an SSH target instead of Local. Orca will:
- Run agents remotely through the SSH connection.
- Sync file events so the editor, diff, and browser still feel local.
On the first connect, Orca installs itself on the host over your own SSH connection; Settings lists these under **Orca on your SSH hosts**. Your code and files stay where they are. Only Orca's list of projects, tabs and terminals moves to the host.
## Advanced connection options
Open **Settings → SSH**, edit a target, and expand **Advanced Connection** when the host needs a proxy, jump host, or SSH multiplexing override. Orca enables **Reuse SSH connection for faster setup** by default, which uses OpenSSH connection reuse on macOS and Linux so setup commands do not each pay a fresh SSH handshake. Turn it off only for hosts whose SSH policy rejects multiplexed sessions.
@@ -101,9 +103,9 @@ For remote worktrees, the right sidebar shows a **Ports** tab (toggle with `Cmd+
## macOS hosts: local network access
On macOS 15 and later, a terminal on an SSH host can lose access to devices on the host's local network (for example `kubectl`, Homebrew `node` or `python`, or `.local` names fail with `no route to host`). macOS credits network access to the SSH session that started Orca's managed server, and when that session ends, programs started from the server's terminals are blocked. Apple's own tools such as `/usr/bin/curl` keep working, and loopback connections are unaffected. Full Disk Access granted through **Allow full disk access for remote users** may stop working the same way.
On macOS 15 and later, a terminal on an SSH host can lose access to devices on the host's local network (for example `kubectl`, Homebrew `node` or `python`, or `.local` names fail with `no route to host`). macOS credits network access to the SSH session that started Orca's server on the host, and when that session ends, programs started from the server's terminals are blocked. Apple's own tools such as `/usr/bin/curl` keep working, and loopback connections are unaffected. Full Disk Access granted through **Allow full disk access for remote users** may stop working the same way.
When Orca sees that this happened, the host's status in **Settings → SSH** says so and offers **Restart managed server…**, which starts the server again from your current connection. Orca restarts it only when no terminals are running on the host, because terminals that are still open keep the lost access. Close them first.
When Orca sees that this happened, the host's status in **Settings → SSH** says so and offers **Restart Orca’s server…**, which starts the server again from your current connection. Orca restarts it only when no terminals are running on the host, because terminals that are still open keep the lost access. Close them first.
To avoid the problem altogether, an administrator on the host can exempt local address ranges from the Local Network check (macOS 15.5 and later; see Apple's [TN3179](https://developer.apple.com/documentation/technotes/tn3179-understanding-local-network-privacy)). The exemption applies to every app on that Mac for the listed ranges: