Skip to main content

Varda

Point Varda at your issue tracker. It routes each item to the right agent, runs it in a sandbox, and reports the result back.

Varda is a small Rust CLI. It pulls work items from Azure DevOps, GitHub Issues or Jira, matches each item's project path to a route, checks the agent is allowed there, runs it under whatever isolation you configured, posts the recap and commit back to the item, and commits everything to a git-tracked control plane.

No tracker? A folder of markdown files works too — each task is a file carrying its own project path, zero setup. One operations folder tracks work across every project you own, and Varda can run itself, spawning sandboxed workers that merge their branches back.

varda tracker setup azdo --org acme --project Platform --repo ~/dev/acme/platform   # guided, once
# Agile: tag an item `varda` AND `varda:ready` BEFORE the first pull — readiness is decided at import
# (Scrum: tag `varda` and move it to `Approved`; other processes: see docs/trackers.md)
varda tracker pull                                                                 # imports it as a `ready` task (Agile without `varda:ready`: `backlog`)
varda run                                                                          # ready items → agents → recap on the item
varda task add "Fix the flaky auth test" --exec                                    # or, with no tracker: a local markdown task

→ Issue trackers (Azure DevOps, GitHub, Jira)

Quickstart (local markdown tasks)

brew tap nillebco/tap && brew install varda   # or, from a checkout: make install (→ ~/.local/bin)
# Windows (PowerShell, per-user, no admin; needs Git for Windows):
#   irm https://github.com/nillebco/varda/releases/latest/download/varda-installer.ps1 | iex
# Any platform, from PyPI (or a feed proxying it, where GitHub downloads are blocked):
#   uv tool install nillebco-varda
varda init            # creates the control plane at ~/.varda

Route your project to an agent, then write a task:

varda project add "/path/to/project/**" --agents claude,codex
cd /path/to/project
varda task add "Summarize this project" --edit   # --edit opens $EDITOR
varda task run <task>                       # or: varda run  (runs everything ready)
varda task show <task>                      # the recap

For scripts (cron/launchd jobs, bots) that need only the agent's answer:

echo "say hi" | varda task add t --agent brain-eod --exec --print-result   # answer on stdout, chatter on stderr
varda task run <task> --result-file /tmp/answer.txt                        # answer written to a file

