Grainulator

Grainulator

Evidence and verification for the model you already use.

Keep the evidence. Challenge the answer. Know what to do next. A shared workflow for research, engineering, and model-assisted work.

Quick start · Installation · Upgrading · Tools · Agent setup · Changelog

---

What it adds

Good models still need a way to keep track of evidence, revisit assumptions, and verify their work. Grainulator gives them that process, with a local ledger that stays with the task as it moves between models and sessions.

Capability	What it gives you
Evidence that stays with the work	Typed claims, sources, evidence tiers, and provenance that survive edits and exports.
A check on the answer	Conflict detection, weak-support signals, and explicit gaps to investigate.
Clear next actions	Two lists: what the agent can continue automatically, and what needs your input.
Sessions you can carry forward	Configurable research, stop/resume, reusable context, and credential-free exports.
Verification for your task	A managed command loop that can use a verifier you provide.

Grainulator works with Claude Code and Codex through plugins. It also provides a command-line tool and an MCP connection for other agents. You do not need to install its components separately.

Quick start

Requires Node.js 24+. Node 25 is the development default.

Upgrading from 1.x? Follow the migration checklist to update the plugin and keep your existing research data.

git clone --branch v2.0.4 https://github.com/grainulation/grainulator.git
cd grainulator
npm ci --ignore-scripts
node bin/grainulator.js doctor

To use Grainulator inside your agent, follow the Claude Code or Codex setup guide. The website shows a saved example of an evidence check. It does not send your question to a model.

The local research playground remains available through node bin/grainulator.js preview. It runs models using a provider account you configure locally.

Distribution: v2.0.4 is a GitHub release, not an npm registry release. For a separate local installation, follow the archive installation guide.

Other agents: connect through MCP

From the project you want Grainulator to access:

node /path/to/grainulator/bin/grainulator.js connect --dir "$PWD"

Add the printed MCP configuration to your agent, then restart the connection. This command only prints the settings; it does not install the plugin.

For the full Claude Code or Codex plugin, use the agent setup guide. Codex needs a project folder; the guide shows how to set it. CLI and direct MCP access remain available to other hosts.

Put it to work

With Grainulator connected, give your agent the outcome you need:

Use Grainulator to investigate whether we should migrate this service. Record the evidence, challenge the assumptions, implement the agreed changes, and verify them. Keep the remaining next steps split into Auto and Manual.

The work follows a simple cycle: