Create your Gitmas Memory.
Set up one private memory account for your connected agents, scripts, checkpoints, and session saves.
Automated onboarding · first success
Connect agents to one shared memory.
Gitmas Memory is universal across your connected agents. Setup begins with the account and agent clients, then verifies recall with one real project.
Connect agent clients.
Install the local runtime, configure approved secrets, and register supported tools like Claude Code, Codex, Pi, Hermes, Gemini, or scripts.
Test with one real project.
Use one project to confirm Gitmas captures useful context and recalls it when the next agent needs it.
Confirm resumable work.
Check that Gitmas records what changed, what needs attention, and what the next agent should do.
Minimal setup intake
- Name and preferred support email.
- Agent tools in use: Claude Code, Codex, Pi, Hermes, Gemini, scripts, or future clients.
- One project/repo path to use for the first verification run.
- Whether memory should be hosted or local-only.
- Any data that must never leave the local machine.
Automated setup
- Create or confirm account identity and approved API credentials.
- Configure
GITMAS_*environment variables. - Install the local Gitmas Memory runtime.
- Register MCP clients where available.
- Verify the checkpoint console and encrypted full-session save path.
Prove memory is alive before adding complexity.
1. Connect Gitmas Memory to the selected agent client.
2. Run a normal task in one real project while Gitmas captures useful context.
3. Ask Gitmas Memory to recall the relevant decision or checkpoint.
4. Confirm one checkpoint: changed / needs attention / next.
5. Open the checkpoint console and confirm the state is readable.
Short, specific, resumable
- Project and branch.
- What changed.
- What is still uncertain.
- Next visible action.
Automation first
Gitmas users get a simple setup path and basic support for account or setup issues. The product is automated continuity, not a managed workflow-tuning service.