Skip to content

Reference

github-actions[bot] edited this page Jul 17, 2026 · 19 revisions

Reference

Look up the exact details of the AgentM harness — the install flags, config schemas, detection rules, vault checks, and the log of shipped work. These pages tell you what things are; the How-to pages cover how to do a task, and Architecture covers how it's built.

Install & layout

Page What it covers
Installer CLI The flags and prerequisites for install.sh / install.ps1, and which files each owns.
Supported configurations The install-scope, vault-storage, and state-mode choices, with a pointer to each.
Migration tool The tool that moves an older per-project install to user scope, and what it records.
Repo layout The top-level directory map, and how the host adapters line up.
Compatibility The supported hosts and operating systems.

Detection & config

Page What it covers
Detection rules The built-in rules that spot what a project needs, and why each one fires.
Project config The project.json schema that turns features on and off.
Auto-orchestration config Every setting behind auto-orchestration — the toggles, thresholds, and cooldowns — and its default.

Memory & vault

Page What it covers
AgentMemory context payload The paste-anywhere memory payload, and what's in it.
Vault lint checks The read-only checks the vault audit runs, and what each one looks for.
Note relatedness signals The signals used to suggest links between notes.
Vault write protocol How the vault stays safe when more than one session writes at once, and the habits that help.
Process seam The small read-only interface another process uses to reach memory, instead of calling the engine directly.
Storage seam The interface the engine uses to read and write storage, and its two backends: the device-local store and the synced vault.
Orchestration bridge The read-only bridge that surfaces orchestration state to another process.
Queue status lite The read-only coordinator dashboard that lists every active plan and its status.
Memory MCP tools The memory-engine tool surface exposed over MCP.

Plugin capabilities

Page What it covers
Capability resolver How the harness works out which capabilities are available, on each host.
Design governance The frontmatter convention that ties a design to what it governs, and the resolver behind it.
Persona tier schema The kind: persona manifest fields and the check-personas gate that enforces them.

CI & shipped work

Page What it covers
CI gates What each CI workflow proves, and the script behind it.
GitHub Projects sync The board-sync surface agentm exposes — the config it reads, when phases emit updates, and the graceful-skip.
PII Guardrail What to keep out of the public repo, and how the scan enforces it.
Completed features The log of shipped work, newest first.
Known issues Fixed gotchas worth knowing before you hit them — non-obvious repro conditions, environmental dependencies, surprising interactions.

See also

How-to · Architecture · Home

Clone this wiki locally