LaterbaseLaterbase
Sign inGet started
MCPWorks with Claude Code, Cursor and other MCP clientsmore

Your coding agents keep finding things that aren't today's job. A flaky test, a retry loop that never gives up, a TODO with teeth. Laterbase gives them one shared place to put it, with enough context that anyone can pick it up next week.

Get started See how it works

The problem

Every session turns up things that aren't the task.

Halfway through a ticket, your agent spots something off next door, or you decide part of the job can wait. Do it now and your small PR isn't small. Mention it in chat and it scrolls away with the session.

  • A TODO comment nobody greps for
  • A note-to-self in Slack buried by lunch
  • "I'll remember" you won't
src/payments/billing.ts
  1. // retry until Stripe takes it
  2. export async function deliver(event) {
  3. for (let attempt = 0; ; attempt++) {
  4. const res = await stripe.send(event);
  5. if (res.ok) return;
  6. await sleep(backoff(attempt));
  7. }
  8. }
  10. for (const id of invoiceIds) {
  11. const lines = await db.lines.find(id);
  12. // TODO(2023): handle partial refunds
  • line 42No exit on 409. Already-processed events retry forever.
  • line 50One query per invoice. Fine at 10, not at 10,000.
  • line 51This TODO is old enough to vote. Refunds are live now.

session ended · 3 notes lost

How it works

Pin it now. Pick it up when it's worth it.

Laterbase is an MCP server your agents already know how to talk to. They file out-of-scope finds and what you put off, notice when it's been found before, and when you ask for something to do, they start with the best payoff for the least work.

01 create_pin

Pin it

The agent writes it down while it still has the context: the files and lines, how it came up, the traps, and how risky, valuable and big the job is.

Webhook retry swallows Stripe 409sfilessrc/payments/webhooks/retry.ts:40-88riskhighpayoffhighscopesmall
02 add_sighting

Spot the repeats

Every new pin is checked against what's already there. Found it again? It becomes a sighting, not a duplicate. Four sightings is the backlog telling you something.

Invoice PDF snapshot test fails on Mondaysseen 4 times this month
03 search_pins

Pick it up

Got a spare afternoon? Ask for something worthwhile. Pins are ranked by priority: payoff over effort, risk, and what each one unblocks. The agent claims it, fixes it and links the PR.

What's worth doing in payments?ACME-42 · webhook retry swallows 409ssmall job · high

What's in a pin

Written for whoever picks it up. Probably not you.

A pin is the handover note you wish people left. Enough that someone with zero context, or a fresh agent, can read it in thirty seconds and decide.

OpenbugpaymentsReproduced

Webhook retry swallows Stripe 409s and loops forever

ACME-42 · acme/api · pinned 2 days ago by Sam's agent · 3 sightings
Should you pick it up?Yes. High payoff for a small job, and it gets worse the longer it sits.high
Risk if lefthigh

Duplicate charges under load.

Payoffhigh

Fewer support tickets, calmer on-call.

Size of jobsmall

An afternoon, tests included.

Where

src/payments/webhooks/retry.ts:40-88deliver()
src/payments/stripe/client.ts:112send()

Watch out

Stripe returns 409 when an event was already processed. Treat it as success, not a failure, or you'll double-apply refunds on the retry.

Done when

  • A 409 ends the loop and is logged once
  • Retries stop after 5 attempts with a dead-letter entry
  • A test covers both
  1. A straight answer first

    Should you pick it up? The verdict weighs risk, payoff, size of job and what it unblocks so you don't have to.

  2. Exactly where

    Repo-relative files, line ranges and symbols, pinned at a commit. No vague “somewhere in billing”.

  3. The rakes in the grass

    Gotchas the finder learned the hard way, so the fixer doesn't step on the same ones.

  4. A finish line

    What “done” looks like, written down before anyone starts. Agents love a checklist.

The small print, but good

Built for agents first. Pleasant for people too.

Knows what's lurking

When an agent starts a task it calls pins_near and hears what's already known about that corner of the code.

One backlog per team

Everyone's agents pin into the same workspace, so the thing your teammate's agent found yesterday is already there today.

Words, not made-up numbers

Agents rate risk, payoff and scope as low, medium or high. Leverage is worked out for them, never guessed.

Search that gets the gist

Ask in plain English. Meaning and keywords are both matched, so “slow checkout” finds the N+1 in cart totals.

Areas, not folders

Pins are grouped by what they affect, like payments or search, not by where the file happens to live this week.

Sign in, or bring a key

Claude.ai and Claude Code sign in with your account. Other agents take an API key, stored hashed and revocable in a click. Each connection knows which workspace it's in.

The Claude Code plugin

Your backlog, one slash away.

Install the plugin and Claude Code signs in to Laterbase and picks up 10 skills. Ask for a quick win and it finds the pin, fixes it and opens the PR. Wrap up a session and it pins what you left behind.

claude · ~/acme/apiplugin ✓ signed in
>/laterbase:quick
⏺search_pinsmax_scope small · sort leverage
●ACME-38 looks best: cart totals run one query per line item. Small, high payoff.
⏺set_statusACME-38 → claimed
●Batched the lookups into a single query. 48 tests passing.
⏺update_pinfixed_in acme/api#214
✓PR #214 is up and linked. It resolves when it merges.

Plus /laterbase:triage, /laterbase:epic, /laterbase:random and /laterbase:roulette.Every skill, step by step

Connect an agent

Two minutes to your first pin.

  1. Make a workspace

    Sign in and make a workspace. Many agents sign in when you connect them; the rest take an API key.

  2. Add the server

    Run or paste the snippet for your agent. It's a remote server, so there's nothing to host.

  3. Get on with your day

    Your agent pins what's out of scope and what you put off, as it goes.

claude plugin marketplace add --scope user \
  https://laterbase.dev/claude-code/marketplace.json
claude plugin install --scope user laterbase@laterbase
Run it in your terminal. It brings the server and skills like /laterbase:quick and /laterbase:recommend. In Claude Code, open /plugin, pick the server and press Enter, then sign in and allow it.
get_contextsearch_pinspins_nearget_pincreate_pinadd_sightingupdate_pinset_statusupdate_area

Ten tools, each described for the agent that reads it. You don't have to learn any of them.

Works with the agents you already use

The dashboard

And a dashboard, for the humans.

See what's piling up, which areas are getting worse, and what's worth an afternoon. Claim a pin, hand it to an agent with one copied prompt, close it with the PR. It's optional. Most days your agents do the talking.

Open the dashboard

Questions

Fair questions.

Which agents does it work with?

Anything that speaks MCP over HTTP. Claude.ai, Claude Code, Cursor, VS Code, Codex and Copilot CLI sign in with your account; Antigravity, Windsurf and the rest connect with an API key. See every client's setup.

Won't my agent pin every little thing?

Agents pin only real work: what's out of scope and what you put off. Every new pin is checked for duplicates before it's saved. Repeats become sightings, so noise turns into signal instead of clutter.

If an agent gets overexcited anyway, dismissing a pin takes one click.

What happens to my code?

It stays where it is. We never clone or scan your repository; we store what your agent writes into a pin: titles, summaries, file paths and any snippets it chooses to include. Pin text goes to OpenAI to make it searchable and to spot duplicates, and is never used to train models. If you install the GitHub app, it shares pull request and commit details so pins can follow the work. The privacy policy has the details.

Is this another issue tracker?

No, it's the step before one. Most pins aren't worth a ticket yet, and some never will be. When one is, link the issue and carry on. Laterbase is happy being the place things wait.

Does it work across repos and teams?

Yes. A workspace can span as many repos as you like, and you can belong to several workspaces. One connection works in all of them: each call picks its workspace from the repo the agent is in.

Stick it on the laterbase.

Every session leaves something for later. Give it somewhere to go.

Get started Connect an agent