codevira CLAUDE.md

Codevira — persistent project memory

This project uses Codevira to give every AI coding tool you use shared memory of the project. Decisions, fix history, the structural code graph, and learned style preferences persist across sessions and across IDEs.

When to call which Codevira tool

Call these MCP tools at the moments the description matches your action — they are fast (tens of ms), token-efficient (summary-by-default), and what makes the project's memory available to you.

At the start of every session

• get_session_context() — Always call this first. Returns a ~500-token brief: current focus, recent decisions, top open items. Without it you're blind to the project's history.

Before modifying any file

• get_impact(file_path) — Returns who calls this code (callers, dependents, blast radius). Required before any rename, signature change, or cross-cutting refactor. If callers > a small number, propose a deprecation+migration plan instead of a direct edit.

• search_decisions(query) — Returns prior architectural decisions touching the topic. Decisions with do_not_revert: true MUST be respected; if your proposed change conflicts, surface the decision to the user and wait for approval before proceeding.

Before adopting a pattern, library, or naming convention

• get_session_context() — its style panel carries the top communication preferences (~30 tokens), so match them without a separate call. For code style, read the surrounding code: naming, error handling and test layout are visible there and do not need a tool.

  (search_preferences was removed in 4.0 — see "Removed in 4.0" below.)

When you fix a bug or land an architectural choice

• record_decision(...) — Capture the why: what alternatives were considered, why this won, what would force a re-examination. A one-line decision is enough; the value compounds across sessions and across the other AI tools the user opens this project in.