LaterbaseLaterbase
Sign inGet started

Connect

AGENTS.md

Laterbase tells agents when to use it as they connect, but not every client passes that on. Add this section to the instructions your repo already gives its agents, and every agent that works there pins what gets left for later and checks for known issues before it starts, whichever client each teammate uses. It's optional.

The section

Markdown
## Laterbase

Laterbase is your team's shared backlog of out-of-scope and deferred work from coding sessions. Its tools come from the `laterbase` MCP server; if they aren't available, tell the user they can connect it: https://laterbase.dev/docs/connect

- When work gets left for later, because you notice something out of scope worth doing or the user puts something off ("let's do that later"), pin it with `create_pin` straight away, without asking, and mention it in your next reply. Never leave it as a note in chat.
- When you start a task, call `pins_near` on the files it involves to see known issues there.
- When asked what to work on, use `search_pins`: by default it lists open pins by priority.
- Before starting a pin, read it in full with `get_pin` and claim it; link your PR to it as fixed_in as soon as the PR is open, and resolve the pin once the PR merges.
- If you stop partway, release it with a note saying where you left off.
- When you mention a pin to a person, link its key to the pin's `url`, e.g. [ACME-42](url).

Adding it to a repo

Most repos already have a file of instructions for their agents, usually AGENTS.md or CLAUDE.md at the root. Copy the section to the end of it and commit, leaving the rest as it is. If your team's agents read different files, check which one each reads below.

Or have your agent do it:

Add the Laterbase section at https://laterbase.dev/agents.md to the instructions file this repo's agents read, or to a new AGENTS.md if there isn't one.

If the repo has no instructions yet, download the section as its AGENTS.md and commit it at the root.

Download AGENTS.md

What each client reads

Most clients read AGENTS.md. A few read only their own file, or just the first of several they find, so check the ones your team uses. Claude.ai and ChatGPT don't work in a repo, and get the server's instructions instead.

ClientReads
Claude CodeCLAUDE.md, and AGENTS.md only when the repo has no CLAUDE.md. If it has both, put the section in AGENTS.md and add a line with @AGENTS.md to CLAUDE.md, or paste the section into CLAUDE.md.
CursorAGENTS.md alongside its own .cursor/rules.
VS CodeAGENTS.md, CLAUDE.md and .github/copilot-instructions.md, all of them together.
CodexAGENTS.md, or AGENTS.override.md in its place. Other names only when project_doc_fallback_filenames in its config lists them.
GitHub CopilotAGENTS.md, CLAUDE.md, GEMINI.md and .github/copilot-instructions.md, all of them together.
AntigravityAGENTS.md or GEMINI.md, alongside its own .agents/rules.
JetBrains.junie/AGENTS.md in Junie, or else AGENTS.md, or else the older .junie/guidelines.md. AI Assistant's chat reads only its own .aiassistant/rules.
WindsurfAGENTS.md alongside its own .windsurf/rules.
ClineAGENTS.md alongside its own .clinerules.
Zed.rules, .cursorrules, .windsurfrules, .clinerules, .github/copilot-instructions.md, AGENT.md, AGENTS.md, CLAUDE.md or GEMINI.md, but only the first it finds, so the section goes in that one.
AmpAGENTS.md, or CLAUDE.md where a folder has no AGENTS.md.
opencodeAGENTS.md, or CLAUDE.md when there's no AGENTS.md.
KiroAGENTS.md alongside its own .kiro/steering.
GooseAGENTS.md and .goosehints.
Gemini CLIGEMINI.md, and AGENTS.md once its settings name it: { "context": { "fileName": ["AGENTS.md", "GEMINI.md"] } }.
Other clientsAGENTS.md in most cases, or a file of its own; its docs say which.

The Claude Code plugin already repeats these rules with every prompt, so a team that all uses it doesn't need the section.