Command Reference¶
CLI Overview¶
The agentic CLI provides a unified interface for managing agent instructions
across all your projects.
Installation¶
One-line install (installs to ~/.local/bin):
Ensure ~/.local/bin is in your PATH:
Library Discovery¶
When you run agentic from any directory, it finds the library using this priority:
AGENTIC_REPO_ROOTenvironment variableAGENTIC_ROOTenvironment variable (alias)agentic_rootkey in.agentic/config.yaml(walks up from current directory)- Install-time
LIBRARY_ROOT(embedded by installer) - Error with instructions
Target Auto-detection¶
Most commands accept an optional [target] argument. When omitted, agentic searches
for .agentic/config.yaml in the current directory or parent directories.
# Explicit target
agentic sync /path/to/my-project
# Auto-detected (run from within project)
cd /path/to/my-project
agentic sync
Commands¶
deploy¶
Full deployment pipeline: compose + vendor-gen + deploy skills + activate vendors.
| Argument | Required | Description |
|---|---|---|
profile |
✅ | Profile name — see agentic list profiles |
target |
optional | Project directory, auto-detected from current dir if omitted |
vendors |
✅ | Comma-separated vendors to activate: claude, copilot, gemini, codex, opencode, cursor |
| Option | Description |
|---|---|
--full |
Inline all fragment content into a monolithic AGENTS.md |
--link |
Use symlinks instead of file copies (POSIX only, not Windows without WSL) |
--skills LIST |
Deploy specific skills only (default: all library skills) |
Examples:
agentic deploy golang-hexagonal-cobra-cli ./my-cli claude
agentic deploy typescript-hexagonal-microservice . claude,copilot
agentic deploy python-fastapi-microservice gemini --full
Link mode (
--link): Creates POSIX symlinks instead of copying files — POSIX only, not supported on Windows without WSL. Runtime directories (.agentic/fragments/,.agentic/skills/,.agentic/vendor-files/) stay as live symlinks to the library and should be gitignored. Runagentic syncto re-create broken symlinks.
compose¶
Assemble AGENTS.md from a profile without generating vendor files.
| Argument | Required | Description |
|---|---|---|
profile |
✅ | Profile name — see agentic list profiles |
target |
optional | Project directory, auto-detected from current dir if omitted |
| Option | Description |
|---|---|
--full |
Inline all fragment content into a monolithic AGENTS.md |
--link |
Use symlinks instead of file copies (POSIX only, not Windows without WSL) |
Examples:
agentic compose golang-hexagonal-cobra-cli ./my-cli
agentic compose typescript-hexagonal-microservice --full
init¶
Scaffold a local .agentic/ skeleton for a custom profile workflow.
| Argument | Required | Description |
|---|---|---|
target |
optional | Project directory, defaults to current directory |
| Option | Description |
|---|---|
--link |
Initialize with deploy_mode: link so sync/deploy runs in symlink mode |
--sync |
Run agentic sync immediately after scaffolding |
--no-sync |
Skip sync after scaffolding |
Creates:
.agentic/config.yaml.agentic/profile.yaml.agentic/mcp.yaml.agentic/providers.yaml.agentic/agents.yaml.agentic/project-skills/
Examples:
agentic init
agentic init ./my-project
agentic init ./my-project --link
agentic init ./my-project --link --sync
agentic init ./my-project --sync
switch¶
Switch active vendor(s) via symlinks.
Examples:
agentic switch claude # Activate only Claude
agentic switch gemini # Activate only Gemini
agentic switch cursor # Activate only Cursor
agentic switch claude,copilot # Activate multiple vendors
agentic switch list # Show available vendors
Cursor switch behavior:
- Rule paths are driven by
.agentic/vendor-files/cursor/switch-manifest.json. - Managed paths can include
.cursor/rules,backend/.cursor/rules, andui/.cursor/rules. - If a managed path already exists as a real directory, it is migrated to:
<path>.backup, then<path>.backup.Non collisions. - If activation fails after mutations begin, switch rolls back to the prior symlink/config state.
Agents orchestration switch behavior:
- Canonical outputs are generated under
.agentic/agents/{provider}/. - Agent definitions come from
.agentic/agents.yaml. - Switch creates provider-local runtime paths only when provider outputs exist.
| Provider | Runtime path created by switch |
|---|---|
codex |
.codex/agents -> ../.agentic/agents/codex |
opencode |
.opencode/agents -> ../.agentic/agents/opencode |
sync¶
Regenerate AGENTS.md and vendor files from the local .agentic/profile.yaml.
Active vendors are preserved after regeneration.
Examples:
agentic sync # Auto-detect target from current directory
agentic sync ./my-project # Explicit target
During sync, MCP seeding uses .agentic/mcp.yaml.
If .agentic/agents.yaml is enabled, sync also regenerates .agentic/agents/ from that file.
list¶
List available resources.
| Argument | Required | Description |
|---|---|---|
resource |
✅ | Resource type to list: profiles, skills, fragments, or vendors |
Examples:
uninstall¶
Remove the agentic CLI binary from your PATH.
agentic uninstall # remove from ~/.local/bin (default)
agentic uninstall --global # remove from /usr/local/bin (requires sudo)
This removes only the CLI binary. The library directory (~/.local/share/agentic)
is left untouched — reinstall at any time with the one-line installer.
To fully remove the library: rm -rf ~/.local/share/agentic