Product

Code graphs, context
and change review.

Ten ways to work with the same local graph. Explore the commands and the limits of each workflow.

01

Understand the system

Trace files, symbols, callers, dependencies, and entry points. Find the source behind the explanation.

Terminal
fehm query "authentication flow"

TypeScript and JavaScript have the deepest analysis. Other supported languages have shallower resolution.

02

Give agents focused context

Retrieve source excerpts, related tests, architecture rules and project history within a context budget.

Terminal
fehm context "add refunds" --budget 4000

Token budgets are estimates for rendered context, not exact model token counts.

03

Check architecture and practice drift

Compare changes with approved boundaries. Detect when engineering-practice evidence disappears.

Terminal
fehm practices audit

31 static checks support review; they do not certify compliance or prescribe one universal architecture.

04

Review and verify changes

Follow a diff through dependencies, inspect its blast radius, and run supported checks.

Terminal
fehm impact --base HEAD~1

Verification runs project code and requires a trusted repository and its toolchain.

05

Find quality and reliability gaps

Connect coverage, dependency risk, API contracts, infrastructure, and runtime evidence.

Terminal
fehm health

Heuristic risk reports and static test reachability are not measured runtime guarantees.

06

Engineer AI systems

Version prompts, review tool contracts, compare model behavior, and evaluate changes against held-out cases.

Terminal
fehm ai-evaluations

Live evaluations require an explicitly configured provider. Costs and data transmission are opt-in.

07

Keep the team in context

Watch repositories, explore the local cockpit, preserve decisions, and export onboarding notes.

Terminal
fehm serve .fehm/graph.json --watch

Local operation supports trusted teams. It is not an isolated multi-tenant service.

08

Testing & coverage

Inspect test quality, ingest measured coverage, and explore mutation testing and historical bug replay.

Terminal
fehm test-quality

Without a coverage artifact, test reachability is a static estimate. Test execution requires a trusted repository.

09

Security & delivery

Review security paths, dependency risk, API contracts, and infrastructure configuration together.

Terminal
fehm security-graph

Supported static patterns provide review signals, not a complete vulnerability assessment.

10

Review agent claims and outcomes

Check graph-backed claims and preserve agent outcomes, recurring mistakes, and resolution history.

Terminal
fehm agent

Unsupported claims remain unverified. Recorded outcomes do not guarantee future agent behavior.

SCAN · QUERY · REVIEW

Start with your repository.

Start with Fehm ↗