Collections and tagging

Raindrop files saved links into named collections and labels them with tags. A Beam agent watches for each new bookmark, reads its title and source page, and places it in the right collection using rules your team approves, adding tags such as topic or priority. When a saved page arrives with no description or lands somewhere odd, the agent corrects the entry and notes what it changed. Bookmarks that fit no existing rule, or that look like duplicates worth merging, go to a person who decides where they belong before the agent writes the final label.

Dead link and duplicate cleanup

A saved library slowly fills with broken pages and repeated saves. A Beam agent works through stored links on the interval you set, tests whether each still resolves, and reads the saved details to spot copies. Following rules you define, it archives dead entries and merges obvious repeats, then leaves a short note of what moved. Links that return uncertain errors, or near-copies that differ in ways that might matter, are handed to a person. That reviewer decides whether to keep, replace, or drop them, and the agent stores the choice for next time.

Highlights and saved reading

Raindrop can hold full articles and highlighted passages beside a link. A Beam agent reads new highlights as they land, groups them by collection or topic, and updates a running notes file your team keeps. When a highlight mentions a task or a date, the agent drafts a reminder for approval rather than acting alone. Passages that look sensitive, or that name people and figures the agent cannot confirm, are flagged for a person to read first. Everything the agent files stays inside the collections and permissions your account already grants it.