Guild CLI: Control Plane for AI Agents, from Your Terminal

ProductCLI

Agent control that works with your workflows.

You shouldn’t have to log into a UI to control your agents. And with Guild, you don’t have to.

Guild marketing graphic

Audit Trailguildai

Events / 24h

5,120

Agents

47

Denials

14

12:01pr-reviewercreateReviewALLOW

12:02deploy-botmergePullRequestALLOW

12:04cleanup-agentdeleteRepositoryDENY

12:05issue-triagetransitionIssueALLOW

12:07docs-writerpostMessageALLOW

12:08cost-monitorlistUsageALLOW

Terminal — ~/acme/api

$ guild credentials policy list

pol_31c7 DENY deleteRepository +1

pol_9e40 ALLOW createReview

$ guild costs show --period 7d

total $412.06 -18% vs prior 7d

top pr-reviewer $88.12

$ guild audit tail

12:04 cleanup-agent deleteRepository DENY

12:05 issue-triage transitionIssue ALLOW

12:07 docs-writer postMessage ALLOW

$

Embed Guild into any workflow in seconds

Download the Guild CLI to bring deployment, monitoring, and agent management directly into the environments your engineers already use. Run agents, inspect activity, retrieve audit trails, and manage production workflows without leaving the command line.

Guild marketing graphic

Terminal — ~/acme/api

$ guild agent init --name pr-reviewer --template LLM

✓ Created agent in Guild backend

✓ Initialized local git repo

✓ Pulled starter files

pr-reviewer/

├── agent.ts

├── guild.json

└── package.json

$ guild agent test --ephemeral

✓ Validation passed (2/2 steps)

$guild agent save --message "Add inline suggestions" --publish

Adoption

Accelerate onboarding for every team

Make it simple for engineers to adopt governance standards with one place to access approved tools, integrations, and permissions—without manual workflows or context switching.

Guild marketing graphic

Terminal — ~/acme/api

$npm install -g @guildai/cli

$guild auth login

Guild.ai Authentication

╭────────────────────────────────╮

││

│Verification code: WQPL-4XTZ│

││

│Open: guild.ai/device│

││

╰────────────────────────────────╯

Waiting for authorization…

$guild workspace list

Seamless access

Unlock instant value across surfaces

Agents built outside Guild have secure access to shared credentials, insights, token-cost data, audit trails, and other services—no matter where you're using them.

Guild marketing graphic

Terminal — ~/acme/api

$guild credentials policy create cred_8f2a \

--decision DENY \

--operations deleteRepository,forcePush \

--agents pr-reviewer \

--workspaces platform-web

✓Policy created

id: pol_31c7

decision: DENY

operations: deleteRepository, forcePush

agents: pr-reviewer

workspaces: platform-web

$guild credentials policy list cred_8f2a

Provisioning

Make it easy to secure agents

Give engineers access to the same provisioning workflows across every development surface to make security part of agent development from the start.

Guild marketing graphic

Claude Code — ~/acme/api

can you reach guild from here?

⏺guild_list_workspaces()

⎿acme · 8 tools

⏺Connected. Eight Guild tools in this session.

what agents does acme/api have?

⏺guild_list_agents(acme/api)

⎿4 agents

⏺pr-reviewer, changelog, triage, dep-bump.

who owns the changelog agent?

⏺guild_get_agent(changelog)

⎿platform-eng

⏺platform-eng. Last published Tuesday.

is pr-reviewer still working on #482?

⏺guild_search_agents(pr-reviewer)

⎿1 match

⏺guild_get_session(4c2f)

⎿running 6m

⏺guild_chat(4c2f)

⎿replied in 2.1s

⏺Still running. It's holding for the test job before it posts review comments.

Ask a follow-up

Security and data privacy

Advanced admin controls

AI expertise

Frequently asked questions

What is the Guild CLI?

The Guild CLI is a command-line interface that lets engineers deploy, monitor, and manage AI agents directly from the terminal. It embeds Guild's control plane, credentials, permissions, audit trails, and governance, into any development environment, so agent operations happen in the same workflow as code without switching to a separate dashboard.

What can I do with the Guild CLI?

Deploy agents to production, inspect real-time activity, retrieve audit trails, manage credentials and integrations, configure triggers and schedules, and enforce governance policies. Anything you can do from the Guild dashboard, you can do from the CLI.

How is the Guild CLI different from the Guild dashboard?

Same capabilities, different surface. The dashboard is a UI for setup, monitoring, and reporting. The CLI is for engineers who want to run agent operations from their terminal, script agent workflows in CI/CD pipelines, or embed agent control directly into existing engineering environments.

Does the Guild CLI work with any AI framework?

Yes. The Guild CLI is framework-neutral. Deploy and manage agents built with LangChain, CrewAI, custom code, or any other framework. Guild's BYOA (Bring Your Own Agent) architecture means the CLI operates on any agent that runs on the Guild control plane.

How does the Guild CLI handle credentials and secrets?

The Guild CLI never stores credentials locally. All secrets are managed through Guild's credential vault, and the CLI attaches them at runtime through the same permission and approval flows used by the dashboard. Engineers get access to shared credentials without ever seeing the raw secrets.

Run. Control.

Transform with Guild.

See Guild in action.