I ended up taking a different path.
I went through the same “SSH into a VM from my phone” phase, but eventually realized the problem wasn’t the infrastructure it was the interface.
Today my workflow is almost entirely GitHub-native: Create issues, Prioritize work, Review PRs, Leave feedback
An orchestrator watches projects, assigns work, spawns coding/review agents, responds to my comments, and merges when everything checks out.
The biggest unlock wasn’t moving Claude Code to a server.
yesterday i put claude code on a VPS and then locked it down like rob here so i could code from my phone securely on some of my projects
i was so damn excited about it, finally i could not bring my laptop with me everywhere
but so far its been awful and not fun. cant copy paste things from a terminal on phone. images dont paste. the lines im reading keep shifting as new info comes on screen. i have to be a caveman and ls/cd in ubuntu from a phone
so now i will come up with my own solution instead or ill rig up some always on device to claude remote control and see if i can finally draft support tickets and resolve from my phone or ipad later today without it taking 10x longer than normal from my pc
the lesson here for me is that my initial thoughts were right, coding on a phone is not very fun! but i think it would be solved if i can use claude app on all places and have it synced, that would be the ideal. and all of it is synced based on ONE core device (my docked mac)
Omarchy Quattro's new network panel is a delight. All the major stats on the connection, easy-to-run speedtest, and direct selection for DNS. Of course mine is set to @Cloudflare 😄
people are confusing initial implementation cost with total cost of ownership.
building is often the cheapest part. maintaining, supporting, securing, and operating it is where the bill shows up.