Device management
taiku lets you register devices to your account and manage them from a web dashboard.
Registering a device
Section titled “Registering a device”When you run taiku while logged in, your device automatically registers itself. The CLI sends a heartbeat every 60 seconds with your device ID, OS, and current session URL. Devices not seen for 5 minutes are pruned.
Dashboard
Section titled “Dashboard”Visit taiku.live/dashboard to:
- See which devices are online
- Start a remote session on any connected device
- View active session URLs
- Manage your API key and subscription
Remote sessions
Section titled “Remote sessions”Click “Start session” on a device in the dashboard. The server queues a command, the device’s CLI picks it up via long-poll, and a new session starts automatically. This requires the CLI or desktop app to be running on the target device.
Desktop app
Section titled “Desktop app”The desktop app is a native Tauri application that wraps the web UI. It runs in the background and keeps your device registered for remote access. When you run taiku, the desktop app opens automatically (use --no-app for CLI-only mode).
The app adds native macOS menus and keyboard shortcuts for terminal management. Running taiku again while the app is open navigates to the new session.
Authentication
Section titled “Authentication”taiku loginOpens a browser for Google or GitHub OAuth. Credentials are saved to ~/.config/taiku/credentials. On headless machines, a URL and code are printed for manual entry.
Token resolution order: --token flag → TAIKU_TOKEN env var → credentials file → anonymous.
Plans and limits
Section titled “Plans and limits”| Free | Pro | |
|---|---|---|
| Concurrent sessions | 1 | 3 |
| Devices per session | 3 | 10 |
| Terminal windows | 4 | Unlimited |
| Static subdomains | No | Yes |
| Viewer auth control | No | Yes |
“Devices per session” counts write-access and tunnel-admin connections. Device slots are sticky for the session’s lifetime.