Capture: save what an AI session used

A coding session with an AI tool reads a lot of web pages. A few of them solve the problem. When the session closes they are gone, and next month you or a teammate searches for the same answer again. A capture saves those few pages to tagit, with a note on what was learned.

This guide covers running a capture, choosing the tags, and what it will and will not save. You need Claude Code connected to tagit first. That takes one key and one command: see AI tools.

Run a capture

There are three ways to start one. They all do the same thing.

Say yes when Claude offers. After work that leaned on web pages, Claude asks once, in one line, whether to save the useful ones to tagit. Answer yes.

Ask in your own words.

• "Save what we used to tagit."
• "Capture this session to tagit."

Type the command.

/mcp__tagit__capture_session

A capture never starts on its own. Claude may offer, but nothing is saved until you ask or agree.

Choose the tags

Before anything is saved, Claude shows you what it picked:

1. HNSW indexes (supabase.com)            pgvector, supabase
2. IVFFlat indexes (supabase.com)         pgvector, supabase
3. Going to production (supabase.com)     pgvector, performance

The tags are suggestions. Claude looks at the tags already in your library and reuses them where they fit, so you do not end up with both vector and vectors.

Now it waits for you. Answer in plain words:

• "ok" saves the list as shown.
• "Tag the last one checklist, not performance."
• "Add postgres to all of them."
• "Drop the second one."
• "Use only these tags: database, search."

Tags you name are used exactly as you wrote them.

What gets saved

The pages, eight at most. Each one is a normal save: it gets a summary, a preview image and an archived copy of its text, and it shows up in your library with the tags you chose.

One note that ties them together. The title says what was done, in words someone would search for. The text says what was learned or decided, then lists the pages under "Sources" with a line on why each one mattered. The note carries the tags the pages share.

The note is the part that pays off later. Search finds it by meaning, so "how did we set up the vector index" leads to the decision and from there to the pages behind it. See Notes.

What gets left out

A page qualifies if it changed what was done or settled a question. Search result pages and pages that were opened and set aside are skipped. If nothing in the session is worth keeping, Claude says so and saves nothing.

Some things are never saved through an AI tool, whatever it is asked:

• Pages on localhost or an internal host. Nobody else could open them.
• Addresses that carry a token or a key. The address itself is the secret.

Claude is also told to keep secrets, credentials and customer data out of the note. You see the list before it is saved, so a page you would not want in the library is one "drop it" away. The note is written after you confirm, so read it once in tagit when the session touched anything sensitive.

With a team

A capture goes to the workspace the key covers. With a key for a team workspace, the pages and the note land in the team's library, where your teammates and their AI tools can find them.

That is the point of it: the answer one person found is there for the next person who asks. It also means a capture is something you share, so look at the list before you say ok. See Team workspaces.

Fewer approval prompts

By default Claude Code asks you to approve each save, which is up to nine prompts for one capture. To approve tagit's two save tools once, add this to .claude/settings.local.json in a project, or to ~/.claude/settings.json for every project:

{ "permissions": { "allow": ["mcp__tagit__save_page", "mcp__tagit__save_note"] } }

You still get the list and the tags to confirm first. This only removes the prompt on each save after that.

If something does not work

• The command is not listed. Start a new Claude Code session. A session that was open before tagit was connected, or before the command existed, does not have it.
• Claude never offers. It offers once, and only after work that used web pages. You can always ask or type the command.
• Claude saved without showing the list. Tell it: "show me the pages and tags before saving". It is meant to ask every time.
• "tagit does not save this URL". The page is on localhost or an internal host, or the address carries a token or key. Save it yourself with the extension if you need it.
• "Rate limit reached". A key can make 10 saves a minute. One capture fits inside that. Two in the same minute do not, so wait a moment.
• A saved page has no text. tagit could not fetch it from its servers, usually because of a login or a bot wall. Save it with the browser extension, which captures the page as you see it.

Limits

Captures are part of connecting AI tools, which is included in Premium and Team.

A capture saves at most eight pages and one note. It works in Claude Code and other MCP clients that support prompts. In a client without them, asking in your own words still works.

An AI tool can add to your library. It cannot edit or delete, so undoing a capture means moving the pages to the bin yourself.