Launched this week
aImsg
Code From The Coffee Line. Ship from the Subway.
121 followers
Code From The Coffee Line. Ship from the Subway.
121 followers
Code from your phone in 30 seconds. No setup, no IDE, just text. Write, edit, and review code via text message.
We loved what OpenClaw does - AI coding agents that plug into your GitHub repos and actually move code forward. But the irony was impossible to ignore: getting an AI coding agent running felt like provisioning infrastructure. CLI installs. Config files. Environment variables. API keys passed through terminals. You don’t just “try it.” You allocate an hour.
And that’s where the friction lives.
The issue wasn’t intelligence. It wasn’t capability. It was activation energy. Every extra step between “I want to see what this can do” and “I’m actually using it” quietly kills momentum. Curiosity fades fast. Setup friction compounds.
So we asked a simple question: what if the setup disappeared?
Not streamlined. Not improved. Gone.
What if you could just text it?
aImsg connects to your GitHub repos directly through iMessage. You verify your phone, link GitHub, and you’re live. No IDE required. No terminal. No Docker container spinning up. You send a message. It proposes edits. You confirm. It pushes to a new branch. Nothing touches main without your explicit approval. From zero to first action takes under a minute.
The idea didn’t start there.
Initially, we were building what we thought was a better CLI experience — cleaner commands, smarter defaults, smoother onboarding. But that approach still assumed developers were willing to invest setup time before seeing value. We realized the real bottleneck wasn’t the interface layer. It was the barrier to entry.
Every dev tool competes on capability. Very few compete on immediacy.
iMessage was already installed. Already trusted. Already habitual. No app store. No downloads. No learning curve. Just a conversation in a place you already use daily. Instead of introducing another dashboard or terminal abstraction, we embedded the control layer inside something universal.
That shift changed everything.
The challenge then became architectural: how do you make something feel instant and conversational without sacrificing safety? GitHub write access is not casual. So every destructive or write action requires explicit confirmation. All changes are isolated to new branches. There are no silent mutations, no background merges, no surprise pushes. You remain in control at every step.
What started as an attempt to refine a tool evolved into a rethink of how coding agents should be accessed at all. Instead of treating AI as another piece of infrastructure to deploy, we treated it like a persistent channel — always available, lightweight, and responsive.
The goal wasn’t to replace the IDE. It was to compress the distance between intention and action.
If you can reduce “I need to handle this” to a single message, you unlock an entirely different workflow. Quick reviews while commuting. Lightweight fixes without opening a laptop. Async approvals. Repo questions answered instantly. A control plane for your codebase that fits in your pocket.
That’s what aImsg became: not just an AI coding agent — but a frictionless layer between you and your repositories.
We almost didn’t ship this.
Not because it didn’t work.
Because it felt too simple.
A coding agent that lives in messages. No installs. No setup. Just text.
We kept wondering if people would take it seriously.
But every time we showed it, the pattern was the same.
Someone would try it, watch a branch get created, then pause for a second.
You could see the moment it clicked.
That reaction made the decision for us.
So we shipped.
And this is just the start.
We’re exploring Claude Code, OpenClaw integrations, and bringing this into places people already work like email, Slack, and Teams.
The goal is simple.
AI that meets you where you already are.
If you have any input or criticisms, please let us know!