> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on a user's behalf in Guild, use the Guild REST API at https://api.guild.ai/v1.
> The OpenAPI spec is unauthenticated: https://docs.guild.ai/openapi.json (or openapi.yaml).
> Authenticate with an account API key, sent as HTTP Basic (key id as username, secret as password) or as `Authorization: Bearer <api_key_id>:<api_key_secret>`. See https://docs.guild.ai/api-reference/introduction#authentication.
> To run one agent on demand without account-wide access, use an API trigger instead: https://docs.guild.ai/platform/api-triggers.
> To act on Guild from an MCP client, connect to https://api.guild.ai/mcp (OAuth) or run `guild mcp` locally. Setup: https://docs.guild.ai/api-reference/mcp.
> To search these docs from an MCP client, connect to https://docs.guild.ai/mcp. The full page index is https://docs.guild.ai/llms.txt.

# Run Goose recipes as governed agents

> Goose recipes run on Guild without SDK code: typed interfaces, versioning, and governance underneath. Deploy your recipe in minutes.

Integrations · Goose

Goose is an open-source agent framework where the agent consists of a “recipe” of instructions, parameters, and a response schema, declared in YAML. Guild runs that recipe as a real agent without a line of SDK code. You supply `recipe.yaml`, Guild validates it at build time, derives typed input and output schemas from it, and runs it on a governed platform your whole team can call.

> **[Bring your recipe](https://app.guild.ai)**
>
> One YAML file in, a governed, versioned, callable agent out.

> **[Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)**
>
> See how teams run and govern Goose recipes in production.

## Your recipe is your agent’s DNA

A Goose recipe declares what the agent does, including instructions, acceptable parameters, and answer schemas. And that declaration is exactly what Guild needs. Parameters become a typed, validated input schema. A response `json_schema` becomes the output schema. The description becomes how your team finds it.

```yaml theme={null}
description: Review code with a configurable focus
instructions: You are a {{ language }} reviewer focused on {{ focus }}.
prompt: Review the code provided below.
parameters:
  - key: language
    input_type: select
    requirement: required
    description: Language under review
    options: [python, typescript]
```

That file, unchanged, is a Guild agent with an interface other people and other agents can call.

## How it works

**1. Initialize**

`guild agent init --name my-goose-agent --agent-type goose`. Or start from the web editor, which validates `recipe.yaml` as you type.

**2. Drop in your recipe**

Replace the template `recipe.yaml` with yours. Guild validates the whole file at build time and reports every issue at once, so a recipe that builds is a recipe that runs.

**3. Save and run**

Your recipe is now a versioned agent: typed inputs, a declared output schema, and a runtime anyone on the team can call. Publishing a new version is deliberate, and versions are immutable.

## Declaration in, governance out

Guild treats the recipe as the contract, and the platform enforces the rest. The model and provider are platform-controlled, so a recipe cannot pin its own: every model call routes through Guild's gateway under your policies, with spend attributed to the agent that made it. A recipe that declares its own extensions fails the build with a clear error instead of running half-wired in production. Credentials never enter the recipe, the container, or the prompt; they resolve server-side after the policy check. And when something misbehaves, any session can be stopped mid-run.

Two-thirds of organizations with agents had an agent-related incident last year. The recipes were rarely the problem. The runtime underneath them was.

## Frequently asked questions

> **Do I have to rewrite my Goose recipe for Guild?**
>
> No. You supply your `recipe.yaml` as it is. Guild validates it at build time and derives the agent's typed input and output schemas directly from it. No SDK code is required.

> **Which recipe fields does Guild honor?**
>
> `description`, `instructions`, `prompt`, `parameters`, `response` and `skills` are honored. `title`, `version`, `author` and `activities` are ignored. `extensions`, `settings`, `sub_recipes` and `retry` are rejected at build time with an error naming the field.
>
> The authoritative table is in [Goose agents](https://docs.guild.ai/guide/goose-agents.md#recipe-fields).

> **What happens to my recipe's extensions?**
>
> A recipe that declares extensions fails the build, on purpose. Running a recipe without the extensions it expects produces confusing behavior, so Guild tells you at build time, the earliest possible moment. Reusable capability comes through Guild skills instead.

> **Can my recipe choose its own model?**
>
> No, and that is the point. Provider and model are platform-controlled: calls route through Guild's gateway under your model policies, with spend attributed per agent. Your admins decide what models run, not each recipe file.

> **What happens if the agent misbehaves in production?**
>
> Stop any session mid-run. Disconnecting a credential immediately denies calls from sessions that are already running.

## Bring your first recipe

One YAML file in, a governed, versioned, callable agent out. Running in minutes.

> **[Bring your recipe](https://app.guild.ai)**
>
> Start from the web editor or the CLI.

> **[Book a demo](https://guild-ai.cal.com/gtm/meeting-with-guild.ai)**
>
> Walk through governance with the team.

## Related

**Also runs on Guild:** [OpenClaw](https://docs.guild.ai/integrations/openclaw) · [GitHub](https://docs.guild.ai/integrations/github.md) · [Slack](https://docs.guild.ai/integrations/slack.md) · [Splunk](https://docs.guild.ai/integrations/splunk.md)

**Read:** [the Goose launch post](https://www.guild.ai/blog/product/bring-your-own-agents-goose) · Docs: [Goose agents](https://docs.guild.ai/guide/goose-agents.md) · Glossary: [AI agent runtime](https://www.guild.ai/glossary/ai-agent-runtime) · [Agent control plane](https://www.guild.ai/glossary/agent-control-plane)