That sounds really cool, though. I'm currently trying to "train" our kids to manage their own schedules, e.g. reminding me that they have somewhere to be instead of vice versa.
Maybe a wall-mounted solution would help put it front and center for them.
(Offtopic but since we're already there, and a standalone post for this seems inappropriate..)
@dang/tomhow, could we consider amending the "no accusations of astroturfing" rule to cover "accusing people of being bots (or using LLMs)"?
> Please don't post insinuations about astroturfing, shilling, brigading, foreign agents, and the like. It degrades discussion and is usually mistaken.
For the same reasons as the former, the latter are virtually never adding to the conversation.
I agree it's (increasingly) a threat to the quality of discourse here, but adding to the noise does not solve it.
Each time I've dug into this for someone, it's because they're filling up their context window with a bunch of tokens before any real work even starts.
Highly encourage people having issues to do /context and start removing heavy things. It's usually some sprawling MCPs they rarely use, or huge CLAUDE.md files they generated or cargo-culted from someone else.
I'm not suggesting these are the only ways to hit the limits, it's just (so far) almost always the answer when someone hits the limits doing something that I wouldn't expect to be problematic.
Update Claude, turn on all of the MCPs you've been using, start a new Claude session from scratch in an empty folder.
Run /context.
Observe that your MCPs are killing a sizable chunk of the usable context window.
The utility here is that it'll break down exactly which MCPs are consuming how many tokens, just in tool descriptions. Then you can decide if that's worth it to you, even if you continue using Codex or OpenCode or etc.
> [..] machine-readable archive of information associated with your account in HTML and JSON files. [..] including your profile information, your posts, your Direct Messages, your Moments, your media ([..]), a list of your followers, a list of accounts that you are following, your address book, Lists that you’ve created, are a member of or follow, [..], and more.
(Note that I actually elided some additional things that are included in the export, for readability's sake.)
You can't actually use your followers and following list from X on other sites. With Bluesky, you can move your profile onto other infrastructure, continue to see posts from people you follow, and make new posts that your followers still see like nothing happened. It's like how if you own your own domain name, you can set your MX records to whatever email service you want and change it when you want without affecting anyone you're having email conversations with.
Ah, I see. Your use of the term "export" made me misunderstand. Though now that I've thought about it for a few minutes, I'm not sure what verb makes sense [to me] there. I guess "migrate?"
The whole thing is worth reading, multiple times over, if you want to find success in using the tool. But I'll call attention to this passage especially:
> Include tests, screenshots, or expected outputs so Claude can check itself. This is the single highest-leverage thing you can do.
Thanks to another comment here I went looking for the strategy guides that are injected. To save everyone else the trouble, here [0]. Look at (e.g.) default/STRATEGY.md.jinja. Also adding a permalink [1] for future readers' sake.
I think I need a bigger kitchen, haha.
That sounds really cool, though. I'm currently trying to "train" our kids to manage their own schedules, e.g. reminding me that they have somewhere to be instead of vice versa.
Maybe a wall-mounted solution would help put it front and center for them.
reply