Tidebreak is in alpha. This page covers the client and the wider agent infrastructure we are building around it. It is an honest list, not a launch calendar.
The desktop app is the Tidebreak experience. It is where you sign in, grant a folder or a repository, pick a model, and get a file or a pull request back.
Packaged builds ship for macOS, Windows, and Linux, including ARM64. The native sandbox, computer use, agent-driven browsing, and the managed LibreOffice install remain macOS-only.
Intel and Apple Silicon, signed and notarized. Local-first, no Tidebreak account. State in SQLite on disk.
A Windows installer plus Linux AppImage and Debian packages, from the same release as macOS, for x86_64 and ARM64. Release builds check for updates on every platform. The Windows installer is not Authenticode-signed yet.
Sign in with ChatGPT Plus or Pro, drop in a key for Anthropic, OpenAI, Gemini, xAI, Fireworks, Together, or OpenRouter, or point the OpenAI-compatible slot at Ollama. Switch mid-chat.
Plan, Ask, Auto, and Allow all. Overwriting a connected file always asks. Every MCP tool asks in Ask and Auto.
Group chats and code workspaces under a project with its own files. One inbox lists everything waiting on you, across both modes.
Dictate with a local whisper.cpp model downloaded on demand, or through OpenAI or Gemini transcription.
The same runtime as the desktop app: a local server, one-shot prompts with a permission mode, an MCP server over a workspace's files, and an MCP server another agent can use to drive chat and code mode.
Outputs are a catalog, not a transcript. Same filename appends. Restore appends too.
Work saved to output/ lands in the chat catalog with who produced each version and when. Delete is soft, with undo.
Spreadsheets, Word, PowerPoint, PDFs, images, and interactive Plotly charts open without leaving Tidebreak. Source links jump to the page, line, sheet, or cell.
Restoring v2 from v5 produces v6. A wrong file is a recoverable event.
Markdown and plain-text outputs are editable in the app. Save publishes a new version with the one you started from as its precondition. Nothing is overwritten.
Ask once for a triage view and keep a sandboxed mini-app in the Apps library, with a manifest per revision.
Word, PDF, PowerPoint, spreadsheets, and charts ship as packaged instructions. Add your own skills and prompts, or install a plugin from a pinned git URL, including plugins that bring their own MCP servers.
Each revision lists the sources the producing turn retrieved. Sentence-level citations on the file itself are still ahead.
Code mode is the second surface. You point it at a repository, pick an engine, and review every change before it reaches your branch.
Claude Code, Codex CLI, opencode, and Grok CLI. Tidebreak downloads the pinned engine the first time you pick it and uses the engine's own sign-in. macOS, Windows, and Linux.
Every workspace gets its own branch and git worktree under a root you can see and move, so agents never write over each other or your working copy. Archive a workspace and keep the branch. Release it and Tidebreak bundles the branch before dropping it.
Keep several conversations in one workspace, each in its own tab, and run workspaces side by side. Fork any finished turn. Engine subagents show up as child rows with their own transcripts. Turns on a shared worktree run in sequence.
Each turn is a checkpoint with its own diff. The same permission modes as work mode apply, and you can change the mode between turns. Deny with a reason and the agent reads it.
Open or update a pull request, move a draft to ready, read checks and review comments, update a stale branch, resolve conflicts, and merge by squash, merge, or rebase. Stacked pull requests render as lanes. Merge only ever starts with you.
Hand the agent failing job logs, review feedback, or conflicts. Watch and fix survives an app restart, handles new failures as they land, and stops when the pull request is ready for you.
Durable rules that react to failed checks, conflicts, requested changes, a stale branch, ready-to-merge state, a merge, or a close. Each fires once per head commit.
One page tracks pull requests, workflow runs, and deployments across repositories. Analytics shows turn outcomes, tokens, prompt-cache traffic, estimated cost, and subscription usage. A command palette reaches all of it.
Several terminals per workspace, as tabs or split panes, running in the worktree. Open the worktree in your own editor whenever you want to type.
Every turn already lands as a checkpoint. Rolling a worktree back to one is not built.
Same exec tool. Different backends. Credentials stay out of the sandbox. The model never sees an absolute path.
The default execution backend on macOS, with per-chat network policy: offline, package installs, custom hosts, or open.
Available today, opt-in. Only a chat set to no network is fully enforced there.
Managed sandboxes for the same exec tool when you want the work off-box.
A native picker, attached to that chat, with separate list, read, write, and run grants. Nothing about siblings or your home directory. Disconnect from one chat, or forget the folder everywhere.
Host folders reach the sandbox on macOS. Managed providers cannot see them.
Queue follow-ups behind a live turn, or steer the turn while it runs, in both modes. The queue survives a restart.
Parallel jobs from one turn, one level deep, up to four at a time. They check in for direction instead of stopping, you can resume or cancel them, and an admitted job survives a restart. Nothing keeps running after you close the app.
macOS. Its own profile, never your everyday browser, with a reset path. In work mode, downloads land as outputs. In code mode, Claude Code, Codex CLI, and opencode get scoped browser tools over MCP: snapshots, clicks, forms, waits, responsive viewports, an inspect overlay. Windows and Linux agent control is not in the release yet.
Screen capture and consent-gated app control. In the product on macOS, not finished. Unavailable on Windows and Linux.
Tidebreak can search the web, connect MCP servers to chats, expose REST APIs to the agent, and serve its own workspaces to other agents over MCP. There will not be a Tidebreak-owned OAuth catalog.
Exa, Tavily, Brave, Firecrawl, or self-hosted SearXNG, or the built-in search on Anthropic and OpenAI models.
stdio or HTTP, added in Settings with save-and-verify, or imported from JSON. Every MCP tool counts as sensitive, so Ask and Auto both ask.
Register operations from an OpenAPI document with an explicit allowlist. Credentials never reach the app or the model.
Expose a workspace's files read-only over stdio, or let another agent drive chat and code mode.
Tidebreak signs in to a Model Gateway for hosted models and machines today. The managed catalog of MCP-connected apps behind that gateway is still being built.
Tidebreak is the open desktop surface. We are also building the shared control and access layers teams need when agents move from local files into company systems and production infrastructure.
These products are in development. The capabilities are the commitment; their names and packaging are not final.
One self-hosted control plane for model providers and MCP-connected apps: identity, team grants, credentials, routing, usage, spend, and audit. Tidebreak already uses it for on-behalf-of inference and hosted machines.
A code workspace can run on a Model Gateway machine that clones, commits, pushes, and works with pull requests as you. Server images, a compose stack, and a browser sign-in exist. The packaged desktop still embeds its own server and cannot point at a deployment.
Policy-bound agent access to Kubernetes, PostgreSQL, cloud CLIs, SSH, and SaaS without distributing long-lived downstream credentials.
Start a code session from a Slack thread and have it run on a hosted machine, under the same approvals. The design is published and the machine side is in. The adapter ships as a gateway add-on, and approvals are still answered from the desktop.
An iOS and Android client that pairs with a gateway and supervises hosted sessions: live timelines, approvals, steering, follow-ups. Not in the app stores yet.
Watch and fix, triggers, and CI repair are in. What is still missing: a scheduler, checkpoint restore, and tests an agent is trusted to act on.
Tidebreak is pre-1.0. Schema changes are migrations now, not resets, but treat the local profile as replaceable until 1.0. This is what we are willing to say is next, and what is still only a direction.
Triggers already fire on pull request facts. A clock-driven scheduler on the same run journal, one-time, daily, weekly, is next. Not cloud cron.
The in-app browser and its agent tools are macOS-only today. The other two platforms follow the same release bar.
An experimental memory layer is in the build, off by default under Settings. Turned on, conversations receive memory records and a memory tool. Shared and searchable memory are only a direction.
Sentence-level sources on the work product, so a claim can be walked back to the file it came from.
Plugins install from a pinned git URL today. A browsable catalog of instruction-only plugins is a direction, with explicit updates and no background auto-update.