Conversations and channels
DirectionWork with the same agent and company context in Continual, Slack, Teams, and other channels.
A conversation is an interface to the Company Runtime, not a separate copy of its context. The actor, project, branch, available tools, and work history determine what the agent can see and do.
One agent, many surfaces
People should be able to begin work in Continual, continue it in a connected channel, and review the resulting records and changes in the project. Channels carry conversation; the Company Runtime remains the source of business state and authority.
Choose the right surface
ConversationExplore, explain, draft, and handle ambiguous work.
Work queueResolve durable questions, exceptions, and approvals.
AppHandle visual, structured, spatial, or high-volume work.
External agentUse specialized clients through the project MCP interface.
Keep work durable
Conversation is useful context, but it is not the system of record. Material decisions become records or events. Pending judgment becomes a work item. Structural improvements become reviewed source changes.