Skip to main content

Ortus

test

Ortus (Latin: "rising, origin, birth") — the point from which something springs into being.

Ortus autonomously closes a backlog of bd-tracked issues using Claude Code or Codex, one fresh subprocess per task. Inspired by the Ralph Loop concept: fresh window per task, drive the queue to zero, no context drift.

Install

Requires uv on PATH. Ortus is distributed via PyPI and installed by uv; we don't auto-install uv.

One-liner (recommended):

curl -fsSL https://github.com/who/ortus/releases/latest/download/install.sh | sh

Direct PyPI:

uv tool install ortus
ortus --version

From source / pinned commit:

uv tool install git+https://github.com/who/ortus.git
# Pin a specific tag/branch:
uv tool install 'git+https://github.com/who/ortus.git@v0.1.0'

Troubleshooting:

Symptom Fix
uv: command not found Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh (see uv docs)
ortus: command not found after install uv tool update-shell then open a new shell
bd: command not found brew install beads (mac) or grab a release from https://github.com/gastownhall/beads/releases

Quick start

# Install Ortus globally (system-wide — don't add ortus as a project dependency)
curl -fsSL https://github.com/who/ortus/releases/latest/download/install.sh | sh

# Bootstrap YOUR project
cd your-project
ortus init .

# Verify prereqs for the configured backend
ortus check .

# Decompose a PRD into bd issues
ortus plan . path/to/feature.md

# Or run the idea→interview→PRD→tasks flow with no PRD path
ortus plan .

# Drive the bd queue to zero — one task per fresh agent subprocess
ortus grind .

# Override the project backend for one run
ortus grind . --backend codex

# Bounded: stop after N tasks
ortus grind . --tasks 5

Note: Ortus is a global CLI you install once and use everywhere. You don't clone this repository into your project — ortus init only adds a small set of per-project files (.beads/, AGENTS.md, .ortusrc, .gitignore, and the selected backend's config directory) to an existing directory. It is not a Python dependency.

The eight verbs

Verb Purpose
ortus init <repo> Bootstrap a fresh repo; `--backend claude
ortus check <repo> Verify bd, selected agent, sandbox, and backend config; strictly read-only
ortus plan <repo> [<PRD>] Decompose a PRD into bd issues, or interview-then-PRD-then-decompose if no PRD path
ortus grind <repo> Drive the bd queue, one task per fresh Claude or Codex subprocess
ortus interview <repo> [<feature-id>] Interactive PRD-building interview for an open feature
ortus tail <repo> Follow logs/{grind,goal,ralph}-*.log with stream-json filtering
ortus triage <repo> Walk the human-flagged bd queue interactively
ortus human <repo> Render HUMAN-TODO.md from bd issues flagged for a human decision

Run ortus <verb> --help for flags. Run ortus --version for the installed version.

Supported platforms

Platform Status Notes
Linux (Ubuntu/WSL2) full requires bubblewrap for ortus grind
macOS full Seatbelt (sandbox-exec) is built-in

Windows is not supported (decision 2026-05-17). Windows users should run ortus inside WSL2 (Windows Subsystem for Linux), where ortus runs as a normal Linux process.

Prerequisites

Tool Why Install
uv install + run ortus docs.astral.sh/uv
bd (beads) v1.0.0+ issue tracking (backed by embedded Dolt) brew install beads or GH release
claude or codex agent running inside ortus grind; Claude is the default Claude Code / Codex CLI
jq bd JSON post-processing brew install jq / apt install jq
bwrap (Linux) or sandbox-exec (Mac) OS-level sandbox for ortus grind apt install bubblewrap / built into macOS

Optional: CodeGraph. If .codegraph/ exists in a project, ortus grind's prompts use it for faster symbol/caller/callee lookups; otherwise the loop falls back to grep + Read.

Agent backends

Claude remains the default. Select Codex at project creation with ortus init . --backend codex, per run with --backend codex, or through ORTUS_BACKEND=codex. Precedence is command-line flag, environment, .ortusrc, then the Claude default.

Claude workers run a narrow claude -p '/goal …' session. Codex workers run the same logical single-issue task as a plain codex exec '…' prompt. Codex slash commands belong to its interactive UI; Ortus does not pass a literal /goal to codex exec. In both cases the outer ortus grind scheduler trusts only observable bd state and starts a fresh process for the next issue.

Why ortus

  • One install, all projects. uv tool install ortus once; every repo uses the same canonical tooling. No more copier update chasing N repos.
  • bd ready IS the queue. No README task lists, no TodoWrite scratchpads. The queue is data.
  • The scheduler is the loop. Backend output is advisory; observable bd state decides whether an iteration succeeded, orphaned a claim, or made no change.
  • Sandboxed by default. ortus grind refuses to launch unless bwrap/Seatbelt is available; Codex workers retain workspace-write, while Claude uses its generated sandbox policy.

Configuration

Optional <repo>/.ortusrc (TOML) overrides ~/.ortusrc:

prefix = "myproj"       # bd issue-id prefix
project_type = "python" # python | typescript | go | rust | polyglot
backend = "claude"      # claude | codex

Per-repo or user-wide prompt overrides live at <repo>/.ortus/prompts/<name>.md or ~/.ortus/prompts/<name>.md; the bundled defaults under src/ortus/prompts/ are the fallback (FR-025).

Session-close protocol

When ending a work session, push your work:

bd close <id> --reason "..."
git add -A && git commit -m "..."
bd dolt push
git push

Work is not done until pushed. The generated AGENTS.md repeats this in every project.

Development

# Local editable install
uv pip install -e '.[dev]'

# Tests
pytest                              # unit + integration (fast)
pytest -m smoke                     # end-to-end smoke
pytest --slow                       # everything, including real-claude smoke

License

MIT

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

ortus-0.1.4.tar.gz (71.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

ortus-0.1.4-py3-none-any.whl (88.9 kB view details)

Uploaded Python 3

File details

Details for the file ortus-0.1.4.tar.gz.

File metadata

  • Download URL: ortus-0.1.4.tar.gz
  • Upload date:
  • Size: 71.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.14

File hashes

Hashes for ortus-0.1.4.tar.gz
Algorithm Hash digest
SHA256 0a071357bb5707ee3df6ec3eccb410fc75016101b92f18b515359e7376c15be9
MD5 45d9bb658d18257523f91585de82c36a
BLAKE2b-256 ad915e228a565e46aa9579ff3a27fd32ff20965ce21612dfe89eba8008324176

See more details on using hashes here.

Provenance

The following attestation bundles were made for ortus-0.1.4.tar.gz:

Publisher: release.yml on who/ortus

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file ortus-0.1.4-py3-none-any.whl.

File metadata

  • Download URL: ortus-0.1.4-py3-none-any.whl
  • Upload date:
  • Size: 88.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.14

File hashes

Hashes for ortus-0.1.4-py3-none-any.whl
Algorithm Hash digest
SHA256 1a268b3cce70f0932f32aa344328001cb38d19d6455dec6694a3c723b45cab30
MD5 18ffb185b8341ddad527096f0f1484cf
BLAKE2b-256 b6077b9cc43dabf7d2c6075c974ee27832ea42853277d8d401b1d12295c79441

See more details on using hashes here.

Provenance

The following attestation bundles were made for ortus-0.1.4-py3-none-any.whl:

Publisher: release.yml on who/ortus

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page