@garrytan Harness Wars are already here!
The frontier labs are playing to lure customers into an intractable vendor lock, Every business should be doing everything they can to keep their infra portable and separate the app layer from the Agents and LLMs.
"If you're prompting Claude Code, you're using it wrong".
That's literally what this thing was built to do. My bet with Aileron is that most work can be accelerated with AI, and most people don't want to touch an agent to do it.
@stuxnet_vt@blackgirlbytes "If I had more time, I would have written a shorter letter."
I'd give myself a break on this. Editing into excellence takes the time many won't commit.
@mitchellh And legal indemnification. RHT basically absorbs risk.
It’s brilliant and also as a lead of the open source project, watching the productization rebuild process up close was 🫠
Lots of dunking today. I’m not among them.
Empathize with every customer who lost business and real dollars. At the same time:
Running infra at this scale means relying on partners, and I saw Railway and @JustJake do everything to remediate and communicate.
Google? Hard to reach, slow to respond to their customer.
Google Cloud has blocked our account, making some Railway services unavailable. We have escalated this directly with Google. The Railway Platform team has since confirmed access to Google Cloud and is working on restoring access to all workloads.
We have access to some of our Google Cloud–hosted infrastructure and are working to restore the rest of the service. We apologize for the disruption.
@RhysSullivan This tracks. It’s the best approach I’d come up with, too.
The only way I can surmise to reliably put the approval into the same terminal window as the agent is to own the shell.
This is the most insane shit I have ever seen. Look at all the possible skill folder installation locations
Why does IBM bob have its own skill folder?
What the hell is CodeArts Agent? Why can't they all use .agents??
Agents make mistakes every day. Here's one from today.
The great mistake we accepted was to put rules into context rather than deterministic guardrails. Rules are suggestions.
I want my agents to fly and --dangerously-skip-permissions.
I *think* if we capture the LLM Gateway and OS sandbox both, we can intercept everything we need for policy to let the agents off the leash.
Anyone taking this approach?