Automate Your Team's Work with Managed Agents

Type runs managed agent automations for your team. An automation starts on its own, from a schedule, a Slack message, a GitHub event, a webhook, or an email. Then it does the job and posts the result where your team works.

You do not run servers, queues, or schedulers. You do not hold credentials in code. Type runs each automation in a Space, with the Space’s connections, skills, and memory.

One automation, four parts

Each automation comes with a managed agent: Claude or Codex, working in your Space. Each run can use any of these, alone or together.

Code

TypeScript that filters events, reads data, and makes changes. Fast, low cost, and the same result each time. Run code.

Skills

Your team’s reusable workflows and scripts. Write the method one time and use it in many automations. Use skills.

A managed agent

Claude or Codex, for research, writing, and decisions that need judgment. Run a managed agent.

A sandbox

An isolated Linux machine for shell commands, Git, the GitHub CLI, and scripts. Use the sandbox.

All together

Use each part for the work that fits it, in one automation. Code does the fixed steps, the sandbox does the system work, and the managed agent uses a skill for the judgment. Combine them all.

For example, a deploy-failure automation can work like this:

Slack: "deploy failed" in #ops
  └─ Code checks the message and replies with the runbook link.
  └─ Code reads the last CI run with the GitHub CLI in the sandbox.
  └─ The managed agent uses the team's incident skill to find the cause.
  └─ The managed agent posts the cause in the Slack thread.

Build this automation step by step.

What can start an automation

Trigger	Examples
Schedule	A daily report, a weekly review, a check every 15 minutes
Slack	A message with a keyword, a mention of Type, an emoji reaction
GitHub	A merged pull request, a failed CI run, a new issue
Linear	A new issue, a priority change, a project update
Webhook	An alert from Sentry, a payment, an event from your own system
Email and RSS	An email to the Space, a new post in a feed

Start in minutes

Create a Space for a team, and connect the tools that the team uses.
Describe the job to Type in the Space, for example “Every weekday at 9:00, summarize new support tickets.”
Select Test to see one run in a private thread.
Select Enable. The automation now runs on its own.

To write the automation in TypeScript, follow the Quickstart.

Where automations run

Automations belong to a Space. A Space is a shared computer for a department or a durable team. It holds the connections, skills, memory, and AI settings that the managed agent uses. Your team sees each run in the Space, and can continue the work in a shared thread.

Managed agent automations The four parts of a run, the two ways to build, and examples.

Spaces Shared computers that run Claude or Codex with a team's connections, skills, memory, and work.

Connections and skills Connect the tools and data that your team uses, and save reusable workflows.

Channels and threads Organize the work, and see each automation run in a shared thread.

Report a bug