Every token should
earn its place.

Your coding agent can already read your repository. Fuzit engineers what it sees—turning repositories, PRs and issues into the minimum sufficient context for each task.

npm install -g @fuzit/cli

GitHub

CONTEXT REQUEST

TASK / 01

TASK PROMPT

"Investigate why auth sessions expire after refresh flow"

EVIDENCE ENGINE TRACEEXPLAINABLE DECISIONS

src/auth/session.ts

refreshSession()

Reason: Target symbol definition & token refresh handler.

session.refresh.test.ts

VERIFIED TEST

Reason: Associated unit test verifying token rotation.

src/user/avatar.ts

OMITTED

Reason: Outside task relevance boundary.

BOUNDED CONTEXT BUNDLE READY

3 EVIDENCE ITEMS

Your repository is a system, not a folder.

Code isn't just text lines; it's a web of typed relationships. Fuzit constructs a typed context graph linking routes, symbols, schemas, tests, and configuration.

TYPED RELATIONSHIP GRAPH

5 CONNECTED NODES

ENDPOINT

/auth/refresh

HANDLES

SYMBOL

refreshSession()

CALLS

SERVICE

SessionService

READS

SCHEMA

SessionSchema

VERIFIED BY

TEST

session.refresh.test.ts

Context, with receipts.

Never wonder why an AI agent received or missed a piece of code. Fuzit provides an explicit audit ledger for every selection, omission, and security exclusion decision.

INCLUSION LEDGER: session.refresh.test.ts

SCORE: 0.94

Exact symbol relationshiprefreshSession()

Related test signalVERIFIED TEST

Git commit recencyMODIFIED 2H AGO

Graph path distance1 HOP FROM TASK

OMISSION LEDGER: avatarUpload.ts

OMITTED

Relevance ThresholdSCORE 0.12 < 0.60

Budget constraintEXCEEDED LIMIT

Security PolicyCLEARED (NO SECRETS)

07 / GITHUB & REMOTE REVIEW

The context isn’t all in the code.

A PR is more than its diff. Fuzit binds live local repository structure with explicit remote GitHub signals: PR threads, issues, checks, and commit lineage.

PR · 184: "Refactor Auth Session Token Validation"

EXPLICIT PROVIDER REQUEST

CHANGED FILES

3 modified files, 142 additions, 38 deletions

REVIEW THREADS

2 active threads regarding token TTL refresh

CI STATUSES

Unit tests passed, lint clean, security clear

FUZIT CONTEXT

Bounded PR Review context set ready for agent

PRIVATE REPOSITORY AUTHENTICATION

$ gh auth login

$ fuzit auth status

# ✓ Authenticated with GitHub CLI

$ fuzit review https://github.com/OWNER/PRIVATE_REPO/pull/42

MODEL NEUTRALITY

Your repository intelligence
shouldn’t belong to your AI vendor.

Fuzit sits beneath your tools as open context infrastructure. Use the exact same repository model across your choice of models, agents, and IDEs.

Claude AI

Anthropic

OpenAI Codex

Cursor

VS Code / MCP

DeepMind

Gemini CLI

DeepSeek

Mistral AI

Hugging Face

Perplexity

Groq

Ollama

xAI

ElevenLabs

GitHub

One understanding.
Everywhere you work.

Fuzit is not a collection of disconnected plugins. Five native surfaces consume the exact same local context-engineering engine.

CANONICAL LOCAL ENGINE

SINGLE INDEX & CONTEXT APERTURE

CLI

Direct command line interface for scanning, packing, and task context.

Watcher / Local Daemon

Background filesystem watcher maintaining real-time index freshness.

Read-Only Stdio MCP

Standard MCP server exposing safe context tools to Model Context Protocol clients.

VS Code Extension

Native editor integration built directly on top of the canonical local engine.

Restricted Plugin Host

Out-of-process isolated plugin runtime for custom team rules.

Your repository isn’t the price of admission.

Fuzit operates local-first. Core indexing, analysis, and graph operations remain inside your local machine boundary. Remote access is explicit and attributable.

LOCAL MACHINE BOUNDARY (TRUSTED)NO BACKGROUND TELEMETRY

Local-First Processing

Index, static analysis AST, and graph traversal stay on your local disk.

Secret Redaction

API keys, tokens, and sensitive paths are automatically filtered prior to context output.

Controlled Boundary Crossing

Remote GitHub operations only execute when explicitly invoked by user command.

Under the hood.

A 10-stage deterministic pipeline converts raw repository inputs into explainable, task-bounded context.

INPUT: RAW REPOSITORY & TASK ANCHOR

MULTI-FILE DISTRIBUTED REPOSITORY

Discover

Identify repository roots, workspaces, manifests, config & policy.

Scan

Stream files through ignore rules, sensitive paths & hashing.

Index

Store canonical, content-free records in atomic incremental index.

Analyze

Extract normalized multi-language symbols, imports & exports.

Graph

Construct typed nodes & edges for code & ecosystem relations.

Enrich

Add framework intelligence, Git evidence & lifecycle facts.

Rank

Score & expand task-relevant context with exact relevance.

Explain

Preserve score components, graph paths & audit ledger.

Package

Produce deterministic context in structured formats.

Serve

Expose same services through CLI, Watcher, MCP & VS Code.

OUTPUT: MINIMUM SUFFICIENT CONTEXT

EXPLAINABLE & BUDGET-BOUNDED

12 / ARCHITECTURAL COMPARISON

Extending point-in-time repository packing.

Point-in-time file bundlers are useful for snapshotting. Fuzit extends the workflow into persistent, incremental, and explainable context engineering.

COMPARISON MATRIX

Compare Fuzit vs Repository Packers & Vector Search

Explore Full Matrix