Skip to content

v0.1.1 — Developer surface + team onboarding

Choose a tag to compare

@Ghost-xDD Ghost-xDD released this 10 Jun 04:09
· 46 commits to main since this release

MemForks v0.1.1 — Pre-release

Git for AI agent memory. Branch-aware, verifiable, mergeable memory for autonomous agents — built on Sui + Walrus + MemWal.


What works today

Core protocol (Phases 0–2 — complete)

  • Move package live on Sui testnet: memforks::tree, memforks::acl, memforks::resolver
  • Full branch → commit → recall → propose_merge → attest → finalize_merge ceremony verified on testnet
  • Model A architecture: commits are off-chain Walrus blobs (fast, free); merges are Sui transactions (settled, auditable)
  • 5 resolver kinds: LastWriteWins, Union, JuryReconcile, LlmReconcile, Sequence/And combinators
  • Ed25519 attestation verification on-chain
  • Package ID: 0x080722f5b7025679aa17792a3b07ef9b875b4ad3cee7640ecf9b8b7abd5b5347
  • Reference tree: 0xeb88a31b9ef8c015e0182929c6b499126e176939ccfe5fd419dd8e1b35bea93c

SDK — @memfork/core

  • MemForksClient / MemoryClient (alias) with branch, commit, recall, proposeMerge, finalizeMerge, grantDelegate, revokeDelegate, createResolver, waitForFinalization
  • Zero-arg connect(): auto-reads .memfork/config.json + ~/.memfork/credentials.json + MEMFORK_* env vars
  • resolvers.{lastWriteWins, union, jury, llmReconcile, and, sequence} BCS config builders
  • perms / PERM bitmask constants
  • MemForksIndexer — event-driven branch + merge state tracking

CLI — memfork

Command Description
memfork init [--quick] Automated provisioning: keygen → faucet → MemWal account → tree (~30s)
memfork join Team member onboarding — generates keys, prints grant commands for owner
memfork doctor Health check — config, credentials, Sui RPC, MemWal, delegate status
memfork install cursor|codex Wires MemWal MCP + agent rules into Cursor or Codex
memfork branch <name> Create a branch (on-chain Sui tx)
memfork checkout <name> Switch active branch
memfork commit -m <msg> --facts ... Manually anchor facts as a Walrus blob
memfork diff <a> <b> Semantic fact diff between two branches
memfork merge <from> <into> --resolver <id> Propose a merge
memfork grant / grant-memwal / revoke Access control
memfork ui [--share] DAG visualizer (local or Walrus Site)

Framework adapters

  • @memfork/langgraphBaseCheckpointSaver; each thread maps to a branch
  • @memfork/vercel-aiwithMemForks middleware; recall before generate, commit after

Coding-agent plugins

  • Cursor — MemWal MCP (Streamable HTTP) + memforks.mdc rule. memfork install cursor auto-configures ~/.cursor/mcp.json
  • Codex — same pattern. memfork install codex auto-configures ~/.codex/config.toml

Quick start

npm install -g @memfork/cli

memfork init --quick       # keygen → faucet → MemWal account → tree (~30s)
memfork doctor             # verify everything is working
memfork install cursor     # wire into Cursor

Team member onboarding:

# Teammate (after cloning repo):
memfork join

# Owner runs:
memfork grant --agent <address>
memfork grant-memwal --agent <address> --pubkey <hex>

# Teammate confirms:
memfork doctor

Known gaps (coming in v0.2.0)

  • memfork proposals — currently redirects to memfork ui; real table view coming
  • memfork install-hooks — git post-checkout auto branch-sync not yet built
  • createMemForksCheckpointer() no-arg form for LangGraph
  • mem.on('commit', ...) event subscriptions on the SDK client
  • memfork migrate — import from LangGraph / JSON into an existing tree
  • CrewAI adapter (memfork-crewai)
  • Conformance test suite

Docs