@latentforce/latentgraph

v1.0.30

Published

3 days ago

Latentgraph CLI - AI-powered code intelligence with MCP support

0High
0Medium
0Low

latentforce

mcp model-context-protocol cli node typescript

@latentforce/latentgraph

AI-powered code intelligence CLI and MCP server.

Latentgraph indexes your codebase, builds a dependency relationship graph (DRG), and provides AI-powered insights via MCP tools - enabling AI coding assistants to understand your project's structure, dependencies, and blast radius of changes.

Installation

Install globally from the npm registry:

npm install -g @latentforce/latentgraph

Verify the install:

lgraph --version

To upgrade an existing install to the latest published version:

npm install -g @latentforce/latentgraph@latest

Getting an API Key

Go to https://latentgraph.latentforce.ai/auth
Sign up for an account
Sign in to your dashboard
Copy your API key from the dashboard under Account Settings

From the dashboard you can also create a project or can do directly from the CLI.

Quick Start

All commands must be run from your project's root directory:

cd /path/to/your/project

Option A — Interactive (recommended)

lgraph start    # Step 1: Configure API key and project, launch daemon
lgraph init     # Step 2: Scan and index project files
lgraph status   # Step 3: Verify everything is connected

When you run lgraph start interactively, it will:

Ask for your API key — paste the key from your dashboard, or choose guest mode
Ask to create or select a project — you can either:
- Select an existing project from your account
- Create a new project directly from the CLI (prompts for a name and migration template)

Option B — Non-interactive (CI/CD)

lgraph init -k YOUR_KEY -n "My App"

If a project named "My App" already exists in your account it will be reused; otherwise a new one is created.

CLI Reference

| Command | Description | |---|---| | lgraph start | Start the daemon and configure the project | | lgraph init | Scan and index project files | | lgraph status | Show current status | | lgraph update-drg | Update the dependency relationship graph | | lgraph update-wiki | Refresh Wiki module documentation | | lgraph update-implicit | Run incremental implicit dependency analysis | | lgraph update-file-index | Refresh per-file enrichment metadata | | lgraph update | Run full incremental update pipeline (drg → implicit → wiki → file-index) | | lgraph analyze | Collect code metrics for the dashboard | | lgraph stop | Stop the daemon | | lgraph add [tool] | Add Latentgraph MCP server to an AI coding tool | | lgraph join [project-name] | Join a shared project as a contributor | | lgraph config | Manage configuration |

`lgraph start`

Resolves authentication, configures the project, and launches a background daemon that maintains a WebSocket connection to the Latentgraph backend.

Interactive flow (no flags):

Prompts for your API key or guest mode
Prompts to select an existing project or create a new one
- If creating: asks for a project name and lets you pick a migration template
Saves config to .lgraph/config.json
Launches the background daemon

| Flag | Short | Description | |---|---|---| | --guest | | Use guest authentication (auto-creates a temporary project) | | --api-key <key> | -k | Provide API key directly (skips the key prompt) | | --project-name <name> | -n | Create new project or match existing by name | | --project-id <id> | | Use existing project UUID | | --gh-token <token> | | GitHub token for PR insights (optional) |

lgraph start                                    # Interactive setup
lgraph start --guest                            # Quick start without API key
lgraph start -k <key> -n "My App"               # Non-interactive
lgraph start -k <key> --gh-token ghp_...        # Set API key and GitHub token at once

`lgraph init`

Performs a full project scan — collects the file tree, categorizes files (source, config, assets), gathers git info, and sends everything to the Latentgraph backend for indexing. Automatically starts the daemon if not running.

If the project is already indexed, you will be prompted to re-index. Use --force to skip the prompt.

| Flag | Short | Description | |---|---|---| | --force | -f | Force re-indexing even if already indexed | | --guest | | Use guest authentication | | --api-key <key> | -k | Provide API key directly | | --project-name <name> | -n | Create new project or match existing by name | | --project-id <id> | | Use existing project UUID | | --gh-token <token> | | GitHub token for PR insights (optional) |

lgraph init                                      # Interactive initialization
lgraph init -f                                   # Force re-index without prompt
lgraph init --guest                              # Quick init with guest auth
lgraph init -k <key> -n "My App"                 # Non-interactive
lgraph init -k <key> --gh-token ghp_...          # Set API key and GitHub token at once

`lgraph status`

Displays a comprehensive overview of the current Latentgraph setup — API key status, project details, backend indexing state, and daemon health.

lgraph status

`lgraph update-drg`

Scans source files across all supported languages, detects git changes, and sends file contents to the backend for dependency analysis.

Supported languages:

| Language | Extensions | |---|---| | JavaScript / TypeScript | .js .jsx .ts .tsx .mjs .cjs | | Python | .py | | C# | .cs | | C / C++ | .cpp .cc .cxx .c .h .hpp |

| Flag | Short | Description | |---|---|---| | --baseline | -b | Full re-analysis of all source files (slower) | | --mode <mode> | -m | Explicit mode: baseline or incremental |

