holy sh*t. I built my own research agent and left it with 9 years of saved links overnight
Anthropic's own test: one agent found 14 to 27 of 70 planted bugs, hundreds working together found 66. so I stopped giving one agent a huge job and split it across a team
bookmarks from 3 browsers, a Pocket export, 4 years of saved posts, my own "saved messages" chat, and one rule: "delete nothing. dead links go to a graveyard folder, not the bin"
give each group of agents a specific job:
→ readers pull every saved item out of the browsers, exports and chats, and strip the tracking junk off each URL
→ rescuers fetch whatever is dead from web archives and keep a full local copy of the page
→ sorters tag by topic and separate what still holds from what expired two years ago
→ the builder puts it all in one library you can search offline, in your own words
a link can open fine and still be worthless. the post was rewritten, the domain was resold, the tool shut down and now the URL sends you to a casino. checkers compare today's page against the snapshot from the week you saved it and flag everything that changed underneath you
by 7am: 11,482 saved items became 6,901 unique pages. 1,412 dead links came back from the archive. 318 are gone for good, with the reason written next to each one. 2,274 are still live but no longer say what they said. 0 deleted. 1 question waiting for me
give Claude Code your bookmark exports, then ask:
"Turn my saved links into one searchable library
1. Read every bookmark file, export and saved-message log. Strip tracking parameters, resolve redirects and group the same page saved in different places. Keep the date I saved it
2. For every link that is dead, redirected or paywalled, pull the closest archived snapshot and save a local copy with its archive date. If nothing exists, write down why
3. Compare each live page with its archived version from around the date I saved it. Flag the ones whose content changed, whose domain changed hands, or that now sell something different
4. Build a library I can search by topic and by date, plus one page: what's worth keeping, what died, what quietly turned into something else. Ask before anything is removed"
start with one browser's bookmarks and open 20 pages by hand before you let it loose on the rest
keep delete on the "ask" list. agents sort and rescue, you decide what actually goes
the whole build below
ANTHROPIC KEEPS CLAUDE CODE OUT OF ITS FREE PLAN WHILE 10 OPEN REPOS WITH 700,000+ STARS PUT THE SAME AGENT IN YOUR TERMINAL TONIGHT FOR $0
an agent is a loop around a model. the loop is open source now. so the only bill left is tokens, and even that one is optional
[4 agents worth installing]
01 opencode → MIT, 220k stars, 75+ providers, and a batch of models that currently cost nothing to run. plan agent and build agent included
https://t.co/dTUzVMIlQr
02 Codex CLI → OpenAI's own, Apache-2.0. runs its code in a sandbox before it reaches your files
https://t.co/jFURQvBiMb
03 grok-build → xAI open-sourced its harness. plan mode, subagents, git worktrees, headless for CI
https://t.co/hXDqOKhzQA
04 aider → commits to git after every edit, so any AI change is one command from gone
https://t.co/dhIcUIoOYv
[2 more, if the first four don't fit]
05 Cline → the same agent as a CLI, an extension or an SDK, with your own key
https://t.co/ShX8K7dHMT
06 goose → Linux Foundation, MCP-first, any provider, running on your machine
https://t.co/6gw5iWyJVJ
[4 that keep it from costing you]
07 ollama → the model runs on your laptop. no key, no bill, nothing leaves the room
https://t.co/SaH2ChS4Ie
08 E2B → hand the agent a sandbox instead of your computer. a bad command kills a container
https://t.co/gZFaqKLN4u
09 MCP servers → connectors to files, git and databases, so it stops guessing
https://t.co/ST0LRFifyB
10 Langfuse → every run on record: what it read, what it wrote, what it burned
https://t.co/34EDs9LbXH
[pick by what's bleeding]
paying monthly just to type in a terminal → 01
scared to point an agent at a real repo → 08
want it running with the wifi off → 07 + 01
one rule before any of them touch your code: commit first. 04 does that part for you
GROK BOT BOOKED ME 4 TINDER DATES WITH ONE ROUTINE WHILE I WAS ASLEEP
Grok Bot works on a computer and in a browser, and runs routines on a schedule. I gave it one job for the night
[what it did overnight]
→ read my new matches and their profiles
→ replied to chats that had been sitting for over a day
→ suggested a time and place to the ones already going well
→ checked everything against my calendar
→ sent me a morning summary: 4 dates, times, places, what we talked about
[the routine I gave it]
"every night at 2:00 open Tinder. reply to messages older than 24 hours in my style. if a chat is going well, suggest meeting at one of these places: [list]. check my calendar. send me a summary in the morning"
[the honest part]
→ Tinder bans bots and automation. you can lose your account
→ there's a real person on the other side who thinks they're talking to you
→ so now I do it this way: the bot drafts the replies and picks the places, I hit send
a bot can get you the date. it can't show up for you ↓