Skip to main content

Message flow control and delivery

Parent concept​

Scope​

This page describes the operational mechanics around conversational flow once a message has entered a session: dedupe, debounce, queueing, loop control, outbound delivery, typing, and formatting.

Inbound dedupe​

Channels can redeliver the same inbound message after reconnects and retries. Tyrum prevents duplicate runs by deduping inbound deliveries before they enqueue work.

Dedupe is typically keyed by stable identifiers such as:

  • (channel, account_id, container_id, message_id)

Entries are durable and time-bounded so dedupe remains correct under clustered gateway edges.

Debounce and burst handling​

Rapid consecutive messages from the same sender/container are batched into a single agent turn using a per-container debounce window:

  • text-only bursts can be coalesced
  • attachments flush immediately
  • explicit control commands bypass debouncing

Queueing while a run is active​

When a run is already active for a (session_key, lane), Tyrum uses explicit queue modes:

  • collect
  • followup
  • steer
  • steer_backlog
  • interrupt

Queueing is durable, lane-aware, and bounded by caps and overflow policy.

Loop control​

Tyrum uses multiple layers of loop control:

  • per-turn step budgets
  • within-turn loop detection on repeated tool signatures
  • cross-turn repetition warnings
  • bounded session retention that is separate from execution limits

Outbound delivery​

Outbound messages to channels are side effects:

  • each send carries an idempotency key
  • risky sends remain approval-gated
  • provider receipts and failures are captured as audit events and, when useful, as artifacts

Operator clients receive the same state through typed event streams rather than connector-style message delivery.

Typing, streaming, and formatting​

Tyrum supports responsiveness features without weakening determinism:

  • block streaming for long replies
  • typing indicators with explicit start modes and bounded cadence
  • small pacing delays when a connector needs less bursty delivery

Markdown is chunked before connector-specific rendering so formatting does not break across delivery boundaries. See Markdown Formatting.

Constraints and edge cases​

  • queueing behavior must survive retries and restarts
  • steer and interrupt only apply at safe execution boundaries
  • non-interactive lanes should not emit typing by default
  • channel formatting caps must not silently truncate semantically important content without an observable fallback