Ask anything with the team already in the room.
Perception-first chat grounded in your Lifecycle Graph, wiki, and live integrations.
Where your team, workstreams, and agents meet.
The workspace hub above every workstream. Orient in plain English, see activity across the org, then hand off into governed execution.
In the hub
Orient with the team. Then open a workstream.
Shared room for the workspace - chat, activity, and workstream handoff on one surface.
See workstreams and activity without leaving Conflux.
Status, approvals, and the workstream list sit next to the same hub conversation.
Workspace hub
One place to get oriented before you execute.
Conflux is the shared room for the whole workspace - not another project thread. Ask across context, scan what is moving, then open a workstream when the work needs a canvas.
- Ask anything firstPerception-first chat for orientation - grounded in your Lifecycle Graph, wiki, and live integrations.
- Everyone is already hereWorkspace and org members land on the Conflux roster automatically - no invite choreography for the hub room.
- Hand off to workstreamsWhen intent is clear, spin up a workstream from the same conversation and move into Analyze, Action, Plan, or Reports.
Team chat that sits above the execution canvas.
Conflux keeps human collaboration and agent activity in one surface so operators do not lose the plot between Slack threads and agent runs.
Live activity across workstreams
See status, runs, and approvals move without hopping tabs for every canvas.
Share context without polluting runs
Attachments stay as chat cards in Conflux - display and discuss, not silent agent tool context.
Same governance perimeter
Orientation stays read-aware. Execution and write-backs still gate through workstreams and approvals.
Find what you need
Search the thread, the evidence, and the record.
Evidence, transcripts, and attachments stay in Conflux so you can retrieve what was said without reconstructing a Slack export.
Perception to action
Orient in Conflux. Execute in a workstream.
Conflux answers "what is going on?" Workstreams answer "get this done." Start a sync when the conversation needs to go live.
- Perception mode in the hubConflux general chat is perception-first - ask your business, cite sources, and decide what deserves a run.
- Workstreams for the mandateBrief a team, quote NTUs, collaborate on canvas, and release only when a human signs off.
- Sync live, keep the recordJump into a Conflux sync, then search the evidence and transcripts that landed from the room.
Hub conversations still feed the ecosystem.
Orientation, activity, and workstream launches sit inside the same Nimbus loop - wiki, connectors, agent teams, governance, and the Lifecycle Graph.
Grounded in your graph
Answers pull from institutional memory instead of a generic chat model with no tenant context.
Agents in the same orbit
Workstreams and agent teams stay one click away when Conflux surfaces a gap worth closing.
Audit-ready by design
Execution still lands in Decision History - Conflux is the front door, not a side channel around governance.
