The local configuration inspector for coding agents

Know what your agent
actually sees.

Trace every instruction. Find the missing rule.
See why your agents see things differently.

Open source. Local. Yours.

AGENTS.override.md160 of 375 bytes reach CodexFollow the source
One repository.
Every perspective.
Codex
Claude Code
GitHub Copilot
Gemini CLIExperimental
CursorExperimental
OpenCodeExperimental
SightlineExample workspace
/checkout/src/payments/refund.ts
Local scan
Try another client
Instruction sources
AGENTS.override.mdTruncated
Only part of this file reaches Codex.

Every loading decision, traced to its source.Open full inspector

A real scan of the bundled example. Switch clients to see what changes.

You wrote the rule.
Now follow it through.

Configuration has become its own codebase. A file here. An override there. Different names, different scopes, different loading rules.

Sightline reads the chain for you. Pick the file you’re working on and see exactly where an instruction lands.

Take the two-minute tour
Sightline instruction explorer with source loading order and provenance
Inspect a source, read its loaded content, and see why it applies to your target file.Try it in the demo

Beyond the
instruction file.

Explore the guide

MCP, skills, hooks & permissions

Spot missing commands, invalid metadata, duplicate definitions and permission rules that mask one another.

The reason behind every decision

See the file, line, scope and loading rule behind what’s active, conditional, overridden or truncated.

A report you can actually share

Export a self-contained, redacted HTML report. Your teammate can explore it without installing anything.

Fits right into your workflow

Run it in a terminal, open the local inspector, or set a finding threshold in CI. Stable JSON comes included.

It all happens
on your machine.

The scan runs locally. Your files stay put. No account, API key, telemetry or model calls are needed to inspect your configuration.

Environment and header values are redacted before they reach a report.

Different agents.
Different rules. Accounted for.

Each adapter records the official rule sources, verified date and known limits. Experimental support is clearly marked.

ClientRule targetSupport
Codex CLI0.167.2 · binary, source & schemaRuntime + fixtures
Claude Code2.1.322 · binary & official docsNative checks + fixtures
GitHub Copilot CLI1.0.110 · binary & official docsNative settings + fixtures
Gemini CLI0.68.0 context imports & local settingsExperimental
CursorProject rules & local MCPExperimental
OpenCode V2Local config & AGENTS.mdExperimental

Codex configuration values and source files have native API comparisons. Twenty-one scripted requests also verify AGENTS.md bodies, byte limits and selected profile budgets/fallback filenames. Other profile fields use versioned fixtures. Session flags, plugins and remote policies have additional limits. Read the coverage notes ↗

See what’s
really going on.

One command opens your repository in the local inspector. Follow a finding to its source, compare clients, and see which instructions reach your agent.

v0.3.47MIT licenseNode.js 22+
Inspect your repository

Run this from your project folder. The inspector opens in your browser.

npx --yes https://github.com/iamzwxyy/agent-sightline/releases/download/v0.3.47/agent-sightline-0.3.47.tgz ui
Project and user configuration are inspected locally. Press Ctrl+C in the terminal to stop.
Install the CLI for repeated use
npm install -g https://github.com/iamzwxyy/agent-sightline/releases/download/v0.3.47/agent-sightline-0.3.47.tgz

Then run agent-sightline ui in your project, or agent-sightline demo --ui to explore the bundled sample.

Download CLI package Installation guide Node.js 22 or later on macOS, Windows or Linux.

Good questions.

Does Sightline change my configuration?

Scans and the inspector are read-only. You receive source locations and suggestions, then choose how to edit your configuration in your own editor.

Can it inspect a running agent session?

Sightline models a fresh session launched in the target file’s directory. It resolves the local configuration it can inspect. Runtime toggles, extra command-line flags and remote policies can change a particular session.

Do I need my agents installed?

You can inspect configuration without installing its client. The inspector marks missing executables and checks extension commands against your local PATH.

What does “conditional” mean?

Some sources depend on workspace trust, MCP approval or a runtime decision. Sightline keeps those visible and shows what condition must be met. The trust selector lets you model a trusted or untrusted workspace.

Can I use it in CI?

Yes. Run agent-sightline ci --no-user --fail-on warn for repository-only diagnostics with a stable JSON report and an exit code determined by the finding threshold.

Does it start my MCP servers or run hooks?

The default scan checks local definitions and executable discovery. An explicit doctor --probe starts local stdio MCP servers for initialization and tools listing. Hook commands and MCP tools are never invoked by the scan.

Copy this command

Copy the selected command with ⌘C or Ctrl+C. On a phone, press and hold the text and choose Copy.