KDCube with agent frameworks
Keep the graph, crew, SDK agent, or custom loop. KDCube supplies the application boundary around it: authenticated turns, streaming, users, conversations, files, connections, economics, and deployable surfaces.
These layers combine
An agent framework decides how the agent works. KDCube operates the product in which that agent works. Settling an existing solution in KDCube is host integration, not a framework conversion.
| Framework keeps | KDCube adds around it |
|---|---|
| Graph, crew, loop, prompts, and domain behavior | Authenticated asynchronous turn execution and ordered delivery |
| Framework tool bindings and multi-agent semantics | App and agent tool, MCP, skill, and named-service configuration |
| Framework checkpoints, internal state, and agent-owned memory | User-facing conversation record, files, search, reload, and user memory |
| Framework-specific progress and output events | Stream adapter to chat, UI, API, event, job, and other app surfaces |
The four host seams
- Async turn seam: invoke one accepted turn without changing the framework's internal control flow.
- Stream adapter: map progress, files, and final output onto KDCube's ordered delivery contract.
- State-scope mapper: bind the authenticated user, conversation, turn, workspace, and framework thread consistently.
- Accounted service seam: route participating model and provider calls through the attributed runtime boundary.
That is the first useful finish line. Attachments, web access, generated-code execution, managed files, model choice, and multi-agent dispatch are optional connections, not prerequisites.
Examples inside this niche
LangGraph
Keep nodes, edges, checkpoints, interrupts, and graph-owned state. The adapter binds a KDCube turn and projects graph progress and output.
CrewAI
Keep agents, tasks, crews, flows, and their internal memory. KDCube hosts the crew behind application and conversation surfaces.
Claude Agent SDK
Keep the SDK loop, tools, and session model. KDCube provides the caller, conversation, delivery, and service boundary around it.
Custom agent loop
Keep the existing implementation and domain persistence. Add only the explicit seams needed to operate it as a KDCube app.
What the KDCube boundary contributes
- Application surfaces: an app may provide agents, REST, MCP, widgets, main views, events, jobs, cron, and public content, and consume tools, MCP, named services, jobs, and reactive events.
- Multi-user operation: turns are accepted under bound identity, ordered per conversation, streamed, recorded, searchable, and associated with hosted files.
- Connections and authority: per-agent delegated grants, connected-account consent, and server-side credentials remain outside model-supplied arguments.
- Economics: integrated model, embedding, web-search, and participating custom calls can be verified, reserved, accounted, and settled.
- Generated-code isolation: when an agent generates code, the reference split profile runs it in a separate networkless executor while trusted tools retain credentials and external authority.
Boundaries to preserve
- The framework's checkpoints and the KDCube conversation record remain separate stores with separate owners.
- A hosted adapter does not silently inherit KDCube native-agent rounds, governance, cache, memory, or live event-folding semantics.
- KDCube does not take ownership of the solution's domain database or internal working memory.
- Application backend code is trusted deployment code. Generated or otherwise untrusted code belongs to a separate, profile-dependent execution boundary.
- Reviewable operational records are not automatically immutable evidence or a compliance attestation.
Use the agent-framework matrix to compare framework capabilities. Use this page when the actual question is how a framework-based solution fits into the wider KDCube product runtime.
Sources reviewed
Reviewed 2 August 2026 against LangGraph's official overview, CrewAI's official documentation, KDCube's solution-settling recipe, hosted-agent conversation contract, shared agent harness contract, and security and trust model.