Modes:

incremental (default) — sends only git-changed files for faster updates
baseline — sends all source files for a full re-analysis

lgraph update-drg                      # Incremental update (default)
lgraph update-drg -b                   # Full re-analysis (short)
lgraph update-drg --baseline           # Full re-analysis (long)

`lgraph update-wiki`

Refreshes Wiki module documentation using snapshot-based incremental delta detection. Sends all project source files to the backend; the server compares SHA-256 hashes against its saved snapshot and regenerates only what changed.

Delta modes (resolved server-side):

| Mode | Condition | |---|---| | noop | No source changes detected — returns immediately, zero LLM calls | | incremental | Only changed modules regenerated (< 50% of files changed) | | full | All modules regenerated (first run or ≥ 50% changed) |

lgraph update-wiki

`lgraph update-implicit`

Triggers implicit dependency analysis for changed files only. The server auto-detects whether to run an incremental update based on git commit history, or a full scan if no prior run exists.

Does not re-run explicit dependency analysis (DRG), knowledge graph, or Wiki documentation. Use lgraph init for a full pipeline run.

lgraph update-implicit

`lgraph update-file-index`

Refreshes per-file enrichment metadata with incremental delta detection. Sends all project source files to the backend; the server regenerates only what changed based on SHA-256 hash comparison.

lgraph update-file-index

`lgraph update`

Runs the full incremental update pipeline in sequence: update-drg → update-implicit → update-wiki → update-file-index. Use this after making significant code changes to keep all indexes in sync.

| Flag | Short | Description | |---|---|---| | --baseline-drg | -b | Run update-drg in baseline (full re-analysis) mode | | --skip-drg | | Skip the update-drg step | | --skip-implicit | | Skip the update-implicit step | | --skip-wiki | | Skip the update-wiki step | | --skip-file-index | | Skip the update-file-index step |

lgraph update                      # Full incremental update (all steps)
lgraph update --baseline-drg       # Full DRG re-analysis + remaining steps
lgraph update --skip-wiki          # Skip Wiki regeneration

`lgraph analyze`

Scans the project to collect code metrics — lines of code, token counts, comment counts by language, and git commit activity. Results are sent to the backend and viewable in the web dashboard.

Requires lgraph start to have been run first (API key + project config). Does not require lgraph init.

lgraph analyze

`lgraph stop`

Stops the background daemon process. The daemon can be restarted with lgraph start.

lgraph stop

`lgraph add`

Configures the Latentgraph MCP server in your AI coding tool. Run lgraph add without arguments to see the list of supported tools. See MCP Integration

| Flag | Short | Description | |---|---|---| | --yes | -y | Skip the consent prompt and apply Claude/Kiro integration changes automatically |

lgraph add [tool]

`lgraph join`

Joins a shared project that you have been added to as a contributor, or a publicly shared project via share ID. Writes .lgraph/config.json so MCP tools can access it immediately. No scanning or indexing is performed — the project is already indexed by its owner.

| Flag | Short | Description | |---|---|---| | --public-id <id> | -p | Join a publicly shared project by its share ID (from a public share URL) |

lgraph join                          # Interactive project selection
lgraph join "My Team's App"          # Join by exact project name
lgraph join -p <share-id>            # Join a public project by share ID

Run lgraph start afterwards to connect the daemon.

`lgraph config`

Manages Latentgraph configuration. Running lgraph config with no subcommand displays the current configuration.

Subcommands

| Subcommand | Description | |---|---| | lgraph config show | Display current configuration (default) | | lgraph config set <key> [value] | Set a configuration value | | lgraph config clear [key] | Clear a specific key or all configuration |

Configurable keys

| Key | Description | |---|---| | api-key | Your Latentgraph API key | | gh-token | GitHub token for PR insights (enables PR-based code knowledge extraction) | | api-url | Backend API URL | | orch-url | Orchestrator URL | | ws-url | WebSocket URL |

URLs can also be set via environment variables: LGRAPH_API_URL, LGRAPH_ORCH_URL, LGRAPH_WS_URL.

lgraph config                                      # Show current config
lgraph config set api-key sk-abc123                # Set API key
lgraph config set gh-token ghp_...                 # Set GitHub token for PR insights
lgraph config set api-url http://localhost:9000    # Set API URL
lgraph config clear gh-token                       # Remove GitHub token
lgraph config clear api-key                        # Clear API key
lgraph config clear urls                           # Clear all custom URLs
lgraph config clear                                # Clear all config

MCP Integration

After initializing your project, use lgraph add to configure the Latentgraph MCP server in your AI coding tool.

Supported Tools

