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):

curl -sSL https://raw.githubusercontent.com/soulcodex/agentic/main/install.sh | bash

Ensure ~/.local/bin is in your PATH:

export PATH="$HOME/.local/bin:$PATH"

Library Discovery¶

When you run agentic from any directory, it finds the library using this priority:

AGENTIC_REPO_ROOT environment variable
AGENTIC_ROOT environment variable (alias)
agentic_root key 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.

agentic deploy <profile> [target] <vendors> [options]

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 skills declared in the profile)

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. The target repo stays minimal: only config.yaml, profile.yaml, and project-skills/ are committed; fragments, skills, and vendor-files are live symlinks to the library. Run agentic sync to re-create broken symlinks.

compose¶

Assemble AGENTS.md from a profile without generating vendor files.

agentic compose <profile> [target] [options]

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.

agentic init [target] [options]

Argument	Required	Description
`target`	optional	Project directory, defaults to current directory

Option	Description
`--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/project-skills/

Examples:

agentic init
agentic init ./my-project
agentic init ./my-project --sync

Library recipe equivalent:

just init /path/to/project

switch¶

Switch active vendor(s) via symlinks.

agentic switch [target] <vendors>
agentic switch [target] list

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-specific behavior: - switch uses .agentic/vendor-files/cursor/switch-manifest.json to manage one or more Cursor rule paths (for example .cursor/rules, backend/.cursor/rules, ui/.cursor/rules). - If a managed Cursor rules path is a real directory, it is migrated to deterministic backups: <path>.backup, then <path>.backup.N. - If activation fails mid-switch, agentic rolls back to the prior symlink/config state.

Agents orchestration switching behavior: - Canonical generated outputs live under .agentic/agents/{provider}/. - agents are defined in .agentic/agents.yaml; provider-local subagents paths are created by switch. - Switching codex creates .codex/agents -> ../.agentic/agents/codex when available. - Switching opencode creates .opencode/agents -> ../.agentic/agents/opencode when available.

sync¶

Regenerate AGENTS.md and vendor files from the local .agentic/profile.yaml.

agentic sync [target]

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.

agentic list <resource>

Argument	Required	Description
`resource`	✅	Resource type to list: `profiles`, `skills`, `fragments`, or `vendors`

Examples:

agentic list profiles
agentic list skills
agentic list vendors

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