axon install

Install a registry module into the agent project at the current directory. The command resolves the project from the working directory, so it is used directly as axon install rather than through a project-type subcommand.

axon install <id>
axon uninstall <id>

axon i is a shorthand for axon install — same command, same arguments.

axon i @axon/arxiv

<id> is the registry identifier, always scoped: @scope/name. Every artifact in the registry carries its scope as part of its identity, so a bare name resolves to nothing.

Installing exposes the module source as node_modules/@scope/name, merges its npm dependencies into the agent's package.json, and materializes them locally. Installed modules are discovered and plugged into the agent automatically; modules/ remains for local, relative-path modules.

If the module declares environment variable requirements, the CLI reports them. Local development values belong in the project's .env; deployed values are read from the agent project's .env on deploy.

axon install @acme/github
# → exposes source at node_modules/@acme/github/
# → merges dependencies
# → prints required environment keys

See Modules for the module authoring reference.

Options

axon uninstall

The mirror of install: removes a module from the agent in the current directory, or an extension from your profile.

axon uninstall @acme/github        # a module, from this agent
axon uninstall @axon/nord          # an extension, from your profile

Routed by what is being uninstalled, the same way install is — you name the thing, not the kind. What the profile DECLARES decides it: an extension it lists is an extension, and anything else is a module.