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?
We have a junior in our team. In the past 2 years he hasn't written any code himself, because he can't code. He's been using chatgpt to write his code for 2 years, and he mostly delivers stuff, but the code is shit. Our manager isn't aware because he doesn't read our code, but I do and it's super obvious. But the point is the junior can't code.
Over the past month the company deployed Claude internally with tools etc. I, who can code well, picked it up in about 2 days despite the fact that I had never regularly used AI. Now I can produce code using Claude as reliably as the "experts" in our company (to be clear in our company by "experts" I mean good users, not people who actually understand how these machines work). The junior is still struggling go get Claude to do what he wants.
The point is the following: This new technology, like all new technologies, raises the minimum amount of things you have to be proficient at in order to even be at the bottom of the corporate ladder. The more you know the faster you learn, therefore those who know less (juniors) will struggle for longer with the new technology than without it.
I feel like I've been doing multiplications with pen and paper and the other guy doesn't understand the concept of multiplication. Now someone gave us a spreadsheet. I can do multiplications a billion times faster, and the other guy still doesn't understand the concept of multiplication.
You can say that our junior is especially bad and I don't disagree. But the phenomenon of "the more you know the faster you learn therefore new technologies impact juniors harder" is on average true regardless.
Because you need to understand the output of coding agents when there is an issue or even a decision to be made. Even Opus-4.6 gets into rough states where it spews out garbage or suboptimal code and juniors might not catch it. Reading somebody else's code and evaluate it quickly is a tough skill to learn compared to writing one's own code; slow thinking vs fast thinking mode.
True, but junior developers used to provide a lot of value while doing this. Now their value, while they are still figuring it out, has gone down immensely. For a company, there is no value in letting a junior dev write code anymore. And for reviewing the AI output, you need someone more experienced.
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).
