We Keep On Trying
Four quiet months, but we never stopped. We are still refining conversations every day, and laying the parts you cannot see from outside: security, architecture, stability.
Four months have passed since we said hello in February. This page has been quiet, so here is where things stand. The short version: we are still building. Every day.
Conversation is still the center
An agent begins and ends with conversation. So the team still spends much of each day talking with agents. Does the answer stream without breaking, does it pick up the right tool at the right moment, does it keep its context through a long task. Every day we put each other’s agents to work, write down the awkward moments, and cross them off the list the next day. Before any showy feature, one conversation has to flow smoothly from start to finish, and we keep raising that bar.
Security first
Before you hand an agent your inbox and your calendar, there has to be trust. A large share of the past months went into security: how credentials are handled, how services authenticate to each other, where permission boundaries sit, and the mechanism that stops in front of a risky action. Sending mail or deleting data should make the agent ask a person first, and that question has to be enforced by the system, not requested by a prompt. These are hard to retrofit after launch, so we are building them into the foundation now.
An architecture that survives scale
One agent running and thousands running are different problems. We simplified the execution path and redrew the role and boundary of each service: the road that carries conversations, the place that runs them, and the place where records accumulate each got pulled apart and named. A structure raised slowly now costs less than a structure patched in a hurry later, so we put this work first even though it takes time.
The boring work of stabilization
Run the same scenario hundreds of times, find where it breaks, fix it, run it again. It is not the kind of work that produces screenshots, but most of how a product feels is decided here. Runs never getting lost. Failures never being swallowed in silence. Work continuing after the tab closes. We repeat until sentences like these become unremarkable. The spot that works a hundred times and slips once takes the longest, and we know the one slip is what a user remembers.
Groundwork for an ecosystem
We are also digging the foundations where connectors and skills will accumulate: a common frame for reaching external services, a format for packaging ways of working, a base others can build on later. The cheaper it gets to build one more connector, the faster an ecosystem grows, so we are spending time on the structure that makes the eleventh connector easier than the first ten. An ecosystem starts the day it opens, but its floor has to be laid before that day.
What comes next
A season of internal groundwork is also a season with little to show, and we are sorry about that. Still, we believe this is the right order. Next time something appears on this page, we hope to greet you with the product instead of a letter. We keep on trying.