Token-efficient codebase indexing for AI coding tools.

AI assistants waste 60–80% of their token budget exploring your repo on every new conversation. CodePulse maintains a persistent, git-diff-aware index and injects a compact snapshot — repo structure, exported symbols, import graph — at session start.

Works with Claude Code (skill), OpenAI Codex CLI (pipe or AGENTS.md), Cursor/Continue.dev (MCP server), and any tool that can consume CLI output.

Token Savings

Without CodePulse, an AI assistant typically reads 10–30 files per session just to understand your repo before it can help. With CodePulse, it gets a pre-built snapshot instead — no exploration needed.

Estimates based on typical file-read patterns. Actual savings vary by repo structure and session type. Use codepulse context --budget to tune the snapshot size.

At current API pricing (Claude Sonnet ~$3/MTok input), saving 20,000 tokens per session adds up fast across a team:

Beyond cost, fewer tokens spent on exploration means faster responses and more of the context window available for actual work.

Quick Start

npm install -g @aicodepulse/cli

# In your repo: build the index (one-time)
codepulse init

# Emit context into any AI session
codepulse context

# Keep it fresh after commits
codepulse update

In Claude Code: install the skill, then type /codepulse at the start of a session.

How to Use

There are three ways to use CodePulse depending on your AI tool. Pick the one that fits your workflow.

Option 1 — CLI (any AI tool)

Install and index your repo:

npm install -g @aicodepulse/cli
cd your-project
codepulse init

Pipe context into any AI session:

codepulse context --format markdown

Keep the index up to date:

codepulse update              # incremental (fast)
codepulse watch               # auto-update on file changes
codepulse install-hooks       # auto-update after every git commit (recommended)

Option 2 — Claude Code Skill

1. Copy skill/codepulse/ into your project's .claude/skills/ directory
2. Run codepulse init in your repo once
3. Type /codepulse at the start of any Claude Code session — it injects a fresh context snapshot automatically

For always-on injection without typing the command, add this to .claude/settings.json:

{
  "hooks": {
    "PreToolUse": [{
      "matcher": ".*",
      "hooks": [{ "type": "command", "command": "codepulse context --format xml" }]
    }]
  }
}

Option 3 — MCP Server (Cursor, Continue.dev, etc.)

Install the MCP package:

npm install -g @aicodepulse/cli @aicodepulse/mcp
cd your-project && codepulse init

Add to your MCP config (e.g. .cursor/mcp.json):

{
  "codepulse": {
    "command": "codepulse-mcp",
    "args": []
  }
}

The MCP server exposes three tools your AI editor can call on demand:

• get_context(budget_tokens, focus_path?) — full context snapshot
• search_symbols(query) — find exported symbols by name
• get_file_summary(path) — symbols, imports, and importers for one file

Commands

Smart Context

CodePulse ranks what goes into the snapshot so the most useful files fit within the budget:

Task-aware ranking — pass --task to rank files by relevance to what you're working on:

codepulse context --auto --task "fix the login bug"

Keywords are extracted from your task description and matched against file paths, symbol names, exported function signatures, and stored file summaries. Files most relevant to your task appear first.

Git-aware ranking — even without --task, CodePulse checks which files you've recently changed (git diff) and boosts those automatically. Files with a longer history of changes rank higher by default.

Auto budget — --auto scales the token budget to your repo's complexity score (symbols × 2 + imports + lines/50). Tiny repos are skipped entirely:

If the budget is too small and files were cut off, CodePulse warns you and suggests the next tier.

Symbol Search

Search exported symbols across your entire indexed codebase:

codepulse search "validateToken"
codepulse search "auth" --limit 10

Returns kind, name, signature, file path, and line number for every match — useful for navigating large repos without opening an editor.

Auto-Update with Git Hooks

Install a post-commit hook so the index updates automatically after every commit:

This appends a single line to .git/hooks/post-commit (or creates the file). It runs codepulse update after each commit — incremental, so it's fast. Remove it any time:

codepulse uninstall-hooks

Supported Languages

JavaScript, TypeScript, Python, Go, Rust, Java, C, C++, C#, Ruby, PHP, Bash, Kotlin, Swift

Claude Code Skill

Copy skill/codepulse/ into your project's .claude/skills/ directory, then use /codepulse in any Claude Code session.

Always-on injection (opt-in): Add to .claude/settings.json:

{
  "hooks": {
    "PreToolUse": [{
      "matcher": ".*",
      "hooks": [{ "type": "command", "command": "codepulse context --format xml" }]
    }]
  }
}

OpenAI Codex CLI

Codex CLI supports an AGENTS.md file for project-level instructions and can read context piped into it via stdin.

Option 1 — Pipe context directly into a prompt:

codepulse context --format markdown | codex "refactor the auth module"

Option 2 — Inject into AGENTS.md at session start:

Add a setup script to your repo (e.g. scripts/codex-init.sh):

#!/usr/bin/env bash
# Regenerate AGENTS.md with a fresh CodePulse snapshot before each Codex session
cat > AGENTS.md << 'HEADER'
# Project Context (auto-generated by CodePulse)
HEADER
codepulse context --format markdown >> AGENTS.md

Run it before starting Codex:

bash scripts/codex-init.sh && codex

Codex will pick up AGENTS.md automatically on startup, giving it instant structural awareness without exploring the repo itself.

Option 3 — Always-on via shell alias:

# Add to ~/.zshrc or ~/.bashrc
alias codex='(codepulse update --full 2>/dev/null; codepulse context --format markdown > /tmp/cp-context.md); codex --context /tmp/cp-context.md'

Note: --context flag availability depends on your Codex CLI version. Check codex --help for the exact flag name.

MCP Server (Cursor, Continue.dev, etc.)

Add to your MCP config:

{
  "codepulse": {
    "command": "codepulse-mcp",
    "args": []
  }
}

Tools available:

• get_context(budget_tokens, focus_path?) — full context snapshot
• search_symbols(query) — find exported symbols by name
• get_file_summary(path) — symbols, imports, and importers for one file

How It Works

1. Index: Tree-Sitter parses all source files, extracting exported symbols, import edges, and a compact per-file summary into a SQLite database (.codepulse/index.db). Git history is scanned to record how often each file changes.
2. Update: On each update, only files changed since the last indexed git commit are re-parsed — a 50k-line repo updates in milliseconds. With install-hooks, this runs automatically after every commit.
3. Context: Given a token budget, a layered generator fills it from most to least important: repo overview → directory map → symbol table → import graph. Files are ranked by task relevance, then change frequency (most-edited files first), so the most useful content always fits within the budget.
4. Smart budget: --auto scales the token budget to your repo's actual complexity — tiny repos are skipped entirely, saving 100% overhead.

The index is stored per-repo (not globally) so each project has its own isolated snapshot.

Packages

License

MIT