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.30

Published August 10, 2026.

1.0.30

A security fix for anyone who shares terminal sessions, plus the first piece of biometric support.

Your account key no longer sits in a shared terminal

If you hosted a session and gave someone write access, they could read your permanent account key out of the shell environment. That key outlives the session and is not what sharing a terminal is meant to hand over.

It was in two places, and both are fixed. The environment no longer carries it into any shell, sandboxed or not. And the taiku helper script that lives inside a session, which needs a copy so taiku new and taiku share work, is no longer readable by other accounts on the same machine.

Nothing to do on your side, and nothing about how you share changes. If you have shared a session with someone you would not trust with your account, sign out everywhere from Settings to roll the key.

Nobody can take over a pane you are using

A guest with write access could claim one of your terminal panes, and taiku would then refuse your own keystrokes in it. Claims are how two people stay out of each other's panes, so the exclusivity was working as designed and pointing the wrong way.

Your panes are now yours. A guest can still claim panes they opened, and your own other devices are unaffected.

Groundwork for Touch ID and Windows Hello

taiku can now ask your device to confirm it is you, before doing something that deserves a check. This release adds the capability, not a feature that uses it yet.

Where it works today: Touch ID and the login password on macOS. Windows Hello is detected but not yet wired to a prompt. Linux has no system-wide way to ask, so taiku will not pretend otherwise, and anything built on this will simply not offer itself there rather than showing a check that does nothing.

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.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.