I just launched Open Duet.
Your agents learn what matters to you, find useful work, and prepare it for your approval.
Run it with Claude Code or Codex.
last week I visited some labs in the valley to sell them our on prem browsers for their agents.
1 day later my engineers receive hiring emails from the same teams.
Is this how sales works in SF?
GPT-6 Astra is in its own league on our browser benchmark.
> Astra medium: 80.6
> Sol medium: 66.9
> Opus 5.5: 59.4
$8.87/task though 😅
@OpenAI we'd love this at Luna prices.
Introducing Agency. Never prompt again. AI prompts you 🫡
Get 100x more done. Your agent finds useful work. You approve.
> full context of your life with me.md
> catches things you forgot
> fixes issues before you see them
> never open Gmail, Chrome or Slack again
Runs locally, free and 100% OSS. New interface for everything.
⏩ Tell your agent: start Agency.
Today I launch an 24/7 recording iPhone app. So that your agents are not excluded from your live.
Astra installs it on your phone and sets it up.
It records in the background and syncs audio to your Mac, where local Whisper writes life . md so your agents have context of your life.
Open source + Codex setup skill:
I always wanted to set up an A/B test for our pricing page.
I knew you can do this with PostHog somehow.
Procrastinated on it.
But now that I trust Astra with Browser Use CLI I just told it to set it up in Posthog.
Now it's live.
Browser Use CLI solves the last mile for end-to-end automation.
Introducing: Browser Use agents support WebMCP 💯
> UI is made for humans
> Direct HTTP calls are made for agents
> WebMCP makes interaction 100% deterministic
No more flaky UI. Let's build the new web for web agents.
Open source is here one of the biggest advantages. If you don't have to hide your harness, your user-facing agent can have full access to its own codebase, and if there's a bug, it can just, in real time, fix it.
But if you are closed-source, then you need to hide your implementation, and the agent has no context and cannot fix it on the fly.
HOW TO FIX YOUR AI AGENTS (it's called "self-healing agents")
If you've run AI agents, you know they BREAK constantly.
The FIX is something called a "self healing" agent!
A normal agent hits a dead end and just stops, leaving you a half finished mess and that's why output sometimes isn't ideal.
BUT, a self-healing one hits the same wall and thinks "okay, that didn't work, let me try another way"
HOW TO BUILD SELF-HEALING AGENTS (4 steps):
1. Make it check its own work. After each step, the agent asks "is this what I expected?" instead of assuming it worked and moving ahead.
2. Have it name what broke. Not just "it failed," but which kind: the tool timed out, returned an error, came back empty, or gave a wrong answer. Wrap your tool calls so the error gets passed back to the agent, because it can only fix a failure it can actually see.
3. Match the fix to the failure. Glitch, retry it. Tool down, switch to a backup. Keeps failing, break the task smaller. Anything risky like money or deleting data, stop and ask you.
4. Make it log every fix. It writes down what broke and what worked, so it stops repeating the same mistake in a session, and you get a list of what to fix at the root.
That's it.
Now, you've got agents that fix themselves.
How many agents do you have right now running. yes, right now in this moment.
This is how productivity will be measured in the future.
0 to 1 is the biggest step from 1 to 10, and 10 to 100 is much easier.