Core concepts

A workspace is the boundary for team memory, API keys, compliance policy, model access, usage limits, and analytics. The intended mental model is simple: a workspace should remember what the team has already done.

A session is a conversation or API/CLI activity stream inside a workspace. Sessions can come from the web UI or from external clients such as Claude CLI, Codex CLI, or direct API calls.

Memory is not just chat history. Conflux uses evidence, citations, tool activity, file changes, and user corrections to build durable knowledge that can help later users in the same workspace.

Context optimization is how Conflux handles long tool output, logs, diffs, test output, and context-window recovery without treating the user's current prompt as disposable. It is used for evidence readability, memory support, optional provider payload reduction, and retry after upstream context errors.