# Tidebreak roadmap

What's live. What's next. Tidebreak is in alpha; this covers the client and the wider agent infrastructure we are building around it. It is an honest list, not a launch calendar.

Status labels:

- Live: In the current macOS build
- Partial: Works, with limits we are honest about
- Next: Specified or in progress, not shipped
- Exploring: A direction, not a commitment

## The coworker on your machine

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.

- macOS Universal app (Live). Intel and Apple Silicon. Local-first, no Tidebreak account. State in SQLite on disk.
- Your ChatGPT plan, an API key, or Ollama (Live). Start on the subscription you already pay for, drop in a key, or stay fully local. Switch mid-chat.
- Four permission modes, per chat (Live). Plan, Ask, Auto, and Allow all. Overwrite of a connected file always asks.
- Windows and Linux installers (Next). The tree builds. Packaged releases are macOS-only until those lanes are back on.

## A file you can put your name on

Outputs are a catalog, not a transcript. Same filename appends. Restore appends too.

- Versioned outputs (Live). Work saved to output/ lands in the chat catalog with who produced each version and when.
- In-app preview (Live). Spreadsheets, Word, PowerPoint, PDFs, and images open without leaving Tidebreak.
- Append-only restore (Live). Restoring v2 from v5 produces v6. A wrong file is a recoverable event.
- Local apps that persist (Live). Ask once for a triage view and keep a sandboxed mini-app in the sidebar.

## How the work actually runs

Same exec tool. Different backends. Credentials stay out of the sandbox. The model never sees an absolute path.

- Native macOS sandbox (Live). The default execution backend, with per-chat network policy.
- Local Docker (Partial). Available today. Only a chat set to no network is fully enforced there.
- E2B and Daytona (Live). Managed sandboxes for the same exec tool when you want the work off-box.
- Folder grants (Live). A native picker, attached to that chat. Nothing about siblings or your home directory.
- Connected folders inside code execution (Partial). Host folders reach the sandbox on macOS. Managed providers cannot see them.
- Background agents (Partial). Parallel jobs from one turn, while the app is open. Not a worker that keeps going after you close the laptop.
- Computer use (Partial). Screen capture and consent-gated app control. In the product, not finished.

## Search and connections

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.

- Web search and extract (Live). Exa, Tavily, Brave, or self-hosted SearXNG.
- MCP servers (Live). stdio or HTTP, added in Settings without a config file, behind the same approval gate.
- REST APIs (Live). Selected OpenAPI operations exposed to local apps, with credentials that never reach the app or the model.
- Organization-managed connected apps (Next). MCP-connected applications granted through an organization gateway, not a Tidebreak-owned OAuth catalog.

## The system around the client

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.

- A governed model and app gateway (Next). One self-hosted control plane for model providers and MCP-connected apps: identity, team grants, credentials, routing, usage, spend, and audit.
- Governed access to real infrastructure (Next). Policy-bound agent access to Kubernetes, PostgreSQL, cloud CLIs, SSH, and SaaS without distributing long-lived downstream credentials.
- A fully supported coding workflow (Next). Evolve Tidebreak from general code execution into a complete coding agent: repository context, terminals, sandboxes, background work, tests, and reviewable changes.

## After this alpha

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.

- Scheduled and recurring work (Next). A modest local scheduler on the existing run journal: one-time, daily, weekly. Not cloud cron.
- Project-scoped context (Next). Optional chat organization has landed. Project context is specified, not built.
- Citation system (Exploring). Sentence-level sources on the work product, so a claim can be walked back to the file it came from.
- A Tidebreak-managed browser (Exploring). Its own profile, visible control, and a reset path. Not your everyday browser.
- Instruction-only plugins from git (Exploring). Pinned sources, explicit updates, no background auto-update.
- Memory systems (Exploring). A native Tidebreak memory layer for durable context, plus integrations with popular memory systems so teams can bring the one they already use.

---

Canonical: https://www.tidebreak.io/roadmap
Site briefing for agents and crawlers: https://www.tidebreak.io/llms.txt