Assign a supervisor for this agent and configure automated daily status briefings across email, WhatsApp, or Telegram.
Every agent can have a manager — someone it reports to. This can be another AI agent in your organization or a real person (via their email address). When a manager is assigned, the agent knows who to escalate issues to and who receives its daily status updates.
The Daily Catch-Up is an automated briefing the agent sends to its manager at a scheduled time each day. It covers what the agent accomplished, any issues it encountered, and upcoming tasks. Think of it as a morning standup, but your AI sends it automatically.
The Manager & Daily Catch-Up section edits two top-level config keys on the agent:
config.manager — An object with type ("internal" or "external"), plus agentId for internal or name/email for external.config.dailyCatchUp — An object with enabled, time (HH:MM), timezone (IANA), and platform ("email", "whatsapp", or "telegram").For external managers, messaging platform identities (WhatsApp number, Telegram ID) are stored under config.messagingChannels.managerIdentity. This lets the agent recognize the manager across multiple communication channels with full trust.
Saves are sent via hot-update (POST /agents/:id/hot-update) if the agent is running, or via config patch (PATCH /agents/:id/config) if stopped. Legacy support maps config.managerId to the new config.manager.agentId format.
There are three options for the manager assignment:
The agent operates independently. Escalations go to the system admin. Daily catch-ups have no recipient (a warning is shown if catch-up is enabled without a manager).
Another AI agent in your organization supervises this one. The supervisor agent receives escalations, status reports, and daily catch-ups. This creates a reporting hierarchy between agents — useful for multi-agent workflows where a coordinator agent oversees specialist agents.
The dropdown lists all agents in the organization except the current one (an agent cannot be its own manager). Each entry shows the agent's display name and role.
A real person outside the system — identified by name and email address. The agent sends reports, catch-ups, and escalations to this person. Additional fields let you specify the manager's WhatsApp number and Telegram ID so the agent can recognize them across messaging platforms.
When you choose an external manager, you can optionally provide:
+1234567890). Enables the agent to send catch-ups via WhatsApp and recognize the manager in WhatsApp conversations.@userinfobot). Enables Telegram-based catch-ups and recognition.These identities are stored under config.messagingChannels.managerIdentity and allow the agent to establish trust with the manager across platforms — the agent knows that messages from these accounts carry managerial authority.
When selecting an internal manager, the agent's config.manager is set to:
{
"type": "internal",
"agentId": "selected-agent-id"
}For backward compatibility, the legacy config.managerId field is also set. The resolveManager() function handles both formats, looking up the agent's display name from the full agent list.
The daily catch-up is an automated status briefing. When enabled, the agent sends a structured update to its manager covering:
Configuration fields:
09:00).The available delivery platforms depend on your configuration:
The system includes 30+ pre-configured IANA timezones covering major business centers worldwide. The catch-up is scheduled according to the selected timezone — if you set 09:00 in America/New_York, it fires at 9 AM Eastern regardless of where the server runs. The default timezone is America/New_York.
Email is the most reliable delivery platform and requires no additional setup. Start with email catch-ups, then add WhatsApp or Telegram once you've verified the agent's reporting is useful.
Set the catch-up timezone to the manager's local timezone, not the agent's server timezone. A catch-up arriving at 9 AM in the manager's morning is far more useful than one arriving at 3 AM.
When running multiple agents, assign a coordinator agent as the manager for specialist agents. The coordinator receives all catch-ups and can synthesize a summary for the human owner — reducing notification fatigue.
A catch-up without a manager has no recipient. The dashboard warns you about this, but it's best to assign the manager first, then enable the catch-up.
Check that a manager is assigned. If the manager type is "No manager," the catch-up has no recipient. Also verify the manager's email address is correct for external managers.
Ensure the manager's messaging identity (phone number or Telegram ID) is set in the external manager configuration. Also check that the corresponding messaging channel is configured in the agent's Channels tab.
If the agent is running, saves use hot-update. If the hot-update endpoint fails, try stopping the agent, saving, then restarting. Also check that required fields (name and email for external managers, or agent selection for internal) are filled in.
Older configurations may use config.managerId instead of config.manager.agentId. The resolveManager() function handles both, but saving the form will migrate to the new format automatically.
Double-check the timezone setting. The time is interpreted in the selected timezone, not UTC or the server's local time. Ensure you've selected the correct IANA timezone from the dropdown.