evo-agents
Run coding agents across your repositories, on machines you control.
evo-agents gives your team a place to hand off work to Claude Code, Codex CLI or opencode and follow it through. Agents work through a plan, run its checks and push their changes. You can watch the work in your browser, answer questions when needed, or take over a run.
Get started | Website | Documentation
Less time coordinating agents
A change can span an API, a frontend and a shared library. Keeping the agents supplied with the right context, tracking what passed, and picking up work on another machine can become a job of its own.
- Hand off a whole plan. Each step has dependencies and checks. A worker runs the checks again before recording completion, with commits and results attached to the run.
- Keep project context between sessions. Agents share plans, memories and a searchable knowledge graph of code and documents across your repos.
- See what needs you. Follow live runs in the Monitor. Answer decisions in the Inbox or through Telegram when configured. Your autonomy settings determine which actions need approval.
- Use your own machines. Run workers on a laptop, desktop or server, using your coding-agent accounts. You can host the hub yourself, too.
The hub holds the plans and shows progress. A worker runs the agent on a machine you connect.
Give it a piece of work
On your project's Plans page, choose New plan and describe the change:
Add saved carts to checkout. Cover the API and frontend, and include tests for restoring a cart after sign-in.
An agent on your worker drafts the plan. Review its scope and checks, then choose Run plan. Follow each step and its output in the browser; you can send the agent a message or stop the run there.
Quick start
Run agents with a team. You'll need access to a hub and a machine with a coding agent installed and signed in. Ask for an invite, use your team's hub, or self-host. Install Python 3.11+ and uv, then run:
uv tool install 'evo-ak[graphify,worker]'
evo-agents hub login --url https://hub.example.org
Use your hub's URL in place of https://hub.example.org. Then follow the
setup guide to connect a project and worker. Workers run on macOS and
Linux, or inside WSL on Windows.
Try the knowledge graph on its own. You can index a local repository and explore its code without a hub account or a running agent. Follow the local walkthrough.
The package is named evo-ak on PyPI; the command is evo-agents. evo-agents is pre-1.0: commands and formats can
change between releases.
See the roadmap for current capabilities and unfinished work.
Documentation
| I want to... | Read |
|---|---|
| Set up a project and run a plan | Getting started |
| Monitor runs and manage workers | Operations |
| Index repos and configure the graph | Graph setup, query reference |
| Set permissions and handle credentials | Autonomy, credentials |
| Host a hub or build a plugin | Deployment, plugins |
| Contribute code or documentation | Contributing |
Agent instructions and MCP details are in AGENTS.md and the agent guide.
License
1 maintainer
Metadata
1 maintainer
Release files for evo-ak 0.54.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| evo_ak-0.54.10.tar.gz | 4.2 MB | With provenance | Details for evo_ak-0.54.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| evo_ak-0.54.10-py3-none-any.whl | Python 3 | none | any | Details for evo_ak-0.54.10-py3-none-any.whl |
Total release size: 9.2 MB
Release files / evo_ak-0.54.10.tar.gz
| Download URL | evo_ak-0.54.10.tar.gz |
|---|---|
| Size | 4.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e57f527f10d38a2369eb730cdf70c79d5503ca6b924a05e518b975e1b3820488
|
|
BLAKE2b-256 checksum How to use checksums |
0d0146781ea17c0ba3e0c342a7e4173162d2841b1444d1f99ed72b6216d6d527
|
| 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 4, 2026.
Transparency logRelease files / evo_ak-0.54.10-py3-none-any.whl
| Download URL | evo_ak-0.54.10-py3-none-any.whl |
|---|---|
| Size | 5.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7acddc138132cc61f290dd57e9f616734474cf4d853c7b7228ebbadd82b026e2
|
|
BLAKE2b-256 checksum How to use checksums |
4c3648664ad5229112a205d3a3d58728ccc1e9be5954df50e4d46a0290f72893
|
| 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 4, 2026.
Transparency logSecurity for evo-ak 0.54.10
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 2 files in this release have been uploaded with provenance metadata.
Attestation for evo_ak-0.54.10.tar.gz
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 4, 2026.
Transparency logA 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.
