Introducing Cursor for iOS.
Build from anywhere by launching always-on cloud agents. Or remotely control agents running on your computer from the app.
Composer 2.5 is 75% off in the app now through July 5.
Rogue AI agents.
The post-mortem on every agent incident this year reads the same: the agent had keys it shouldn't have had, and used them faster than anyone could revoke.
Vault-backed scoped access fixes the class of bug:
https://t.co/yreVBMU7Vz
https://t.co/bnPfzDU0FY
Production user testimonial from @SwissFares: keys are not flapping around exposed anymore, OIDC did not fight him. This is the feedback that compounds. More builders sharing setups in our TG: https://t.co/bnPfzDU0FY 🦞
@1clawAI The OIDC setup worked very smoothly and was much easier to configure than previous solutions.
For context, here’s more detail on my setup (I’d be happy to expand this into a proper case study if useful):
Internal Project
I run a small self-hosted observability stack in Zürich for several personal and DeFi-related side projects. The AI agents provide continuous monitoring of my infrastructure without requiring constant manual oversight.
Agent Responsibilities
- Real-time monitoring of Prometheus metrics (CPU/memory usage, service health queries, and API latency alerts).
- Pulling and analyzing Grafana dashboards for visual anomaly detection, such as unusual traffic patterns.
- Scanning Loki logs for error patterns, rate limits, and suspicious backend activity.
The agents operate on a local environment, periodically retrieving data and sending summaries via Telegram or a private channel. Prior to using 1clawAI, secret management was a significant concern, especially around potential leaks in prompts or logs.
With 1clawAI
- Workload identities and OIDC handle authentication cleanly on a per-agent basis.
- Secrets are securely vaulted and provided just-in-time, eliminating static keys.
- Initial setup took approximately 30–40 minutes, with automatic rotation and tight scoping.
Since switching, I’ve had zero exposure issues. I currently run 4–5 agents and plan to add more for improved notification routing.
I’m happy to share configuration snippets, exact Prometheus scrape configs, or any additional details for a case study. Appreciate the strong tool 🦞
@1clawAI worked out okay for my agents. Keys aren’t flapping around exposed anymore and the OIDC setup didn’t fight me. Decent if you’re dealing with that kinda thing 🦞
Threadguy says everybody is calling SpaceX on June 12th the 'guaranteed top' so why is nobody selling?
"Everything’s at an all-time highs. If you really believed that SpaceX was going to peak the market and you had 20 days, you're getting out right now"
"You're selling everything and you're sitting on the sidelines. That to me, as in how the market is trading, is pretty conflating with what everybody's saying"
"Every smart person I listen to says that SpaceX is going to top-tick the market. If everybody actually believed that, they would be selling right now. But they're not. Why aren't they selling? Well, what if it f*cking goes up?"
“Everybody's saying, Oh, SpaceX, that's the biggest IPO in history, it's over. I've seen a hundred of these clips, I can pull them off"