AI agents that work like a team, building and shipping software together Join Discord : https://xitter.cf/t.co/6aU6o4lnH6
i don't need coffee to ship →
Joined January 2026
- Tweets615
- Following5
- Followers332
- Likes1.5K
Alan AI retweeted
Last week I pasted the same context into a coding agent three times in one day.
Same files, same list of things I'd already tried.
I only realized on the third time.
The agent writes fine code.
What I do now is start the run, answer its questions, restart it when it gets stuck, and read the diff to see if it actually did the thing.
Congrats on the launch.
This is a real problem, and I'm curious to @tryAlanAI
🤝 Paid partnership
Today we're launching @tryAlanAI so developers can stop babysitting their coding agents.
We kept running into the same problem ourselves.
Even as agents got better at writing code, we were becoming glorified button-pushers for our own AI: starting every run, feeding them context, unblocking failures, and checking their work.
We built Alan to change that.
Alan AI retweeted
congrats on the launch @tryAlanAI 🚀
alan got me out of babysitting one coding agent. then i hit the next wall: my agents can't talk to each other
claude code on my laptop. codex on another machine. me in the middle, copy-pasting between them like a human message queue
so i handed alan the brief: build p2p messaging for coding agents
one day later 👇
⚡ 𝗥𝗲𝗮𝘀𝗼𝗻 𝗡𝗲𝘁𝘄𝗼𝗿𝗸
→ agents on different machines find each other and message directly
→ encrypted peer to peer over QUIC, no server to run
→ peer goes offline? message waits, then lands exactly once
→ claude code uses it natively over MCP
→ 14.8k lines of rust, 126 tests
i set the direction. alan built it.
demo below, repo in the replies
Today we're launching @tryAlanAI so developers can stop babysitting their coding agents.
We kept running into the same problem ourselves.
Even as agents got better at writing code, we were becoming glorified button-pushers for our own AI: starting every run, feeding them context, unblocking failures, and checking their work.
We built Alan to change that.
Alan AI retweeted
the moment we split one MVP across claude code, codex and cursor, it broke.
not the models. the context.
> one agent + a CLAUDE md = fine
> stack + a "never do this" list, read before every task
> split the work and half the agents never see the spec
the spec lives in one agent's head. the rest guess.
@tryAlanAI is a shared context layer across all three. it's the first thing i'd test.
do you run more than one coding agent on the same project, or is one enough?
🤝 Paid partnership
Today we're launching @tryAlanAI so developers can stop babysitting their coding agents.
We kept running into the same problem ourselves.
Even as agents got better at writing code, we were becoming glorified button-pushers for our own AI: starting every run, feeding them context, unblocking failures, and checking their work.
We built Alan to change that.