Skip to content

v0.7.0 — Network

Latest
Latest

Choose a tag to compare

View all tags
@STiFLeR7 STiFLeR7 released this 13 Jul 06:07
v0.7.0
cf8e906

First team/governance milestone for memex — pivots from single-developer tool to a shared, access-controlled knowledge graph, per docs/internals/VISION-2026.md.

Highlights

  • Project Identity — git-remote-derived project_id lets multiple developers/agents converge on one shared graph instead of diverging by local filesystem path. memex migrate project-id backfills existing graphs.
  • Per-Agent Attribution — every write now records which harness (Claude Code, Gemini CLI, …) produced it; per-harness confidence config is live for the first time since it shipped in v0.6.0.
  • RBAC / Team Auth — Principal identity with three roles (viewer/contributor/admin) layered on the existing write-policy ACL. Hashed bearer-key storage with full backward compatibility for pre-upgrade plaintext keys. /graph and /stats are now authenticated (previously open). Ships on a migrated StreamableHTTPSessionManager(stateless=True) transport, fixing a task-boundary bug that would have silently broken per-request identity for remote callers.
  • Write Topology — documents and validates the one supported team-deployment topology (one shared memex-server process, many remote authenticated clients); explicitly marks N-processes-one-Neo4j unsupported.
  • Governance Report — scheduled weekly team-wide summary (decisions, confidence, corroboration), delivered as file + Markdown under .memex/reports/ and via GET /report.
  • Team Dashboard — browser-based read surface (activity, confidence, conflicts, graph) with session-cookie auth, gated by real RBAC roles. No IDE or repo clone required.
  • Self-Hosted Team Deployment — production memex-server Docker image and an additive docker-compose.team.yml: Neo4j is never exposed outside the Docker network, principal/role state lives in its own volume separate from graph data. Live-verified against a real Docker daemon (build, fail-fast on missing secrets, network isolation).

Packages

  • npm: stifler-memex-mcp@0.7.0
  • PyPI: memex-mcp@0.7.0
  • MCP Registry: io.github.STiFLeR7/memex

Full phase-by-phase breakdown: .planning/ROADMAP.md in this repo.

Assets 2
Loading