--print-result / --result-file mark the task bare_result (the agent prompt omits Varda's recap/Files touched/requires_user contract), send all Varda output to stderr (or stdout for --result-file), skip live streaming, and exit non-zero if the agent run fails. Interactive and background runs are unchanged (the flags conflict with --interactive/--background).

varda init also runs git init on ~/.varda, because every task update, recap and notification is committed there.

The loop

  1. Route — the task's project path picks a route; the route decides which agents are allowed.
  2. Run — Varda marks the task running and launches the agent, in a sandbox if the route says so.
  3. Instruct — the agent is handed your CLAUDE.md / AGENTS.md / copilot-instructions.md, the task body, and a hard requirement to produce a recap listing every file it touched.
  4. Bound — it runs under a cooperative time and token budget rather than an unbounded loop.
  5. Resolve — the task lands on review, needs_user, or failed, and the recap is written.
  6. Commit — Varda commits the task update and recap to the control plane.

needs_user raises a desktop notification, so a task that stalls on a question doesn't sit silently.

Sandboxing

A route can pin a task to a sandbox, and the agent never sees your host:

[[routes]]
glob = "/path/to/project/**"
agents = ["claude"]
sandbox = "worker"

Providers: docker (or podman, via engine = "podman"), microsandbox (microVM), and processcontainer (Windows MXC, no admin); varda doctor shows which work on this host. Each box gets a scoped credential minted on the host — never your ~/.aws, never your ~/.azure — an egress allowlist instead of open internet, and only the mounts you declare — with identity files forced read-only and credential paths denylisted.

Credentials are named, not embedded: config references a host env var or a secret-store key, and the value is resolved at launch. A repo-committed .varda is treated as untrusted and clamped to a hardening floor.

Windows without admin rights

primitive = "processcontainer" runs the agent in a Windows MXC BaseContainer, built on mxc-sdk 1.0.1. It needs no administrator rights, no Hyper-V, no Docker and no WSL, so it works on managed corporate laptops and Cloud PCs. Egress goes through a host-side proxy that enforces the same hostname allowlist as the other providers. A host service such as a local MCP broker can be allowed by naming it, e.g. "127.0.0.1:8765".

From Windows 11 24H2/25H2 build 26100.9711 / 26200.9711 (the October 2026 cumulative update), git, Node's realpath.native and Rust's canonicalize resolve paths inside the container (microsoft/mxc#1464). Agent CLIs like Copilot CLI therefore run there unpatched. On earlier builds they fail with "access denied". Check yours with varda doctor, which prints the build and marks processcontainer unavailable below it, or Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select CurrentBuild, UBR. Still unsupported: anything that starts the MSYS runtime (Git Bash, shell-script git hooks; microsoft/mxc#1061) and file-target credentials (use env credentials).

→ Sandboxing

Orchestration

Varda can drive itself. varda orchestrate starts a resident agent that reads the task board, spawns sandboxed workers into isolated git worktrees, and merges their branches back — surfacing conflicts rather than clobbering them.

varda orchestrate --interactive --workspace .

Workers reach the host only through a narrow MCP broker: spawn, collect, integrate, and task-board tools. Nothing else crosses the boundary, and an agent can never grant itself more capability than its route allows.

→ Orchestration

Agents

varda init ships four ready to use. Add any of them to a route's --agents.

Agent Backend Permissions Resume
codex OpenAI Codex CLI --sandbox workspace-write yes
claude Claude Code CLI --permission-mode acceptEdits yes
copilot GitHub Copilot CLI --allow-all-tools yes
opencode opencode --auto no

Agents can declare max_prompt_tokens; Varda estimates the full prompt and picks an allowed agent that fits, or tells you which ones would.

→ Configuration · The agent contract

Daily driving

varda task list                  # tasks for this project
varda task dashboard --web --all # kanban board, every project
varda plan                       # a reviewable plan of ready work
varda task inspect <task>        # agent, route, live processes
varda task doctor <task>         # probe the last run
varda task resume <task>         # continue a needs_user task

→ Tasks · Git behavior

Claude Code skill

varda skill install        # or --link to stay in sync with the repo

Then /varda in any Claude Code session to manage tasks in natural language.

Development

make test      # tests
make fmt       # formatting
make build     # debug build
make release   # release build
make install   # install to ~/.local/bin

Releasing: bump version in Cargo.toml, then git tag vX.Y.Z && git push --tags. The release.yml workflow (generated by cargo-dist; regenerate with dist generate after editing dist-workspace.toml) builds macOS/Linux/Windows binaries, publishes a GitHub Release, and pushes the formula to nillebco/homebrew-tap (needs the HOMEBREW_TAP_TOKEN repo secret).

Documentation

Issue trackers Azure DevOps / GitHub / Jira: setup, status_map, lifecycle, conflicts
Tasks creating, running, inspecting, resuming
Configuration routes, agents, config.toml reference
Sandboxing providers, credentials, isolation invariants
Isolation what each primitive actually blocks, verified vs not
Orchestration sub-task spawning, the resident, roles
The agent contract what the agent is told, execution bounds
Git behavior what gets committed, verification gate

Current limitations

  • Agents are driven as subprocesses — spawn the CLI, pipe the prompt on stdin, scrape the recap from stdout — not over the Agent Client Protocol. kind = "acp" is a vestigial config field with a single legal value that selects nothing.
  • Notification is file-backed JSON plus terminal output, with a best-effort macOS native signal for tasks that need user input.
  • Task handoff to another agent is represented by review plus recap metadata; automatic reassignment is not implemented yet.

Metadata

Release files for nillebco-varda 0.6.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for nillebco-varda 0.6.1
File Actions
nillebco_varda-0.6.1-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details for nillebco_varda-0.6.1-py3-none-win_amd64.whl
nillebco_varda-0.6.1-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl Python 3 none Linux glibc 2.17+ x86-64 Details for nillebco_varda-0.6.1-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
nillebco_varda-0.6.1-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl Python 3 none Linux glibc 2.17+ ARM64 Details for nillebco_varda-0.6.1-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
nillebco_varda-0.6.1-py3-none-macosx_11_0_arm64.whl Python 3 none macOS 11.0+ ARM64 Details for nillebco_varda-0.6.1-py3-none-macosx_11_0_arm64.whl
nillebco_varda-0.6.1-py3-none-macosx_10_12_x86_64.whl Python 3 none macOS 10.12+ x86-64 Details for nillebco_varda-0.6.1-py3-none-macosx_10_12_x86_64.whl

Total release size: 24.4 MB

Release files / nillebco_varda-0.6.1-py3-none-win_amd64.whl

Download URL nillebco_varda-0.6.1-py3-none-win_amd64.whl
Size 5.6 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
3d165d6fafce1e783d623f032d42c1dc89ec3ccb8831ece84f8801a64293ddbf
BLAKE2b-256 checksum
How to use checksums
8d1ed78bf5b52aafb58ef95d3e50ef435080e8f0e6e1c202ac98704c1fc014cb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / nillebco_varda-0.6.1-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl

Download URL nillebco_varda-0.6.1-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
Size 4.9 MB
Tags Linux glibc 2.17+ x86-64 Python 3
SHA-256 checksum
How to use checksums
c5fde1135319d9f146e23c1ac7c52d1cd084372b141a12c6c897bcbc52bb3e0c
BLAKE2b-256 checksum
How to use checksums
da7f3e1a81fcb077f10f5037bc2333613679e30750eb8990a5557f92f794658a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / nillebco_varda-0.6.1-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl

Download URL nillebco_varda-0.6.1-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
Size 4.8 MB
Tags Linux glibc 2.17+ ARM64 Python 3
SHA-256 checksum
How to use checksums
fa79a2ad6b61584b7167446d728b1acc59893906e5e849cb9180c3b915c2e0fe
BLAKE2b-256 checksum
How to use checksums
189c593849522a38f58229fec88c62ccdc4d32b99a50408f4e0e6a858b667742
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / nillebco_varda-0.6.1-py3-none-macosx_11_0_arm64.whl

Download URL nillebco_varda-0.6.1-py3-none-macosx_11_0_arm64.whl
Size 4.4 MB
Tags Python 3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
23df0d54f983bf9efa0af47a21816aa081ab1c2fe6faff6ef8faef1204cbefc2
BLAKE2b-256 checksum
How to use checksums
c8d0b0e65026a99e00679919c532a34683efdccdf6c0ae9e93e0dee05df596be
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Release files / nillebco_varda-0.6.1-py3-none-macosx_10_12_x86_64.whl

Download URL nillebco_varda-0.6.1-py3-none-macosx_10_12_x86_64.whl
Size 4.7 MB
Tags Python 3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
1f48d6356ba972df23f96271f8e842a8cf73a40ecb7c2df994e33d32860b805f
BLAKE2b-256 checksum
How to use checksums
1f0fb0f6ac313b468fa86e446493150d7db231df3e320222124bc86362b0c911
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

Security for nillebco-varda 0.6.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 5 files in this release have been uploaded with provenance metadata.

Select from 5 files

Attestation for nillebco_varda-0.6.1-py3-none-win_amd64.whl

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 17, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page