Send a link, get a summary that stays in your base

A “read later” list does not get read. A two-minute summary solves half the problem, and then gets lost in the chat — which is why here it is also stored, so a month later you can ask “what was that about suppliers?”

What is inside

1. A link that was sent — the entry.
2. Read and summarise — an agent with a page-reading tool. The tool is wired with link_extension: the model decides whether to open the link, so a message with no link costs no extra request.
3. Save to the base files the summary in your knowledge base.
4. The summary goes to the person.

The same text travels in two directions: into the answer and into the base. A month later that is a record of what you read, and you can ask about it in a normal sentence — which is what “a second brain” does.

What to set up for yourself

• The agent’s prompt. It currently asks for three to five key points and an opening line with the title and the address. Those are not decoration: without them a stored fragment cannot be traced back to its source.
• The knowledge base — the same id as the second brain, if you want one base.
• What to do about paywalls. The tool reads what the server returns: behind a paywall it sees an invitation to subscribe. The prompt already forbids summarising from the URL alone.

What to connect

A knowledge base under Documents, and a Telegram bot if sending links to a messenger suits you better. Page reading runs on the platform; no separate key.