Like it on X. Keep it forever.
Every post you like or bookmark on X lands in your own library: the post, the full X Article if it is one, the rest of the thread, the quoted post, its images, what its video says, the pages and repos it links to, and a short note from your agent on why it matters.
You scroll X, you see something worth keeping, you tap like or bookmark, and you never find it again. This blueprint fixes that. Your agent installs a small tool that reads your likes or bookmarks through X's official API, signed in as you. For each new post it saves the full text, the whole X Article when the post is one, the rest of the author's thread, the post it quotes, its pictures, a transcript of its video made on your own computer, and the web pages, GitHub repos, papers and video captions it links to. Then your agent writes a short note: what it is, the key claims, a few quotes you can check. Run it whenever you like, or every night on a schedule.
A note for every saved post in library/sources/x/, the full text in library/originals/x/ (kept off GitHub), and a ledger so a re-run only pulls what is new.
The posts you save are the best signal of what you want to learn. Now your agent can search them, compare them and build on them, instead of them disappearing into your feed.
X's own API, signed in as you, reads only what is new. The tool follows each post's links and keeps the text. Your agent writes the notes from that text, never from memory.
You make your X developer app, add a little credit, set a spending limit and click Authorize. Your agent installs the tool, runs it and writes the notes.
Likes or bookmarks?
The tool reads your likes by default. If you already bookmark the posts you want to keep, it reads your bookmarks instead. The price per post is the same either way, and both have been tested on a real account.
- Likes (the default). Each like also trains your X feed, and the author is told you liked their post. It can read back as far as you like.
- Bookmarks. Quiet: only you know, and your feed does not change. X only lets the tool read your 800 most recent, which matters only for an old backlog.
Make a second X account just for learning. Follow only the people you learn from, and like whatever you want saved. X's For You feed learns from your likes, so over time that account's feed turns into a research feed, and every like doubles as "keep this". X allows more than one account for different purposes. Two rules keep it safe: never like or repost your main account's posts from it, and never copy your main account's likes.
What it costs
X's API is pay as you go: you buy credits in the X Developer Console. Reading your own likes or bookmarks costs about $0.001 a post when the account you read from also owns the developer app (other accounts pay $0.005). A run reads one page of 20 posts by default, so a run every night is about 60 cents a month. You set a spending limit in the console, so it can never run away, and every run tells you what it cost. X charges for a post once per day, so running twice in a day costs no more than once.
- Threads: a little extra. When a saved post is part of its author's thread, the rest is saved too, at X's standard $0.005 a post, up to 10 per thread: at most 5 cents a thread. One setting turns it off.
- Images and quoted posts: free. They come with the post (we checked X's usage page), and images are saved next to it so your agent can read screenshots, charts and paper pages.
- Video transcripts: free. An optional add-on writes out what a video says on your own computer: a one-time 142 MB download, then about 15 to 20 seconds for a 4-minute video. Nothing is uploaded.
- Linked pages, repos and captions: free.
- X Articles: free. X returns the whole Article with the post.
- Optional: if X ever returns an Article as a title only, your agent can fetch it through Apify for a fraction of a cent, and it shows you the price before it does.
In our test, 30 real likes cost about 6 cents: 3 cents for the posts and 2.5 cents for one 5-post thread. It saved 4 images and wrote out 12 videos, at no extra cost.
The build, checkpoint by checkpoint
Ten checkpoints, and your agent waits for your yes at each one. Here are the main ones.
- You pick likes (the default) or bookmarks, and which account to read from.
- You make your X developer app at console.x.com: a little credit, a spending limit, an app set to Native App with one callback address, and its Client ID. Your agent walks you through every click.
- It installs the tool in
work/x-saves/. Python only. Windows and Mac. If you want video transcripts, it adds the free transcriber too. - A practice run on made-up posts, so you see a saved post and a note before anything touches your account.
- You click Authorize on X's own page. The tool keeps the sign-in in a private file on your computer.
- The first pull: your newest 20 saves, the full text in your library, and a note for each one.
- Optional: run it every night with the Heartbeats skill, and ask your agent questions across everything you saved, straight from your notes.
x-saves setup --source likes --client-id <your Client ID> x-saves auth login # your browser opens on X; you check the account and click Authorize x-saves sync # reads only what is new; prints a one-line summary and the cost x-saves export --to library/originals/x # one file per post: the post, its Article, thread, quote, images, transcript, linked pages
Every command prints a short report. When something needs you, it says what to do in plain words.
The only thing your agent needs from the X console is the Client ID, which is public by design. X also shows you a client secret, a bearer token and consumer keys: you don't need them, so don't paste them anywhere. Your sign-in happens on X's own page, and the tool stores it itself.
X keeps one live sign-in per app and account. Signing in here with an app another tool already uses (n8n, a script) cuts that tool off. A second app is free, and it uses the same credits.
What a note looks like
One note per saved post, short enough to skim, with everything checkable against the original.
- Gist. One to three sentences: what it is and why you saved it.
- Key claims. What the post, its Article or its links actually say, one line each.
- Key quotes. A few short quotes, word for word.
- Thread, quote and media. What the rest of the thread adds, what the quoted post says, what an image shows, what the video says, each marked where it came from.
- Deeper notes for Articles, threads, videos, long posts and posts with real linked pages: the concepts, the commands, the versions and numbers.
- Gaps. What it couldn't capture: a page behind a sign-in, a video it couldn't write out, a thread older than a week.
- Topic tags, reused across notes, so you can ask for everything on one subject.
What you can ask your agent, from now on
Six asks that work once a few saves are in your library.
Run my X saves: sync, export, write notes for anything new, add the ledger rows, then tell me how many and what it cost.
From the notes in library/sources/x/ this week, give me the five most useful ideas, one line each, with a link to each note.
Show me every note in library/sources/x/ tagged claude-code, newest first, with its gist.
From my notes in library/sources/x/, which repos and tools have I saved about agents, and which look worth trying? Cite the notes.
List every saved post marked release: yes from the last month, with what was released and the date.
Use the heartbeat skill to run my X saves every night at 6 AM and leave a receipt. Show me the job before you turn it on.
Words you now own
- X API. X's official way for programs to read your account, signed in as you and billed per post read.
- Developer app. Your own entry in the X Developer Console that the tool signs in through.
- Client ID. The app's public name tag. Safe to share with your agent; the secrets next to it are not.
- Callback address. Where X sends your browser after you click Authorize: a spot on your own computer where the tool is listening.
- Original. The full text of a saved post and its links, kept in
library/originals/x/, off GitHub. - Note. Your agent's short write-up of one saved post, in
library/sources/x/. - Transcript. The words spoken in a video, written out by a small program on your own computer.
Fair questions
No. The tool signs in to X itself and keeps the sign-in on your computer. To run it every night, the Heartbeats skill uses your computer's own scheduler.
One at a time. Switching is one setting and one new sign-in.
No. The transcriber runs on your computer, and the video file is deleted once its words are saved.
No. What was pulled stays in your library.
No. It only reads, and X no longer lets programs like posts anyway.
Source Packs pulls the latest from accounts you follow. X Saves keeps the posts you picked. Both write the same notes into the same library and share one ledger.