Remote desktop
A whole desktop, in a tile beside the terminal
Open a streamed Linux or Windows desktop from a session and take control of it. Anything that needs a screen rather than a shell runs on the machine and arrives as video.
Read the guide
Run taiku, share the link, and open your shell in the browser with room for the tools around it: editors, previews, and a whole desktop.
... for your favorite robot ...
Not ready to install? Open a session in your browser and type in it. The machine runs in the tab.
A session wants the whole screen on a phone, so this one opens on its
own page. The shell in it is real enough to poke at: try
ls,
git diff, and
tour.
Remote desktop
Open a streamed Linux or Windows desktop from a session and take control of it. Anything that needs a screen rather than a shell runs on the machine and arrives as video.
Read the guideRemote dev machines
Run a project on a managed Linux machine with your local files synced to it. Close the laptop and the build keeps going; open the link tomorrow and the session is where you left it.
Read the guideLocal web previews
Publish a port from the session and it opens in a tile next to the shell that runs it. Reload on save, and send the same view to whoever is on the link.
Read the guideAI agents
Start Claude, Codex, or OpenCode in a taiku terminal and the session recognizes it from its own output: a status dot per terminal, token usage and tool calls per agent.
Read the guideFour arguments, one per thing I think is going to change. Each is written and set on its own terms.
Access to your own computer is a setup project, and it does not have to be one.
A screen share is a picture of a machine. The person looking at it should be able to type into it.
An agent that stops to ask a question is invisible until somebody looks.
A cloud workspace normally arrives stripped of everything that made your setup yours.
Terminal bytes are encrypted on your machine before they leave it, and the key rides in the fragment of the session URL, which browsers do not send to servers. Session metadata is not encrypted: names, presence, focus, chat, and terminal sizes. Docs ↗
Whoever holds the link, so treat it like a credential. Reader, writer, and admin links each carry their own secret, so handing out the reader link never reveals the other two. Docs ↗
No. They open the link in a browser and get the terminals, editors, previews, and a streamed desktop if you opened one. Phones work the same way. The native iOS and Android apps are in private testing. Docs ↗
macOS, Linux, and Windows, through the CLI or the desktop app. The Linux and Windows builds are not tested as thoroughly as macOS yet, and on Windows the CLI is the most battle-tested option. Docs ↗
The session is held for about five minutes and reconnects on its own. Stay away longer than that and it is gone. Docs ↗
Not if you start the session with --sandbox and a path on macOS or Linux, where Seatbelt or Landlock confines the shell to that directory and --sandbox-ro makes it read-only. On Windows the same flag only sets the working directory and prints a warning, so nothing is enforced and a guest can still reach the rest of the disk. Docs ↗
Nobody until you turn it on. Remote access is off on a fresh install, and once enabled each connection goes through the guard you pick: ask every time, require a password, or auto-accept. Docs ↗
Sharing, tunnels, plugins, agents, recording, and remote desktop all work on Free, with 1 session at a time, 3 viewers, and 1 cloud workspace of up to 15 GB. Pro raises that to 3 sessions, unlimited viewers, 3 workspaces of up to 200 GB, and Windows cloud machines. Docs ↗
Install it on the machine you already work on. The first session takes one command.