| Tool | Command | Config method | |---|---|---| | Claude Code | lgraph add claude-code | Runs claude mcp add-json | | LatentCode | lgraph add latent-code | Writes latent-code.json | | Opencode | lgraph add opencode | Writes opencode.json | | Codex | lgraph add codex | Runs codex mcp add | | GitHub Copilot | lgraph add copilot | Writes .vscode/mcp.json | | Cursor | lgraph add cursor | Writes .cursor/mcp.json | | Factory Droid | lgraph add droid | Runs droid mcp add | | Kiro | lgraph add kiro | Writes .kiro/settings/mcp.json |

For CLI-based tools, if the tool's CLI is not found on PATH, the command will print manual setup instructions instead.

Claude Desktop (manual)

Add to your Claude Desktop config file:

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "lgraph": {
      "command": "lgraph",
      "args": ["mcp"],
      "env": {
        "LGRAPH_PROJECT_ID": "YOUR_PROJECT_ID",
        "LGRAPH_API_URL": "https://latentgraph.latentforce.ai",
        "LGRAPH_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

LGRAPH_API_KEY is optional if the key is already saved in ~/.lgraph/config.json via lgraph config set api-key. LGRAPH_API_URL is optional if you are using the default backend.

Scan Targets

Latentgraph uses .lgraph/scan_target.json to control which parts of your codebase are scanned and in which language. This is especially useful for monorepos or multi-language projects.

A default template is automatically created the first time you run lgraph init or lgraph start. When left as the default (single entry with language: null), the server auto-detects scan targets.

Format

The file is a JSON array. Each entry has:

| Field | Type | Description | |---|---|---| | language | string \| null | Language to use, or null for auto-detect | | path | string | Relative path from project root ("" for root) |

Valid language values: javascript, typescript, python, cpp, csharp

Default (auto-detect)

[
  {
    "language": null,
    "path": ""
  }
]

Examples

Single-language TypeScript project:

[
  {
    "language": "typescript",
    "path": ""
  }
]

Monorepo with multiple languages:

[
  {
    "language": "typescript",
    "path": "frontend"
  },
  {
    "language": "python",
    "path": "backend"
  },
  {
    "language": "csharp",
    "path": "services/auth"
  }
]

C++ engine in a subdirectory:

[
  {
    "language": "cpp",
    "path": "engine/src"
  }
]

MCP Tools

| Tool | Description | |---|---| | get_context | Default first call for any artifact. Pass targets=['project'] for architecture summary + module tree, a file path for file/module context, or a symbol for callers/callees | | get_file | AI-generated summary of a source file: exports, key functions, imports, API endpoints, module role, and modification impact | | get_dependencies | Bidirectional file dependencies — what a file depends on and what depends on it, with relationship types, imported names, and edge summaries | | get_change_impact | Every file that imports or depends on a given file, grouped by dependency depth, with affected modules | | get_design_knowledge | PR-mined invariants and architectural decisions for a file or module | | get_call_chain | Callers and callees for a specific symbol, with confidence scores | | get_symbol | Locate a function/class/method by name across the project | | get_dependency_path | Shortest path connecting two files through the dependency graph | | search_codebase | Topic-based discovery across file summaries, module wiki, and PR knowledge | | ask_codebase | Natural language questions answered with RAG over the indexed codebase | | update_graph | Record AI-discovered insights into the DRG/CodeWiki (queued for owner approval) |

Each tool accepts an optional project_id parameter. If omitted, it falls back to the LGRAPH_PROJECT_ID environment variable.

Recommended call order:

get_context(targets=['project']) — understand the overall structure
get_context(targets=['<file-or-module>']) — learn a subsystem before editing
get_file — inspect a specific file
get_dependencies + get_change_impact — before any edit or refactor

Configuration Files

| File | Location | Description | |---|---|---| | Global config | ~/.lgraph/config.json | API key and server URLs | | Project config | .lgraph/config.json | Project ID, name, and agent info | | Scan targets | .lgraph/scan_target.json | Language and path targets for scanning (auto-created) |

Requirements

Node.js: 18 or newer
npm: 8 or newer (bundled with Node.js)
A free API key from latentgraph.latentforce.ai (or use --guest mode for a quick try)

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme

@latentforce/latentgraph

Table of Contents

Installation

Getting an API Key

Quick Start

Option A — Interactive (recommended)

Option B — Non-interactive (CI/CD)

CLI Reference

lgraph start

lgraph init

lgraph status

lgraph update-drg

lgraph update-wiki

lgraph update-implicit

lgraph update-file-index

lgraph update

lgraph analyze

lgraph stop

lgraph add

lgraph join

lgraph config

Subcommands

Configurable keys

MCP Integration

Supported Tools

Claude Desktop (manual)

Scan Targets

Format

Default (auto-detect)

Examples

MCP Tools

Configuration Files

Requirements

Links

`lgraph start`

`lgraph init`

`lgraph status`

`lgraph update-drg`

`lgraph update-wiki`

`lgraph update-implicit`

`lgraph update-file-index`

`lgraph update`

`lgraph analyze`

`lgraph stop`

`lgraph add`

`lgraph join`

`lgraph config`