How to reset your X (Twitter) algorithm
Last updated 2026-10-11. People search “how to reset the X algorithm” and “how to reset the Twitter algorithm” for a switch that clears For You. Commit cb45b55 of xai-org/x-algorithm does not contain that switch. There is no reset endpoint, no “clear my algorithm” parameter, and no published timer that says old likes fall out of the model after N days.
What the code does publish is the input list for the next request. That list is the only honest answer.
What the next For You request actually reads
README.md and the playbook’s reading of home-mixer/candidate_pipeline/phoenix_candidate_pipeline.rs hydrate a request from:
- The viewer’s recent engagements. The README calls this the model’s main input.
- The follow list.
- Blocks and mutes.
- Muted keywords.
- Posts already seen and already served.
- Followed topics.
Phoenix retrieval is a user tower over that engagement history. The playbook notes there is no learned per-user id embedding in production retrieval (phoenix/README.md, home-mixer/sources/phoenix_source.rs). Personalization in that retriever is the history sequence, not a permanent user-id vector stored beside the account. The repository does not publish how many actions are in the sequence, or a command that empties it.
What changing those inputs can and cannot do
Follows, blocks, mutes, and muted keywords are fields the hydrator reads. AuthorSocialgraphFilter drops an author the viewer has blocked or muted. MutedKeywordFilter drops a post that matches the viewer’s own muted keywords, including a hashtag keyword. Unfollowing removes that account from Thunder, which is the in-network source. Those are real code paths. They are not labeled “reset.”
Engagements you make after that become the next request’s main input. not_interested is a scoring head at −47.52, mute_author is −58.8, and block_author is −31.2 (home-mixer/params/param.rs). Those coefficients multiply a predicted probability for a post you are being shown. They are not a button that rebuilds your history.
PreviouslySeenPostsFilter uses an impression bloom filter plus an explicit seen-id set (home-mixer/filters/previously_seen_posts_filter.rs). A post shown once is not re-served. Clearing an app cache on your phone is not described in this repository, so this page does not claim that a reinstall empties that bloom filter.
AgeFilter drops posts older than 48 hours from For You. That is a cut on candidate age, not a reset of the viewer.
What this page will not tell you to do
It will not list a seven-day mute ritual, a “like 20 posts in your niche” procedure, or a claim that the feed is clean after 48 hours. None of those procedures are in the tree. The code also does not say that logging out creates a new viewer embedding.
If the feed feels different in 2026, the published default changes are on X algorithm changes in 2026. Visibility drops that are not ranking at all are on Shadowban on X.
Related
FAQ
How do you reset the X algorithm?
You don’t, from this repository. Commit cb45b55 has no reset control. The next For You request is built from recent engagements, follows, blocks, mutes, muted keywords, seen posts, and followed topics. Changing a follow or a mute changes an input the hydrator reads. It does not publish a guarantee that the old history is gone.
How do you reset the Twitter algorithm?
Same code. X is the product name on the repository. The Twitter-algorithm searches are the same For You pipeline. There is still no reset function in home-mixer/.
Does clearing cache or waiting 48 hours reset For You?
The 48-hour figure in this tree is AgeFilter on posts, not a viewer-reset clock. Cache clearing is not specified. PreviouslySeenPostsFilter is a server-side bloom filter plus a seen-id set, and the repo does not say a client cache wipe clears it.