Orvlet preview

remote & integrations

Wherever the work is

Your Mac stays the owner of every task. From there Orvlet reaches your servers, your containers, your phone and your other tools — directly, with no relay in between.

Remote workspaces

Open a project that lives somewhere else and keep the same agent, editor, terminal and approvals.

  • SSH hostsRun tasks, tools and terminals on a remote machine, with jump-host routing and one agent list across your SSH machines.
  • Docker and Dev ContainersDetect a project's devcontainer.json and run the agent's tools and terminal inside it, locally or on an SSH host.
  • Terminals that surviveMosh and SSH terminals ride out a dropped connection, and local shells reconnect after Orvlet restarts.
  • Remote filesBrowse SFTP, S3 and WebDAV locations, with portable connection profiles you can export encrypted.
  • Secure Enclave SSH keysGenerate SSH keys in the Mac's Secure Enclave, served by Orvlet's own agent; the private key never leaves the chip.
  • Port forwardingManage SSH port forwards and SOCKS tunnels visually.

Your phone, paired to your Mac

Remote control is served by the desktop app itself over your local network or Tailscale, using HTTPS. It is off by default and there is no cloud relay.

  • Pair a phone or browser with a QR code or pairing code; each device gets its own token you can revoke.
  • Read tasks, reply, approve once or deny, and stop work from the phone.
  • Start a new task on the Mac from your phone, in folders you allowlisted.
  • Notifications name the task that is waiting, so you know what you are approving.
A hand holding a glowing phone screen in complete darkness
Paired directly, no relay · Photograph — Andrew Guan via Unsplash

Working with other people

Sharing is opt-in, scoped and on your network. The Mac that owns the work decides what a guest can see.

Live session sharing

/collab shares one live task, read-write or view-only, by invitation link and pairing code on your local network or Tailscale.

Group conversations

Invite up to four people on your network into a conversation with an AI participant, using single-use codes bound to a pinned certificate.

Shared projects

Share a scope you choose — selected conversations, files, instructions and pinned knowledge — with named members on your network.

Share the engine

Let another machine you own use this Mac's local model over TLS with a pinned identity and a key, and unlink it when you stop.

Publish an artifact

Send a finished artifact to a destination you own — a secret gist or a folder you choose — with comments and review threads on any artifact.

Network cables in a dark equipment rack lit by green status lights

Everything opt-in that talks outward says so where you turn it on.

Photograph — Tyler via Unsplash

Integrations

Use Orvlet from the tools you already have open, and let other tools use it.

  • VS CodeShare the open file, selection and diagnostics with Orvlet, start or continue a task from VS Code, and see Orvlet's diffs there.
  • Zed and ACP editorsorvlet acp runs the agent behind any editor that speaks the Agent Client Protocol.
  • Other coding agentsLaunch coding CLIs you have installed from inside Orvlet, or drive them as providers.
  • MCP serverOrvlet can serve its tools to other apps over a private socket — off by default, with new tasks confirmed by you.
  • Shortcuts, Siri and SpotlightSystem-wide Ask and Run agent actions.
  • Quick Entry and menu barA global-hotkey prompt that converses in place, and a menu bar item with running models and quick controls.
  • Finder and ServicesQuick actions on files and selected text from any app.
  • CLI, SDK and HTTPThe orvlet CLI, a Python SDK, a local agent-run HTTP API and a client protocol for other apps.
  • Import your historyBring sessions from other coding agents and assistant data exports into Orvlet.

One owner per task

However many windows, phones and editors are connected, each task has exactly one owning Mac. Remote state is never merged just because two paths look the same, and stale clients are refused rather than allowed to overwrite newer work.

Command line

orvlet --prompt "Summarize this repo"
orvlet acp
orvlet engine logs --follow --stats

CLI basics →