Tidebreak is a desktop app for handing real work to an AI agent. You start a chat, attach the files the work depends on, and the agent reads them, runs code, searches the web, and writes the result out as a file you can save.
It runs on your machine. Your conversations, your documents, and the files the agent produces live in a local database and a local folder. Your provider API keys live in your operating system's credential store. Nothing is routed through a service the project operates — the only outbound traffic is the requests you configure: your model provider, your search provider, and whatever the agent explicitly fetches.
Tidebreak is pre-alpha and under active development. Interfaces, storage formats, and behavior change frequently. Expect rough edges.
What you can do with it
- Work over your own files. Attach documents to a chat from the composer, or connect a folder on your machine that the agent can list and read.
- Run code in a sandbox. The agent writes and executes scripts to analyze spreadsheets, render PDFs, build charts, and generate documents. Commands run confined, with network access off unless you grant it.
- Produce files, not just answers. Anything the agent saves to its
output/directory becomes a versioned output you can preview and export with a native save dialog. - Use any model. Anthropic, OpenAI, Google, xAI, OpenRouter, a local Ollama daemon, and any OpenAI-compatible endpoint. You can switch models mid-conversation without losing the thread.
- Decide how much rope to give it. Every chat has a permission mode, from read-only planning up to full autonomy.
Who it's for
People who want an agent that can touch real data and produce real artifacts, and who would rather that happen on their own machine than in someone else's cloud. It assumes you are comfortable obtaining a model-provider credential and entering it in settings.
What it is not
It is not a hosted service, and there is no account to create. It is not a coding assistant bound to a repository — the unit of work is a conversation with files attached, not a checkout. And it is not finished: several subsystems exist in the runtime before they have any UI.