evo-agents

Shared tooling for agent harnesses: a cluster of repos plus the manifest, plans and documents that tell a coding agent how the cluster fits together.

The first piece is a multi-source knowledge graph. Connectors read git repos, the harness itself, wikis and project CLIs, speak one JSON Lines protocol (kg/1), and feed an append-only log per project. A deterministic pipeline turns that log into a SQLite graph that agents query over MCP. Every node and edge carries provenance and a sensitivity label, and a session only sees what its clearance allows.

Status: early prototype. Interfaces will change.

Install

uv tool install 'evo-ak[graphify]'   # or: pip install 'evo-ak[graphify]' (PyPI name; the command is evo-agents)
uv tool install 'evo-ak[graphify] @ git+https://github.com/maycuatroi1/evo-agents'   # unreleased main
# or, from a checkout: python -m pip install -e '.[test,graphify]'

The core needs Python 3.10+ and PyYAML; nothing else. The graphify extra adds graphify's tree-sitter extractors, which give code symbols for about 40 languages; without it only Python files get symbols, and kg build and kg status warn with the number of code files left without them. A source that sets code: {backend: graphify-ast} fails the build instead when the extra is missing.

Quick start

A harness opts in with a knowledge.yaml next to its harness.yaml:

version: 1
project: demo
policy:
  levels: [public, internal, customer, secret]
  sinks:
    - id: claude-code@anthropic
      kind: agent-session
      clearance: {level: internal}
sources:
  - id: harness            # plans, contracts, bindings, docs of the harness itself
    connector: harness
    label: {level: internal, integrity: U}
  - id: app                # a repo declared in harness.yaml
    connector: git
    repo: app
    refresh: 1h            # due for kg sync --due once an hour
    label: {level: internal, integrity: U}
  - id: wiki               # any command that speaks kg/1
    connector: exec
    command: [my-cli, kg-connector, wiki]
    credentials: [{key: my.wiki.token, env: WIKI_TOKEN}]
    label: {level: customer, integrity: U}
identifiers:
  - kind: UseCase
    pattern: '\bKB-\d{2}\b'

A git source reads the text of markdown, YAML, text, config and code files (or of what its include: globs match) and records other files by path only. It skips the paths its exclude: globs match, plus a default list: build output, lock files, virtualenvs and agent folders such as .claude/ and .agents/. allow: takes globs that bring paths from that default list back, for example allow: [".claude/CLAUDE.md"]; exclude: still wins over allow:. Only the git connector reads allow:.

A markdown file whose frontmatter id: matches an identifier pattern is where that code is defined; a copy says derived_from: in its frontmatter, and kg status lists codes defined in more than one place.

Then, from the harness:

evo-agents harness validate          # schema and reference checks for every harness file
evo-agents kg sync --build           # run connectors, build the graph
evo-agents kg status                 # freshness, coverage and held deletions per source
evo-agents kg build --verify         # rebuild from scratch and compare hashes
evo-agents kg query kg_search "KB-01"
evo-agents kg query kg_impact --arg 'paths=["app:src/search.py"]'

Corpus and graph live in ~/.evo/kg/<project>/ (override with EVO_KG_HOME), never in a repo. Every source sync and every build appends one line to audit.jsonl there: ids, times, counts and versions, never item content.

To keep graphs fresh, give sources a refresh interval (30m, 6h, 1d). kg sync --due runs only the sources whose interval has passed since their last ok run; --all does that for every project that has synced on this machine. On macOS, kg schedule install loads a LaunchAgent that runs kg sync --due --all --build every hour (kg schedule print shows the plist, kg schedule uninstall removes it; output goes to ~/.evo/kg/schedule.log). On a machine signed in to a hub, the command also gets --push, which sends the runs the hub lacks (evo-agents hub kg push does the same by hand).

Using it from Claude Code

claude plugin marketplace add https://github.com/maycuatroi1/evo-agents
claude plugin install evo-kg@evo-agents

The plugin registers the MCP server evo-kg, a using-project-graph skill, and three hooks. The server binds to the project of the session directory; pass --project in .mcp.json to pin one, or run evo-agents kg bind --project NAME DIR once to tie a directory and everything below it to a project (kg bind --list and kg bind --remove DIR manage those bindings). When the machine is signed in to a hub that has a graph of the project, the server answers from the hub with the same tools (kg serve --backend auto, the default; local and hub force one or the other).

Hooks:

• SessionStart prints a short note: the bound project and the snapshot age.
• PostToolUse, after every evo-kg call, joins the labels of what the result revealed into a session label under ~/.evo/kg/sessions/. It only rises; kg_status shows it.
• PreToolUse, before Grep, Glob, or rg or grep in Bash, may add a note with the ids of graph nodes named like the search. It never allows or blocks the call. Set EVO_KG_GREP_HINTS=0 to turn it off.

The plugin needs uv on PATH and pins the release it runs: the server starts with uvx --from evo-ak==0.4.0 evo-agents, which downloads and caches that version on first start. The hooks run uvx --offline --from evo-ak==0.4.0 evo-agents, so they never wait on the network; they stay silent when uvx is missing or until the server has cached the package.

The team hub

evo-agents hub login --url https://hub.example.org   # once per machine; the token stays in ~/.evo/hub
claude plugin install evo-hub@evo-agents

