← LOLCODED TOOL / dispatch GITHUB ↗

01 / TOOL

dispatch

Hand a ticket to your coding agent. Get back a tested commit.

Dispatch is the layer around the coding agent you already use, not another agent. Paste a ticket or a work item link and it spins up a fresh worktree and branch, starts your CLI, then runs your tests, lint and build against the exact tree the agent produced. A run is ready only when every required check passes on that revision. Nothing is pushed unless you turn it on.

Typing a ticket, pressing dispatch, and watching the agent work: its browser runs live, then checks pass and the Result drawer opens.

what it does

  • Paste a ticket, walk away — text or a work item link; dispatch picks the repository, creates a worktree and branch, and starts your CLI.
  • Checks decide "done", not the model — tests, lint and build run against the exact tree the agent produced.
  • Scoped checks — the diff decides what runs, so a docs tweak skips the e2e suite.
  • One repair, same session — a failing check goes back to the agent that wrote the code, with bounded output and no runaway loops.
  • Rewind anything — the Timeline replays tool calls, file changes, browser actions with screenshots, check videos and Playwright traces.
  • Your agent providers, as-is — each keeps its own login and sandbox; dispatch copies no credentials.
  • Delivery when you want it — push a branch, open a draft PR, or update the work item, each off until enabled per repository.

screenshots

Answering a question from the task list: the run resumes, changes one file and passes its checks.Replaying the agent's browser steps in the Timeline, each with its screenshot and the element acted on.

built with

  • Node.js
  • React
  • Playwright
  • Git

get it