Decide what counts
as work.
A board adapter defines assignment. Activity sources turn reviews, comments, and CI changes into signals that wake an agent.
Board + ActivitySource
Custom workflows for agents
Put your agents
to work.
Keep them moving.
Build custom workflows around the agents and tools you already use. Connect your task sources and communication tools through adapters to keep work flowing, for coding and non-coding tasks alike.
Run Patchwake locally on your own machine. Keep your workflow in its own project and upgrade the engine through npm.
Deterministic workflows. Fewer tokens. Lower costs. Patchwake runs coordination in code, saving model tokens for the work that needs your agent.
TypeScript · Node.js 22+ · Linux + macOS
EXAMPLE / 001
WORK COMES FROMTrello / Ready
01
claim a task
patchwakeSESSION / TASK-42
Codex CLIIncluded Trello + GitHub starter
implement → open a PR
WORK HAPPENS INGitHub / Pull request
Code review + CI
02
Review or CI activity → resume
the same session
Health updates → ConsoleINCLUDED
1 agent turn at a timeCheck every 5 minNo auto-merge
See it in action
Watch Patchwake in 30 seconds.
From a setup prompt to work moving through Trello and GitHub. One example of a workflow you can make your own.
THE AGENT DOES THE WORK.
YOU DEFINE THE WORKFLOW.Bring your boardChoose your agentKeep your conventionsRun it locally
YOU DEFINE THE WORKFLOW.Bring your boardChoose your agentKeep your conventionsRun it locally
01 / From prompt to process
Runs locally.
On your own machine.
Create a project, use your coding agent to build the workflow, then preview and launch your first task. Patchwake runs with your installed agent CLI and keeps task state and logs on your machine.
Start with the example in Customize and adapt it to your workflow. Enable recurring ticks after your first task works.
The npm installer becomes available with the first release; until then, use the source setup guide.
Node.js 22+ · Linux or macOS
Python + a C/C++ toolchain to
build fs-ext, the only runtime dependency.
# Create your editable workflow project
npm create patchwake@latest my-workflow
cd my-workflow
Create a project with a pinned engine dependency. Next, choose Customize to build your workflow with your coding agent.
npm start runs one tick. New reviews, CI activity,
and plan approvals need a later tick to resume work. Use your
workflow README to install a five-minute schedule, check its logs,
and keep the host awake.
02 / The moving parts
You define the workflow.
Patchwake keeps it moving.
Deterministic rules decide when to start, when to resume, and where to send updates. Each scheduler tick checks for work and applies those rules in code, with no model call for scheduling. That saves tokens and money on routine coordination while your agent handles the task itself.
Decide what counts
Keep the context.
Manage the lifecycle.
One resumable session per task, in an isolated directory. The core handles concurrency, priority, crash backoff, and stalled turns.
Engine + AgentRuntime
Put updates where
you will see them.
Use the included console and audit channels, or add a channel for Slack, Teams, or your own tool. Notifications run last and cannot change scheduling decisions.
Channel
Choose your board and code host independently. Start with the included Trello + GitHub example using Claude Code or Codex CLI, or mix and match tools like Jira, Linear, GitLab, Bitbucket, and your own tools through custom adapters, all running on the same workflow engine.
Designed for the details
The unglamorous parts,
already thought through.
The boring parts stay deterministic.
Scheduling, priority, and retry decisions run in code without model calls. Routine coordination uses no model tokens, saving your budget for the work that needs an agent.
Context survives the next tick.
A runtime-namespaced session ID, append-only log, and file-backed state let each task return to the same conversation between ticks.
An outage isn't an empty board.
An unreadable board is unknown, never empty. Failed observations preserve existing work instead of treating it as unassigned.
Your conventions belong in your code.
Repository mapping, review gates, and merge rules live in your adapters and task instructions.
Build around how you work