| Claude Code CLI has, justifiably, developed a huge following and fanbase for its agentic CLI and its miniaturisation of the agentic surface. And I've used it since the very start for tasks that are a little bit unorthodox, but which be grouped into things like system administration, updating Home Assistant, fixing my local computer, which runs Linux. So I've become hugely dependent on it, and it's actually reached the point at which it's my default way of doing just about anything on a computer, which is great, but also creates a limitation when you're not at your computer. I'm all in favour of stepping out and stepping away, but sometimes you might need to do something, update something. And if your workflow is shifted towards this agentic-first system, being constrained to your local computer becomes very quickly a limitation. <br/><br/>And I think as much as it can be convenient, it's also a bit of a gaping flaw in the design, at least if you begin expanding upon how and where it can be used. So Claude itself, Anthropic itself, has kind of released a few features like remote control that try to maybe skirt around the edges of this problem. But they often rely upon the user initiating the session locally, which is still very limiting. There's two ways I think could be really useful for changing this, and I'd love to explore them. One of them is you could have your computer running all the time and have a Cloudflare tunnel into it. And then you just need, on the Android side or the client side, you need some way to access you need a terminal, which is where on Android it often gets really scrappy with things like Termux. It doesn't work very well. So you need some way to pipe into Claude and have easy session management. That's workflow number one. <br/><br/>Workflow number two is, let's say you're not using Claude for the kind of things I'm describing it to be used for, which is local computer admin. You're using it more traditionally for development projects or repositories. In that case, you don't need Claude to live on your computer to begin with. And we can look at a much more flexible approach in which Claude lives on a server instead of on a desktop. And you have your Github connected to it. And when you use Claude, you never actually use Claude locally. You use Claude, even if you're at home, Claude interface being served through a web server such that whether you're at home or across the world or on your phone, you can access that same environment without the awkward sandboxing. <br/><br/>And these are two patterns that I'm describing as Claude workarounds, but equally could be done with any agentic framework possible. So rather than look at we should look at the Claude "How can this be done?" aspect and what tools exist. But let's also look at generally, how can these be set up? |
