@s0 joins your team in Slack

For most of the last two years, working with an AI agent meant going somewhere to do it — a tab, a separate app, a workspace apart from the room where your team actually talks. You copied context in, copied results out, and spent the day translating between the conversation and the agent.

@s0 removes that seam. Mention it in a Slack thread and the Schema0 agent is simply there — reading the thread, picking up the task, and replying in the same place everyone else is already working.

The third shape of working with an agent

It helps to place this. The first way we used large models was a website you visited. The second was an app you installed on your machine. Both put the agent somewhere else — a destination you leave your work to go to.

The third shape is different in kind: a persistent, asynchronous teammate that lives inside the tools your organization already uses, carrying its own context, memory, and permissions. You don't visit it. You talk to it — the way you'd talk to anyone else on the team — and it works alongside you.

“The agent stops being a place you go and becomes a teammate you talk to — in the same thread as everyone else.”

Lewis Luu, Founder

What @s0 does in a thread

• Mention @s0 to start or change an app, ship a fix, or answer a question — it replies in-thread with a live preview or a deploy.
• It carries context across the workspace: the app it's building, its database, its past deploys, and the decisions your team already made.
• It works asynchronously — hand off a task, keep talking to your team, and come back to finished work.
• Everything happens in the open: the request, the reasoning, and the result all live in the thread, so the whole team stays in the loop.
• It respects your boundaries — channel membership, workspace isolation, and per-app secrets are enforced, not assumed.

The work that makes it feel like nothing

An agent only joins a team seamlessly once the unglamorous parts just work: the tools it can reach, the integrations it plugs into, the compute it runs on, the memory it keeps, and the security that holds every workspace apart. That is exactly the layer Schema0 already builds — a real backend, live sandboxes, sealed secrets, and a one-action deploy path — so @s0 shows up with hands, not just a voice.

@s0 for Slack is in private beta. If your team already lives in Slack, this is the most natural home we've found for an agent: not another tab, but the conversation itself — doing the work with you.