Deterministic multi-agent pipeline for AI agents

Why Worca?

Eight things a chat window with a model can't do.

worca.dev
The difference in one breath

A HARNESS

One agent.

One loop.

One person.

WORCA

Pipelines of agents.

Gates, budgets, policy.

For a project and a team.

01 · Gates

Human on the gates.
Not in the loop.

Autonomous end-to-end — you open the gates that matter.

mergespend > $10prod
off-hours runs · planned
worca — gates
✓ ✓ ✓ plan implement review merge 🔒 gate waiting for you 🔓 ✓ 🌙 23:40 → 07:10 · 3 gates queued
02 · Graph engineering

Prompt engineering
→ graph engineering.

The work has a shape you can see, edit and version.

The graph grows at runtime — one agent per task.

deterministicreplayablereusable
worca — workflow composer
Step 1
Step 2
Step 3
Step 4
phase 1 · 3 tasks · parallel
Plan
Decompose
3 tasks
Implement
Review
Implementtask: schema
Implementtask: API
Implementtask: UI
sequentialfeedback looprewritten at runtime
workflow.v3 · run #142 · replay ▶
03 · Costs & budgets

Every run
has a price tag.

Per step. Per model. Per agent. Before the invoice.

Spot the step that burns 60% of the budget.

Set a budget — the run stops itself.

worca — run #142 · costs
run #142 · $5.10 · 38 min plan implement review tests docs $0.42 $3.10 $0.88 $0.51 $0.19 opus sonnet opus haiku local 61% budget $6.00
04 · Cloud · on-prem · local

Cloud. On-prem. Local.
One pipeline.

Judgment is expensive — buy it per token.

Bulk work — run cheaper on-prem.

Chores are free — run them locally.

worca — models
☁ CLOUD 🏢 ON-PREM 💻 LOCAL complex reasoning plan review bulk work implement fix review findings chores tests PR description same pipeline · a fraction of the bill
05 · Chat control

Runs live
where the team talks.

Start, question, nudge, approve — from chat.

Replies flow back into the run.

Not one laptop. A shared, visible activity.

TelegramSlackDiscordTeams
#dev-pipelines
worca · #dev-pipelinesRun #142 · review passed.
3 files, +212 −40.🔒 gate: merge to dev?
approve
worcaMerged. $4.12 · 38 min.✓ done
06 · Guardrails

Policy travels
with the run.
Not with the developer.

Pick a guardrail set when you start — Normal, Strict, or your own.

Every agent the run spawns gets the same rules — denies + scrubbed env.

Lower scopes can add rules, never remove them. The set is on the run's record.

worca — run #142
run #142
run #142
guardrails: strict
plan
implement
review
fix
every spawn · same seal
+ add repo settings
✕ remove ~/.claude
07 · Isolation

Worst case:
a thrown-away clone.

Every run works in its own cloned tree.

A bad run is discarded with zero blast radius.

Many runs, one repo, no collisions.

worca — runs
your repo never touched run #140 · worktree run #141 · worktree run #142 · worktree run #141 · discarded ← branch / diff
08 · Ask Worca

Ask Worca.
It was there.

A conversation over every run, log, cost and diff.

Answers grounded in actual run data.

An audit trail you actually use.

ask worca
Why did the review step reject the plan?▍
Reviewer flagged two blocking issues: the migration had no rollback, and guardrails/strict.json protects infra/**.
run #142review-cycle1.md · L14$0.88
What did last night's run cost, and what changed?
$4.12 · 38 min · 3 files, +212 −40 — merged to dev at 07:12.
run #143statsdiff

Pipelines,
not prompts.

01Human on the gates
02Graph engineering
03Auditable costs
04Mixed models
05Chat integration
06Run-level guardrails
07Contained runs
08Ask Worca
worca.dev