I agree with this, and it's more approachable to less experienced users by serving a well thought out AI use case right by the tool itself. Agent chat feels more like an open-ended power user tool that puts more weight on the user to steer it well.
One UX hill I'm willing to die on: The best in-product AI features are task-oriented instead of open-ended chatboxes.
❌ "How can I help you today?" chatbox
✅ "Describe your desired outcome for [feature]" that's colocated with the actual feature itself
Chatboxes might still be good for getting high-level insights from your workspace, but shouldn't be front & center imho
Seeing the same in SMB segment. While a few power users learn to use Claude beyond a glorified Google search, building AI into the underlying tools and flows has a far greater effect without behavioral change.
This post resonated deeply with one of my core beliefs as an engineer and founder. It's all just systems, whether organizational, human or technical. Systems thinking can be applied to everything.
Agents aside, it's sad that they didn't give this enough love - it was never featured enough to replace our company inboxes, which would have been a killer feature given the Notion ecosystem (e.g. route to databases)
We’re winding down the Notion Mail inbox across web, desktop, and iOS on September 22.
We launched Notion Mail with a belief that your inbox should think like you—more personal to how you work and over time, more capable with AI.
As Notion agents have gotten more capable, we’ve seen more users hand off email workflows to them. Today, more than half of Notion Mail users manage emails without ever opening their inbox. So, we’re going all in on using agents to run your inbox.
We’re grateful to each and every one of you for building your routine around Notion Mail and trusting us with something that mattered as much as your email. More to come!
The Notion Mail Team.
We were so impressed by the @laravelphp Cloud CLI by @joetannenbaum that we built our own internal one: Core CLI.
It lets us share internal tooling + proxy sensitive actions through our Core backend so devs don’t need local secrets.
Meet our Core CLI:
@conductor_build a feature request - make it possible start agents in the root outside the worktree. For quick edits without the setup overhead. Using Claude CLI for this right now, but would be nice if I did not have to leave Conductor.
Finalizing the UI for our object translation solution✨ Multi-language support often feels like an afterthought – we're making it feel native to our platform instead.
Introducing Core — the composable operations layer for the AI era.
We've spent 15 years building operations inside real businesses. Today that work has a name: Core.
Connects your systems. Automates your workflows. Gives your team, your clients, and AI one place to operate.
@taylorotwell This is a great improvement! It would be amazing if you could expose it in an "billing API" too. We're building a platform where every tenant needs its own cloud resources. Currently "still" on Forge since this is a missing piece for us.
@lochieashcroft@mattpocockuk Thanks for sharing!
You said it used a lot of tokens, but I didn't find a number. How much did this experiment cost in Claude $ spend? Would be interesting to know as a reference point.
@jsnnsa Even without the IDE, they can continue to innovate on their web app to become *the* background agent orchestration platform - already using the current version a lot from Slack and mobile PWA