The evo-hub plugin registers the MCP server evo-hub (evo-agents hub mcp, which carries the session to the hub's /mcp), a using-agent-hub skill, and two hooks. Its tools are the seven kg_* tools and memory_search, memory_get, memory_write, plan_list, plan_show, plan_step, skill_list and hub_projects. In a harness whose harness.yaml names hub.project, plans live on the hub and the files under plans/ are read-only copies: mark a step with plan_step, evo-agents hub plan step or evo harness step, never by editing the YAML.

Hooks (evo-agents hub hook session-start|stop, same pins and || true as evo-kg):

• SessionStart pulls the hub's memories of the session directory into Claude Code's memory directory, writes the plan copies of its harness (no commit; a copy edited by hand is left as it is and named), counts the skills evo-agents hub skills sync would change, and prints one line: hub, project, memories pulled, skills to sync.
• Stop pushes the memory files that changed since the last sync, so the next session on another machine has them. A turn that wrote no memory sends nothing; when the hub does not answer, the files wait and a later Stop pushes them (state in ~/.evo/hub/memory-state.json).

Both exit 0 whatever happens, give up after a few seconds, print at most one line without tokens or memory text, and send nothing when the machine is not signed in.

Workers

A worker is your own laptop or desktop running plan steps for you. You dispatch a ready step, the hub queues a run, and your worker claims it, runs the step with Claude Code, opencode or Codex CLI, and sends its log, state and evidence back, so the hub can record the step in the plan. The daemon needs the worker extra:

uv tool install 'evo-ak[worker]'    # or: pip install 'evo-ak[worker]'; with graphify: 'evo-ak[graphify,worker]'
evo-agents worker join --url https://hub.example.org --code K7QM-4XPD   # the code from the hub's Workers page
evo-agents worker register --name mac-mini --project demo --slots 1    # or this, once signed in with hub login
evo-agents worker service install   # keep the daemon running in the background

Then, from any machine signed in to the hub:

evo-agents hub run dispatch rollout 2 --project demo
evo-agents hub run logs 41 --follow --project demo
evo-agents hub run approve 41 --project demo

A worker can also take a whole plan as one plan run: its agent does every step not done yet in the order depends_on allows, in a worktree of each repo those steps name, and reports each step as it goes, verified, committed and pushed on the plan's branch. It stops for you only on a decision it may not take alone (a deploy, deleting data, a migration on real data, sending outside, spending money, or an architectural or scope choice the plan leaves open), which waits in the Inbox on the web or on the command line:

evo-agents hub run plan rollout --worker mac-mini --timeout-h 8 --project demo
evo-agents hub decision list --state open --project demo
evo-agents hub decision answer 7 --option postgres --project demo
evo-agents hub notifications --unread

The agent on a worker runs with the full rights of the machine's owner, and only that owner dispatches runs to it. docs/workers.md describes the protocol and plan runs, docs/hub.md every hub run and hub decision command, and docs/notifications.md decisions, notices and notifications.

Running a hub

The hub is an API server, a job worker and a web interface, published as two images on GHCR for each release and run with deploy/hub/docker-compose.yml next to a Postgres database and a Cloudflare R2 bucket. evo-agents hub serve and evo-agents hub worker need the server extra: pip install 'evo-ak[hub-server]'. docs/hub.md covers the API and its OpenAPI document, sign-in from the CLI and the web, who sees what, the plan copies in git, workers and runs, blobs on R2, the job worker and its queue, and operations: migrations, backup, restore and health checks.

Running steps on your machine

A member's laptop or desktop can run plan steps the hub hands it, with that member's own coding agent:

uv tool install 'evo-ak[worker]'
evo-agents worker join --url https://hub.example.org --code XXXX-XXXX   # the code from the web's Workers page
evo-agents worker run                                                    # the daemon, in the foreground

The daemon claims runs, works in a git worktree of its own under ~/.evo/worker, runs the agent's verify commands again, and pushes the plan's branch, never the default branch. docs/workers.md covers the protocol and the daemon.

Writing a connector

A connector is a generator in process or any executable. It writes JSON objects, one per line: hello first, then item, tombstone, listing, state, error, log, and closed last. Item IDs are <source>:<kind>:<native key>; every item carries a revision and a content hash over canonical JSON. Deletions are only inferred from a scoped listing that ends with complete: true, so a connector that dies half-way never deletes anything.

evo-agents kg connector test -- my-cli kg-connector wiki --fixture tests/fixtures/wiki

checks protocol, determinism, replay and permutation, truncated listings, golden output and labels.

Layout

evo_agents/
  harness/    schema and loader for harness.yaml, knowledge.yaml, contracts.yaml, plans
  kg/         protocol, connectors, corpus, pipeline, store, policy, MCP server
  hub/        team hub: server, client commands, MCP proxy, plugin hooks
  worker/     the worker daemon, `evo-agents worker`
plugins/      Claude Code marketplace (plugins evo-kg and evo-hub)
web/          the hub's web interface (Next.js, its own image)
deploy/hub/   the hub's Dockerfile and compose files
docs/         hub.md: running and using the hub; workers.md: workers, runs, plan runs and the daemon;
              notifications.md: decisions, notices and notifications

License

Apache-2.0. See LICENSE.