Skip to content
Memory & Knowledge

Auto-Captured URLs

How Armbrain automatically detects and tags URLs you share in conversation, making links searchable and preventing the "I already gave you that link" frustration.

The Problem

During client work, you share URLs constantly -- Google Drive folders, campaign dashboards, competitor websites, reference articles, shared docs. In a normal conversation, those links are lost the moment the session ends. The next time you need that link, you have to dig through chat history or ask the client again.

Armbrain solves this by automatically detecting URLs in any memory you store and tagging them for easy retrieval.

How It Works

Whenever you store something -- a full memory, a quick note, or just mention it in conversation -- Armbrain scans the content for links. If it finds any, it automatically:

  1. Adds url and shared_resource tags to the memory
  2. Returns the captured URLs in the response so you can confirm they were picked up

This happens silently. You do not need to do anything special -- just mention a link naturally.

"Remember: Acme's brand guidelines are at https://drive.google.com/drive/folders/abc123"

Armbrain stores the memory as usual, detects the URL, and adds the tags. The response includes:

{
  "memory_id": "...",
  "summary": "Acme's brand guidelines are at https://drive.google.com/dri...",
  "urls_captured": 1,
  "urls": ["https://drive.google.com/drive/folders/abc123"]
}

Finding URLs Later

Because URLs are tagged, you can search for them:

"What links have I shared for Acme?"

Or search by what the link was about:

"Where are Acme's brand guidelines?"

Both approaches work. The first uses tag-based filtering. The second uses semantic search -- the memory content around the URL provides the context Armbrain needs to match it.

What Gets Captured

SourceAuto-Captured?
Links in something you rememberYes
Links in a quick noteYes
Links mentioned in meeting transcriptsYes, when the transcript is ingested
Links inside code blocksNo -- skipped to avoid false positives
Localhost / 127.0.0.1 URLsNo -- system URLs are skipped
api.armbrain.io URLsNo -- internal system URLs are skipped
URLs longer than 500 charactersTruncated for display but still stored

Real-World Examples

Sharing a Client Resource

You: "Store this: Acme's Q2 campaign tracker is at
      https://docs.google.com/spreadsheets/d/1abc123/edit"

Armbrain: Stored. 1 URL captured.

Three weeks later:

You: "Where's Acme's campaign tracker?"

Armbrain: "Acme's Q2 campaign tracker is at
https://docs.google.com/spreadsheets/d/1abc123/edit
(stored March 5, tagged: url, shared_resource)"

Multiple URLs in One Memory

You: "Remember: Acme's competitor analysis sources are
      https://www.competitor-a.com and https://www.competitor-b.com/pricing"

Armbrain: Stored. 2 URLs captured.

The response shows the first 5 URLs found. All are tagged on the memory.

URLs During Transcript Ingestion

When you ingest a meeting transcript that contains URLs (e.g., someone shared a screen with a link visible, or said "check out example.com/demo"), those URLs are preserved in the extracted memories and tagged the same way.

What Is NOT Captured

Deduplication

If you already tagged a memory as a link yourself, Armbrain leaves your tag alone -- auto-capture only fills in when there's no link tag yet.

Saved links also benefit from the usual smart dedup: store the same link with very similar context twice and Armbrain updates the existing note instead of creating a duplicate.

Key Details