User GuidePluginsAPI Reference

Changelog

What's new in taiku's published desktop and CLI releases.

The latest packaged release below comes from the same manifest used by taiku's desktop and CLI updaters. The browser service deploys continuously, and mobile builds follow their app-store release cadence, so their build identifiers can differ.

Desktop updates install in the background, and the CLI updates with taiku update.

Latest release: 1.0.53

Published November 4, 2026.

1.0.53

Terminal client

  • In the PDF page view, a selection or cursor highlight over Chinese or Japanese text covers all of it. It used to stop about halfway along.

taiku agent

  • taiku agent import brings your Claude Code and Codex setup into a taiku agent: MCP servers, skills, commands, and settings such as the model. It says what each item becomes and asks first. --dry-run only lists what it found.
  • A CLAUDE.md or AGENTS.md you accept in an import goes with the agent into its runs, after taiku's own instructions. One from a project applies only while the agent is tied to that project's repository.
  • The / picker lists every command the agent console runs. /status, /usage, /new, /clear, /resume, /continue, /questions, /login and /logout worked when typed but weren't listed.
  • /exit and /quit leave the agent console, as Ctrl+C does.
  • With --local, a Codex conversation runs /compact, /review and /init as the Codex CLI does. /review reviews your uncommitted changes, or what you ask for after it, and /init writes an AGENTS.md. None of them worked before.
  • With --local, a Claude Code conversation says "Conversation compacted" when Claude Code compacts it.

Agent runs on your machine and your boxes

  • An agent you made can start subagents on its own box, except in a Claude Code run. Each shows as a row in the sessions sidebar, the run waits for them, and in Guarded mode you're asked before each one starts.
  • A run on your box can use the agent's skills that ask first, and asks you before loading one. Box runs used to leave them out, as a Claude model's run still does. An Unattended run loads only the ones you've already allowed.
  • A step a read-only or plan run refuses because of its mode no longer shows as an approval waiting on you, or lists the run under Needs you. The step says why, such as "refused: plan mode does not act".
  • A document a run on your box publishes or makes in a new conversation shows in that conversation's Outputs and the Gallery. The run said it was published, but it showed in neither.
  • What a subagent on your box publishes or files is listed under the agent's conversation. A subagent's file is named after it, such as Review-findings.md, so it doesn't replace the agent's file of the same name.
  • When the Sentinel reviews a pull request on a project you haven't let it post on, its verdict is kept in taiku and shows on that pull request's row in Reviews, marked as not posted to GitHub. Setup offers Allow posting.
  • An agent run on a box now has only a narrow token in its environment: taiku's model, package and GitHub proxies accept it, and every other taiku endpoint refuses it. The run's own token reaches taiku's tools alone (with Claude Code, through the run's MCP config file, which the run's account can still read). On a server rolled back to before the narrow token existed, a box keeps its old environment and the narrow token is not limited.

Sessions and machines

  • On the dashboard, a computer's details show what each of its sessions is working in: its layout as it looks now, its repository and branch, and the ports it tunnels. A row opens the session, a port's with its preview in front.
  • A session reports its repository and branch to the dashboard once its computer runs this version.
  • On Ubuntu, Debian and most other Linux systems, a command's run lists the files it touched, where strace is installed. The system's default limit on tracing kept taiku from seeing them, and the run said they weren't captured.

Cloud workspaces

  • Once your workspace is updated, a cloud workspace that wakes from sleep keeps the session it brought back. Every wake used to end that session seconds later, so the next Open started a new one with new shells and lost its layout.
  • Once your workspace is updated, opening a cloud workspace that has just woken works within seconds. Its session could take five minutes or more to check in with taiku again, and Open waited for it.

Remote desktop

  • Starting a remote desktop host no longer moves the pointer of the person at the computer. It used to jump to the top-left corner whenever someone opened the computer's desktop, even just to watch.
  • When taiku rd-host encodes more slowly than it captures, as on a slow or busy machine, the viewer's picture keeps moving. It used to stop for seconds at a time while the tile still said Live.
  • When a Linux computer shares its screen, a lost packet no longer freezes the picture until the next full frame. On a lossy link, such as weak Wi-Fi, that meant freezes of up to a second.
  • A viewer whose direct connection to taiku rd-host fails and moves to taiku's relay gets the picture. It used to wait on "Attaching to the host" for good.
  • taiku rd-host --auto-accept starts right after taiku login. The first try used to be refused with "Lower this computer's remote desktop guard at the computer itself.", and only a second try worked.
  • taiku rd-host --auto-accept from a second taiku install on a computer, such as another user's, says only the main install can lower the remote desktop guard, and what to do instead. It used to say to lower it at the computer.

Desktop

  • Closing the desktop app's window, or quitting it, while an editor has unsaved changes asks first, with the Save and Discard choices closing an editor tile gives. The window used to close and the changes were lost.

This version isn't on npm. Install or update with the curl installer, Homebrew, or the desktop app.

Download this release

Release history

Curated highlights for the 1.0 line. The current packaged release appears above and updates itself whenever a new version is published. There was no separate 1.0.0 build: the 1.0 line began at 1.0.1 on mobile and unified onto desktop and the command line at 1.0.6.

1.0.35

