-
Notifications
You must be signed in to change notification settings - Fork 0
Reference
github-actions[bot] edited this page Jun 13, 2026
·
6 revisions
Lookup-oriented technical detail for the Agent M harness — CLI flags, config schemas, detection rules, lint checks, and the shipped-work log. These pages document what is, exactly; the How-to pages cover how to do a task and Architecture covers how it's built.
-
Installer CLI — flags, prerequisites, and the ownership table for
install.sh/install.ps1. -
Migration tool —
migrate-to-user-scope.{sh,ps1}, the 4-state matrix, and the.agentm-migrate-record.jsonschema. - Repo layout — the top-level directory map and the adapter parity table.
- Compatibility — supported hosts, the OS matrix, and the adapter contract.
- Detection rules — the built-in rules and what each attaches a rationale to.
-
Project config — the
project.jsonenablement-block schema. -
Auto-orchestration config — every config key + default (toggles · thresholds · cooldowns) and the
auto-orchestration-state.jsonshape.
- AgentMemory context payload — the canonical paste-anywhere payload's sections.
-
Vault lint checks — the read-only
vault_lint.pychecks: id · severity · what each checks · suggested-fix shape. -
Note relatedness signals — the signals + thresholds
notes_link_discovery.pyscores on. - Vault write protocol — the lock path, content-hash CAS, atomic-writer, and the pin-offline / partitioning operator habits for N≥2 concurrent writers.
- CI gates — what each CI workflow proves and the script behind it.
- Completed features — the reverse-chronological log of shipped work.
How-to · Architecture · Home
🔧 How-to
- Installer CLI
- Detection rules
- Project config
- Migration tool
- CI gates
- Repo layout
- Vault lint checks
- Note relatedness signals
- Vault write protocol
- Queue status lite
- AgentMemory context payload
- Process seam
- Storage seam
- Auto-orchestration config
- Capability resolver
- Design governance
- Compatibility
- Completed features
- Memory MCP tools