Skip to content
All flagships

Published CLI and MCP server

Cartograph

Find the files that matter before changing a repo.

Start with the packaged refresh-token example: map the code, locate its implementation and test, and load a focused context bundle without an API key. Then use the same commands with a task from your own repository.

Run the packaged example Follow the guide

What you can do with it

Who it's for: Developers and coding agents working in an unfamiliar repository.

A task packet and source bundle containing the refresh implementation, clock dependency, and regression test, with unrelated billing and catalog code left out.

Your first useful result

Install in your development environment

npm install @anthony-maio/cartograph@1.2.2
  1. 01

    Install the example locally

    Run these commands in a new working directory. The package includes the complete example and its walkthrough.

    npm init -y
npm install @anthony-maio/cartograph@1.2.2
npx cartograph --version
  2. 02

    Map the code and identify the test

    Inspect keyFiles, minimalContext, and validationTargets in the packet. Look for src/auth/refresh.js and tests/auth-refresh.test.js.

    npx cartograph analyze ./node_modules/@anthony-maio/cartograph/examples/auth-refresh --static
npx cartograph packet ./node_modules/@anthony-maio/cartograph/examples/auth-refresh --type bug-fix --task "fix refresh token expiry"
  3. 03

    Load the relevant source

    Expect the refresh implementation, its src/clock.js dependency, and the test, each with source text. Billing and catalog files should be absent. Replace the sample path and task when you try your own repository.

    npx cartograph context ./node_modules/@anthony-maio/cartograph/examples/auth-refresh --task "fix refresh token expiry" --static --json
  4. 04

    Check the behavior

    Expect three passing tests covering clock conversion, the expiry boundary, and revocation. The sample is already correct; these checks describe the behavior to preserve during an investigation.

    node --test ./node_modules/@anthony-maio/cartograph/examples/auth-refresh/tests/auth-refresh.test.js

Know the limits

  • Static selection uses file names, symbols, and dependency relationships. It can miss relevant files or include unrelated ones; review the source before making a change.
  • The packaged example verifies installation and a small, known workflow. It does not establish selection quality across real repositories, locate a bug with certainty, or run tests for you.
  • Keep --static for the local workflow. Omitting it selects the separate model-backed workflow and requires provider configuration. Installing the package does not configure an MCP host automatically.

Source & further reading