That's my understanding too, though i haven't checked it. running claude -p would be horribly inefficient.
I would not be surprised if openclaw added some compatibility layer to brute force prompts through claude -p as a workaround. This isn't the first time that openclaw was "banned" from claude subscriptions.
I would love to be able to share all my sessions automatically. But I would want to share a carefully PII/secrets redacted session. I added a "session sharing" feature to my agent wrapper that just grabs innerHTML and uploads to cloudflare. So I can share how I produced/vibe coded an entire project from start to finish.
I think it's valuable to share that so people who are interested can see how you interact with agents. Sharing raw JSONL is probably a waste and contains too many absolute paths and potential for sharing unintentionally.
Why would you be worried about junior engineers? I see this expressed a lot. It seems kind of condescending to me. It's just a different build toolchain. We can build faster, and having a lot of experience helps you know how things should fit together. People figure shit out. There are plenty of juniors that are way smarter than you or I. Do you mean like a junior who is not as clever as you will have a hard time getting their foot in?
I agree. I spend a lot of time working from my phone so I had to make my own workflow that works for me. I've been following all these bans and drama with the subscription keys and custom harnesses etc. I think there's room for a "universal control plan" that lets you leverage the CLI providers (and whatever crappy interfaces / apis they give you).
Same. When I can't be at my desk, my projects don't stop -- I just do the tasks that work well enough on the phone. Brainstorming, planning, etc. Or tasks that the agent can easily verify.
Having access to my local repository and my whole home folder is much easier than dealing with Claude or ChatGPT on the web. (Lots of manual markdown shuffling, passing in zipfiles of repositories, etc).
I left some notes about this. I agree with you directionally but practically/economically you want to let users leverage what they're already paying for.
In an ideal world we would have a pi-cli-mono or similar, like something that is not as powerful as pi but gives a least common denominator sort of interface to access at least claude/codex.
ACP is also something interesting in this space, though I don't honestly know how that fits into this story.
It's not an argument whether you can be more productive on phone or desktop. Some people (like myself) simply don't have much time to be dedicated at desks so we have to build workflows that support being able to at least be reasonably productive from our phones.
I'm super happy Anthropic finally releases this tool. It's a starting point and I hope they'll improve it. I did a comparison with its features / capabilities here: https://yepanywhere.com/claude-code-remote-control.html
Basically if you start up a claude terminal session, you can enable remote control for that one time, or you can go to /config and change the global setting so that by default each session will be auto-connectable
You can connect via claude.ai/code on the web, or via the mobile app.
You can't connect via the web/app to VS Code sessions, and you can't connect to sessions created by Claude SDK.
One thing it does not do is let you create new sessions. So if you have a heavy remote first workflow (like you work from your phone a lot). People who are used to tmux/tailscale/termius etc or other mobile wrappers/orchestrators won't find this very useful (yet).
Will you add remote / a mobile control plane? I love your approach of using CLI. https://yepanywhere.com/ has a similar approach but it's mainly about access via mobile. [I'm frequently away from my desk]
Ah, actually after looking at your approach, I see you don't use any agent SDK or --json outputs. You just embed a terminal window. That makes mobile interfaces a non-starter. I can see why you are only focusing on desktop, it makes integrating with more providers easier.
I made a basic "claw starter" that you could try. You can progressively go deeper. It starts with just a little "private data" folder that you scaffold and ask the agent to setup the SOUL and stuff, and then you can optionally add in the few builtin skills, or have your assistant start the scheduler/gateway thing if you want to talk to it over telegram.
If you've been shy with using openclaw, give this a try!
That's I think basically what you describe. I've been using it for the past two days it's very very basic but it's a I think it gives you everything you actually need sort of the minimal open claw without a custom harness and 5k loc or 50k or w/e. The cool thing is that it can just grow naturally and you can audit as it grows
You wouldn't typically give it access to your own telegram account. You use the telegram bot API to make a bot and the claw gateway only listens to messages from your own account
I think this is basically obvious to anyone using one of these but they're just they like the utility trade off like sure it may leak and exfiltrate everything somewhere but the utility of these tools is enough where they just deal with that risk.