Commands - Guild

Every Guild CLI command follows the pattern guild <command> <subcommand>. Each command has its own reference page.

Command	Description
`guild auth`	Log in to Guild, log out, and inspect your authentication state.
`guild workspace`	Create, select, and manage workspaces, their agents, and their context.
`guild agent`	Build, test, publish, and manage agents.
`guild chat`	Chat with The Smith, Guild’s built-in support agent.
`guild session`	List and inspect sessions, their events, and their tasks.
`guild trigger`	Create and manage triggers that run agents automatically.
`guild factory`	Set up, start, inspect, and test a Software Factory.
`guild integration`	Build, version, and test custom integrations.
`guild llm`	Manage LLM credentials and model policies.
`guild skill`	Create and manage reusable skill packages.
`guild container-image`	Register and manage container images.
`guild runtime-environment`	Create, modify, and test runtime environments.
`guild api`	Call any Guild REST API endpoint directly.
`guild config`	Read and write global CLI configuration.
`guild doctor`	Diagnose problems with your Guild CLI setup.
`guild setup`	Install Guild skills for your coding assistant in the current project.
`guild version`	Show the Guild CLI version.

Global options

These options are accepted by every guild command.

Option	Description
`--mode <format>`	Output format: `interactive` (default), `json`, or `jsonl`. Use `json` or `jsonl` for machine-readable output in scripts and CI pipelines.
`--debug`	Enable debug mode with verbose logging.
`--quiet`, `-q`	Suppress progress and log messages, but keep warnings and errors.
`--non-interactive`	Disable interactive prompts, for CI, scripts, and coding agents.

--mode is read from the full command line, so it can go before or after the subcommand, and --mode=json works as well as --mode json:

guild --mode json agent list
guild agent list --mode json

--json is a hidden backward-compatible alias for --mode json. It still works but does not appear in guild --help. Use --mode json in new scripts.

Event filtering

guild chat, guild workspace chat, guild agent test, and guild session events accept --events <types> to choose which session event types to show. The flag requires a value.

Value	Shows
`user`	User-facing events. This is the default.
`system`	System and debug events only.
`all`	Both groups.
`none`	No events. On `guild session events`, `none` applies no filter and lists every event.
`<type>,<type>`	Only the named types, for example `agent_console,llm_start`.

Whatever you pass replaces the default entirely, so --events system hides user-facing events rather than adding to them. User events, shown by default: user_message, agent_notification_message, agent_notification_progress, agent_notification_error, container_log, credentials_request, agent_install_request, trigger_message, system_error System and debug events, hidden by default: agent_console, runtime_start, runtime_running, runtime_waiting, runtime_error, runtime_done, llm_start, llm_done These two groups mirror the Filter by type modal in the web UI.

​Global options

​Event filtering

Global options

Event filtering