You have a decision problem. Patchwork is the layer between your AI's impulse and the action — a local-first runtime where anything consequential stops and asks you first.
$ npx patchwork-os@beta init $ patchwork start
Every action is classified by blast radius — can it be undone, and how much breaks if it's wrong? Reversible things flow freely. Risky things wait in an approval queue with the evidence attached: what will run, why it fired, what happens if it's wrong.
Workers earn independence from their track record, per action type — good at filing issues doesn't mean allowed to push code. Every decision leaves a receipt you can replay later. All of it runs on your machine. Nothing phones home. Your keys stay yours.
Tests fail at 2am. Patchwork triages the stack trace, links the breaking commit, opens a Linear issue, and sends you a Slack summary. You wake up knowing exactly what broke and why.
Customer emails come in while you're with a client. Patchwork reads them, drafts replies in your voice, and queues them for your one-tap approval. Nothing sends without you.
6am: Patchwork pulls your commits, Linear assignments, calendar, and Slack DMs — and composes one clean brief. You read it over coffee. Already done.
One command. Detects your tools, sets up starter recipes, and opens the oversight dashboard. Link Gmail, Slack, Linear, GitHub and more — OAuth in one click.
Plain YAML files describe what to watch and what to do. Share them like dotfiles. No code required. Browse 5 community recipes to start.
Patchwork acts autonomously. Anything risky lands in your approval queue. One tap — approve or reject. That's the whole loop.
Plain YAML. Describe what to watch, what to do, and when to ask. Version-controlled. Shareable. No code required.
Every write, send, or commit lands in your approval queue before it goes anywhere. Approve from the web dashboard, terminal, or your phone.
Claude, GPT, Gemini, Grok, or local Ollama. Your keys, your models, your costs. Swap models per recipe. Nothing phones home.
Browse and install recipes in one command.patchwork recipe install github:Oolab-labs/patchwork-os/templates/recipes/morning-brief.yaml
Daily digest combining unread Gmail, calendar, recent git activity, and assigned GitHub issues into one clean brief — waiting in your inbox before coffee.
The flagship worker: root-causes an incident against your repo, drafts the smallest correct patch, gets it judge-reviewed, and opens a ready-to-merge PR.
Fetches git activity, open issues, and diagnostics in parallel, then writes a health summary — run on demand before a sprint review or standup.
Nothing sends, deletes, or commits without your approval. Patchwork shows the proposed action — exactly what will happen — on one screen.
Approve from the web UI, the terminal dashboard, or your phone. One tap. That's it.
$ npx patchwork-os@beta init # scaffolds ~/.patchwork, prints your dashboard login $ patchwork start # bridge + dashboard at localhost:3200
Automate triage, PR summaries, test failure alerts, and sprint prep. Keep the oversight. Lose the toil.
Triage inboxes, draft responses, escalate issues, and run daily briefs — without a dedicated ops person.
Build custom recipes for anything. Connect any API. Run local models. Use your own keys. Own your automation stack.