Skip to content

v0.14.0 — Federated org structure, ops tooling & team positioning

Choose a tag to compare

View all tags
@yamantaka520 yamantaka520 released this 11 Jul 15:56
v0.14.0
68547cf

The team layer becomes correct end to end: the org structure federates so project:<id> means the same thing on every node, plus ops tooling for the messy realities (orphaned memory, reindex, updates).

Federated org structure (migration 14)

  • Convergent org sync: bundle v3 carries each team/project with an updated_at + full member set; import applies last-writer-wins and REPLACES the member set, so additions AND removals converge. Deletions propagate via org_tombstones (a reused id can't resurrect a deleted scope). Org export is scoped like memory; the subset invariant is preserved on import.
  • Membership audit (org_audit): every create/delete + member add/remove is recorded (actor + timestamp); client.org_audit_log() / GET /api/org/audit.

Ops & maintenance tooling

  • Orphan memories — a memory scoped to a team/project with no members is visible to nobody. agent-memory maintenance orphans [--delete], /api/maintenance/*, and a console Maintenance panel find and clean them; removing a member warns when it orphaned memory.
  • agent-memory maintenance — scan / orphans / reindex / vacuum.
  • agent-memory update — detects host (pip) vs Docker + OS, checks PyPI, and upgrades via pip or prints the docker pull steps.

Also

  • README repositioned around AI-agent team operation.
  • Ships the v0.13.0 review fixes (create_project team-repoint, register_agent membership-preservation, project sharing in the API, CLI error handling, deleted-scope grant revocation).

245 tests; migrations 13 & 14 self-apply; validation PASS. Two-node org convergence verified.

Install / upgrade

pip install -U 'agent-memory-os[full]'   #  or: docker pull yamantaka520/agent-memory-os:0.14.0
agent-memory update                      #  <- the new self-updater

🤖 Generated with Claude Code

Assets 2
Loading