Live CI for just pipelines. Watch every run in a browser, attach from a terminal, or let an agent diagnose failures while other jobs continue. The same service is the Nix binary cache your runs push to.
Documentation · Website · Binary cache · Agent skill
Nix is the only supported way to run Odu. From a repository whose justfile tags its pipeline's root recipe with [metadata("ci")]:
nix run github:juspay/odu -- ci run --host x86_64-linux=localhost --no-postUse your Nix system in place of x86_64-linux. Open http://127.0.0.1:18440: the command starts the service and watches the run. Ctrl-C stops watching; CI continues.
To adopt it — the cache line in flake.nix, the tagged recipe, the machines, required checks, agents — read Use odu from your repository. examples/consumer/ is those files whole.
- Use odu from your repository — the three files, lanes,
ci protect, what odu promises - The web service and the board — and access through Tailscale or a proxy
- Self-host on NixOS, metrics, contract versions
- Server mode — GitHub sign-in, roles, tokens, running the server's CI from your shell
- Daily workflow, CLI reference, troubleshooting
- Coding agents — the same verbs over
odu surfaceand MCP - Nix binary cache — buckets, tokens, pushing, retention and pins, S3 stores, the protocol
This repository is an Agent Plugin: the odu skill and its MCP server. With agent-distro, add "github:juspay/odu" to your profile's plugins; otherwise run nix run --accept-flake-config github:juspay/odu -- mcp as a stdio MCP server.
just install
just typecheck
just test
just e2e # e2e-cli + e2e-web
just web # serve this checkout's odu
just website # preview the docs siteBoth e2e suites exercise the Nix-built application: Bun drives CLI/MCP/lifecycle tests; Cucumber + Playwright drives the browser. Both are required on Linux and Darwin. Odu's own CI is ci/mod.just, run by odu.
User docs live in website/src/content/, not here. See package architecture, CLI e2e tests, and browser e2e tests.