How to install a curated set of packs in one command

Use this when: You want to install a role’s whole toolkit or a repo’s full governance setup in one command instead of running agentbundle install --pack multiple times. Prerequisites: agentbundle CLI and a catalogue URI; see Prerequisites. Result: Every pack in the chosen profile installed at the correct scope for your agent.

Install a role’s whole toolkit, or a repo’s full governance setup, in one command instead of running install --pack N times. A profile is a first-party-curated, single-scope set of packs the catalogue ships ready to install.

Prerequisites

• The agentbundle CLI on your PATH (python -m pip install agentbundle, or the clone-and-pip route).
• A catalogue URI — a local checkout path or git+https://github.com/<owner>/<catalogue>.

Discover what’s available

agentbundle list-profiles <catalogue>

It prints each profile’s id, scope, and description. The profiles the catalogue ships today:

Profile	Scope	Installs
solution-architect	user	architect + desk-research + contracts — a solution architect’s portable toolkit, carried across every repo.
inception	user	desk-research + product-engineering + architect — the portable toolkit for taking an idea from zero to a buildable repo; use as much as the venture warrants. See Run a full inception.
full-ceremony	repo	core + governance-extras + product-documentation + monorepo-extras — a repo’s full governance setup.

Install a profile

agentbundle install --profile <name> <catalogue>

For example, to set up a repo’s full governance bundle:

agentbundle install --profile full-ceremony git+https://github.com/<owner>/<catalogue>

The command installs every pack in the profile at the profile’s declared scope, in the authored dependency-first order (so core lands before the packs that build on it), onto one adapter target. A pack already installed at that scope is left alone and reported already present, skipped. When it finishes, you get a per-pack summary of what was installed, skipped, or failed.

A profile install is never less safe than installing each pack by hand: it runs every pack’s preconditions — scope, dependencies, adapter, path confinement — before writing anything. If any pack can’t be installed, the command refuses before the first write and names the pack.

Pick the adapter

By default the install resolves one adapter for the whole batch the same way a single-pack install does (your configured adapter, else the auto-detected one, else the default). To pin a specific IDE for every pack in the profile:

agentbundle install --profile solution-architect <catalogue> --adapter codex

The adapter is applied to every pack. If one pack in the profile doesn’t support the chosen adapter, the command refuses before any write and suggests a compatible one.

Upgrade or remove later

A profile is a one-time convenience for installing a set — it is not recorded as an entity. To change versions or remove packs afterward, act on the individual packs with the normal verbs: agentbundle upgrade --pack <name> and agentbundle uninstall --pack <name>. There is no upgrade --profile or uninstall --profile.

Pitfalls

Caution

--profile and --pack are mutually exclusive. Pick one. To install a single pack, use --pack; to install a set, use --profile.

Caution

--scope is rejected with --profile. A profile declares its own scope in its manifest — solution-architect is user-scope, full-ceremony is repo-scope. You don’t (and can’t) choose the scope at install time.

Caution

A pack already installed at the other scope blocks the profile. Profiles are single-scope and won’t install the same pack across scopes. If a pack in the profile is already installed at the opposite scope, the command refuses and names it — uninstall it from that scope first, or install the remaining packs individually.

Caution

A partial install is not rolled back. On a genuine I/O failure mid-batch (a full disk, say), packs already written stay; the dependency-first order guarantees the installed prefix is still consistent, and the per-pack summary tells you exactly where it stopped. Re-running the command resumes — already-installed packs are skipped.

Related

• The pack catalogue — what packs and profiles are, and the two-scope model.
• Install routes — the install→adapt chain a profile install inherits per pack.
• How to upgrade an installed pack — the per-pack upgrade verb.
• How to ship your organization’s standard stack as a reusable pack — author the org pack a repo-scope profile installs.