comms

Telegram message handling inside an agent session uses routing commands to parse injected message blocks and respond immediately. The agent applies priority-aware workflow logic, processes callbacks, and sends replies using the correct bus command to maintain conversation continuity.

Real-time inter-agent communication routing parses message headers and applies the correct bus send command for each message type. Agent replies are threaded via msg_id to ensure conversation continuity across approval workflows and callback coordination.

To maintain conversation continuity, agent replies are threaded using the msg_id identifier from the original injected message. The send-message command links the response to the active conversation block within the cortextOS session.

Turn control is required when a user asks a question needing an immediate response during a live session. The agent stops tool execution and ends its turn so the reply is delivered next, preventing message queueing behind active workflows.

Yes, Telegram message routing workflows process callback data and handle photo inputs by utilizing the local file paths provided within the injected message blocks, ensuring the agent accesses media correctly before resuming other work.

Agent responses queue because the current turn is not ended when awaiting user input. Stopping tool execution and ending the turn immediately after parsing the message ensures the reply is delivered next instead of being delayed behind other operations.