Slovey
Sign inGitHub

Memory for coding agents

Your agents forget.Slovey remembers.

Slovey learns your team’s decisions from GitHub and stops any change that breaks one, with the PR it came from.

Start free

Every decision

Nothing your team
decided gets lost.

Slovey reads every pull request, review and incident, and keeps the calls that last.

What it keeps

Everything your team
already decided.

Pull requests, code and commits being pulled into a laptop's memory

Pull requests, reviews, commits and incidents go in. What comes out is a memory your agents can ask.

Where it learns

Learned from
your own history.

PR #418

Every merged PR becomes a decision, with its reason attached.

Pull requests

Change blocked
INC-2207

A postmortem becomes the reason a rule exists.

Incidents

Bug caught
Review on #455

When a reviewer says no, the rule gets sharper.

Reviews

All of it

One question
away.

The product

Watch it stop a change.

Projects / Payments / billing-service
~/billing-service agent/retry-charges $ slovey preflight
Checking 6 changed files against 214 decisions
Blockedsrc/charges/retry.ts:22
- maxRetries: 3+ maxRetries: 8
Breaks decision “Charge retries stay capped at 3”
From PR #418, after incident INC-2207 double-charged customers
Keep the cap at 3 and add backoff, or reopen the decision on #418.
5 files clear   1 blocked, nothing committed

Before the commit

Preflight stops the change on the machine that made it.

Under every agent

One memory.
Wherever code gets written.

$ slovey preflight
6 files, 214 decisions
Blocked retry.ts:22 breaks #418
5 files clear
Preflight

Stops it before the commit

Runs on your machine and blocks a change that breaks a decision.

Retry failed charges more aggressively
1 conflict Slovey decisions
Passed Tests, lint, build
GitHub App

Reviews every pull request

Cites the decision and the PR behind it, right in the review.

Why do charge retries stop at 3?
Because of INC-2207: retries ran 8 times during a processor timeout and some cards were charged twice. PR #418 capped them at 3.
PR #418INC-2207Decision: retries stay at 3
Ask

Answers why it was built this way

Every claim links to the PR, review or postmortem it came from.

Claude Codeasks before writing
slovey.decisions("charge retries")
returns #418, retries stay at 3
MCP server

Your agents ask first

Claude Code, Cursor and any MCP client check Slovey before they write.

gumballchief/slovey
MITTypeScriptSelf-host
npm i -g slovey
Open source

Yours to run

MIT licensed. Self-host it, or let us run it.

Pricing

Free for one engineer.
Per seat after that.

Starter

For one engineer

$0forever
  • 1 repository
  • Pre-commit review
  • Basic decision graph
  • Community support
Start free

Team

For teams shipping with AI every day

$19per user / month
  • Unlimited repositories
  • Full decision graph
  • Company rule enforcement
  • MCP server and API access
  • Slack, Notion, Jira, GitHub
Get Team plan

Enterprise

For orgs with strict requirements

Custom
  • Self-hosted or VPC
  • Audit logs
  • SSO and SCIM on request
  • Custom integrations
  • A dedicated engineer
Contact sales

Questions

Asked and answered.

No. Slovey sits under them. Your agents keep writing code the way they do today, and Slovey checks each change against your team's decisions before it is committed or merged.

Stay ahead of your agents

Give your agents
a memory.

Start free

One repository free, forever. Or install the CLI: npm i -g slovey

Memory for coding agents.
Open source under MIT.
Start free
Every decision,
on the record.