

Claude Code Game Studios
Turns one Claude Code session into a game studio with 49 agents and 74 skills

Code graph and project memory for coding agents in one local Rust program

About
`graphicle setup` indexes the repo, builds a tree-sitter code graph (files, functions, classes, calls, imports), connects the coding agents it finds over one MCP server and installs Git hooks that keep it current. Before each answer it syncs the files you changed, then returns ranked excerpts from code, docs (Markdown, PDF, Office, HTML), captured sessions and reviewed memories, each with its source, within a token budget you set. The tools call no model; your agent's own model reads the excerpts. Memories that agents propose wait for your approval in a local web app (`graphicle open`), and each memory is tied to the functions it is about, so it goes stale when that code changes. Everything lives in one SQLite file. The README is candid about results: in its tests Graphicle tied grep on finding code and the authors do not claim token savings, while it beat Graphify on indexing speed and fact recall. Uses Graphify's tool names, with a migration guide.
Features
Install
Five tools that give Claude Code memory across sessions, agents and machines, with install commands, honest caveats and when CLAUDE.md is enough.
I compare Serena, XERJ, Graphicle, Graphify and Vesalius for giving Claude Code codebase context: setup, pricing, license and honest caveats.
Seven tools that cut Claude Code, Codex and Cursor token usage by compressing shell output, searching code and fetching current docs, with honest caveats.



Free. I review every submission.
is in the review queue. I'll install it, test it and list it if it passes.