Describe the work,consider it done.

Build an agent with a role, a model, and the tools it needs. Chat with it directly — or put it on standing duty from Slack, forms, webhooks, or a schedule. More time for the work only you can do.

Use cases

What will you hand off first?

Work you could hand off this afternoon — equip an agent once, then delegate.

Slack

Issue triage

A GitHub issue lands — the agent reads it, checks the repo, replies in-thread, and labels it.

Schedule

Monday digest

Every Monday at 9, your agent searches the week's activity and posts a summary where the team will see it.

Form

Request intake

A shared form takes requests; the agent sorts and answers each one — and waits for your sign-off before anything big.

Build it

Build the agent. Delegate the work.

Give an agent a role, a model, and the tools of its trade. Publish it once: chat with it directly, or put it on standing duty.

Persona

Who it is

A role and a way of working, in plain language — “pragmatic senior engineer, reads before it writes.”

Model

How it thinks

Powerful for hard problems, balanced for everyday work, quick for the rest — the model and how hard it thinks it through.

Context

What it's equipped with

The connections and skills it works with — Linear, Notion, Sentry and more in a click, or bring your own.

TriggerWhen it happensA Slack mention, a form, a webhook, or a schedule.
AgentWho handles itOne of the agents you've built and published.
InstructionsWhat to doPlain language, with @refs into the trigger.

A workflow is a standing instruction — “watch these Slack messages and prepare a report.” Publish it instantly; when it fires, your agent gets the instructions and gets to work.

Copilot

Build it by talking.

Tell the copilot what you want changed, in plain language. It proposes the edit, shows you exactly what changes, and waits — you Apply or Dismiss. Nothing changes behind your back.

Triggers

Starts where you work.

One agent, five doors. Reach it from chat, Slack, a form, a webhook, or a schedule — wire up as many as you like.

ChatAsk it directly, any time.
WebhookAnything that can send a request can start a run.
FormShare a form — every submission starts a run.
SlackMention it, or message it directly.
ScheduleRuns itself — daily, weekly, whenever you set.
Agentanswers on every door
Reliability

It finishes what it starts.

Every step is saved the moment it happens. If the server running your agent dies mid-run, another picks up exactly where it left off — no lost work, no starting over.

Control

You stay in control.

The quiet guarantees that make it safe to hand real work to an agent.

Your team, with roles

Share a workspace with your team — roles decide who can build, run, and administer, with single sign-on if you use it.

Private credentials

The accounts and keys your agents use are encrypted at rest and never shown again — not in logs, not to the model.

No surprise changes

A running session keeps the exact version of the agent it started with. Publishing an update never breaks a run in flight.

You approve the big steps

An agent can pause and wait — for hours if it has to — until someone signs off, then pick up right where it stopped.

Your models, your rules

Powerful, balanced, or quick per agent — the model and how deeply it thinks, from the ones your workspace has approved.

Runs on your machines

Open source and self-hostable. Your keys and your data stay on infrastructure you control.

Under the hood: every agent you publish compiles into its own versioned, self-hosted process on a durable worker pool.Read the architecture →

Describe. Delegate. Done.

Your first agent is a conversation away. Open source, self-hostable, and ready to take work off your plate.