Tidepane v0.4.2
November 10, 2026
New
- 0.4.2 announces the Android app, Files and Graph, Create Workspace, rounded panes
- Create Workspace dialog with templates and backgrounds
- Smooth workspace open/close in a plain stack
- Collapse the Agents section, with a smooth fold
- Files and Graph panel beside the panes
- Rounded pane style, cards with centred terminals
- Settings in the chats' look, titled cards with icon tiles
- Push "update available" so phones check at once
- Release script for app updates
- Settings › About with the version and the updater
- Download, check and silently install app updates
- Verify the signed update manifest and decide what to do
- Serve the phone app's update files from R2
- The Mac acts only on commands signed by the phone's approved key
- The person at the Mac approves each phone's screen-lock key
- The screen-lock key, its prompt, the held list, and the key banners
- Verify a phone's Keystore attestation: roots, key, boot and app
- The link offers the key at pairing, signs in Mac time, and holds for an unlock
- Paired phones keep a control key, in a file older builds can't read
- Signed command bytes with vectors shared by the Mac and the phone
- Control key and command signature messages
- Full licence texts in the host bundle, shown in the app
- The phone's host link carries the host's bearer token
- Tidepane-host runs ChatHost and the daemon and speaks the phone protocol on loopback
- This phone as a chat host next to the Mac
- The phone's chat host runs under the sandbox service
- Loopback trust from HTTP and a safer eviction order
- Install, launch and supervise the phone's chat host
- A loopback HTTP and WebSocket server over POSIX sockets
- First launch asks what you want, and walks the sandbox setup when it's the phone
- Tools and setup lead to Claude Code's sign-in
- Claude sign-in: the link reaches the app, opens in the browser on a tap, and only Anthropic's
- Settings › Sandbox: background, Wi-Fi only, storage, reset, delete and licences
- Tools: Claude Code, Codex CLI, Python and ripgrep, detected and installed in the sandbox
- Workspaces: clone a repository or choose a folder, and open it in the terminal
- Pick parts of a page for a chat or a terminal agent
- The Terminal tab with sessions that outlive the screen, and the extra-keys row
- Workspaces tab, bottom tabs and the sandbox setup flow
- A specialUse foreground service that keeps terminals and installs alive
- Terminal sessions that close cleanly, a stray-process sweep, and when to keep running
- A resumable installer: download, unpack, Node and Git, with Wi-Fi and space checks
- Rootfs fixes for Android and the proot command line
- Extract the rootfs safely without root, and delete or measure it without following links
- Pinned artifacts and a resumable, verified downloader behind a Wi-Fi gate
- Vendor Termux's terminal emulator and view at v0.118.3, built 16 KB aligned
- Proot and its loader for arm64, 16 KB aligned, shipped as native libs
- Phone settings for alerts and previews, and an optional fingerprint before Allow
- A worker that needs you buzzes the phone, and the tap opens its question
- Firebase when configured, and the phone's push token registered with each relay
- The relay socket, and the phone remembers and uses its Mac's relay
- The link tries the Mac directly first and the relay otherwise
- The relay's proof, control messages and the push seal on the phone
- A relay address in Settings › Phone, and pushes for asks that need you
- Add Ink, Moss, Nord and Atom One theme families
- The Mac's one socket to the relay, proven, kept alive and reconnecting
- Phones on the relay are ordinary links, bundled every 500 ms
- Bundle relay frames every 500 ms per phone, and plan pushes for asks
- The Mac tells paired phones its relay, in welcome and the invite
- Data-only FCM pushes carrying the Mac's sealed blob
- One Durable Object per Mac forwards ciphertext between proven devices, hibernating
- The relay project, its wire and the key proof
- Pushes sealed for one phone, which only it can open
- The relay's wire: ids, the key proof, control messages and envelopes
- Stop with the workers-it-started warning, new chat, ask the chat about a worker, task output, and asking for control
- Send and steer with screenshots, Allow and Deny in place, and each command's state
- The outbox and its screenshots are kept on disk, and the link stops 30 seconds after the app leaves the screen
- The link client drains the outbox once connected, resends what the Mac did not take, and asks for control
- A durable outbox for commands, with expiry, and screenshot parts
- The phone sees each chat's context, tasks and workspaces, and the Mac asks before giving control
- Phone commands run through the Mac's own send, steer, stop, new chat and answer paths
- The link works off the main thread, with a send window, and pushes each result when it is ready
- The link checks, records and acks each phone command, and takes control requests
- A persisted ledger so each phone command runs once, and staging for screenshot parts
- Pairing times out, counts wrong codes and binds Allow to its number; control is a scope
- Revisions are a digest of what the phone sees, and no view can outgrow a message
- The link module reads and writes the command and control messages
- Commands, control and screenshots join the protocol, with fixtures
- Chat text shows its formatting
- Version rules; the Mac sends update-phone, the phone reads welcome.v
- A paired phone records its scope, view for now
- A tidepane://pair link opens pairing
- Jump to the latest message in a chat or worker
- Read-only chats, chat and worker screens
- Pairing screens
- Link client with reconnect, the phone's key in Keystore, Mac discovery
- Settings › Phone, pairing sheet, and the Mac's chats as the link's source
- Link sessions over Noise, and the Bonjour WebSocket server
- A phone that leaves while pairing keeps the code open
- Project chats and transcripts into phone views
- Paired phones and the pairing desk
- Noise IK channel and message framing, checked against cacophony vectors
- Pairing code, invite URL and pairing number, same on Mac and phone
- Wire types in the link module, tested against the shared fixtures
- Wire types and shared protocol fixtures
- Scaffold the Android app under mobile-app/
- A folder that is not a Git repository starts as it is, its choice in a chip
- The visuals brief teaches by example and asks for a plan
- Thinking orbs show what a chat's agent is doing, in its working line and its sidebar row
- A new chat in a Git folder starts as is; a worktree chip offers a new or other worktree
- A Codex chat shows Codex everywhere a Claude chat shows Claude
- Choose Codex as a new chat's agent, with its accounts, models and effort
- Codex chat permission modes, model and effort
- A chat runs on its own agent: Codex executable, account, daemon, resume and reattach
- Chat agent profile and Codex model catalog
- CodexAdapter runs a user's chat: policy per turn, steering, token usage, saved state
- Replies stream in as Claude writes them
- 0.4.2 chats keep working while Tidepane is closed
- Pong says the daemon runs pipe sessions
- A held chat says it is reconnecting, and can be started again
- Keep chat file locks and hold chats when the daemon list is late
- Chats keep working while Tidepane is closed
- Pending permissions survive a detach, gap note is a log notice
- Sessions detach from the app and reattach
- DaemonTransport runs a session in the daemon
- Wire messages for daemon pipe sessions
- Pipe sessions with a numbered line log
Fixed
- The Chat host row drops the line that only described Restart
- A waiting app update shows it and downloads when Wi-Fi returns
- An aborted install session no longer clears a ready update
- The offline note waits 15 s before it shows
- A relay socket that was up comes back at once
- Answer Claude's questions on the phone with their choices
- The sandbox's /tmp and /var/tmp keep the sticky bit
- The sandbox's DNS follows the phone's network
- A chat's phone commands reach its agent in the order accepted
- Offer on a new link once a link's 4 offers are used
- Answer every key offer, tell lapsed requests
- Offer a refused key again, sign on monotonic time
- A development key counts as no key once the dev allowance is off
- A removed phone's key request never shows; re-pair key test
- Task 8 review minors
- A held command stays held across a restart
- Attestation pins one app certificate and reads -1 as ANY
- Bound the re-offer after a registered for another key
- Review minors for the link's key handling
- Review round 1: block survives a stored key, docs name the paired-phones file
- Version 0.6.8, so phones on 0.6.7 take main's daemon and session changes
- A delivered continuation is saved before its observers run; a gap ends a reconnect wait
- The SQLite notice names the version only
- Check the host bundle inside the built APK and app bundle
- Bound what the Licences screen reads from the host bundle
- Reattach sends a continuation once, waits for its own handshake
- Read only the local host's public key where that is all that's needed
- VerifyHostBundle checks the asset the variant packages
- A reattached chat owed a continuation gets it
- Carry on a chat owed a continuation, not any Reconnecting one; host 0.6.4
- An install after Reset starts a failed host; Failed with nothing installed reads Not installed
- Crash-loop guard holds through a late daemon list; host 0.6.3
- A crash-stopped phone host waits for Try again
- Host carries on only mid-turn chats; list moves while a turn streams; host 0.6.2
- A chat started on the phone keeps its workspace; host 0.6.1
- Host 0.6.0 and an out-of-memory backstop for its install
- Pinned clone delete, writes and helpers; source offer; notices
- Non-dumpable from the first line, early stop signals, SigBlk tests that can fail
- Tie the host bearer to the host's own port
- Cap the bundle's xz dictionary at 8 MiB for low-heap phones
- Xz limit re-measured after a GC; memory copy; staging stays unpinned
- Review round: pinned-only linked dest, heap-based xz limit, trash leftovers
- The phone host's refusals name the phone; LinkHub tests
- Settings offers Reset and Delete for a half-done setup
- Setup can't hang on an Error; Node unpacks into a pinned usr/local
- Verify the bundle per variant; stricter dirty-tree check
- Task 10 review round 1
- Phone chats name the chat host, never a blank page
- A hidden chat host is stopped, and round-1 review fixes
- Trust a linked extract destination only when pinned
- Release builds verify the bundle, a checkout without it skips
- Don't recreate an extract destination that is a pin's link
- Keys row sits on the keyboard, notification updates throttled
- Loopback trust stays with its request; fresh sockets aren't idle
- Carry a chat on once after a crash; a stopped chat stays put
- Loopback server bounds output and favours trusted peers
- Walk from the pin, not through its /proc/self/fd link
- Pin the host folder so a guest swap can't redirect it
- Permission asks don't crash, fragment 1.8.5 over biometric's 1.2.5
- A retry repairs a half-configured dpkg before configuring
- Proot gets canonical paths, so link2symlink's links resolve
- Review round for Task 16 part A
- Setup keeps its percent and says Removing, tools use a monotonic clock, host made off main
- The Chats tab from first launch's terminal roots at home before pairing
- A clone can be cancelled, missing workspace folders show, the tab reuses the cached size
- First launch survives a link's pairing, the Both flow roots at chats
- Inbox listing can't crash the poll, close-on-exec on API 26, stamp read off main
- Sign-in inbox pinned by fd, never blocks or recurses; stale sign-in not shown
- Delete frees tmp and inbox, every remove clears workspaces, no stale size after a wipe
- Tools review round 1: forget drops the queue, stale results, log throttle
- A failed register exchange never sends the FCM token
- A failed register exchange never sends the FCM token
- Harden clone URLs, git protocols, folder names and leaving mid-clone
- The address bar can be typed in beside another pane
- Prove open runs off main; keep zoom and pending typing per process
- A reaped shell is never signalled, no wake lock while waiting for Wi-Fi, stops can't sweep late work
- The sweep lists pids in numeric order and killAll always takes a recheck
- Closes survive a cancel, every handle is released, the sweep spares only real app processes
- Task 6 review round 2: a drain test that discriminates
- Task 6 review round 1: jobs drain, start cancel, installer resume
- Bind sources never follow a guest's symlink
- Extract into a symlinked dest, cap xz memory, refuse a truncated archive
- A short download resumes, a cancel during the hash never renames, ensureDirs fails loudly
- Proot tests declare their inputs; harden Elf reader and build script
- Seeded asks clear, ask text cleaned, relay change reaches relay phones
- Phone tells each relay its token again after 24 h
- The via relay chip sits under the Mac's name
- Pin the fingerprint gate's mapping, a broken prompt never crashes, and the notifications note stays current
- The register socket answers the relay's close instead of racing it
- A tapped ask from another Mac opens after the link moves, and the tap secret stays put
- Pairing never waits on push, and notifications are asked once, only with push
- A seen Mac is retried directly again, and the relay socket tests prove its keep-alive
- Tell programs the terminal draws 24-bit colour
- A relay failure tries the Mac directly again
- The push gate forgets by the Mac's clock, so skew lets no replay in
- AskEnded reaches every allowed phone; reconnect the relay on network change
- Back from Code, a chat whose last card grows late still scrolls to its end
- The relay's close code comes from the task's delegate
- A late relay failure can't wipe another link's frames
- Relay address vectors, length caps and a lenient r
- Idle register sockets time out, and only FCM's own 404 drops a token
- The group keeps room for the Mac, drops empty frames, and a dead prover changes nothing
- Relay wire is strict: canonical base64url, 146-byte transcript, typed key failure
- The outbox belongs to one Mac and settles when that Mac forgets the phone
- A resend after re-pairing or view-only gets its stored answer
- A phone with control keeps commands while the Mac is away, and says they go when it is back
- Stop only where the Mac stops, no draft across a worker swipe, and the new chat opens or returns
- Allow and Deny on every waiting ask, 48dp targets, and a failed send keeps its draft and screenshots
- An outbox set aside is kept a day from when it was set aside, and discarding never deletes a screenshot an entry holds
- Android 8 screenshots decode, an M1 Mac is never asked for control, and the outbox notice, dismiss and old set-aside files are handled
- A message never overtakes an earlier one still uploading; only stops and approval answers go first
- A store failure keeps the link up, screenshots go after sent, and stops never wait behind an upload
- The outbox survives a damaged file, stops resending after 6 days, and puts back a failed first write
- A command is checked for control again before it runs, and Make view-only says when it fails
- Phone commands check the agent is ready, clean up screenshots, and keep to the 20 MB limit
- A stopped server's callbacks are ignored, one large batch never closes a caught-up phone, and slow phones are tested
- A message names at most 10 screenshots, each once; the link rechecks a removed phone under the ledger lock
- The ledger evicts a finished command before a running one; a phone's stale images free its room
- A pairing link answers only its own request, by key and number; control asks keep their first time
- A long run with control characters no longer slows chat text
- Chat formatting stays fast and safe on any text
- The status bar icons are light on the dark screens
- A pairing link is handled once, even after Android restarts the app
- The keyboard no longer hides the pairing code
- Typing the pairing code no longer freezes the app
- An invite host with a leading-zero part or IPv6 brackets is refused
- Harden the Mac side of the phone link
- Worker revisions carry the launch base; moves and workspace renames bump
- A pairing link asks first and must point at the local network
- Chats follow a moved Mac, retry after an update, stop views in the background
- Pairing review fixes: forget Macs on a new key, startup error, waiting for discovery
- An unreadable dev key file is an error, never replaced
- The dev run keeps the Mac's phone key in a sandbox file
- A refusal this build does not know stops the link client
- The context gauge keeps up with a compaction and a long turn
- A rename, delete or read of a chat reaches the phone, and a relaunch never reuses an old revision
- Withdraw the pairing sheet only when this link's own request leaves the desk
- A screenshot sent with a steer shows under "You steered"
- Tidepane's own MCP server is not offered as a dev server
- A chat's session shows on the board as a chat, not as an outside session
- A screenshot sent with a steer shows under "You steered"
- An orb drawn a moment before the orbs' clock started no longer crashes the app
- A chat that was Done at quit is picked up again, and a leftover copy never blocks its restart
- A chat that was Done at quit is picked up again, and a leftover copy never blocks its restart
- A Codex approval nobody answered says so, not "You declined"
- A Codex file-change card names its files
- An account switch turns the stopped agent's mouse modes off and clears the line before restarting it
- A session never inherits another agent's account folder
- The Codex mark in a menu draws without the app's theme
- A Claude stopped for an account switch is gone when its process is, so it starts again
- Codex Auto approves only read-only commands
- Codex Auto never approves work outside the chat's folder
- A command or edit the user declines stops the Codex turn instead of failing it
- An added Claude account shows its name, email and plan; Main's footer never wraps
- A terminal started fresh does not bring back its old agent
- A sent draft is trimmed, as the box checked it
- A chat's unsent message survives switching views
- Shift-Return breaks the line at the caret
- Choices still answer after a /compact turn
- Ask a reattached chat for its context use
- Run chats in the daemon only when its pong says it runs pipe sessions
- A chat whose daemon forget is still queued waits instead of starting beside its copy
- A queue-full error forgets the daemon copy before any respawn
- A chat that starts while the daemon is unreachable runs on a process
- Deleting a held chat tells the daemon to forget its copy
- Writes and forgets made while the daemon link is down are sent after the re-attach
- The rate-limit nudge never resumes a chat held for the daemon's list
- Keep a detached worker's questions and waiting edits so they survive a reattach
- Pipe session stdin has its own writer thread so a stalled child never blocks the connection
- Keep a gone chat's record when its launch resume runs or fails
- Keep a held chat's daemon copy until its resume can run
- Start a held chat again only after its daemon copy is forgotten
- A message to a held chat queues instead of respawning
- Reattach keeps permission hashes and expiry, checkpoints coalesce
- Attach keeps a pending spawn's recovery
- Attach resumes from the caller's seq
- DaemonTransport keeps callbacks on detach, one exit on terminate
- Re-attach after exit sends nothing twice
- One id space for terminals and pipes; exactly-once reattach
- Scan private keys in linear time