Desktop and command line. September 25, 2026.

  • taiku skills installs taiku's own skills for Claude Code and Codex, including one for writing plugins, and keeps them current.
  • A guest who joins without signing in no longer runs your coding agents on your login by default. See --agent-credentials to change that.
  • Paste what claude setup-token prints into Settings → Agent and Claude starts signed in on your own cloud boxes. A box made from a Linux laptop now gets the Claude login too.
  • Agents can no longer write or delete through links they plant, or reach another agent's credentials on the same machine.
  • taiku's git calls skip programs a repository names for itself, so a guest cannot get one run outside the sandbox.

1.0.34

Desktop and command line. September 21, 2026.

  • Work queued for an agent on a hosted machine is no longer used up without running. A scheduled job is not counted against its run limit, and an answer to an agent's question is not spent, unless the run can actually start.
  • Agent availability reflects whether a run can really begin, and when it cannot, the reason given is the real one.

1.0.33

Desktop, command line, and Android. September 21, 2026.

  • taiku tui opens the native terminal client, with account sign-in and switching, tiled workspaces and file previews. It shows the release notes for the version you have installed.
  • Agent conversations keep their context across follow-up messages. You can approve guarded actions, cancel a running turn, read what the agent published, and answer its optional questions after it finishes.
  • The Android app decodes H.264, so a phone can open a Mac or a Windows machine over remote desktop.

1.0.32

Android. September 10, 2026.

  • Android can open a Mac or Windows machine over remote desktop. It used to connect and show nothing, because it could only decode VP9.
  • Fixed remote desktop failing to connect to hosted sessions with a TLS error.

1.0.31

Desktop and command line. September 9, 2026.

  • Every viewer can open every host over remote desktop. A Windows machine can view a Linux host, a phone can view a Mac or Windows machine, and a Mac can be viewed by an app that only speaks VP9.
  • Linux remote desktop works on Wayland, for both the picture and your input, and your desktop shows its own permission prompt first.
  • The macOS Accessibility row in Settings checks whether the permission actually works, and tells you when a grant has gone stale.

1.0.30

Desktop and command line. August 10, 2026.

  • Your account key is no longer readable from inside a terminal you share. If you have shared a session with someone you would not trust with your account, sign out everywhere from Settings to roll the key.
  • A guest can no longer claim one of your panes and lock you out of it.
  • Groundwork for Touch ID and Windows Hello. Nothing uses it yet.

1.0.29

Desktop and command line. August 9, 2026.

  • Opening a session in the browser uses a single-use link that expires after two minutes, instead of putting your account key in the URL.
  • Your login lives in the macOS Keychain, Windows Credential Manager or the Secret Service on Linux. taiku login prints which store holds it.
  • When a plan limit refuses a session, the CLI and the desktop app say what the limit is and what you have.
  • Revoking anonymous access disconnects the people it had already let in.

1.0.28

Desktop and command line. August 6, 2026.

The first release since 1.0.10, so it carries everything from the versions in between.

  • Your shell prompt and theme come back when a half-installed oh-my-zsh is left on the machine.
  • Side panels can be resized by touch on phones and tablets.
  • Machines and People are separate views, and both open with your information already on screen.
  • Waking a cloud workspace restores the tiles you left open.

1.0.9

Desktop and command line. July 24, 2026.

  • The desktop app needs macOS 12.3 or later. Older versions crashed at launch.
  • taiku switch jumps between git worktrees and branches with a fuzzy picker.
  • Terminal input is protected against being replayed.

1.0.8

Desktop, command line, and mobile. July 22, 2026.

  • Remote desktop can capture an entire screen, one app window, or an individual tab from a supported Chromium-based browser. The selected target remains interactive.
  • The native mobile apps can open links as in-app browser tiles with navigation and multiple tabs, then switch between the browser and other session tiles from the mobile tab bar.
  • Mobile Settings now opens one section at a time, invite links use the native iOS share sheet, and cloud project creation opens in a keyboard-safe sheet with a direct Windows-machine choice when the account supports it.

1.0.7

Desktop, command line, and mobile. July 16, 2026.

Packaging and reliability release. Rounds out platform coverage so every desktop and command-line download installs cleanly, including the full desktop app for Linux and Linux on Arm.

1.0.6

Desktop, command line, and mobile. July 12, 2026.

First release where the desktop app, the command-line tool, and the mobile app share a single version number. Earlier builds versioned each surface on its own.

1.0.5

Mobile (iOS). June 30, 2026.

Fixes to the on-screen keyboard bar and the accessory bar above it.

1.0.4

Mobile (iOS). June 16, 2026.

Added a swipe-from-the-edge gesture to go back.

1.0.3

Mobile (iOS). June 16, 2026.

Fixed a crash on launch and taught the app to open taiku links directly.

1.0.2

Mobile (iOS). June 16, 2026.

Replaced the placeholder app icon with the taiku icon.

1.0.1

Mobile (iOS). June 16, 2026.

First TestFlight build you can sign in to inside the app.

0.4.3

Earlier release.

Onboarding & permissions

  • First-run onboarding asks only for the device permissions a feature actually needs, and explains why in a sentence.
  • The permission list adapts to remote access: turn it off and the screen-share, remote-control, and file-sync permissions disappear (a local-only device doesn't need them).

Remote desktop

  • Access controls live in the desktop app's Settings: choose whether an incoming connection asks you each time, requires a password, or auto-accepts.

Reliability

  • Auto-updates are hardened: signed artifacts, atomic installs that can never leave a half-written binary, and a fallback update source so an outage can't block a fix.

Releases before this page predate the live release feed. The current packaged release above updates automatically whenever a new manifest is published.

On this page