kagura-engineer
An autonomous, memory-grounded coding harness. It drives a GitHub issue to a pull request, and reviews pull requests.
The actor runs through kagura-brain
using Claude Code (the default) or Codex. Grounding comes from
Kagura Memory Cloud or an offline
SQLite store, so each run starts with what previous runs learned.
This is a 0.x project: minor releases may include breaking changes. Check the
changelog
before upgrading.
Install
Requires Python ≥ 3.11.
uv tool install kagura-engineer # uv can also fetch a suitable Python
pipx install kagura-engineer
pip install kagura-engineer
The standalone review command invokes
kagura-code-reviewer.
Install both together, or review degrades to a clean FAIL gate:
uv tool install "kagura-engineer[review]"
Quick start
kagura-engineer init # scaffold a git-ignored repo.yaml
kagura-engineer doctor # check the dependency chain
kagura-engineer setup # install what's missing, bootstrap auth
kagura-engineer run 42 # drive issue #42 to a pull request
run verifies the environment, recalls relevant memory, isolates a git
worktree, drives start → implement → ship with a gate between each phase, and
opens a pull request — checkpointing as it goes, so a blocked run resumes by
re-running the same command.
Beyond Python, a run expects git, gh, the brain CLI (claude or codex),
and the gh-issue-driven plugin; ollama is used by the reviewer.
kagura-engineer doctor reports exactly which of these are missing, and
setup installs what it can.
Commands
| Command | What it does |
|---|---|
init |
Scaffold a commented, git-ignored repo.yaml |
doctor |
Check the dependency chain; --exec-probe also live-tests headless permissions |
setup |
Install missing dependencies and bootstrap authentication |
run <issue> |
Drive one GitHub issue to a pull request |
review [ref] |
Review a branch or PR and gate on the verdict; --fix runs the auto-fix loop |
eval <issues…> |
A/B the memory-grounded loop against an ungrounded control arm |
Exit codes are consistent across the operational commands: 0 success, 1 hard
failure, 2 blocked or resumable. Full behaviour, flags, and exit codes are in
the command reference.
Configuration
kagura-engineer init writes a commented repo.yaml. A minimal offline config
is two lines:
profile: dev
memory_backend: local
A Cloud-backed config adds the workspace, context, and agent identity. Every field is documented in the configuration reference.
Headless runs need Claude Code permissions granted up front — an unattended
claude -p has no human to answer a permission prompt, so a missing grant
shows up as a red-halted run. See
headless permissions,
and verify with kagura-engineer doctor --exec-probe.
Documentation
| Page | Contents |
|---|---|
| Commands | Every command, flag, and exit code |
| Configuration | repo.yaml fields, memory backends, task fidelity, brain auth |
| Headless permissions | Allowlist and workspace trust for unattended runs |
| Development | Layout, tests, release process |
| Changelog | Shipped and breaking changes by release |
kagura-engineer <command> --help is authoritative for the version you have
installed.
As a Claude Code plugin
The repository also ships a thin Claude Code skill-plugin wrapper. Its skills
shell out to the installed CLI; the harness logic stays in the Python package.
Install the CLI first, then add this repository as a marketplace source. The
plugin is also referenced by the public
kagura-plugins marketplace.
Related repositories
| Repo | Role |
|---|---|
kagura-brain |
Headless launcher seam for the Claude/Codex actor |
memory-cloud |
Persistent memory service and MCP server |
kagura-memory-python-sdk |
Memory SDK used by the Cloud client and MCP setup |
kagura-code-reviewer |
Standalone reviewer invoked by review |
kagura-plugins |
Public Claude Code plugin marketplace |
License
Apache License 2.0 — © 2026 Kagura AI. See NOTICE for attribution.
Release files for kagura-engineer 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| kagura_engineer-0.7.0.tar.gz | 279.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kagura_engineer-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 428.2 kB
Release files / kagura_engineer-0.7.0.tar.gz
| Download URL | kagura_engineer-0.7.0.tar.gz |
|---|---|
| Size | 279.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a5faf31903cbae903b6ad26658b773215a42fe0b883ab7eeed6c924407192bb
|
|
BLAKE2b-256 checksum How to use checksums |
1725c9013d95e03ddff8233c958b9e1d59203077ba7a5be3f97cb786199ef8e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 25, 2026.
Transparency logRelease files / kagura_engineer-0.7.0-py3-none-any.whl
| Download URL | kagura_engineer-0.7.0-py3-none-any.whl |
|---|---|
| Size | 149.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dccebe9c6bc4962b9dda13725915565213c93ad4cd3dea0261432d3e348c4875
|
|
BLAKE2b-256 checksum How to use checksums |
9d05f302cca9a06291bdaf8261cab0ae4d544da58c21f6fd0274315bb3f072c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 25, 2026.
Transparency log