MY PROBLEM
I love analyzing my stats. Whether it’s trading or my X account, I like having data to understand what works and what doesn’t.
For X, I was doing that with Codex. The problem was that before every conversation, I had to collect the same data and explain the same context again. My posts, my replies, their performance, how I write… It got a bit annoying.
I did it manually for a few weeks, then ended up building a tool for it.
That’s how PilotMyX started.
PILOTMYX
Basically, you connect your X account and the app collects your posts, replies and their metrics. You can see what brings you impressions, engagement or profile visits, and compare one period with the previous one.
Replies count too. When you start with a small account, you spend time commenting on other people’s posts. I wanted to analyze that work as well as my own posts.
Then there’s a calendar where you can write drafts, review them and schedule them. I also added an MCP so Claude or Codex can use the same data and the same drafts.
For example, I can ask my agent to analyze my week, find the posts that worked and actually read them to see what they have in common. If it then helps me prepare a post, it already has my history and context.
Personally, I mostly use it for analysis. I write what I want to say myself, and AI helps me rephrase it in English or schedule it. I want my account to stay personal. Giving an agent my stats doesn’t mean letting it make up my life to fill a calendar…
You can also use the analytics and scheduler directly in the app without connecting an agent.
THE BUILD
I started the project on July 9, 2026 and first deployed it to production on July 21. I was already using it for my own account, but the public launch came later.
The stack is what I use for my web projects: Elixir, Phoenix LiveView and PostgreSQL, with Oban for background jobs.
One fairly important part of this project is the cost of the X API. The data is synchronized and then cached. When I ask my agent several questions, it can work with that data without requesting everything from X again each time.
That sounds obvious, but I still managed to build a tool for keeping my history that could miss data if I didn’t log in for three days… I fixed that in early August. It now syncs every day, even when I don’t sign in.
I also wanted one subscription plan at first. Except a small account and someone posting hundreds of replies a day don’t create anywhere near the same amount of data to collect. So I ended up with two plans, Basic and Growth.
LESSONS
- Build something I use. PilotMyX came from something I was already doing manually. I use it every day, so I notice fairly quickly when something doesn’t work as expected. The sync that depended on me signing in is a good example…
- AI needs context. Asking it to help me on X without giving it my posts and results means asking it to guess. That’s why I started by making the data accessible to it.
- Explain what the app does. I talked about PilotMyX for weeks before realizing I’d barely explained who it was for. Talking about the MCP and the build isn’t enough for someone discovering the project.
AUGUST 24, 2026 - THE LAUNCH
I announced the public launch on August 24, 2026, with a 7-day free trial. I’d been using the tool on my own account for about a month.
PilotMyX is available for founders and creators who want to understand what works on their X account and use their own data to prepare their next posts.
As for me, I keep using it every day to analyze my account and see what I can improve.