KalaReach holds a terminal session open on the machine that owns it. Attach from an ordinary terminal with kr attach, or from the desktop and mobile apps. Close the window, lose the connection, pick up a different device: the session and the agent inside it keep running on that host.
# On the host: start a session and work in it normally.
$ kr new --attach
session 7 · studio-mac · zsh · live
$ codex
…agent running…
# Close the window. The attachment goes; the agent does not.
# Later, on that host or over SSH to it:
$ kr attach 7
attached · the agent kept working while you were away
What it is
A session belongs to a computer, not to a window.
Every session has its own process on your host. That process owns the pseudo-terminal, the canonical screen state and the record of what was approved. Windows, tabs, phones and laptops are attachments to it.
Attach from an ordinary terminal
Against a qualified terminal at the session’s own size, kr attach runs in direct mode and forwards the approved bytes: native mouse reporting, keyboard handling and hyperlinks. Otherwise it falls back to projected mode, which renders the canonical screen and does not reproduce your emulator’s own scrollback. kr status names the mode and the reason for it.
Agents keep running when you disconnect
Detaching removes your view. It does not stop the work. An agent mid-task keeps its process, its file handles and its pending questions, for as long as its host keeps running it. A reboot ends a session. Logging out of the desktop ends a desktop-bound one; a headless profile survives it only where the platform and the configuration say so. A sleeping machine resumes its work on waking rather than carrying on through the night.
Pair without an account
Scan a QR code, or type a ten-character code shaped XXXX-XXX-XXX. The invitation lasts five minutes and you approve the new device on the machine that issued it.
Open-source clients and host
The kr command, the local host and the desktop and mobile apps are BSD 3-Clause licensed. Direct connections and local sessions never need a KalaReach account.
Companion apps for the times you are not at the desk
The kr command talks to the host it runs on. Reaching a session from somewhere else is what the apps are for, on Linux, macOS, Windows, iOS and Android, with a conversation view for agents and a terminal view for everything else.
Optional managed services
Relay bandwidth beyond the free allowance, encrypted storage and metered voice are sold as a hosted service. Basic push stays free within its abuse limits, and nothing you can do locally depends on paying for anything.
Authority
The host decides. Clients ask.
A client shows you what a session looks like and submits what you want to do. The host checks that request against the session’s current state and the grant the device actually holds. Traffic passing through a relay and text produced by a model create no permission at all.
Each paired device has separate keys for transport, signatures, stored envelopes and notification previews. One key is never reused for another purpose.
Enlarging a grant, trusting a new repository root or issuing a persistent invitation needs a fresh confirmation on the owner’s machine, bound to that exact action.
Revoking a device stops future access. Personal owner grants stay valid until you revoke them, so a cloud outage cannot lock you out of your own computer.