Skip to content

v3.0.0 — Agent M V3 close-out (paired with toolkit v1.0.0 — Cricket 1.0)

Choose a tag to compare

View all tags
@alexherrero alexherrero released this 24 May 07:15
· 350 commits to main since this release
v3.0.0
3c1fadf

Agent M V3 ships. The harness version now matches the memory implementation V-versioning: V3 = merged-Obsidian-and-GDrive vault with auto-recall in every harness phase + controlled write under the permeable A3 boundary + the full /memory skill surface on the Cricket side. Paired with agent-toolkit v1.0.0 which ships Cricket 1.0 — the toolkit's 1.0 commitment to a stable public API surface.

What Agent M V3 is (operator-facing):

  • The system as a whole — this repo + Cricket + your AgentMemory vault folder, working together.
  • Markdown-and-frontmatter knowledge layer. Agent reads at every session start, writes under controlled conditions, harness phase commands hook in at natural boundaries.
  • Self-modulating offer-save, cursor-tracked promotion, evidence-tracked task closeouts, quality-gates bundle for one-command install.

What V3 doesn't yet do (deferred to V4, on its own roadmap):

  • Vectorized recall / dynamic retrieval during conversation
  • Conversational surface ("open a project file for M")
  • Multi-domain scope beyond dev
  • Cross-surface protocol (Claude.ai / Gemini / Antigravity reading the same vault)
  • Vault-backed harness state
  • FRIDAY-style natural-extension surface

Full V1→V4 evolution narrative: Agent Memory Evolution. V3 arc retrospective: V3 Retrospective.

V3 arc — 13 paired releases (v1.0.0 → v3.0.0) over ~12 days

Plans #0 / #1+#2 / #3 / #4+#5 / #6 / #15 / #18 / #7a+#7b / #13 / #8 / #9 / #10 / #12+#27+#31 (this release).

This release

  • README.md — Agent M brand-framed rewrite.
  • wiki/Home.md — Agent M-centric landing for the harness wiki.
  • wiki/reference/Completed-Features.md — v3.0.0 row.

Brand: Agent M = the system as a whole; Cricket = the sibling toolkit. Code paths preserved as literals (agentic-harness/, AgentMemory/, harness_memory.py, MEMORY_VAULT_PATH).

8th consecutive paired-release pair + first MAJOR-MAJOR pair. Harness V-versioning now matches memory implementation V-versioning explicitly.

Full detail in CHANGELOG.md.

Assets 2
Loading