Skip to content

List · reads url

Bookmarks / URLs

Saved links.

One row per item, the plainest possible view.

Every entry says why. Without that column this is a folder nobody reopens.
  • coffee-standards.org/roastRoast profile terminology, use in the glossary
  • packnord.fr/volumePrice breaks at 500 — the wholesale maths
  • atelier-lm.comTheir service page structure is better than ours
  • legifrance.gouv/…/allergenesThe actual rule on menu labelling

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

The reason it was kept, which is what stops a bookmark becoming noise within three weeks.

Private and unlimited, unlike the public link list.

Findable by reason as well as by title, which is how people actually remember a link.

How it works

  1. 1

    A link is saved with the reason it mattered at the time.

  2. 2

    Search covers the reason as well as the title, which is how people actually remember a link.

  3. 3

    Private and unbounded, unlike the public link list.

  4. 4

    A bookmark whose reason no longer applies is easy to spot and delete.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
LinkrequiredtextThe address, kept as it was found.
Why keptrequiredtextThe reason. Required — without it a bookmark is noise within three weeks.
AddedrequireddateWhen, which is often the only other thing you remember about it.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • No archiving, so a dead link stays listed and broken.
  • No tags or folders; the reason text is the organisation.
  • No content capture — if the page disappears, so does what it said.
  • Nothing deduplicates the same URL saved twice.

Before it works

What you have to provide, if anything.

  • Write the reason as you save it. Doing it later does not happen.
  • Pair with Knowledge base when the link is really a note you have not written yet.

In practice

A team with two hundred unsorted browser bookmarks between them.

Keep the packaging price-break page — it is the wholesale maths.
What was said to the agent

What the agent built

A bookmark with the reason it matters attached.

What changed

Six weeks later the packaging link was found in one search, by the reason rather than the URL nobody remembered.

Questions

What data does the Bookmarks / URLs page use?

It reads url records the agent has collected. Saved links. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