Research, on your terms
Your question.
Your model. Your workflow.
Try a setup here. Take the whole session into your work.
Checking the local research connection…
Run this setup locally
Export your session, then use your local Grainulator installation. Your provider credentials stay on your machine.
First time here? Set up the local build. Use the GitHub release; this version is not published to npm.
grainulator previewOpen the local playground and choose Open session, or continue in your terminal:
grainulator research --session session.json --dir ./research-sessionFrom a source checkout, use node bin/grainulator.js in place of grainulator. Configure OPENAI_API_KEY or OPENROUTER_API_KEY locally, or enter your key in the local playground.
02 / Follow the work
From question to decision.
- Research
- Challenge
- Blind spots
- Claims
- Synthesize
A workflow you can inspect.
Watch each pass arrive. Read the findings, inspect sources, and see how the recommendation develops.
Your session keeps the model settings, context, and completed passes together. You can stop here and continue locally.
The example shows a blocked evidence gate. It makes no API calls.
03 / Take it with you
Keep the work. Keep going.
Export a session to reopen here or resume from the CLI. Export a brief to carry the context into your agent.
node bin/grainulator.js research \
--session session.json --dir ./research-sessionUses your local provider key. Completed passes are reused; editing the question or settings starts a new run.
For an authenticated compatible endpoint, set a local environment variable such as MODEL_API_KEY and add --api-key-env MODEL_API_KEY to the CLI command. Use the variable name, never the key itself. Exported sessions do not carry credentials.