Connect your X account to Claude Code so it can read your own bookmarks, check whether what you saved is actually true, and go deeper on the ones worth it. This is how I work now.
Saving a post is easy. Working out whether it is real is not. A lot of what circulates about building with these tools is exaggerated, some of it is auto-generated filler, and a little of it is a straightforward scam selling a course.
Once Claude can see what you saved, you can hand it the whole pile and ask it to do the work you would not do by hand: check each claim against the actual source, tell you which ones are hollow, dig into what the person is really doing, and find whoever is doing it better. It turns a saved list into something that answers back.
There is no subscription and no minimum. X charges only for what you read. Their words: "No contracts, subscriptions, or minimum spend. Start and stop anytime."
| What | Price |
|---|---|
| Reading a post | $0.005 each |
| Reading your own posts and saves | $0.001 each |
| Asking only "how much is being said about this" and getting a number back, no posts | $0.005 per question |
So reading everything you have ever bookmarked is somewhere between about 10 cents and a dollar, depending which of those rates your saves fall under. My whole list came to 99 posts, which it gets through in one go. Put a small amount of credit on it, ten dollars rather than a hundred, and see what a real sweep actually costs you before adding more.
Two settings, before anything else. At console.x.com, under Billing, there is a box for the most you are willing to spend in a month, and a switch for automatically topping up when you run out. Set the first to something small. Leave the second switched off. Together they mean the worst thing that can happen is that it stops working and tells you, rather than quietly carrying on spending. Mine is set up exactly that way.
You do this part yourself, because it is the part that involves your own account and your own card. It is four things and none of them are technical.
Then you hand the rest to Claude, and it does the installing. The step where you paste those long strings into the vault comes later, and Claude will stop and wait for you at exactly that point.
Most things you can do with this need only a simple key. Your bookmarks are different, because they are private to you, so X wants proof that you personally said yes rather than just proof that the app exists.
In practice that means switching on a sign-in option in your app's settings and ticking a few permission boxes, including one that keeps the connection alive rather than letting it expire in a month. Claude knows which ones and will point at them, so you do not need to learn the names.
Expect this bit to take a couple of attempts, and let Claude drive it. It took me more than one go. There is nothing you can break by getting it wrong: the only thing that happens is that it does not connect yet, and you try again.
Signing up gets you access. It does not get you a working setup, and on its own it gets expensive fast, because nothing stops you paying again next week for the posts you already read. So there is a small kit to install, and two of the four pieces exist purely to stop that.
| Piece | Why it is there |
|---|---|
| The connector | Talks to X, and pulls your keys out of the vault at the instant it needs them, so no key is ever written to a file on your machine. Tells you what something will cost before it does it. |
| The memory | Keeps a list of the posts it has already shown you. Ask it again next week and it skips those and brings only what is new. Without that list it would start from the beginning every time, and since you are charged for each post it reads, you would be paying for the same ones over and over. |
| The spending guard | Speaks up inside Claude the moment a command is about to cost something, before it does. Once per session, never blocks you. |
| The judgement | What Claude follows when it reads your saves: check the source, not just the idea, and assume you have no way to check it yourself. |
Your keys go in a vault, not in a file. A file gets copied, backed up, or shared by accident; a vault does not. It is free for one person, and there is one Terminal line per key that lets you paste it in without it ever appearing in your command history or in a chat. If Claude ever asks you to paste a key into the conversation, say no. It does not need to see them.
You do not have to install any of that by hand. There is a single file that Claude reads and then works through with you: it fetches the four pieces, puts them where they belong, sets up the vault, and stops at the one step it must not do for you. Copy the line below into Claude Code and it starts.
Type /bookmarks. That is the whole thing.
The setup put the instructions on your machine, so Claude already knows to go to the real source rather than trust the post, to tell you who is saying it and what they gain if you believe them, and to be blunt about the ones not worth your time. You never have to explain any of that again, or remember it.
Ask for something different in your own words whenever you like: only the last week, only the design ones, go deeper on that third one. But plain /bookmarks is the one you will use.
These are the rules my own setup uses when it reads X, learned over a year of doing it monthly. They are worth knowing yourself, not just handing to Claude, because they are mostly about resisting the obvious signal.
We have overspent on this three times, so these are earned rather than theoretical.