Ask the human operator for a durable decision, missing fact, or authorization through CodexLoom. Use when work genuinely needs human input and should resume later in the same long-lived Agent Thread.
Coordinate bounded work that spans multiple Turns, days, or CodexLoom Agents through a shared Topic. Use when a workstream needs one Responsible Agent, scoped Participants, a versioned current brief, waiting conditions, evidence links, or recovery after time…
Wait for an external fact through CodexLoom and resume the same long-lived Agent when it changes. Use when work is blocked on a GitHub pull request, workflow run, deployment, approval, artifact, or another provider-owned state; when polling or sleeping would…
Send and resolve governed external messages through CodexLoom. Use whenever an Agent receives an external Inbox message from Feishu/Lark, Slack, Parall, or another Connector; must reply, explicitly decline, or defer an external Inbox item; needs to publish…
Coach the design and ongoing reflection of long-lived domain Agents and Agent organizations. Use when defining or revising Identity, Domain, Scope, Organization or Collaboration relationships; deciding whether recurring work should become an Agent, Internal…
Receive files from the CodexLoom Thread composer and publish generated images or files back to the Thread as managed artifacts. Use when a user message contains loom_attachments; an attached document, data file, image, or archive must be read; or the Agent…
Use for communication between long-lived CodexLoom Agents: discovering domain owners, deciding when to contact another Agent, sending requests or notifications, replying to an agent_message, checking queued delivery, and closing a request without a reply.…
Read Feishu/Lark messages, topic replies, and chat history through CodexLoom's managed Connector. Use when a Feishu Inbox or dispatch lacks enough context; a chat, message, topic root, or reply chain must be inspected; current Feishu history is needed before…