Home

The agent harness that gives you the assistant you want — part Star Trek Computer, part J.A.R.V.I.S.

_{Works with Claude Code + Antigravity — see compatibility}

Agent M is an agentic memory implementation that combines a persistent knowledge layer with personally curated content (i.e. your own notes in markdown format) through a combination of skills, sidecars, and vectorized indexing. Imagine those workflows you saw in the movies. You're talking to your agent, "Let's open a new file for project M" and off you go. It remembers your projects and files together, can talk to you about them, and it learns and grows with you as you work. The context it builds is self-maintaining and it improves automatically as you go. No need to spend time maintaining your own knowledge graphs, and it can help you with your personal notes too, when you want it to.

Agent M has grown over time across the paired releases of agentic-harness and agent-toolkit. The full V1→V4 evolution — what shipped, what's deferred, where the design is going — lives in Agent Memory Evolution on the toolkit side. This page is the entry point for the harness itself.

Note

This wiki documents the agentic-harness repo for contributors. Target projects get templates/wiki/ installed instead. See ADR 0002 for why.

Get started

Once both repos are cloned and the vault folder exists, Agent M is operational.

1. Install both repos as siblings

git clone https://github.com/alexherrero/agentic-harness.git ~/Antigravity/agentic-harness
git clone https://github.com/alexherrero/agent-toolkit.git    ~/Antigravity/agent-toolkit

2. Point the vault at your existing Obsidian + sync setup

mkdir -p "<sync-root>/AgentMemory/personal-private/_always-load"
mkdir -p "<sync-root>/AgentMemory/personal-projects"
mkdir -p "<sync-root>/AgentMemory/_meta"
export MEMORY_VAULT_PATH="<sync-root>/AgentMemory"

Any sync layer works (Google Drive, Dropbox, syncthing).

3. Install the quality-gates bundle and the memory skill into your target project

bash ~/Antigravity/agent-toolkit/install.sh <target-project> --bundle quality-gates
bash ~/Antigravity/agent-toolkit/install.sh <target-project> --skill memory

The bundle lands the evaluator sub-agent + four base hooks (kill-switch, steer, commit-on-stop, evidence-tracker) in one operation.

4. Seed your always-load entries

Capture your locked conventions, coding-style rules, project invariants under <vault>/personal-private/_always-load/. One entry per concern. The first pass is co-created — you and the agent walk through it together; you approve each entry.

5. Verify

python3 ~/Antigravity/agentic-harness/scripts/harness_memory.py recall --phase setup

Should print your always-load entries within the 4000-token budget. Empty = vault is reachable but un-seeded. Errored = MEMORY_VAULT_PATH is unset or unreadable.

📚 New here? Learn by doing.

• Tutorial 1 — Your first harness install — fresh clone to a healthy installed scratch project in ~5 minutes.

🔧 Trying to do something specific?

• How to install the harness into a project — add the scaffold to an existing repo.
• How to refresh an installed harness — pull a newer harness version into a project that already has one.
• How to cut a release — tag, changelog, GitHub release via the ship-release skill.
• How to use auto-context in harness phases — tune MemoryVault recall budgets, save modes, and confidence thresholds for each phase.

📖 Looking up a detail?

• Installer CLI reference — flags, prerequisites, ownership table for install.sh / install.ps1.
• CI gates reference — what each CI workflow proves and the script behind it.
• Repo layout reference — top-level directory map and four-adapter parity table.
• Compatibility — supported hosts (Claude Code, Antigravity) + OS matrix + adapter contract.
• Completed features — reverse-chronological log of shipped work.

💡 Want to know why?

• Agent Memory Evolution V1→V4 — the full HLD: where Agent M started, how it grew, where it's going. The architecture, the schema, the workflows, the V4 design space.
• V3 Retrospective — what shipped across the V3 arc, what we learned, what's deferred.
• Product intent — what problem the harness solves and for whom.
• How the pieces fit — narrative of how phases, adapters, templates, and scripts interact.
• GitHub Projects integration — why and how the harness writes to ProjectsV2.

Architecture decisions

• ADR 0001 — Phase-gated workflow
• ADR 0002 — Documentation convention
• ADR 0003 — ProjectsV2 ownership and linking
• ADR 0004 — Diátaxis documentation spec
• ADR 0005 — Drop Codex support; three-adapter scope
• ADR 0006 — Split customizations into agent-toolkit
• ADR 0007 — Auto-context into harness phases

Conventions

Page templates, filename rules, and the Diátaxis four-mode split are described in templates/wiki/README.md — the same conventions this wiki follows.