Roadmap

Tidebreak is still pre-1.0. This page states the direction. It does not set dates.

Code mode takes a Git repository from task prompt to reviewed pull request. It runs Claude Code, Codex CLI, opencode, or Grok CLI in isolated Git worktrees, then adds review, CI, and delivery. Work mode turns documents and folders into versioned spreadsheets, presentations, reports, charts, and apps. Both halves ship today. 1.0 is about keeping them stable, not choosing one of them.

What 1.0 promises

1.0 is a compatibility commitment, not a feature dump.

• Data upgrades in place. Desktop upgrades from v0.61.0 onward already keep local data (decision 61). 1.0 means a supported upgrade window, not another wipe.
• Stable CLI and agent-mcp. Commands, flags, and the attach contract stay compatible across 1.x. Breaking changes increment major.
• macOS first. Production releases already ship a signed, notarized macOS app. Windows and Linux packages exist; they return as first-class 1.0 platforms before 1.0 ships, including the remaining distribution work recorded in the release guide.

The full 1.0.0 checklist lives in docs/releases.md.

What stays parked

Ideas that are valuable but not part of that promise live in docs/deferred.md. That list is not a ticket queue and it does not make dates. It covers scheduled work, browser work beyond the macOS release, a desktop-owned OAuth catalog, and other long-horizon capabilities.

Do not treat a parked idea as implied by 1.0.

What is already in motion

Hosted machines (Model Gateway), the hosted web UI, and the mobile client are product, not parked scope. See Code mode and Running headless.