Deterministic StateWhat deterministic state means, in plain words.Read the thesis →

Give every agent
a shared record to work from.

Hunch keeps decisions, completed work, and commitments with their sources. Start with engineering memory for coding agents, or connect agents to a self-hosted state server.

Get started See how it works
the missing context

AI can read your code. It cannot see the whole story.

It sees files, not why decisions were made, what failed before, or what a small change could break.

Monday

Your team fixes a logout bug.

They keep sign-ins on the server so a stolen key stops working as soon as someone logs out.

Months later

The code stays. The reason gets lost.

The old discussion is hard to find. The safer code now looks more complicated than it needs to be.

Next session

AI sees complex code and “simplifies” it.

The change looks clean, but it brings the same logout bug back.

With Hunch

The original reason reaches the next agent.

With the lesson recorded and the integration active, Hunch can show the decision and the bug it prevents before the edit.

Hunch Memory in 2 minutes. Then go deeper in the 7-episode series: setup, hooks, capture, delivery, rules, drift and teams.
available today

Keep the work connected across sessions.

Hunch keeps structured records in Git. Inspect them in a browser or connect agents through MCP, HTTP, the CLI, TypeScript or Python.

memory

Keep the reasons

Save decisions, rejected approaches, bugs, and open questions alongside the code they explain.

decisions

Make changes explicit

Conflicting current decisions are refused. Replacing a decision leaves a history of what changed.

access

Share with the right agents

Choose which agents can access a partition, then narrow access to individual records when needed. Optional key-bound credentials add request signing.

actions

Track done and still to do

Inspect completed work, open commitments and cited sources in the browser. Unknown or unverified work keeps that status.

control

Choose what becomes a rule

Record sourced user, team and organization conventions. They stay advisory; blocking requires an explicitly trusted rule and strict mode.

git

Keep the record yours

Records are readable files. Git lets you review and revert committed changes; indexes can be rebuilt.

how hunch works

Remember. Retrieve. Check.

Hunch gives the assistant a focused brief and tools to check its work. The assistant still plans and carries out the task.

01 / remember

Save the useful history.

Capture decisions, corrections, and findings. Link them to code and sources so the reason remains findable.

02 / retrieve

Bring back what matters.

Select relevant memory for a task through MCP and supported assistant hooks. Coverage depends on the integration.

03 / check

Check and show the result.

Evaluate supported rules and keep a task report of delivered memory, reported use, and observed checks.

see the evidence

See what reached the agent—and what was checked.

Task reports show the memory delivered, what the agent says it used, and the results of rules and commands that actually ran.

npm i -g @davesheffer/hunch
deliveredthe memory Hunch supplied to this task
reportedwhat the agent says it applied
checkedrule and command results kept as separate evidence

A passing test alone does not prove Hunch caused the result. Missing evidence stays unverified. Read a task report →

inside the coding tools

Understand a change before making it.

Engineering memory connects the reasons behind code to its dependencies and the rules the team chose to protect.

why

Find the reason

Read decisions, rejected ideas, and past failures behind a file or symbol.

blast radius

See what depends on it

Follow indexed code relationships to understand what a change could affect.

project DNA

Learn the conventions

Inspect observed terminology and working habits. These observations stay advisory.

compare

Compare changes

Compare candidate branches against recorded decisions and constraints.

conform

Check recorded intent

Check supported code relationships, such as whether a payment path still calls authorization.

change gate

Protect trusted rules

Flag conflicts with supported rules. Strict mode blocks only where the rule and integration permit it.

Want the technical details? Read how Hunch works →

get started

Start in a repository.

Install Hunch

Install the CLI and run hunch init inside the project you want it to remember.

Add the reasons behind the code

Optionally backfill recent Git history, then review the captured decisions and sources.

Connect and ask

Reload your assistant and ask why a file is built this way. In Codex, trust the hooks through /hooks first.

Claude CodeCursorVS CodeWindsurfCodexAntigravityAGENTS.md
  ~/your-repo
# install from npm — Node 22.13+
$ npm install -g @davesheffer/hunch

# connect Hunch to this project
$ cd your-repo && hunch init

# learn from the last 90 days
$ hunch backfill --since 90d

# see your project's DNA
$ hunch dna inspect

# ask what a file is for
$ hunch why src/auth/session.ts
npm i -g @davesheffer/hunch && hunch init

Hunch gives advice by default. Blocking requires your explicit choice. To update, run hunch update, reconnect the assistant, and review changed Codex commands in /hooks.

Claude Code? Install as a plugin instead:
/plugin marketplace add davesheffer/hunch → /plugin install hunch@hunch
Open VSX

Built for continuity across agents.

The goal: a customer issue becomes a code fix and a verified follow-up. Shared state ships today; the Sofia pilot is testing the complete handoff.

Get started Read the docs