REPL - Human Judgement, Agentic Speed
Sign in

Lead with human judgement, ship at agentic speed

REPL finds the signal across your tools, loops your team in on the decisions that matter, then delegates the busy work to the agents they already use.

01

Your team’s context, already in the room

REPL watches for signal in the ideas, bugs, and discussions across your tools. Four mentions of the same issue converge into one loop.

Slack · #support2dThird “duplicate contacts” complaint this month — same pattern: customers re-import their list and get dupes.
Linear · REL-1482dDetect & merge duplicate contacts. Root cause: CSV import only skips exact name+email matches.
Slack · #product1dThis is hurting onboarding and only gets worse now that import is the default path. Let’s prioritize dedupe.
GitHub · demo#1981dRe-imports will accumulate duplicate contacts until there’s a merge flow — track it.
Suggested loopHigh priority
Detect & merge duplicate contacts

Customers re-importing contact lists end up with duplicates and no way to merge them — the third report this month. Detect likely-duplicate contacts and let the user merge them into one record, keeping the surviving contact’s leads.

Slack · #supportLinear · REL-148Slack · #productGitHub · demo#198
02

Humans make the calls that matter

REPL surfaces key decisions and waits for input before taking the next step. Those answers become the ground truth that steers your team and keeps the work on track.

Open
First cut: match on exact email only, or fuzzy name + company too?
Asked by Claude Code
Fact recorded
Duplicate detection ships exact-email match first, with a confirm-before-merge step — fuzzy matching is deferred.
SKSasha Kimjust now
03

Agents ship the
work you shaped

REPL hands off to the agents you already use, like Claude, Codex, and Cursor. What comes back is exactly what you would have built (you just didn’t have to).

BuildDetect & merge duplicate contactsStep 1 of 4
1Step 1/4Find likely duplicates on exact emailRunning
2Step 2/4Merge UI — pick the surviving recordPending
3Step 3/4Re-point the merged contact’s leadsPending
4Step 4/4Confirm-before-merge guardPending
Review · Changes requestedPending
FixPending
Review · ApprovedPending
Push & PRPR #221 · repldo/demoPending