Skip to Content
How-to guidesBuild and publish a stack

Build and publish a stack

Give your whole organization a ready-made environment for its agents. A stack is a bundle of packages plus the rules around them: the agent, its tools, the credentials it uses, the network baseline, and the compute sizes. You build it once and publish a version. Members then pick it in New manifest and start spaces from it.

Build a stack when a group of people needs the same setup: a “Backend Engineering” stack with Claude Code, GitHub, and your database tools, or a locked-down “Support Triage” stack that can reach only your ticketing system.

Before you start

  • You are an admin or owner. Only they build, publish, and unpublish stacks.
  • The packages you want are installed. In the left rail, open Marketplace, find each package on the Browse tab, and click Install with its version. The Installed tab lists what you have. See Marketplace packages.

Create the stack

  1. In the left rail, open Stacks, then click New stack.
  2. Enter a Name, for example “Backend Engineering”. Marshal makes the slug from it. You can change the slug later in the builder.
  3. Optional: choose an Owner.
  4. Click Create. The stack builder opens.

The builder saves your edits to a draft as you go. The header shows saving… and then saved.

Add packages

  1. Click + Add package, or + Add on a group such as Agent, Tools, or MCP servers.
  2. Search by name, description, or tool (for example gh or kubectl), and pick the package. Select all and Select none act on the filtered list.
  3. Include an agent, such as Claude Code. A manifest with no agent cannot launch a space.
  4. A package you add starts as included. To change it, open the package’s chip and choose under Presence how manifests get it:
    • optional: not included by default. Members can add it in the manifest editor.
    • included: every manifest from this stack gets it. Members can remove it.
    • required: every manifest gets it, and members cannot remove it.

Required cannot be removed. Included can be removed.

The credentials a stack needs come from its packages. They show on the stack’s card as Requires and Optional chips, so members know what to connect.

Set the stack-wide rules

  • Network: the baseline network policy for every manifest from this stack.
  • Compute: the sizes members may choose, and the default.
  • Tool guardrails, MCP guardrails, and the other guardrail groups: rules for what tools, MCP servers, and database connections may do.

To edit the name, description, or slug, click the stack’s name in the builder header.

Publish a version

  1. Click Publish v1 → in the header. Later versions show the next number.
  2. Optional: write Release notes. Members see them in the version history.
  3. Click Publish v1.

A published version never changes. Every manifest pinned to it keeps exactly these rules. To change the stack, edit the draft and publish the next version. Version numbers are never reused.

Give the stack to people

  • Open Automation and turn on Auto-seed new members. Every new member gets a manifest from this stack when they register.
  • In the same menu, Auto-upgrade modules republishes the stack when a module it uses gets a new patch or minor version, and Also update to new major versions lets it follow a major version your organization has installed. See Keep packages up to date automatically.
  • Open More stack actions and choose Push to members. Each current member without a manifest on this stack gets one. Existing manifests are never changed.

Manage versions

  • To change a stack, edit it and publish the next version.
  • Open More stack actions, then History, to see every published version with its notes.
  • In Version history, select Deprecate on an older version to hide it from new manifests. Existing manifests keep it.
  • Unpublish in More stack actions hides the whole stack from the new-manifest picker. Choose Republish to bring it back.

What you should see

  • The toast “Published v1.”
  • On the Stacks page, the stack’s card shows v1 latest. After more edits it also shows unpublished changes until you publish again.
  • Members see the stack under Stack in New manifest, with its versions under Version. See Create a manifest.

Next

Tell your members it is ready, and point them to Your first task.

Create a manifestInstall a package into a manifest