This is basically what dust is. It’s everywhere.

ETA: I said nothing about where I'm planning to host my SMTP server. Apple Mail is a provider-agnostic client-side application, like Thunderbird.

ETA2: Those who read TFA carefully will know that, even though this doesn't affect Workspace aliases, it does affect this feature (Send-As SMTP) for workspace accounts.

–Thomas Jefferson

Because models run for a long time autonomously developers need to manage more agents simultaneously. At that point you basically need a tracker for tasks in flux, and compute for each agent. It also means that the interactive monitoring isn’t as helpful anymore.

Regarding visibility, developers now think in high level architecture rather than lines of code, but implementation details are still important to document. We also want to understand when agents are hitting pain points. Both of these basically require archiving agent outputs more deeply than just code changes and commits.

What are people actually using to manage semi-collaborative agentic coding workflows nowadays? We've moved from on-dev-machine coding to @claude in GitHub, but of course GitHub purposefully weakens the capability of that approach to the point that it's kind of a hack. Github/Linear have somewhat more cohesive experiences but it still feels like tooling for agent teaming is quite lacking and unergonomic.

Coming from storing billions of rows in Clickhouse and performing dozens of materialized operations I shudder to think about what that would look like in a DB that doesn’t even support declarative IVM.