GMGitmas
Quickstart

Start with one remembered decision.

Gitmas Memory is the shared durable memory product. UnifiedMemory is the internal engine behind it.

01 · install

Install the local Gitmas runtime.

The local runtime gives agents a common memory layer and compatibility paths for Claude Code, Codex, Pi, Hermes, Gemini, scripts, and future agent clients.

Private alpha access required: the local Gitmas runtime is available after onboarding. Your invite includes repository access and setup instructions.
02 · configure

Put credentials in approved secret sources.

Secrets must come from environment variables, ~/.secrets, or configured secret tooling. The Gitmas access key is for memory access only, not LLM/model usage. Do not paste credentials into markdown docs or project files.

export GITMAS_API_URL="https://gitmas.com/memory" export GITMAS_API_KEY="provided-during-onboarding" export GITMAS_USER_ID="your-user-id" export GITMAS_AGENT_ID="your-agent-id" # Compatibility aliases still work for older clients: export MEMORY_API_KEY="$GITMAS_API_KEY"
Setup note: Gitmas access keys and account setup are part of the automated onboarding path as the service improves.
03 · MCP

Register Gitmas Memory with agent clients.

The MCP installer wires the local Gitmas Memory server into supported clients when they are present.

cd ~/gitmas-config ./bin/gitmas-mcp-install claude codex

After that, agents can store and search Gitmas Memory through their local tools instead of relying only on chat history.

04 · API

Use the remote API when you need a direct integration.

MCP/local tools are preferred. The hosted compatibility endpoints remain available for scripts and custom clients.

curl -H "X-API-Key: $GITMAS_API_KEY" \ "$GITMAS_API_URL/list.php?limit=20" curl -X POST "$GITMAS_API_URL/save.php" \ -H "Content-Type: application/json" \ -H "X-API-Key: $GITMAS_API_KEY" \ -d '{ "project":"example-project", "tag":"checkpoint", "title":"First durable decision", "content":"We chose the narrow Memory + Checkpoints product scope." }'
05 · checkpoint

Checkpoint the state of the run.

Good checkpoints are short, useful, and resume-oriented. Capture what changed, what still needs attention, and what the next agent should do.

  • Current project and branch.
  • Last meaningful decision or commit.
  • Open blockers and pending approvals.
  • Next visible action.
06 · security

Keep Gitmas honest.

Gitmas Memory is not claiming enterprise compliance yet. It does use authenticated endpoints, controlled access, encrypted full-session saves where enabled, and explicit secret-handling rules.

Read the security and trust notes →