Skip to main content

​
Sub-agents

Under App Blueprint → Sub-agents, GenieForge stores focused AI helpers for jobs that need judgment but not a back-and-forth conversation: classify something, summarize records, or draft a report from data you already have. You describe the bounded job and who may trigger it; GenieForge wires the handoff.

​
Where it lives

App Blueprint → Sub-agents. Sub-agents are part of the blueprint. Runs use the selected project’s data and show up in Executions when they ran in the background.

​
How to verify

  1. Find it under App Blueprint → Sub-agents.
  2. Confirm inputs and which roles may call it.
  3. Trigger it from the flow that should own the handoff (page action, automation, or related capability).
  4. Check the result in project data and Executions if it ran in the background.

​
Limits and notes

  • They take inputs, do the work, and return a result. They cannot ask users questions mid-flight.
  • Declared inputs use the same formats as tools (email, phone, URL, date, datetime, UUID). Invalid inputs are rejected before the run.
  • Portal chat, scheduled automations, event hooks, background forms, and published sub-agents are runtime paths; they are not controlled by builder read-only mode. See Builder read-only mode.