Skip to main content
Agents are programs that accept input, use tools and LLMs, and produce output. They range from simple prompt-driven assistants to deterministic TypeScript workflows. There are two ways to get agents into your workspace:

​
Install from the Agent Hub

The Agent Hub contains pre-built agents ready to use. Browse available agents from your workspace, install one, and start a session. No code required.
  1. Open your workspace at app.guild.ai
  2. Go to Agents and click Add agent
  3. Browse available agents, select one, and install it
The Browse tab shows the organization’s complete agent inventory—public, internal, and draft agents alike. State badges (public, internal, draft) indicate each agent’s visibility.
Agent descriptions shown in the user interface are generated automatically by AI. Guild displays these AI-generated descriptions in place of the static descriptions provided by an agent’s developer.
Installed agents are available to everyone in the workspace and can be run manually or via triggers.

​
Publish to the Agent Hub

To share an agent with your organization (so others can install it), publish a validated version from the CLI. See Publish to the Agent Hub.

​
Build your own

Build custom agents tailored to your team’s workflows. The simplest ones need no code at all; the rest use the Agent SDK.

Native agents

Write a prompt and pick tools. No code and no container — the quickest way to get an agent running.

TypeScript LLM agents

The TypeScript version: a system prompt plus tools, extended with attachments, typed input, or model preferences.

Auto-managed state agents

Write deterministic TypeScript with automatic state management. Best for algorithmic, cost-predictable workflows.

Self-managed state agents

Event-driven state machines with parallel tool calls and explicit state control. Most flexible, but more complex.

Goose agents

Describe the agent in a Goose recipe.yaml, with typed parameters and a response schema. No TypeScript.

OpenClaw agents

Write the agent as a Markdown workspace with skills. No TypeScript.
See Agent types for the full comparison. The quickstart walks through building and publishing your first agent in five minutes.

​
Spend budget

An agent can carry its own monthly spend budget, set from the Spend budget section in the agent’s settings. It works the same way as a workspace budget — admin-only, opt-in, a warning at 80% and a 429 block at 100% — and applies on top of the workspace’s budget, so a call is blocked when either ceiling is reached. See Spend budget for the full behavior.

​
Find agents with the command palette

Open the command palette with Cmd+K / Ctrl+K and search the agents scope by name or owner.

​
Disabling an agent

Archiving an agent removes it from every workspace it is installed in and stops it from running. Archived agents are excluded from agent listings, and new sessions cannot target them. No user can install or fork an archived agent—including the agent’s publisher—even with a direct link or version identifier. Archiving records who disabled the agent and when: To stop a single running session without disabling the agent, see Stopping a session. To pause automated runs without disabling the agent, deactivate the agent’s triggers.