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, pick a model, and get a file back.
Packaged builds ship for macOS as a Universal binary, Intel and Apple Silicon. Windows and Linux still run from source.
Intel and Apple Silicon. Local-first, no Tidebreak account. State in SQLite on disk.
Start on the subscription you already pay for, drop in a key, or stay fully local. Switch mid-chat.
Plan, Ask, Auto, and Allow all. Overwrite of a connected file always asks.
The tree builds. Packaged releases are macOS-only until those lanes are back on.
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.
Spreadsheets, Word, PowerPoint, PDFs, and images open without leaving Tidebreak.
Restoring v2 from v5 produces v6. A wrong file is a recoverable event.
Ask once for a triage view and keep a sandboxed mini-app in the sidebar.
Same exec tool. Different backends. Credentials stay out of the sandbox. The model never sees an absolute path.
The default execution backend, with per-chat network policy.
Available today. 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. Nothing about siblings or your home directory.
Host folders reach the sandbox on macOS. Managed providers cannot see them.
Parallel jobs from one turn, while the app is open. Not a worker that keeps going after you close the laptop.
Screen capture and consent-gated app control. In the product, not finished.
Tidebreak can search the web, connect MCP servers to chats, and expose REST APIs to local apps. Organization-managed connected apps are the next surface.
Exa, Tavily, Brave, or self-hosted SearXNG.
stdio or HTTP, added in Settings without a config file, behind the same approval gate.
Selected OpenAPI operations exposed to local apps, with credentials that never reach the app or the model.
MCP-connected applications granted through an organization gateway, not a Tidebreak-owned OAuth catalog.
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.
Policy-bound agent access to Kubernetes, PostgreSQL, cloud CLIs, SSH, and SaaS without distributing long-lived downstream credentials.
Evolve Tidebreak from general code execution into a complete coding agent: repository context, terminals, sandboxes, background work, tests, and reviewable changes.
Tidebreak is pre-1.0. The local profile is rebuilt when the data shape changes. This is what we are willing to say is next, and what is still only a direction.
A modest local scheduler on the existing run journal: one-time, daily, weekly. Not cloud cron.
Optional chat organization has landed. Project context is specified, not built.
Sentence-level sources on the work product, so a claim can be walked back to the file it came from.
Its own profile, visible control, and a reset path. Not your everyday browser.
Pinned sources, explicit updates, no background auto-update.
A native Tidebreak memory layer for durable context, plus integrations with popular memory systems so teams can bring the one they already use.