Hire a workforce
for your coding agent.

01 — What Jeju is

An agent is a file.
A run is a record.

Jeju compiles a YAML manifest into a running worker. Everything the worker is allowed to be — and everything it did — exists as something you can read, diff, and version.

kind: Agent
metadata:
  name: article-editor
models:
  providers:
    primary:
      preset: deepseek
      model: deepseek-v4-pro
      temperature: 0.1
instructions:
  system: prompts/article-editor.md
tools: [read, search]
permissions:
  access: readOnly
runtime:
  limits: { maxSteps: 24, maxToolCalls: 40 }
output:
  name: editorial_review
  schema: # verdict, findings[]…

02 — From manifest to report

One YAML in,
one report out

Everything in between is enforced, not suggested: the manifest compiles into a bounded worker, every tool call passes the policy gate, and the whole run lands in one JSONL file that jeju view renders as a report.

1. agent.yamldeclare the worker
2. compilevalidate & pin
3. runevery call policy-gated
4. trajectory.jsonlthe canonical record
5. jeju viewrender the report

03 — Why a runtime

Delegation without a runtime is hoping

05 — Build your own

Your agent builds
the next worker

Ready-made workers are the fast path. The base skill is jeju-agent-builder: describe a repeated workflow, and your agent turns it into a new bounded worker — or tells you a plain script would do.

› Turn my changelog drafting into a jeju agent.

npx skills add cosmtrek/jeju --skill jeju-agent-builder -g

changelog-drafter/
├── agents/
│   └── changelog-drafter.agent.yaml
├── prompts/
│   └── changelog-drafter.md
├── workspace/
├── eval/                # smoke evaluator
└── README.md

$ jeju validate agents/changelog-drafter.agent.yaml
✓ manifest ok · readOnly · maxSteps 16
$ jeju run … "Draft the changelog for last week."
✓ run 20260708-c7e2 · $0.002

06 — First recipe

The writing team

The first thing shipped on Jeju — and the builder loop's first product: four catalog workers behind one skill. jeju-writing turns your agent into a dispatcher — plain language in, the cheapest capable worker out. A review step is added only when stakes call for one; simple requests never pay for it.

jeju run --workspace ~/drafts --from ~/drafts/draft.md \
  p:writing/article-editor@0.1.0 \
  "Review this draft for publish readiness. Return only the configured JSON."

{
  "verdict": "needs_revision",
  "summary": "Clear thesis, but the argument is asserted rather than built.",
  "findings": [
    {
      "severity": "high",
      "location": "opening paragraph",
      "issue": "The central claim is stated as absolute but never defended.",
      "suggestion": "Soften the claim or add a concrete comparison."
    }
  ]
}

07 — The open registry

Pinned, verified, immutable

The workers are packages resolved from a static registry — no accounts, no API. Each version pins a commit and a sha256 digest, checked on install. Published versions never change; content changes require a version bump. The catalog starts with four writing workers — the shelf is open.

packages:
  writing/article-editor:
    versions:
      0.1.0:
        source: github:cosmtrek/jeju//catalog/writing/article-editor?ref=<commit>
        digest: sha256:966d…6aff