“Just get the happy path working”

Every coding session leaves something behind. There are really only two ways it happens.

The agent notices something. You ask it to fix checkout, and on the way it reads the webhook handler and sees the retry logic swallowing Stripe's 409s. Worth fixing, but not today's job.

You put something off. "Refunds can wait, just get checkout working." "We'll come back to error handling." You've just made a promise to remember, mid-flow, with no plan for keeping it.

Laterbase treats both the same way: the agent pins it, straight away, without asking.

What that looks like

There's no "want me to make a note of that?". The agent calls create_pin, keeps going, and mentions it in a line in its next reply:

Checkout's fixed and the tests pass. I pinned the refunds flow as ACME-43 so it doesn't get lost.

That's it. If you didn't want it, dismiss it. It's much cheaper to throw away a pin you didn't need than to rediscover one you did.

What goes in a pin

The agent already has all the context, so it writes it down while it's fresh:

• What and where. A one-line title, a short summary, and the files involved, down to the lines or the function.
• How it came up. What the agent was doing when it found it, or what you said when you put it off. "Refunds can wait" is useful history.
• Gotchas. The traps waiting for whoever picks it up. These are usually the most valuable part, and the first thing to vanish from memory.
• An approach. How the agent would fix it, and whether you've talked it through together or it's just the agent's suggestion.
• Risk, payoff and size. In words, not numbers: how bad it gets if it bites, how much better things get once it's done, and whether it's a five-minute job or an epic.

Someone picking it up cold, weeks later, in a fresh session, should be able to start without re-exploring anything.

When it's already pinned

Agents tend to find the same problems more than once, especially in shared code. So before creating a pin, Laterbase checks for one that already covers it. If there is one, the agent adds a sighting instead: "hit this again, here's what's new". The backlog gets clearer as it grows instead of filling up with near-duplicates, and a pin that keeps getting hit rises in priority on its own.

The sweep

Agents are good at this but not perfect. Before wrapping up a session, or before a PR, ask for a sweep and the agent goes back over the session for anything that got left behind without a pin.

To set it up, connect your agent from the docs. With the Claude Code plugin, the pinning rules are also repeated with every prompt, so they're in front of the agent at the moment you say "later", not just at the start of the session.