A perception layer for Claude Code — three signals that surface code context to the AI agent during tool execution.
staleness: Detects when code has changed externally since the agent last read a file, flagging stale assumptions.
diagnostics: Surfaces build errors, linter warnings, and test failures from configured checkers, making problems visible without explicit queries.
blast_radius: Estimates impact of edits by counting how many functions call the edited symbol, alerting on high-impact changes.
The plugin is distributed with Claude Code. To use it, add an intelaisense hook definition to your project's Claude settings.
Control signals via .intelaisense/config.json:
# Show signal status
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cli.py" status
# Toggle signals on or off
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cli.py" enable staleness
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cli.py" disable diagnosticsTo enable diagnostics, configure checkers by file extension in .intelaisense/config.json:
{
"signals": {"diagnostics": true},
"diagnostics": {
"by_extension": {
".py": "ruff check --output-format=concise {file}",
".ts": "tsc --noEmit {file}"
}
}
}The plugin registers PreToolUse and PostToolUse hooks. Both invoke a single
dispatcher (scripts/dispatch.py), which runs the enabled signals whose declared
interests match the current event, formats their findings under a character budget,
and emits them to the agent via additionalContext. For example: a Read records
the file's hash (staleness); a following Edit checks it before the edit lands and
warns if the file changed; a Write/Edit triggers the configured checker
(diagnostics). The dispatcher always exits 0 — any failure is logged to
.intelaisense/log and swallowed, so the hook can never block a tool call.
- Python 3.8+ (standard library only — no third-party runtime dependencies).
greponPATHfor theblast_radiussignal (it degrades to silence if absent).
See the detailed specification at docs/superpowers/specs/2026-06-26-intelaisense-design.md.