I Code From My Phone More Than My Laptop Now
This wasn't the plan.
The plan was simple: I wanted to approve tool calls while I was away from my desk. Claude Code would request permission to edit a file, I'd get a notification on my phone, I'd tap Approve, and it'd keep going.
That was the entire use case in my head when I set up Clautel three months ago.
What actually happened is different.
Week 1: Approvals Only
First week was exactly what I expected. Laptop open at my desk, Claude Code running, I walk away to make coffee. Phone buzzes: "Edit File: src/app/api/auth/route.ts." I glance at the diff, tap Approve, go back to pouring coffee.
Nice. Convenient. Worth $4/month? Probably. Nothing revolutionary.
Week 2: Quick Fixes From the Couch
This is when it shifted.
I'm on the couch, phone in hand, scrolling Telegram. I notice a typo in our landing page. In the old world, I'd open the Notes app, type "fix typo on landing page," and deal with it tomorrow.
Instead, I messaged the bot: "There's a typo on the landing page hero section. It says 'acces' instead of 'access'. Fix it."
Thirty seconds later, Claude found the file, made the edit, asked for approval, I tapped Approve, and it pushed the change.
I didn't open my laptop. I didn't SSH into anything. I didn't switch apps. I typed a message in Telegram and the typo was fixed.
That was the moment something clicked.
Week 3: Starting Tasks Away From My Desk
Saturday morning. I'm at a cafe. I have an idea for a feature — a simple toggle that lets users switch between dark and light mode on a settings page.
Old me would have written it in Notes and come back to it Monday. But I had the bot right there.
"Add a dark mode toggle to the settings page. Use the existing theme context, add a switch component, save the preference to localStorage."
Claude Code started working. I watched it read the existing files, understand the theme context, create the component, wire up the toggle, test the build. It asked me to approve the file writes. I scanned the diffs on my phone screen, approved each one, and went back to my coffee.
Twenty minutes later, the feature was done. I hadn't touched a keyboard.
Month 2: The Laptop Became Optional
This is when I noticed the pattern.
I'd look at my screen time and see that my Telegram usage had gone up, but my total screen time had gone down. I was spending less time at my desk overall because I was knocking out tasks in dead moments — waiting in line, on the bus, during a boring meeting (sorry).
The tasks I was doing from my phone:
- Bug fixes that came from user reports (screenshot in Telegram → describe the bug → Claude fixes it)
- Small feature additions where the requirements fit in a message
- Code reviews — paste a PR link, ask Claude to review it
- Checking localhost after changes with
/preview - Resuming CLI sessions I started at my desk with
/resume
The tasks I still did at my desk:
- Major architecture decisions
- Complex debugging that needed me to stare at logs
- Pair programming sessions where I wanted full screen context
But the ratio shifted. More than half my coding output was now coming through my phone.
The Setup
Here's exactly what I run:
npm install -g clautel
clautel setup
clautel start
My MacBook runs with the lid closed on my desk. Clautel runs as a background daemon. Each project has its own Telegram bot.
For my main project, I message @myproject_bot. For the marketing site, @marketing_bot. For the API, @api_bot. Separate chats, separate contexts, no cross-contamination.
When Claude needs to run a bash command or write a file, I get approval buttons. I can tap Approve for one-time access or Always Allow for the rest of the session. This is the part I worried about — approving stuff on a small screen. It's actually fine. The diffs are formatted cleanly, and for routine operations like running tests or installing packages, one tap on Always Allow and you're done.
The feature I use more than I expected: /preview. I type /preview localhost:3000, and I get a screenshot of my dev server right in Telegram. I can click on elements by coordinates, scroll, type into inputs. When Claude makes a UI change, I check it immediately from my phone instead of walking to my desk.
What Changed
The biggest shift isn't the tool. It's the relationship between ideas and execution.
Before, there was always a gap. Idea happens in the shower, on a walk, during dinner. Execution happens at my desk, hours or days later. The idea decays in that gap. By the time I sit down, I've lost the clarity.
Now the gap is about 10 seconds. The time it takes to open Telegram and type a message.
I'm not writing less code. I'm writing the same amount of code, but in the margins of my day instead of in a focused 8-hour block. The focused blocks still happen — they're just for the work that genuinely needs a big screen and deep concentration.
Everything else? I do it from my phone.
I didn't plan for my phone to become my primary coding interface. But here I am, three months later, and my laptop is starting to feel like the secondary device.
Try It
npm install -g clautel
clautel setup
clautel start
7-day free trial. $4/month after that. Works with any Claude Code subscription.