Skip to content

Questions

Yes. Every original file is Apache-2.0; the Emacs client is MIT. Forks and modified builds use their own name and icon. Licence has the details.

A host session survives detaching. On macOS, closing a remote window asks whether to Close Window on [connection], Detach from [workspace], or Cancel. Close ends that host window and its sessions; Detach closes every local window attached to that workspace and leaves the host running. Multiplexer and sessions has the details.

A shell running only inside a local frontend is different. Share it with the host before relying on it to outlive that frontend.

No. They use the same terminal state, but their renderers and interfaces differ. The platform table describes images, sized text, rich text, transports and consent prompts. The Linux GTK frontend runs local shells rather than attaching to the host.

No MCP tool has an approval argument. The host checks attach consent, and each requested workspace tree edit needs a person’s approval for that exact operation. A standing attach grant does not approve a tree edit. A person may answer a command-policy confirmation from their own terminal.

No. A permitted command runs with the host user’s operating-system permissions. Consent is not isolation, and sharing a pane does not take turns between clients. Embedders must install a capability policy before processing untrusted terminal output. See Security.

In a hosted pane, the file belongs to the selected host. Ubiquitty shows that host and the resolved path before requesting it. Cancel sends no file request; reconnecting or detaching invalidates the question. A foreign hostname in a file URI cannot choose another connection.

There is no native Windows frontend in the source tree. The wscons frontend targets OpenBSD and NetBSD consoles; build instructions describe its device access requirements.