
Randomly stumbled upon @ThatsPranav's new email client today, but have to say that I'm pretty dang impressed. Super feature-rich and polished out of the gate. Check it → bloop.email
Raycast, but for your inbox. ⌘ + K. bloop.email Search is live. ⚡

Dad to four kiddos, Builder, @XMTP_ co-founder

Randomly stumbled upon @ThatsPranav's new email client today, but have to say that I'm pretty dang impressed. Super feature-rich and polished out of the gate. Check it → bloop.email
Raycast, but for your inbox. ⌘ + K. bloop.email Search is live. ⚡

Whoever did the naming for Claude Duet deserves high praise and a raise. Sonnet, Opus …Duet Duet → Do it Duet → user and agent as a pair Bravo 👏🏻
We’re opening a research preview of Claude Duet, a new app where Claude works as a proactive agent. It comes to you with what needs your attention, completes tasks you ask of it, keeps working when you step away, and checks with you before it acts on your behalf.

I really think Notion has got a lot going for it as a "system of record" for personal and company agents, and it's awesome to see all of the attention and effort going into making that a reality. The above are just a handful of things that could make the agent experience even better, so I felt compelled to write them up and send them on over. I've still got some more things to send your way, but will leave it there for now. As more big ones pop up, I'll just tack on another reply to this thread.

6. Externally connected agents have no Notion-native identifier in the system for use in People properties, comments, etc. With named personal agents, like Dots @ChatGPT, my @bot(s), or @muse, bringing them in as first-class actors would be huge on many levels. Especially now that MCP events exist…where perhaps an @ mention of them could trigger a routine on their end. Right now my best workaround has been to set up a separate agents database where they can be named, and @ mention those records. An external app watches for those mentions, and turns them into triggers for those same agents. But it's a lot of extra plumbing that doesn't easily scale, especially since those mentions can't be used in any People-type property.

5. "Last modified by" properties only capture account info, not whether changes happened by way of a connector. It can be helpful sometimes to distinguish between human edits, and delegated ones, for any number of reasons. Additional metadata could be exposed through the Last modified entry, or perhaps a "Last agent interaction" could be a new, separate column. Being able to see which connector, or even a self-described agent identifier, could really help with change tracking.

4. Database properties have no way to @ mention or link to them elsewhere in Notion. The fallback is just using text to describe them, e.g. "the Assignee property" which may or may longer be accurate or even exist. I run into this a ton, often when trying to build skills around using databases in my Notion setup. It's particularly challenging when I'm setting something new up, and drift starts to occur after a simple property rename. Hard coding the property identifier is also just as prone to failure modes too, since it also requires more info to contextualize it.

3. Agents can't see a page's history with the same level of fidelity as humans. The latest change history update is really fantastic…something I've wanted in Notion for years. Quip had something like this ages ago, but the latest Notion changes are very close to that. Giving agents the ability to traverse a page's history would help to close a big gap vs. a typical Git + markdown setup, especially in a multi-agent setup. Currently I've got agents writing an additional collapsible "Changelog" section directly into notes, or add entries to a dedicated changes DB to account for this.

2. Notion custom agents can be used as a value for a "People" property, but not as pre-filled for use in templates or automations. One use case for something like the above might be having an issues tracker, where certain types of issues (as a template) are always assigned to the same custom agent. Though there are plenty of other possibilities if that existed.

In June, @SamAsante and I launched Typeahead, the first product from our new company. Today we're releasing our next Mac app. It's called Beam, and we're live on Product Hunt. I've got Macs all over my house doing different work. Some run agents and local models. Others handle builds. When I want to use one app on another Mac, I usually end up navigating a whole second desktop through Screen Sharing. Beam brings that app's window onto the Mac I'm using. It gets its own Dock icon and shows up in ⌘Tab. I can type into it and resize it while everything keeps running on the other Mac. Sam has put a lot of care into making this feel natural. The video shows it better than I can explain it. Live on Product Hunt → producthunt.com/products/bea…

A step in the right direction for sure. I'm hoping they add support for @NotionHQ custom agents to use ChatGPT subs as that would easily 10x its usefulness to me.
ICYMI, we launched token sharing with ChatGPT earlier this week. Start in ChatGPT. Save the work to Notion where your team can see. Then keep going using your ChatGPT plan in Notion.

Copy/paste to your dot: From now on, prefix any Codex thread you create or take over with ⠕ (Braille “o”), e.g. “⠕ Fix login bug”. Keep tabs on its progress and proactively archive it once the work is complete, leaving threads with unfinished work or pending decisions open.

Dots in @ChatGPT can spin up and manage Codex threads to delegate tasks (on-device or cloud), and it's nice! My dot prefixes their threads with ⠕ so I can tell theirs apart from mine. (It's the braile "o"). You can try it out too, prompt shared below 👇🏻

Picking only 9 games from my childhood is basically an impossible task. So here's my pre-high school collection.

Not sure what's been happening w/ my @ChatGPT / Codex but it's burning tokens at an insane rate. I've got a Pro 20x account and yet this morning I went from 40% left to 1% in 90 minutes. Spent one of my banked resets and went from 100% to 30% in less than an hour. This, despite the app saying I've only used 110M tokens today. 1. I've usually got a few threads going at any time, which I've done for a long time. 2. I'm running some sessions w/ Astra Low with a bit of Astra Medium, then 5.6 Sol otherwise 3. No Blender, Computer Use, etc. at all. Just coding & docs work, and light browsing. 4. Not switching between models, or using my account in any other harnesses. I've halted all processes and feeling stuck…don't even know where to start with how to get this under control and I've already burnt an entire reset w/ this. Please help @thsottiaux @reach_vb @Dimillian

Ok, so I was only half-crazy. Turns out there is a reset available, but it's on the Grok app, not Grok @bot. Wish I could use the reset for bot!

Got the X MCP server up and running for my agents to use, then set up a @ChatGPT MCP tunnel so I can access it via the web too on ChatGPT.com and it's working smoothly! Need to get a writeup going on how to set this up next.