Documentation

Docs for Worca 1.x are on the way.

The site that used to live here described the 0.x line and no longer matches what ships. Rather than mislead you, it has been taken down while the new docs are written.

Until they land, everything you need is one link away: the README covers install and quick start, the changelog shows what shipped, and the deck explains why Worca works the way it does.

Current release @worca/app 1.10.0 Node ≥ 22.13 Requires Claude Code for real runs

# install
$ npm install -g @worca/app
# start the web UI (default http://localhost:4317)
$ worca ui

Start here

README

Install & quick start

How a run works, the feature tour, install requirements, and the web UI, CLI, and Claude Code skill quick starts.

Read on GitHub → What's new

Changelog for 1.10.0

The ship log: every feature that landed since the last release, with screenshots and the PRs behind them.

Open the changelog → Deck

Why Worca

A short narrated deck on the problem Worca solves: deterministic pipelines, hard guardrails, and runs that leave a record.

Watch the deck →

Reference notes

Architecture

The whole stack in one picture

Clients, the engine, the headless Claude Code harness, and model endpoints, and how a run flows through them.

Read on GitHub → Guardrails

Policy model & enforcement

What a run may and may not do, how the limits are enforced at the harness, and where the known gaps are.

Read on GitHub → Scripts

Cards that run your own program

The runtimes, the ports and params a script declares, the test bench, and saved cases with expectations that travel with it.

Read on GitHub → Storage

Where state lives

The Worca home folder, project keys, the SQLite store, and how state migrates between versions.

Read on GitHub → Contributing

Developing Worca from source

Cloning the repo, running the tests and the mock smoke, and how changes get proposed and merged.

Read on GitHub → Releasing

How versions are published

Release candidates, stable releases, tags, and what CI publishes to npm for each.

Read on GitHub → Questions

Ask on GitHub issues

Found a gap, a bug, or something the README does not answer? Open an issue and it gets a reply.

Open issues →