How-to guides

Go from sign-in to an agent that fixes real issues, then put that work on autopilot. Each guide gets one task done in a few minutes and ends with What you should see, so you know it worked, and Next, so you know where to go.

New to Marshal? Start with Your first task.

Tags: admin or owner means you need that role. optional means the guide works once your administrator enables that feature.

Get started

• Your first task: use this when you want to see an agent fix an issue end to end, from connecting Claude to a pull request.
• Install the CLI: use this when you want to start spaces and runs from your terminal or a script.
• Add a Claude credential: use this when your agent needs access to Claude, with an API key or a setup token.
• Connect GitHub: use this when your agent should clone, push, and open pull requests.
• Connect AWS with SSO: use this when your agent needs the aws tool, with your company sign-in and no pasted keys.
• Set package settings for your organization: use this when everyone should connect a package with the same start URL and region. (admin)

Build your environment

• Create a manifest: use this when you want a saved recipe for identical spaces, one per repo or workflow.
• Build and publish a stack: use this when your teams need a new base environment to build manifests on. (admin)
• Install a package into a manifest: use this when your agent needs a new tool, agent, or MCP server. (admin installs, optional)
• Keep packages up to date automatically: use this when you want new patch and minor versions to reach your stacks and manifests without manual upgrades. (admin)
• Create a space from a manifest: use this when you want to work side by side with an agent, in the web or the CLI.
• Change a space’s size: use this when a build or test suite needs more CPU and memory.

Put agents to work

• Create a deputy and a mission: use this when you want an agent that does a repeatable job on its own. (optional)
• Start a run in the web and follow it: use this when you want to launch a mission and watch it work. (optional)
• Start and manage a run from the CLI: use this when you want to hand off a task from your terminal or a script. (optional)
• Steer a live run: use this when a run needs a correction, or you want to take over. (optional)
• Answer a question from a run: use this when an agent is waiting on your decision. (optional)
• Continue a finished run: use this when a run stopped short and you want it to carry on. (optional)
• Run a mission on a schedule or event: use this when work should start every night or when another system sends an event. (optional)

Stay in control

• Approve a blocked domain: use this when your agent needs to reach a host the network policy blocked.
• Archive and restore a space: use this when you want a tidy space list without losing work. (optional)
• Read the audit log: use this when you need to know who did what, and when.

Team and organization

• Invite a teammate: use this when someone new joins your team. (admin)
• Change a member’s role: use this when someone needs more or less access. (owner)
• Remove a member: use this when someone leaves your organization. (admin)
• Create and manage a team: use this when a group should own and share its own resources. (admin)
• Share a credential with a team: use this when your team should use a key without seeing it.
• Change the owner of a resource: use this when a credential, manifest, or stack needs a new home.
• Create an API key: use this when CI or a headless agent needs to call Marshal. (admin)
• Add an HTTP secret: use this when your agent calls an API that needs a token.
• Connect a vault: use this when your secrets already live in AWS, GCP, HashiCorp Vault, or 1Password.

Integrations

• Connect Slack: use this when your team should answer agents from Slack. (admin, optional)
• Use your own Slack app: use this when your security review needs Slack on an app your org owns. (admin, optional)
• Use your own GitHub App: use this when your security review needs GitHub on an app your org owns. (admin, optional)
• Set up OAuth on a custom MCP server: use this when your org’s own MCP server signs in with OAuth, such as Snowflake. (admin, optional)
• Create a webhook endpoint and rotate its secret: use this when your own systems should start work in Marshal. (admin for org-wide, optional)
• Start a run from a Linear issue: use this when labelled Linear issues should start work on a deputy. (optional)
• Connect an AI agent over MCP: use this when you want to run Marshal from Claude Code or Codex. (optional)

Need help?

See Help and fixes.