The AI coworker is a weekend project now

Viktor calls itself an AI employee. Martoshi is an AI coworker you tag in a Slack channel. Claude has its own Slack agent now too. Every one of them reads like a company you would need a year and a Series A to build. We built the same shape of thing this week, in one working session, as a directory of files. The category is thinner than the pricing pages make it look.

The category looks like a moat, and that is fair

Look at what they sell. Viktor gives each user a computer in the cloud that writes and runs code, wired to 3,200 tools, SOC 2 in the footer. Martoshi tags into a channel and drops back a PDF, a dashboard, an ad audit, over a thousand integrations behind it. It reads like platform. Isolated compute, persistent memory, an integrations team, a compliance page. From the outside the hard part looks like everything.

It is a fair read. That is genuinely what an AI coworker needs. The mistake is assuming you have to build all of it.

Most of that moat is now framework primitives

Eve is the tell. Vercel shipped it in mid-2026, a filesystem-first framework for durable agents, Apache-2.0 and still in beta. You do not wire an agent. You lay out a directory. agent/instructions.md is the system prompt. agent/channels/slack.ts is the Slack entry point. agent/tools/*.ts is one typed tool per file. agent/connections/*.ts is your integrations. Eve discovers the files at build time and compiles them into an app that runs on Vercel Functions. No registration code, no glue.

Sessions stream token by token, and they resume after a cold start or a deploy and pick up where they left off. That "his own computer in the cloud" bullet everyone markets? It is just the platform. It is the default.

This is the part that matched our stack so cleanly it felt like cheating. We already ship TypeScript on Vercel and talk MCP all day. Eve is native to all three. There was nothing to bridge.

The integration is one file

The scary number on every one of these pages is the integration count. Here is ours.

agent/connections/juma.ts is a defineMcpClientConnection pointed at our own MCP server, authed per user through Vercel Connect so every teammate links their own account. Connect is the quiet hero here. The OAuth dance, the per-user token exchange, the refresh, the callback route you always dread writing, it owns all of it and hands you a token when you ask for one. I never stood up an auth server. That one file gives the agent the whole surface of Juma: brand profiles, knowledge, projects, and the tools that generate on-brand decks, reports, and images. That is Martoshi's entire deliverable list, sourced from the product we already run.

This session we added a second file. agent/connections/linkedin.ts, a defineOpenAPIConnection with an inline spec and the w_member_social scope, so the agent can draft a post in Juma and publish it to LinkedIn with a human approval gate in front of the publish call. Wiring it was a file, not a project, because with Connect anything that speaks OAuth is one connector away. "3,200 integrations" is a number you reach one file at a time, and half of them are MCP servers already waiting to be pointed at.

What is actually hard is the part you already own

Strip away the Slack bot and the connectors and you are left with the only thing that was ever the product: what the agent knows. Martoshi's deliverables land because of the brand and campaign context behind them, not the channel they post in. Ours land because Juma holds our brand, our knowledge, our source of truth. The Slack agent is a thin shell around that context, and context is the new CMS.

The shell took an afternoon. The context took years, and it is the only part a competitor cannot clone by reading this post.

So the math flipped again, the same way it did when we deleted Jira. When the build cost of the surface collapses, the value moves entirely to what sits behind it. As of mid-2026, the surface is a weekend.

You do not hire the AI coworker anymore. If you own the context, you compile one, and you keep the keys.