Pinned Tweet
How I run an AI agent team from my phone: one lead agent, a review gate where nothing ships on one opinion, and a written memory that survives every session. The one session setup is free to copy (MIT). Link inside.
I took all the feedback you guys gave me and tried to fix it. Give me the good the bad and the ugly truth. you won't hurt my feelings at all. I respect it.
CompilingThings retweeted
🧙🏻♂️ [ Call for testers - Sharing appreciated! ]
Qwen 3.8 Flash Recipe for 96 GB Strix Halo
@high52weeks Halogen Flash recently added support for 96 GB Strix Halos, but my recipes only targeted 128 GB Strix
The good news: The recipe's (experimental) branch now autodetects your Strix variant! It asks questions, installs packages, optimizes your system, and downloads the correct quant for you🎉
Read the 96 GB instructions (also in next post👇🏻):
github.com/claudejaune/Qwen3…
this is how my days end:
Ok, its nightshift time see you in the morning Claude.
Good night, G. I'll keep working on the backlog overnight. Tonight's plan:
1. L04: when Pi's review finishes, I'll get the tests run on the merged code and settle the pin-file question. If the review accepts,
L04 ships.
2. L28: if Pi's revision is still running around 22:00, I'll stop it and rerun it in smaller pieces.
3. Sessions: S2, S7 and S8 keep going on their legs, and I'll take their results as they land.
4. Kit for the 4 pm post: I'll prepare the small /plan fix and the /moa2 review. Making the repo public waits for your go in the morning.
Update from the weekend with the finished open frame case. Designed by Maker 3D PC on Bambu Handy.
CompilingThings retweeted
🧙🏻♂️Qwen 3.8 Flash Recipe update: @high52weeks Halogen Flash now gives you ez 65+ tok/s on real tasks on real codebases
Run `git pull && ./refresh. sh` to update
Recipe changes:
- Default Halogen Flash version to 0.18.16
- `refresh. sh` offers to delete older Halogen Flash images and says how much space it'll free up
- Running `refresh. sh --image latest` specifies the exact version it'll pull (used to just say "latest")
- Removed redundant `"Pull the <version number> image now?"` confirmation when refreshing to a new Halogen Flash version
Get it here:
github.com/claudejaune/Qwen3…
Looking for feed back on my landing page. Give me the good the bad and the ugly. Nothing is off limits, you can't hurt my feelings, I respect honesty.
My Python baseline for every new project from day one:
1. Written contracts for important formats and state
2. One canonical parser/reader/writer per format
3. Fail-closed semantics with explicit UNKNOWN
4. Ruff + Pyright + pytest behind one quality gate
5. Hypothesis on parsers and state machines
6. PEP 8 / 257 / 484 baseline
7. Deterministic dispatch/state handling
8. Frozen gate inputs + reproducible review artifacts
9. Provenance, evidence identity, and resumability
10. Immutable logs from day one Much cheaper to start this way than retrofit it later.
They will often build new, instead of looking for it:
My agent proposed a new RAM test to work out how many workers a machine can run. I said "I bet the answers are in the vault boss". The answer was already in the agent's own runbook.
Sometimes you need to be strict.
My agent kept sending rulings to its worker sessions as free text. I asked "why can you not follow your claude.md, how am i supposed to trust you when you can't follow one form?" Every ruling now goes on a fixed form.
Sunday vibes. Many prints coming together, some need my attention for assembly. Printer is cooking. That picture on the wall is my life long hero. My Granddaddy, he was a maker and a builder. If he needed it. He made it. He taught me so much.
I learned that I can boost posts from people I like and posts I like just by copying the link. You should try it, we all need a little help from our friends.
I am digging deeper, it's what rabbits do.
Claude's numbers check out against the code: a reply is 5 vs 0.66 for a like (about 7.5x), a copy link is 20 (about 30x), "not interested" is about -52 (about 79 likes) and a mute is -58.8 (about 89). The mutual follow boost, the 2-hour test slot for small accounts and the default settings caveat are all right too.
There are two things I'd adjust:
•
"Worth 30 likes" doesn't mean one share equals 30 likes. The weights multiply the model's prediction of how likely each viewer is to do each thing. So a post people are likely to share ranks like one that gets 30 times more likes, but you copying a link once doesn't add 30 likes' worth to that post. That's why sharing your own posts doesn't move them.
•
Saying hashtags do nothing goes a little too far. I found no ranking weight for them. They do feed X's topic models and spam detection, though, so stuffing posts with them could count against you.
Claude's other points match what I found. Links have no penalty in the code, and "answer your repliers" fits the mutual boost, though that part is advice drawn from the code rather than something it states.
The parts that matter for you:
- What counts: a reply is worth about 7.5 likes and a copy-link share about 30. Quotes and DM shares count the same as replies.
- What hurts: one "not interested" cancels about 79 likes, and one mute about 89. Bait or off-topic posts cost more than they earn.
- Mutual follows weigh most: replies between accounts that follow each other get an extra boost. Answering the people who reply to you
does more than posting more.
- The first 2 hours matter: a post from a small account, under 2 hours old with under 200 views, can get a test slot in other people's
feeds. Be around after you post.
- Hashtags do nothing. Posting steadily on one subject teaches the model who to show you to.
- Links aren't penalised in this code. The guide keeps its no-links rule because that's your style.
These numbers are the code's default settings, and X can change the live values without notice.









