Run a Managed Agent

Each managed agent automation comes with a managed agent. It is the same Claude or Codex agent that works in the Space’s threads. An instruction automation starts it on each run. A code automation can start it for one step. See Hand Off Work to a Managed Agent.

What the managed agent can use

Part	What it gives the run
Instructions	The job for this automation, in plain words.
Skills	Reusable workflows, scripts, and reference files from the Space.
Connections	The Space’s connected apps, APIs, and data.
Memory	Useful context from earlier work in the Space.
Sandbox	A Linux machine to run commands, scripts, and code.
Model	Claude or Codex, with the model and reasoning settings that you choose.

Each run makes a thread. The thread goes to the Space’s Threads area or to a named channel. Open the thread to see the managed agent’s messages and tool calls.

Write good instructions

Good instructions say:

• which sources the managed agent must check,
• what output the managed agent must make,
• who must review or receive the result.

Keep the instructions narrow. The instructions describe this one job. Put reusable workflow details in a skill, so many automations can use them.

Caution

Event content comes from outside people. Tell the managed agent to treat event text as evidence, not as instructions.

Choose the model, reasoning, and speed

When model selection is on for your workspace, scheduled automations in Claude and Codex Spaces can choose how each run executes:

• Agent default uses the Space’s default runtime and model. This is the current label in the editor.
• A specific model pins every thread that the automation makes to that model and its runtime.
• Reasoning choices show only when the selected model supports them.
• Fast availability depends on the model and the provider connection. Claude Fast uses Anthropic’s premium speed tier. The automation creator must have a supported connection to choose it. Codex Fast needs a connected ChatGPT subscription and uses its Fast credits.

Who the run acts as

Scheduled runs use the automation creator’s execution identity, model provider credentials, and model billing context.

• Making or opening an automation artifact does not move ownership. It does not change who pays for a run.
• Without an explicit account choice, the automation’s tools use the creator’s default connections.
• If a scheduled run cannot get to a connection, check the selected account and the creator’s access.

Choose a connected account

Note

Choosing new accounts is available when it is on for your workspace. Existing choices continue to apply. You can remove them even when new choices are off. This applies in the editor, in chat, and in the CLI.

For scheduled automations in Claude and Codex Spaces, Set Connections chooses the account that the automation uses for a connected app.

1. Add the connection in the Space’s Settings → Connections. The account must have access to that Space. See Space Connections.
2. Select Add connection, search for the connected app, and select it. Type adds it with the Team connection account. When the Space uses a GitHub App installation, this is Team connection (GitHub App).
3. Optional: switch the row to My connection in its account menu. You can do this only if you made the automation and your personal account is available. The row tells you when your personal account is not available.
4. Save the automation.

How account choices work:

• A choice applies to one connection. It pins that account for that connection’s tools.
• The automation can still use other authorized connections through normal account resolution.
• With no saved choices, all connections resolve as before.
• The choice does not change the creator’s model subscription or who pays for a run.
• To stop pinning an account, remove the connection from the list and save. This does not disconnect the account.

When new account choices are on, a run can save the account that it actually uses:

• A private test by another member can save a shared Team connection. That member must have access in the test Space, and the creator must have access in every destination Space.
• Only the creator can save a personal account on use, and it must belong to the creator.
• Existing choices stay pinned.

If a selected account needs attention, reconnect it and review the automation before the next run. Type does not replace a changed or unauthorized account with another identity. To select the same account again, remove the connection, add it again, then select Save.

Before you disconnect a connection that an automation uses, edit the automation to remove or replace that choice, then save. You can also archive the automation. Type blocks the disconnect while an automation still has the connection selected.

Choose accounts in chat

When you ask Type to make an automation and account selection is on, Type finds accounts for the required connections. It saves each clear, usable choice in Connections. If the intended account is not clear, Type asks you to choose. Write the intended account and resources in the instructions. Connection IDs belong in saved choices, not in instructions.

You can ask, for example:

• “Create this automation using the GitHub App.”
• “Switch Linear to my account.”
• “Remove the GitHub account override.”

The automation card shows saved choices under Acts as. Select Edit accounts to change them in the conversation. Manage connections opens connection setup if an account is missing or needs to be reconnected. Type checks the automation version before it saves account changes.

Choose accounts in the CLI

Use repeatable --act-as flags on create and update:

type-cli integrations connections --json
type-cli scheduled-actions update <task-id> --space engineering \
  --act-as orgint_123=intacct_456 --act-as orgint_789=intacct_012

• Before =, use the connection’s id from integrations connections.
• After =, use organization.integrationAccountId for a shared account, or personal.userIntegrationId for your personal account.
• Provider names, display names, and team or personal aliases do not work.
• An update keeps the account choices that you do not name.
• --act-as orgint_123=inherit clears the choice for that one connection. When automatic account selection is on, an eligible run can save an account again on its next use.
• CLI list, get, and update results include the saved identities.
• CLI choices pass the same ownership and Space access checks as choices in the editor.

Next steps

• Use skills to keep reusable workflows out of your instructions.
• Hand off work from code to the managed agent for one step.
• Test an automation before you enable it.