Set up personal AI agents that join Squad sessions across projects. Manage their roles in a user configuration directory, inspect the combined team, and use agents that read project state and offer advice without writing to it.
User-level AI agents that travel with you across projects
Review the instructions the agent will receive before you install.
A personal squad is a user-level collection of AI agents that travel with you across projects. Unlike project agents (defined in a project's .squad/ directory), personal agents live in your global config directory and are automatically discovered when you start a squad session.
~/Library/Application Support/squad/personal-squad/ # macOS
~/.config/squad/personal-squad/ # Linux
%APPDATA%/squad/personal-squad/ # Windows
├── agents/
│ ├── {agent-name}/
│ │ ├── charter.md
│ │ └── history.md
│ └── ...
└── config.json # Optional: personal squad config
SQUAD_NO_PERSONAL=1 to disable ambient discoverysquad personal init — Bootstrap a personal squad directorysquad personal list — List your personal agentssquad personal add {name} --role {role} — Add a personal agentsquad personal remove {name} — Remove a personal agentsquad cast — Show the current session cast (project + personal)See templates/ghost-protocol.md for the full rules. Key points:
.squad/ stateOptional config.json in the personal squad directory:
{
"defaultModel": "auto",
"ghostProtocol": true,
"agents": {}
}
SQUAD_NO_PERSONAL — Set to any value to disable personal squad discoverySQUAD_PERSONAL_DIR — Override the default personal squad directory pathNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.
Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.
Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.
Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.