Task-oriented guides with concrete setup steps and verification.
Search covers titles, summaries, tags and full article text.
A teammate opens a browser, asks the resident agent to change a file in a git-backed store, watches the work happen as steps, reviews the diff on a desk beside the chat, and commits — under their own identity, with only the capabilities they granted.
Run multiple websites locally on one KDCube, route each by alias or host, and expose the same routes through ngrok.
Configure API, MCP, and widget enablement, visibility, auth, and API CSRF from code defaults, descriptors, or the Apps dashboard.
How a service resolves the approving user's connected credential through the Connection Hub broker - per call, at the trusted boundary, no token in your code.
One chain of configuration, written once. An app declares a protected MCP door; Connection Hub declares what may be delegated there and to whom; the provider behind the door declares which user accounts back its work; and every call crosses two gates before a real credential resolves at the trusted boundary.
Route every caller — a resident agent, an external app, an unattended automation — through one registry, each a small revocable grant bound to specific accounts and permissions.
One KDCube app exposes its functionality over a governed MCP door; its tools act on a user's accounts and your own OAuth-protected server, while Connection Hub authorizes every call and your code never touches a token.
Host your working agent — LangGraph, CrewAI, a raw loop — as a KDCube app with its framework intact. The wrap is a thin async host layer, not a rewrite.
One small, production-shaped KDCube app — surface, contracts, identity, state, tests, release. Twelve stamped operations, from app card to shipped.
One app consumes a narrowly allow-listed MCP service, exposes its own governed tools, and hands automations expiring access — credentials never travel.