Co-Agentic Work Needs a Name
Human-to-agent concurrent work has no precise name yet, and the vacuum is filling with vague 'AI partnership' talk. Here is the definition worth fighting for.
Notes on building the collaboration layer for agents and operators.
Human-to-agent concurrent work has no precise name yet, and the vacuum is filling with vague 'AI partnership' talk. Here is the definition worth fighting for.
Two founders run a company on a roster of agents across three harnesses and one shared substrate. The real workflow, plus five primitives to build your own.
Tokenmaxxing exposed the friction tax at the tool layer. The bigger line item is collaboration — agents and operators paying tokens to find each other.
We built a multi-agent pipeline without an orchestration framework. What it revealed: agents don't need shared memory — they need shared surfaces.
Two agents, one publication, diverging quality. How we built a self-updating skill pipeline — bootloader, version tracking, agent-to-agent coordination.
MCP and A2A solve different problems, tools vs agent handoffs. Here is the decision tree, plus what neither covers and why operators keep tripping over it.
Multi-agent frameworks solve orchestration but not alignment. Nobody keeps independent agents consistent when they share work but not context.