Background sessions

Background apps activate without a live chat turn. State is held in background sessions (per user / app), routed by triggers and channels, and executed by digitorn-background + the daemon.

Session mode

runtime.session_mode	Meaning
mono (default)	One background session per user per app
multi	Up to max_sessions_per_user sessions

yaml

runtime:
  mode: background
  session_mode: multi
  max_sessions_per_user: 5
  max_concurrent_activations: 20

Wiring

1. Declare runtime.triggers and/or tools.channels.
2. Users create / fill sessions via the API / UI your deploy exposes.
3. Activations inject a message and run the entry agent.

Exact REST paths and payload fields: verify against the running daemon OpenAPI / internal/server and background service. Prefer Triggers and Channels for YAML.

Session wake-ups from an agent turn: scheduler.schedule.

Related

• Triggers
• Channels
• Primitives