Product primitive
Realtime Channels
Send ephemeral realtime events bidirectionally between connected clients and services.
Move events that do not need to become durable state
Channels carry realtime events between connected participants. They fit messages and signals that matter while people or services are connected but do not, by themselves, define your application's persistent source of truth.
Common examples include chat messages, typing indicators, notifications, game actions, and events around a tool or background task.
Use Channels for live interaction
- Deliver a new chat message to the people viewing a conversation.
- Share a short-lived signal such as “typing” or “participant joined.”
- Send a notification or activity event to connected clients.
- Exchange events between an application service and a connected interface.
If an update needs to be part of the authoritative application state, your backend remains responsible for recording it. State is the Lynta primitive for syncing backend changes to connected clients.
Send signals around agent activity
An agent application can use realtime events to make messages, tool activity, or notifications visible to connected participants. Lynta carries those events; the application or agent service defines and handles them.
For a longer workflow with progress, participants, and human input, see Tasks.