I think it’s concerning that we’re giving AI easy remote access to so many machines, but I’m pretty sure Anthropic is just doing this because of customer demand. I wrote my own web UI for remote Claude Code months before they made it since being able to orchestrate from your phone is a superpower.
I mean, same, but also CC remote control only being available through the subscriptions, and subscriptions only being available for non-automated work, is an interesting intersection of decisions. Right now you can spin up a docker container or ec2 instance, log into CC over terminal, then control it afterwards via remote control, but that’s quite janky compared to eg adding a CLI flag which serves CC remote control on a port where you configure auth options / can configure SSO—and that way would work fine with non-subscription API tokens, so you could hook up CI so that a test failure gives a CC instance with which to debug which is accessible via SSO to anyone on the dev team.
I think it’s concerning that we’re giving AI easy remote access to so many machines, but I’m pretty sure Anthropic is just doing this because of customer demand. I wrote my own web UI for remote Claude Code months before they made it since being able to orchestrate from your phone is a superpower.
I mean, same, but also CC remote control only being available through the subscriptions, and subscriptions only being available for non-automated work, is an interesting intersection of decisions. Right now you can spin up a docker container or ec2 instance, log into CC over terminal, then control it afterwards via remote control, but that’s quite janky compared to eg adding a CLI flag which serves CC remote control on a port where you configure auth options / can configure SSO—and that way would work fine with non-subscription API tokens, so you could hook up CI so that a test failure gives a CC instance with which to debug which is accessible via SSO to anyone on the dev team.