Skip to main content
Guild supports three agent execution architectures. Your choice determines the programming model, the files scaffolded at initialization, and how the agent transitions to READY.

TypeScript agents

TypeScript agents use the @guildai/agents-sdk to define behavior in code. After you save a version, the agent goes through a build and validation step before it transitions to READY. When you initialize a TypeScript agent, the scaffold includes:
Choose a starting template: See the Agent SDK for how to write TypeScript agent code.

Guild Native agents

Guild Native agents define behavior in Markdown files instead of TypeScript code. When you initialize a Guild Native agent, the scaffold includes:
  • PROMPT.md — defines the agent’s role, behavior, and instructions.
  • DESCRIPTION.md — provides a brief description of what the agent does.
Guild Native agents skip the build validation step. After initialization, the agent immediately transitions to READY.

Goose agents

Goose agents define behavior using a YAML recipe file. When you initialize a Goose agent, the scaffold includes:
  • recipe.yaml — defines the agent’s parameters, instructions, and response JSON schema.
Goose agents skip the build validation step. After initialization, the agent immediately transitions to READY.