Tidebreak vs OpenWorker
OpenWorker is the closest philosophical sibling Tidebreak has: local-first, open source, bring your own model or run one through Ollama, and judged on finished work rather than chat. The practical difference is the center of gravity. OpenWorker leans into connected apps, inbox and calendar work, and scheduled sessions. Tidebreak leans into documents: sandboxed code execution and versioned spreadsheets, decks, and memos on your disk.
Updated August 17, 2026View as Markdown
What OpenWorker is
OpenWorker was announced in July 2026 by Andrew Ng and Rohit Prasad as an open-source agent that “doesn’t just chat with you, but delivers finished work.” It is MIT-licensed, free, and requires no account; the agent loop, history, and keys stay on your machine, and models are strictly bring-your-own, from the major API providers down to fully local through Ollama, switchable mid-conversation.
Its strongest surface is connection to the tools work already lives in: more than twenty-five native connectors covering Slack, Gmail, Outlook, calendars, GitHub, Jira, Notion, and others, plus MCP, with Slack-triggered and scheduled background sessions on top. Writes, sends, and shell commands sit behind approval gates. If your working day is an inbox, a calendar, and a set of team tools, OpenWorker is aimed directly at it, and the people behind it have as much credibility as anyone in this field.
We like this project. It argues the same things Tidebreak argues: that the agent should live on your machine, that the model should be your choice, and that the test is the finished work.
Where the two lean differently
Connectors versus files. OpenWorker reaches into your apps. Tidebreak reaches into your folders. Tidebreak supports MCP servers behind its approval gate, but it deliberately ships no OAuth connector catalog; its everyday interface to your data is documents, folder grants, code execution, and web search. That is a narrower surface, chosen so that the boundary stays inspectable: access exists per chat, granted through the system picker, and the model never sees an absolute path.
What comes out. OpenWorker’s documented outputs are documents, spreadsheets, reports, and actions taken in connected apps; slide decks are not among them today. Tidebreak produces spreadsheets, Word documents, PowerPoint decks, PDFs, charts, and small local apps, and wraps them in the machinery it was built for: every output versioned, restore append-only, and native viewers in the app so you review the real file before you send it.
How code runs. Both projects gate risky actions behind approvals. Tidebreak goes a step further on execution: generated code runs inside a sandbox, the native macOS one by default or Docker, E2B, or Daytona, with a per-chat network policy. Overwriting a file in a connected folder always asks, whatever the permission mode.
Scheduling. OpenWorker has scheduled and triggered background sessions. Tidebreak does not yet; a local scheduler is on the roadmap, and pretending otherwise would be the kind of claim these pages exist to avoid.
Hardware. Tidebreak’s macOS build is universal, so Intel Macs are covered. OpenWorker’s signed build targets Apple Silicon, with an unsigned Windows build and no Linux build at the time of writing.
At a glance
| Tidebreak | OpenWorker | |
|---|---|---|
| Made by | Brightwave | Andrew Ng and Rohit Prasad |
| License | Apache-2.0 | MIT |
| Price | Free; you pay your model provider | Free; you pay your model provider |
| Account | None | None required |
| Models | API keys, ChatGPT plan sign-in, or local via Ollama | Bring your own keys, or local via Ollama |
| App connectors | MCP servers; no OAuth catalog | 25+ native connectors plus MCP |
| Scheduled work | Not yet | Yes |
| Slide decks | Yes, with native preview | Not a documented output |
| Output history | Versioned, append-only restore | No documented version history |
| Code executes | Sandboxed: macOS sandbox, Docker, E2B, Daytona | On the host, behind approvals |
| Platforms | macOS Universal; Windows and Linux from source | macOS Apple Silicon; unsigned Windows build |
Choose OpenWorker when
- The work is operational: triaging an inbox, keeping a calendar honest, answering in Slack, moving tickets.
- You want scheduled sessions running in the background today.
- You want the shortest path from a connected app to an action taken in it.
Choose Tidebreak when
- The work ends in a file: a model in a spreadsheet, a deck, a memo, a report with its history intact.
- You want code the model writes to run inside an isolation boundary, not just behind an approval prompt.
- You are on an Intel Mac, or you want to start from a ChatGPT plan instead of creating API keys.
Both are young
OpenWorker is weeks old as we write this, and Tidebreak is pre-1.0, so treat the details above as dated the day we published them. The split itself should last: apps and operations on one side, documents and their history on the other. Plenty of people will be well served by either, and some genuinely need both.