Graphicle’s first public release, 0.1.0, packages a code graph and project memory in one Rust program. It is for developers who want their coding agents to find relevant code, recover earlier decisions, and see what depends on a function without repeatedly reading whole files.

  • Concrete capability: A parser maps files, functions, calls, and imports without a language model. Documents and captured Claude Code/Codex sessions join the searchable local store. graphicle context "Where are failed requests retried?" returns excerpts with file and line references within a token budget.
  • Agent interface: graphicle mcp exposes graph and memory tools through Model Context Protocol, the tool interface supported by Claude Code, Codex, Cursor, and other clients. Agents can propose memories, but a person must approve the drafts before recall uses them. Memories anchored to a function are withheld when that function changes.
  • Setup: Install with brew install graphicle-ai/tap/graphicle, or use the macOS/Linux release archives, then run graphicle setup in a repository. graphicle open opens the browser interface; graphicle doctor checks the installation.
  • Inspect the defaults: Setup connects detected agents, enables session capture, edits agent instructions, and adds Git hooks. The docs offer --clients, --no-capture, --no-instructions, and --no-hooks controls. Changed files are backed up; graphicle disconnect removes its additions.
  • Cost and privacy: The Apache-2.0 core is free and needs no account or API key for graph extraction and context retrieval. Data lives in a local SQLite store, with HTTP endpoints listening on loopback by default. Written answers from graphicle ask require an optional configured model: Ollama can stay local; hosted providers introduce their own charges and send context off-machine.

The limitation to watch is freshness, not just search quality. Before answering, Graphicle syncs a small set of changed files, but after many changes it can answer from the existing index and ask you to run graphicle sync. That warning matters before using retrieved context to plan a refactor. Native Windows builds are not available, and the project’s WSL2 path is explicitly untested.

The changelog and quick-start guide document the release and its setup side effects. This is an announcement-and-documentation capture, not a hands-on evaluation; no speed or accuracy improvement is asserted here.