Repository vs global

Agents Pack supports two installation scopes. You choose one during agents-pack init.

Repository scope

Choose repository scope when the instructions and capabilities belong to one project.

--scope repository

Agents Pack finds the nearest Git repository root. If there is no Git root, it uses the current directory. State is stored under:

.agents-pack/

The generated provider files are also inside the repository. Review them and normally commit them with the rest of the project so teammates and coding agents receive the same setup.

Repository scope supports Claude Code, Codex, and Cursor.

Global scope

Choose global scope when you want the same baseline available across projects:

--scope global

State is stored under:

~/.agents-pack/

Global scope currently supports Claude Code and Codex. Global Cursor instructions are not supported. Selecting Cursor with global scope stops before writing anything. Use Cursor in repository scope, or initialize global scope for Claude Code and Codex only.

Do not install both scopes at the same time

The current lifecycle intentionally supports one active Agents Pack scope at a time. If both global and the current repository are initialized, Agents Pack reports a scope conflict instead of guessing which one should win.

Start with repository scope if you are unsure. It is easier to inspect, commit, and remove without affecting unrelated projects.

Where files live

Scope	State and user source	Provider output
Repository	.agents-pack/ (canonical user content under .agents-pack/user/)	Native paths inside the repository (for example .claude/, AGENTS.md, .cursor/)
Global	~/.agents-pack/ (canonical user content under ~/.agents-pack/user/)	Corresponding locations under your home directory

The shared pack cache lives under ~/.agents-pack/cache/packs/ for both scopes. That cache should not be committed with a repository.

MCP servers are separate from content scope

The agents-pack mcp workflow always manages provider configuration at the user or machine level. It does not belong to repository scope or global content scope, and it does not require agents-pack init.

This means you can add one remote MCP server for Claude Code, Codex, and Cursor without changing any project files. See Manage MCP servers.

For ownership of official vs user-owned content, see Ownership. For a fuller path map, see File layout.

Next steps

• Initialize with the scope you chose
• First workflows after a clean install