- →Method A (Recommended): Download the Agency Agents desktop app → browse catalog → click Deploy for Claude Code.
- →Method B (CLI): Clone the repo, copy folders to
~/.claude/agents/. 3 commands, 90 seconds. - →Works on macOS, Windows, and Linux with WSL.
- →No API keys, no accounts, no cost. MIT license.
How to Install Agency Agents in Claude Code (2026)
Prerequisites
Before installing Agency Agents, you need Claude Code installed. If you don't have it yet:
Method A: Desktop App (Recommended)
The Agency Agents desktop app (agencyagents.app) is the easiest way to install, update, and manage agents across multiple tools. It's built with Tauri 2 (Rust + Svelte), is fully local-first, and has no telemetry.
Go to agencyagents.app and download for your platform:
- Apple Silicon (M1/M2/M3/M4):
Agency_Agents_x.x.x_aarch64.dmg - Intel Mac:
Agency_Agents_x.x.x_x64.dmg - Windows:
.exe installer(click More Info → Run anyway on SmartScreen) - Linux:
.deb,.rpm, or.AppImage
Or via Homebrew (macOS):
Launch Agency Agents. In the Agents Workspace, browse by division (Engineering, Design, Marketing...). Click any agent to preview the full persona definition before installing.
In the Tools Panel, confirm Claude Code is detected. The app auto-discovers it at ~/.claude/agents/. If not found, set the path manually.
Select individual agents or a full team preset (e.g., “Full Stack Team”, “Security Squad”) and click Deploy. The app copies the correctly rendered files to Claude Code's agents directory.
Method B: Manual CLI Installation
Prefer the command line? Here's the manual 3-command approach:
Verify Your Installation
Run this to confirm the agents are installed:
How to Use Agency Agents in Claude Code
Once installed, activate any agent in your Claude Code session by name:
“Activate Security Engineer mode and audit this authentication code for vulnerabilities.”
“Use the Frontend Developer agent to refactor this React component for better performance.”
“Act as the Data Engineer agent and help me design a PostgreSQL schema for this use case.”
/agents command in Claude Code to list all available agents and invoke them from the CLI directly.Project-Level Installation (Per Repo)
Instead of global installation, you can scope agents to a specific project. This is useful for monorepos with specialized roles:
Claude Code checks project-level agents first, then falls back to global. This means project agents override global ones with the same name.
FAQ
Where does Claude Code look for agent files?
Claude Code looks for agent Markdown files in ~/.claude/agents/ at the global level. For project-specific agents, place them in .claude/agents/ at the root of your project directory. Project-level agents take precedence over global ones.
Do I need to restart Claude Code after installing agents?
Typically no — Claude Code reads agent files dynamically. However, if you've just installed a large batch, starting a fresh session ensures everything is loaded correctly.
How do I use an agent once it's installed?
Simply invoke it by name in your Claude Code session. For example: 'Hey Claude, I need you to act as the Security Engineer agent and review this authentication code.' You can also use /agents in Claude Code to list all available agents.
Can I install only specific agents instead of everything?
Yes. You don't need to copy all 16 division folders. Just copy the specific agent .md files or entire division folders you want. Many developers start with just the engineering/ folder.
What's the difference between global and project-level installation?
Global agents (~/.claude/agents/) are available in all your Claude Code sessions. Project-level agents (.claude/agents/ in your repo) are only active when you're working in that project. Use project-level for specialized roles specific to one codebase.