Email isn’t going anywhere. It’s just going to get a whole lot better.
Introducing Sutro—an email client designed for people and their agents. Bring your own Claude, Codex, or OpenClaw agents and have them work with you directly in your inbox.
Wrote up more on how to play with zclaw:
- helpful local dev env. zclaw ships with tools for debugging & building (agents like 'em). https://t.co/D89bDqvOwV
- real use cases, serious & fun. and why they are interesting on a limited, physical board. https://t.co/JD3iC5ufWl
Do you guys do an evals or anything on the difference?
In practice we've found a basic Sentry CLI we built + Claude Code got us either identical or slightly better results; in rare cases Seer might do something marginally more correct, but not $40/mo/user more correct.
To be fair our issues aren't very complex, just curious how you're thinking about it
Introducing Agentation: a visual feedback tool for agents. Available now: ~npm i agentation
Click elements, add notes, copy markdown. Your agent gets element paths, selectors, positions, and everything else it needs to find and fix things.
Link to full docs below ↓
One reason vibe coding is so addictive is that you are always *almost* there but not 100% there. The agent implements an amazing feature and got maybe 10% of the thing wrong, and you are like "hey I can fix this if i just prompt it for 5 more mins"
And that was 5 hrs ago
@jeffzwang I ended up just building a thing as an internal tool, one click to turn anything in the inbox into a Claude Code task.
https://t.co/bVGGYbzwwH
Spent the weekend with Claude Code and Codex (5.2 xhigh, ofc) replacing Notion and Linear for our (tiny) 4-person team
We were hacking together something simple with a few complex tools. So I just built the simple thing we wanted.
- Markdown files are the datastore, all on a https://t.co/j47pFwxUnd volume, YAML frontmatter for structured data
- SOTA model agent loop
- Manage everything via Slack commands
- Notion-style web UI for writing
- Auth via GitHub
Spent the weekend with Claude Code and Codex (5.2 xhigh, ofc) replacing Notion and Linear for our (tiny) 4-person team
We were hacking together something simple with a few complex tools. So I just built the simple thing we wanted.
- Markdown files are the datastore, all on a https://t.co/j47pFwxUnd volume, YAML frontmatter for structured data
- SOTA model agent loop
- Manage everything via Slack commands
- Notion-style web UI for writing
- Auth via GitHub
Agents are *so* good at reading `--help` from a CLI and figuring out what to do.
I always wondered why people use `gh` for GitHub, now it's become my main interface to the product. I barely look at the app.
For any very frequent task I have just started writing CLIs and creating a Skill the agent can use.
- Explain the to agent what you want to do
- Ask it to create a README for the CLI
- Iterate on the README to ensure it will solve your use case
- Tell the agent to build the CLI
I have a Google Calendar CLI that powers my daily note in Obsidian; it took 15 minutes to build.
We've been exploring the value of letting agents use CLIs vs just navigating a REST API directly. The smartest models can do without a CLI, but take longer and cost more. Even small models can succeed when given CLIs. But the puck keeps moving!
This is a big deal. If AI is going to run everything, this is basically Mercedes admitting they can't build the engine and will use BMW’s instead. Siri had 15 years...
Opus 4.5 is incredible, but as always, let's not exaggerate. From a bug fix session where it got the fix wrong repeatedly:
> This is illuminating. The skill already has the exact example (lines 129-152) showing the comprehensive fix approach. I must have missed it.
@jakedahn@kepano I just run Claude code from my Vault directory and have slash commands, skills, etc. setup for my notes.
I had more complex stuff like cron jobs but it felt silly to try to automate too much