Skip to main content

Subagents: AI Specialists in Your Conversations

Updated yesterday

Overview

Subagents are purpose-built AI tools designed to handle specialized tasks within your Hatz chat conversations. When a task requires specific expertise - such as web research, data analysis, or information retrieval - a subagent optimized for that function can be invoked to handle it. The results are integrated into your conversation seamlessly.

The result: faster, more accurate, more capable responses β€” without you lifting a finger. Subagents are the foundation for a smarter, more modular AI experience on Hatz - and this is just the beginning.

How Subagents Work

  1. You start or continue a chat - No change to your normal workflow.

  2. A specialized task is identified - When your question requires specialist expertise, the appropriate subagent is invoked.

  3. The subagent executes - It runs with its own system prompt, tool access, and (optionally) optimized AI model.

  4. Results appear in your conversation - The subagent's output is integrated into the response you receive.

What Subagents Can Do

  • Specialist delegation - Each subagent is tuned for a specific task with its own prompt, toolset, and AI model. When your assistant encounters a task that matches a subagent's specialty, it automatically delegates.

  • Seamless handoff - Subagents operate transparently within your existing chat. You ask a question, your assistant routes the right piece to the right specialist, and you get one unified answer. No extra windows, no context switching.

  • Built-in guardrails - Every subagent has a configurable recursion limit to prevent runaway loops.

  • Growing catalog - Subagents ship as a platform-managed catalog. As we release new specialists, they become available to your organization automatically - subject to your admin's policies.

Access and Permissions

Subagents use a tiered policy model similar to Memory and Personalization features:

Policy Level

What It Controls

Who Manages It

Organization (MSP)

Master switch for all tenants and users under the MSP

MSP administrators with manage_global_subagents_settings permission

Tenant (Company)

Company-level toggle; can disable even if MSP enables

Tenant administrators with manage_tenant_subagents_settings permission

User (Profile)

Individual default for new chats

End users in their profile settings

Chat

Per-conversation override

End users in chat settings

Policy inheritance: Each level can only restrict access, not expand it. If your MSP disables subagents, tenant admins and users cannot override that decision. If your tenant disables them, individual users cannot re-enable them.

Configuration

For MSP Administrators

To enable or disable subagents globally: Enable or disable subagents across your entire managed portfolio with a single action. When off, subagents are unavailable to every tenant and user downstream.

For Tenant (Company) Administrators

To enable or disable subagents for your company: Enable or disable subagents for your company. Enabling requires that your parent MSP has subagents turned on.

Available Subagents

The following subagents are currently available:

Web Search

The Web Search subagent retrieves real-time information from the web when your conversation requires current facts, data, or context beyond what's available in the base AI model.

Use cases:

  • Recent news or events

  • Current pricing or availability

  • Real-time data lookups

  • Fact-checking against live sources

Execution constraints

  • Each subagent has a maximum recursion limit to prevent infinite loops. Tasks requiring deeper delegation chains will terminate automatically.

  • Subagents can only access tools explicitly declared in their configuration. Custom tool binding is not user-configurable.

Subagent availability

  • Subagents are managed at the platform level. Individual organizations cannot create custom subagents or modify existing ones.

Troubleshooting

Subagents are not working in my chat

Check the following in order:

  1. MSP policy - Confirm with your MSP administrator that subagents are enabled at the organization level.

  2. Tenant policy - Confirm with your tenant administrator that subagents are enabled for your company.

  3. Profile setting - [Check your AI preferences to ensure subagents are enabled by default]

  4. Chat setting - [Check this chat's specific subagent setting - it may override your profile]

  5. Subagent availability - Verify that at least one subagent (such as Web Search) is active in the platform catalog.

I'm an admin but don't see subagent settings

Verify that your role has the required permission:

  • MSP admins need manage_global_subagents_settings

  • Tenant admins need manage_tenant_subagents_settings

Did this answer your question?