Linear-native workflow
Delegate any issue directly in Linear. Use labels to pick the executor, model, and thinking level. Results — PR URL, progress log — come straight back into the issue.
Assign a Linear issue to Delego. Claude Code or Codex runs on your own machine, opens a pull request, and reports back — automatically.
Three things that make Delego different from running AI agents manually.
Delegate any issue directly in Linear. Use labels to pick the executor, model, and thinking level. Results — PR URL, progress log — come straight back into the issue.
The agent runs locally — your code never touches our servers. Use your existing Claude or Codex subscription. No extra cloud execution fees, no vendor lock-in.
Delegate and walk away. Come back to a PR already opened, tested, and reported into your Linear issue — with full progress logs visible in the dashboard.
Four screens. One action in Linear triggers the whole pipeline — here's what each surface shows you.
Open relay routes are getting pounded by unauth'd traffic. Add per-IP rate-limit on /api/runners/* before the auth check. Cap at 100 req/min. Return 429 with Retry-After header.
delego:claude-sonnet-4-5 matched. Queued.marek-mbp-16 claimed00:02main.sonnet-4-5 · thinking high.A lightweight daemon polls the relay, claims work, and streams progress back. Code never leaves your machine.
One action in Linear triggers the whole pipeline.
Assign any issue to the Delego app. Labels pick the executor, the model, and the repo you want the work done in.
Webhook lands on the relay. The job appears in your Delego dashboard with full execution-preference resolution.
Your paired CLI polls the relay, claims the job, and runs Claude Code or Codex on your machine — code never leaves your laptop.
Pull request opens with description and tests already written. Status, log, and PR link land back on the original Linear issue.
Free to use. Pair a runner, connect Linear, delegate your first issue.
401branch (missing header, wrong scheme, empty token, unknown runner)503(transient DB failure) does not count as a failureRunnerAuthResulttype includes429statusRetry-Afterheader set automatically on 429runnerAuthOrResponse(auth)instead of the inlineNextResponse.jsonpattern.