Skip to content

Managed SSH servers: supported temporary return to direct SSH while mobile desktop relay is unavailable? #28340

Closed

Description

@4inn

Question

Is there a supported per-host way to temporarily return a managed SSH host to the previous direct SSH relay workflow, without downgrading Orca Desktop or altering internal state files?

Environment

  • macOS desktop: Orca 1.4.224
  • iPad mobile client: reports version 0.0.55
  • Remote host: Linux, provisioned as a managed Orca server over SSH
  • The remote runtime reports appVersion 0.0.0-dev; managed environment status reports activeVersion 0.1.0+15ec2904eb00

Observed behavior

  1. The iPad is paired with the Mac desktop.
  2. Existing direct-SSH projects and local Mac projects appear on the iPad.
  3. A newly added project owned by a managed server appears in the Mac sidebar, but does not appear on the iPad paired with that Mac.
  4. Updating the iPad to 0.0.55 did not make the managed-server project appear.
  5. The remote server responds normally and worktree.ps returns the project and its attached terminal.

Investigation

The desktop and remote runtime do not advertise mobile.desktop-relay.v1 / pairing.delegated-mobile-devices.v1 respectively. The changes in #26442 appear to address desktop-to-mobile listing and relay of configured servers, but mobile-desktop-relay-contract.ts currently says the desktop relay capability is not advertised until the mobile host-scoped client ships.

For a temporary workaround, environment stop refused with orcad_decommission_terminals_running because two terminal sessions are alive. We did not close those sessions or force removal. Reading the v1.4.224 connect path also suggests an unlinked SSH host will automatically be provisioned or migrated back to managed orcad. The legacy remoteRuntime choice appears to select the relay runtime, rather than opt out of managed-server conversion.

Desired outcome

Keep a single project/workspace list on the iPad paired with the Mac, including this remote project, without downgrading the Mac desktop.

Could you clarify:

  1. Is there a supported per-host opt-out or reverse migration from managed server to direct SSH? If so, how should project metadata and existing agent sessions be preserved, and automatic reconversion prevented?
  2. If not, which desktop/server and iOS versions will enable managed-server projects to be listed and operated through the paired Mac? Does mobile 0.0.55 contain the required host-scoped client, or is that still pending?
  3. Is direct mobile pairing to an SSH-managed server supported as a temporary workaround when the desktop currently accesses that server via an SSH tunnel?

No internal state edits, downgrade, or forced terminal shutdown have been performed.

Activity

  1. AmethystLiang commented on Oct 14, 2026

    @AmethystLiang
    Contributor

    Thanks for reporting. Looking into it

  2. nwparker commented on Oct 15, 2026

    @nwparker
    Contributor

    Is there a supported per-host way to temporarily return a managed SSH host to the previous direct SSH relay workflow, without downgrading Orca Desktop or altering internal state files?

    There's not but you can downgrade Orca
    We're fixing a few issues around SSH -- many fixes are in. And we're working to get a new release out ASAP! Sorry for the trouble

  3. AmoabaKelvin commented on Oct 21, 2026

    @AmoabaKelvin
    Collaborator

    Fixed in v1.4.229 by #26501: a phone or iPad paired with the desktop now lists and opens projects on the desktop's managed SSH servers through the desktop, and the existing mobile app version doesn't need an update. The managed server also has to move to the new build. If terminals are still running on it, that update waits, and the iPad shows "Update Orca on to open its workspaces from your phone" until you close them or force the update from Managed servers. There's still no per-host way back to direct SSH, but it's no longer needed for this. Please reopen if the project still doesn't show on the iPad after updating the desktop and the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions