Changelog — Hunch

Jul 16, 2026

v1.8.3Reviewer-qualified experiments and a clearer market boundary — independent EXP-03 reviews now begin with a plain-language comprehension check, present clearer choices, and keep target authors out of their own timed reviews while preserving the 48-hour separation safeguard. Hunch also ships a dated competitive landscape and a repeatable npm run research:competitors watch command; public positioning stays category-level and grounded in verifiable properties.

Jul 15, 2026

v1.8.2A shorter path from install to useful memory — the README is now a focused five-minute introduction instead of a full reference manual. The documentation leads with three clear paths — set up a repo, use Hunch day to day, or diagnose a problem — and the cookbook now includes a complete local/self-hosted model recipe with explicit safeguards for metered providers.

Jul 13, 2026

v1.8.1Python support — deep code-structure parsing now covers Python alongside TypeScript and JavaScript: symbols (functions, classes, decorated methods), call edges, and import/from … import resolution into component dependency edges, so hunch backfill, blast radius, and structure queries work on Python repos. Built on a new LanguageSpec registry that collapses the extractor's language gates into one entry point — adding a language is now a registry entry plus a tree-sitter grammar. Contributed by MrSampson, who also fixed the commit synthesizer: a squash-merge whose subject says "Merge …" but whose body carries the real PR description is no longer thrown away as noise (and a latent chore(deps) regex bug is gone). The "why" layer — decisions, bugs, rules — was always language-agnostic; now the structure layer starts catching up.

v1.8.0Memory that runs itself — the review queue is gone: every captured decision enters the graph as live advisory memory the moment it lands (auto-trust), and nothing gains blocking power until a human explicitly vouches. The rare decision only you can make is asked inline — hunch escalations lists topic conflicts, candidate rules awaiting review, and proposed rules ready to activate, each as a question with its resolution verb; normally empty. The new VS Code Hunch Memory panel is a source-control view of memory itself: a timeline of every move (capture · adopt · supersede · prune · repair) with click-to-diff and local revert, a Constitution section with one-click audited authority transitions (activate / demote / withdraw / retire), a strictness switch, and approve-to-push — memory auto-commits locally; publishing it is deliberately your click. Renames now self-repair the graph: decision bindings, tripwire and constraint scopes, and policy selectors heal automatically from git's own rename detection (exact matches only, zero guessing), landing as revertable timeline moves; a repaired policy asks once for a fresh proof. The VS Code surface is conformance-certified: its real spawn seam returns byte-identical policy receipts to the CLI, MCP, and CI in an executable fixture.

Jul 10, 2026

v1.7.0Subscription choice without vendor lock-in — Hunch now understands the coding-assistant CLIs available on your machine. Select Claude Code, Codex, or Cursor once with hunch provider <name>; an environment override still wins for a shell or CI run. If several subscriptions are installed and no choice has been made, Hunch deliberately stays on its free deterministic path instead of guessing whose plan to bill. The same policy now governs capture, verification, auto-review, and wiki prose, while Deep Synthesis remains an explicit multi-provider action.

Jul 8, 2026

v1.4.0The verification pipeline — delivery enforced, not hoped for — measured on real zod bugs: instruction skills installed as files were read in 0/20 sessions, and pass rates matched no-skill exactly; guaranteed delivery of the same content flipped hard-bug diagnosis FAIL→PASS on every discriminating cell (Opus and Haiku — Haiku+skill solved what bare Opus couldn't). So the operating loop — scope → evidence → change → verify → attack → report — now ships in the hooks: PostToolUse records observable facts (product edits, verify-shaped commands), Stop refuses to end a turn with unverified product edits (firm/strict only, max twice per turn — a broken gate degrades to advisory, never a lockout), SessionStart injects the loop once. Facts, not claims. No new knob — firmness governs; HUNCH_PIPELINE=0 kills. Plus a cookbook of copy-paste recipes, incl. how to write skill descriptions that actually fire.

Jul 5, 2026

v1.3.1A friendlier first hello — the README now leads with what you gain (a repo that remembers why, sessions consistent with your decisions) and says the quiet part out loud: advisory by default — nothing blocks until you say so. Same guarantees, receipts over threats.

v1.3.0Retrieval that follows the graph, not just the keywords — results now rank by what the graph knows: live decisions outrank superseded ones, human-vouched records outrank drafts, recent work outranks history — and when your query only matches a superseded decision, the topic's current decision surfaces right above it. Measured on a committed golden set: Recall@10 90→100%, MRR +14% — and that eval now gates every future retrieval change. No model in the ranking path.

v1.3.0The wiki knows what's happening — and what's next — hunch now and the wiki's now.md show recent decisions and the roadmap: record intent as a proposed decision and it appears; ship it and it leaves by itself. Renaming a component re-renders every page that links to it; --prose-heal drafts a reconciled overview on adopted docs (the deterministic corrections stay authoritative); and assistants get it all over MCP via hunch_now and hunch_wiki_status.

v1.3.0A quieter, sharper agent loop — identical pre-edit grounding no longer repeats: the full context arrives once per session, a one-line delta after (≈100× smaller on repeats), and sessions open with a graph orientation (recent + roadmap). Every blocking invariant is now content-matched — the strict gate denies the edit that actually breaks the rule, not every edit near it. Auto-drafts that duplicate a decision you already recorded are skipped before the LLM is even called, and hunch review --reject-duplicates sweeps any that slip through. hunch_context answers task phrases too, falling back to the closest graph matches instead of coming back empty.

Jul 4, 2026

v1.2.2The wiki takes over your docs — drift-gated, never rewriting them — hunch wiki renders a component wiki from the graph, and a specs ledger grades every repo markdown deterministically: ✅ grounded, ⚠ stale, ◻ unverified. A stale doc is adopted — a wiki-managed copy healed against the graph, every superseded pin re-pinned to the current decision with the correction inline — while your original is preserved untouched and the copy retires the moment you heal it. Freshness is drift, not a schedule: hunch drift names the stale pages, hunch wiki --heal regenerates only those, --check gates CI, and --private renders the full graph into the overlay repo — nothing private ever lands in the committed wiki.

v1.2.2Honest plumbing — capture replies report what the auto-commit actually did (a safety-backstop skip is no longer claimed as committed; a failed overlay push says so with a retry hint) · Node < 22.13 gets a friendly upgrade message instead of a raw ERR_UNKNOWN_BUILTIN_MODULE crash — and the edit-hook stays silent-exit-0, so an old Node never blocks an edit · reindexing preserves component enrichment (curation, raised fragility) and is byte-identical when nothing changed — no more timestamp churn in committed .hunch/ · releases publish from CI on a version-tag push, with npm provenance.

Jul 2, 2026

v1.2hunch structure — your agent greps; a grounded agent asks — agents burn grep/glob rounds every session rediscovering structure the graph already holds. One call now serves it: the repo map, a directory’s files and symbols, a file’s outline with who-calls-what, or a symbol’s exact definition site with its callers — so the agent knows exactly which file to read, first try. Deterministic, no LLM, straight from the index.

v1.1.1Claude Code plugin + the repo demos itself — install with /plugin marketplace add davesheffer/hunch → /plugin install hunch@hunch: the hunch_* tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile. And the repo now ships a curated slice of its own graph — clone it and hunch why answers on day one. Plus: runbook --find sees runbooks written out-of-band.

v1.1AGENTS.md as a drift surface — memory that gates, not just recalls — Anchor a section of AGENTS.md / CLAUDE.md / any repo markdown to a decision topic: your assistant is grounded with the current decision (and what it rejected) whenever it edits the file, and CI can fail when prose still describes a superseded one. hunch heal shows exactly what to reconcile — and never rewrites your prose.

v1.1hunch impact + hunch path — See what a change actually reaches before review — the dependent files, the invariants, the decisions concerned — and walk the shortest dependency chain between any two points in the codebase. Read-only, instant, no LLM.

Jul 2, 2026

v1.01.0 — zero native dependencies for the index — No install-time native builds, no node-gyp failures, no file-lock errors on Windows upgrades. Install is npm and nothing else. Requires Node ≥ 22.13.

Jul 2, 2026

v0.40One source of truth for memory — Every capture lands in exactly one home — shared cleanly across branches, worktrees, teammates, and agents. A fresh clone connects itself to the team's store, and hunch doctor tells the truth about where memory lives instead of silently reading empty.

v0.40Auto-commit on by default — Captures are committed to their store without being asked. Hunch never pushes or merges your code branch. Opt out per repo with --no-auto-commit.

v0.40Security — team discovery hardened — Opening an untrusted clone can never turn into code execution: the team-store pointer is validated before anything acts on it.

Jul 1, 2026

v0.39Decision-grounding — the doc≠graph spoke — The complement to Architectural Conformance: one spoke holds the code to recorded intent, this one holds the docs to the graph. The graph now resolves which decision is current for a topic — and which were superseded or rejected. Backward-compatible; existing graphs load unchanged.

v0.39Read-time grounding + drift gate — Assistants see the current decision — follow the graph, not a stale doc — before editing, and a file still anchored to a superseded decision is caught deterministically. CI-gateable via hunch drift.

v0.39One live decision per topic — by construction — The graph refuses to hold two live decisions on one topic; /capture interviews a decision to a resolved state — rationale and rejected alternatives included — before it is written; and the one case a git merge can break is caught for human resolution.

v0.39hunch heal + /capture and /heal — Read-only doc↔graph reconciliation, scaffolded as slash commands. It shows where prose and graph disagree; it never rewrites your prose silently.

Jun 27, 2026

v0.38.3Overlay auto-commit safety — Memory sync can never touch your code repo — hardened so the worst case is a skipped sync, never a surprise commit. If you use auto-commit, upgrade.

v0.38Architectural Conformance for AI code — Record the semantic architectural rules a linter can't express — layering, must-reach, dependency direction — and Hunch deterministically blocks any AI change that breaks them, citing the decision behind the rule and the bug it prevents reopening. No model in the gate.

v0.37Enforcement at a glance + grounding everywhere — hunch status shows what's armed, what's waiting on your confirmation, and what went stale — one screen. A rule taught once is held by every assistant, not just the one you taught it to.

v0.36Sharper rule matching — Forbidden-dependency rules now match what the code actually imports — a comment or string can't false-positive — and stay accurate for the file's whole life. Corrections auto-derive the right rule.

Jun 26, 2026

v0.35Content-matched constraints + symlink-safe hooks — Blocking rules fire on the actual violation and stay quiet on harmless edits in the same file. Plus reliable hook delivery on symlinked setups.

v0.34One memory across branches & worktrees — Edit memory anywhere in the repo; it's the same source of truth everywhere. No manual sync.

v0.32–0.33Seamless multi-branch / worktree memory — Linked worktrees and concurrent branches share one memory automatically.

Jun 25, 2026

v0.31Google Antigravity support — One graph now serves Google's agent IDE too — detected and wired automatically, only when installed.

v0.30Intent-conformance — The inversion: not "did this diff touch a guarded file?" but "does the code still satisfy the recorded design?" — silent drift is caught with no diff in scope.

v0.29Inline intent capture — Mark intent where it lives: a hunch-why: comment becomes a decision, a hunch-rule: comment becomes an enforced file rule.

v0.28hunch compare — multi-candidate verdict — Give it N candidate branches (several agent solutions to one task) and it ranks them by architectural fit. The "evaluate 5 solutions in 10 minutes" check.

v0.25–0.27Runbook memory — The how layer beside the why: reusable procedures distilled from real work, returned when the task recurs. Plus self-healing grounding that keeps every assistant's docs fresh.

v0.24Memory drift checks — hunch doctor flags memory that fell out of sync with the code — a smoke detector for stale memory.

v0.23Retrieval eval harness — Retrieval quality is a measured number in CI, not a claim.

v0.22Graph-augmented retrieval — Uses your code's own connections to surface the cross-file evidence plain search misses. Measured +41.7pt recall@10.

Jun 23, 2026

v0.18Deep Synthesis — Several independent readings of a change, reconciled into one more-trustworthy note. Advisory until you confirm it.

v0.17Private memory overlay — Open-source your code without open-sourcing your reasoning: sensitive records live in a separate private repo, visible to your local queries only — public outputs can never leak them. One command to set up.

v0.16Redundancy Guard — "this already exists" — A diff that re-implements something already defined elsewhere is flagged with the original's location. Advisory, tuned quiet.

Jun 21, 2026

v0.15Veto — the Decision Guard — Re-introducing an approach you rejected — the alternative that never existed in code — is caught with a receipt: what you rejected, what you chose instead. Also: relicensed Apache-2.0.

Jun 20, 2026

v0.14Causal Merge Verdict — One cited verdict per diff — BLOCK / WARN / PASS — showing the decision and the bug behind each rule, so a change that re-opens a closed bug is caught with its why.

v0.13Never Twice — corrections become enforced invariants — Correct the agent once and the rule is held against every assistant, in every future session.

Jun 18, 2026

v0.12CI Constraint Guard — A GitHub Action that comments what a PR touches and fails the check on a confirmed blocking rule. Memory that blocks a merge, not just advises.

v0.11On npm + safe strict mode — npm i -g @davesheffer/hunch. Strict mode is safe to enable on a shared repo — it only fails on what you've confirmed.

Jun 17, 2026

v0.10Windsurf support — Five assistants wired to one graph. Also: 24× faster indexing.

v0.9Time-Travel Memory + Regression Guard — Query the graph as of any commit; history is closed, never deleted. And re-introducing deliberately-retired code gets blocked.

Jun 16, 2026

v0.8Agent hooks + firmness — Memory injected before every edit; four enforcement levels, tunable at runtime.

v0.7Multi-CLI synthesis — Codex & Cursor join Claude — learning bills to whichever coding subscription you have.

v0.6Multi-assistant — Cursor, VS Code (Copilot), Codex & AGENTS.md wired to one graph.

v0.5Guardrails everywhere — Pre-commit guard, blast-radius tooling, and VS Code near-violations.

Jun 15, 2026

v0.4Blast-radius near-violations — hunch check flags rules you can break indirectly, through dependencies.

v0.3Drift repair — Stale records re-verify against the code in one command.

v0.2Failure-learning loop — Failing tests become bugs with suspects; recurring bugs are promoted into enforced rules.

Jun 14, 2026

v0.1Initial release — A git-native decision/bug/constraint graph, an MCP server, post-commit learning, auto-maintained grounding, and a VS Code extension.

Every release, since v0.1.