By Jeremy Panasuk · New Auburn, WI · Emails are not allowed**
I wanted one dumb simple thing. Read and post on X without leaving my terminal. Not a toy feed, not a demo. My actual timeline, with buttons that actually do what they say.
That turned into Termy X, a Rust terminal for Windows with an X panel built right in. Hit Ctrl+Shift+X and your feed is sitting next to your shell. You can read your real Home timeline and post, reply, quote-tweet, retweet, like, follow and unfollow.
And no, I'm not paying for the official X API. I looked at the price and said nope. Termy X runs through OpenCLI on your own logged-in browser session, so it acts as you and your wallet stays shut.
Full honesty up front: I don't write the Rust. My AI agent writes the code. I'm the guy who decides what it should do, opens the app, clicks every single button, and comes back with "that's broken" way more than anybody wants to hear. Most of this project is me typing "ok dude give it hell lets fucking go" and then "keep going." Over and over.
It's open source: github.com/jpanasuk-netizen/termy-x.
Here's everything that went sideways, because that's the good part.
My terminal was apparently a space game
The helper CLI that talks to X was called x.exe. Short, clean, obvious. Terrible.
Overwolf and Outplayed saw x.exe running and decided I was launching X: Beyond the Frontier, an old space game. So I'm trying to like a tweet and my PC thinks I'm about to go fly a spaceship. Wtf.
The fix was the least heroic fix in software history. We renamed it termy-xcli.exe. Done. Never name your binary one letter long unless you like surprises.
"Posted!" (it was not posted)
This is the one that actually pissed me off.
The app used to flash "Posted!" before X had confirmed anything. It just assumed. Feels great right up until you find out nothing went out. A fake success is worse than an error, because you believe it and walk away.
So I laid down the law. NOTHING says it worked until X says it worked. Now you hit a button and get rolling dots while it waits for the real answer. Replies, quote-tweets, retweets, same deal. If it says done, it's done.
Same thing with Follow. Click it and you get a "Follow @handle?" confirm, then rolling dots until X answers. If you already follow somebody, the button says Unfollow. Wild concept, I know. Buttons that tell the truth.
Oh, and the reply button says Reply. No extra Comment button sitting next to it. One button. Moving on.
My timeline was secretly fake
I opened Home and it looked fine. Except it wasn't my feed. When the live fetch hiccupped, the app quietly fell back to a little five-post sample, and it looked legit enough you might not notice.
A demo pretending to be real. That's the nightmare.
So now it pulls a real 100-post timeline. We fixed the sort so newest is actually at the top. And there's no more silent fallback, so if something breaks you'll know it broke. When I open Termy X now, that's my people posting their takes. Not a mockup of my people.
No test posts without my OK
This one's a rule, not a bug. My AI agent does not get to fire test tweets off my real account whenever it feels like it. Every live post needs my yes first.
We did catch a quote-tweet posting bug during testing, and I wanted proof it was fixed for real, not "fixed in theory." So I approved exactly one live quote-tweet. It went to @Jasper_Black and said "100 is enough." X confirmed it, the app confirmed it, and that was the end of the test posts. One shot, landed.
The video player saga
We tried building a custom player inside the app. Ambitious. Not great.
So I picked VLC. Videos open in VLC in its own window with real volume, seeking and audio controls. VLC has been doing video right forever, why fight it? Photos still open in the built-in viewer, because that part already worked and I wasn't gonna let anybody break it.
The pop-out composer that won't eat your draft
I wanted New tweet at the top of the timeline, right where you'd look for it. Click it and a composer pops out. If posting fails for any reason, your draft stays put. You don't lose the brilliant thing you just wrote because the network sneezed.
You can attach images to regular tweets. Image quote-tweets are parked for now. Text quotes work, image posts work, images on quotes are on the list. I'm not gonna pretend otherwise.
There was also a stretch where there was no visible caret when you typed. Letters showing up, no idea where you were in the text. Typing blind in a tweet box is a special kind of anxiety. We added an inline caret. Tiny blinking line, massive difference.
My bot got dumber and ate my whole Ultra plan in a day
Partway through this build, my AI agent just... got dumber. Noticeably. Same task, worse answers.
And it didn't fail quietly. It failed expensively. It would re-check the same broken thing, report back that it was still broken, re-check it again, then write me a paragraph about how it was re-checking it. I'm sitting there watching the usage meter drain like a bathtub with the plug pulled while my bot narrates its own confusion.
My whole Ultra plan usage. Gone in about a day.
I told it straight up: stop the chatter. Stop repeating failed checks. Come back with a verified result or a blocker that actually needs me. That's it.
It got fixed and I got a usage reset, which, fair. But that day is permanently burned into my brain. Lesson: an AI agent that loops on a broken check isn't working hard. It's lighting your plan on fire, one "let me verify that again" at a time.
My C: drive filled up with Rust
Then my disk started choking. I literally typed "figure out what is eating all the megabits on c again wtf." Megabits. I know. I was mad.
It was Rust build folders. Every experimental build, every fix branch, every trace build, all leaving fat target folders behind like a dog marking territory. We cleared out the old ones and got back 29 GB. If you build Rust on Windows, go check your target folders right now. I'll wait.
Shipping it: rc.11, then sync
Today, November 9, I tested the whole thing live on my real account. Text posts, image posts, quote-tweets, retweets, likes, follows. Watched each one land. Then we shipped rc.11.
And then I couldn't leave it alone. So: cloud sync.
Cloud sync, and me getting confused by my own app
Termy X now has optional cloud sync built on Supabase, going out in rc.12. Your likes, reposts and follows follow you across PCs. The local database stays primary and works offline. Sync is a bonus, not a leash.
The first version wanted you to paste in project settings. My first question was basically "how will other people know their password and login?" They won't. Nobody's going to dig up a project URL to like a tweet on their laptop. So the sync is built in now with its own sign-in. Users configure nothing. Create an account, sign in, done.
Then I tested it. I pressed Ctrl+Shift+X and no login came up or anything. Sat there staring at it like a jackass. Turns out the account panel lives under Help > Account sync. Ctrl+Shift+X opens the X panel, not the account stuff. Once I found it, signed in, synced. My likes and follows showed up in the cloud.
So naturally I asked "ok, now that I'm synced to the cloud, now what?" and "what does this do for us functionality wise?" Fair questions. Honest answer: right now it's your activity history following you from PC to PC. That's the feature. It's not magic yet. It's plumbing that sets up the cool stuff later.
My final verdict was, word for word: "ok its fine i guess... cut a release with it." That's as close to a five-star review as I give. rc.12 is going out with it.
Note: Each user only sees their own data. Supabase row-level security locks every row to your account. No admin keys ship in the app.
Quick questions people ask
Do I need to pay for the X API? No. That's the whole point. It runs on your own session through OpenCLI.
Windows? Yes. It's a Rust terminal for Windows.
Do I have to use cloud sync? Nope. Optional. Local works fine offline.
Image quote-tweets? Not yet. Text quotes and image posts work.
Can I change it? Please do. Fork it.
What I actually learned
Green checkmarks don't mean it works. Using it does. Almost every one of these bugs got caught by me opening the app and clicking stuff, not by a passing test.
So the rules are simple. Nothing says "posted" until X confirms it. The timeline is real or it tells you it isn't. Your draft survives a failed post. Test posts need my OK. And your bot doesn't get to burn your plan re-checking the same broken thing.
If you live in a terminal and you're on X all day, give it hell. Hit Ctrl+Shift+X, scroll your real feed, post something, and watch the rolling dots turn into a real confirmation. Then break it and tell me how. That's how this thing gets S tier.
Grab it or fork it: github.com/jpanasuk-netizen/termy-x
Jeremy Panasuk lives in New Auburn, WI. He directs and tests AI-built developer tools: his AI agent writes the code, and he opens the app to find out whether it actually works. Say hi at Emails are not allowed.