Skip to main content
Agents are the entry point for AI and deep analysis in Honeydew. Each agent defines which domain the AI can access and which context it loads into analysis sessions.

​
Creating an Agent

Agents can be created in a few ways:
  • Honeydew Studio — use the agent builder in the UI
  • Git repository — commit a file to the ai/agents/ directory in your workspace
  • Coding agent — use a coding agent connected via MCP to create and manage agents (see MCP agent tools)
The Markdown body after the frontmatter is the agent’s AI context. It is injected into the prompt before every analysis session, giving the AI additional guidance specific to this agent — its purpose, analytical focus, or any constraints on how it should respond.

​
Context References

The context field accepts context item names and glob patterns. Items matching multiple patterns are deduplicated automatically.

​
Access Control

Users are granted access to specific agents. Access to an agent grants access to the underlying domain and all referenced context items. The same domain can be exposed through multiple agents with different context sets — for example, a finance-analyst agent and a sales-analyst agent can both access the revenue domain while loading different context.

​
YAML Schema

Each agent is defined by a Markdown file with YAML frontmatter in Git.
Fields:
  • type: Required. Must be agent
  • name: Required. Unique identifier for the agent within the workspace
  • display_name: Human-readable name shown in the UI
  • description: What this agent does
  • welcome_message: Text shown to users at the start of a session
  • sample_questions: Suggested questions; auto-generated in Honeydew Studio if empty
  • domain: Required. The domain the agent has access to
  • context: List of context item names or glob patterns (see Context References)
  • owner: Team or user responsible for this agent
  • model: Overrides the default LLM for deep analysis sessions started by this agent. Accepts a Honeydew model ID or a provider-specific model ID (e.g., claude-sonnet-4-6). When not set, the workspace default model is used. The model must be supported by the workspace’s LLM provider. Supported Honeydew model IDs: