Skip to content
Agents Pack

Eject and uninstall

Eject and uninstall

Section titled “Eject and uninstall”

Use eject to remove an initialized Agents Pack scope from a project or global home directory. Uninstalling the CLI is a separate step.

Eject managed content

Section titled “Eject managed content”

Always preview first:

Terminal window
agents-pack eject --dry-run

Then apply:

Terminal window
agents-pack eject --yes

What eject removes

Section titled “What eject removes”
  • official generated provider files and managed blocks;
  • user-generated provider copies;
  • the official installation configuration and lock; and
  • the user-generated output lock.

What eject preserves

Section titled “What eject preserves”

Canonical user-owned source under .agents-pack/user/ or ~/.agents-pack/user/. You can inspect, archive, or reuse it later.

When eject refuses

Section titled “When eject refuses”

Eject refuses to delete modified, missing, or malformed managed content. This is intentional: Agents Pack will not guess whether an unexpected edit is safe to discard. Resolve drift first — see Troubleshooting.

Scope conflict

Section titled “Scope conflict”

The current release supports one active scope at a time. If both global and the current repository are initialized, Agents Pack reports a scope conflict. Choose which installation should remain, move any user-owned canonical source you want to keep, and eject the other scope. See Repository vs global.

Uninstall the CLI

Section titled “Uninstall the CLI”

Removing the standalone executable does not eject managed project or global content. Run eject first if you also want to remove an initialized scope.

Default install location:

Terminal window
rm "$HOME/.local/bin/agents-pack"

If you installed with AGENTS_PACK_INSTALL_DIR, remove the executable from that directory instead. See Install the CLI.

Should repository-generated files be committed?

Section titled “Should repository-generated files be committed?”

Usually, yes — until you eject. Review and commit .agents-pack state, canonical user-owned source, and provider files so teammates and coding agents share the same setup. The user-level cache under ~/.agents-pack/cache/ should not be committed.

Section titled “Related”