Resolve a Connected Credential: Your Tools, the User's Token, No Token in Your Code
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.
KDCube Writing
Engineering deep dives, industry perspective, implementation notes, and practical recipes.
Search covers titles, summaries, tags and full article text.
Delegated MCP End to End: How an Agent Reaches a User's Account
My agents act on users' Gmail and Slack every day - external agents like Claude Code included - and none has ever held a provider token. Every access is something the user granted, granular and on demand, and it takes two acts they control: connect the account, and permit the agent. Here is the whole machine, fence by fence.
Authenticated MCP in KDCube: The Full Chain, Three Ways In
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.
The instruction your agent gets is computed from what it has
Switch a tool off and every trace of it leaves the agent's instruction — teaching blocks, protocol channels, catalog sections. One authority decides: the effective tool roster.
Telegram Channel Integration: One App, One Event Bus
How a KDCube app verifies Telegram webhooks, admits updates to its event lane, runs its configured agent, and delivers results back.
Governed Connections: Agents and Automations That Act as You
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.
Expose a Governed Service over MCP: Your Tools, the User's Accounts, No Tokens in Your Code
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.
One Agent, Three Instruction Sizes — Same Signals
The KDCube ReAct agent's full instruction body is ~24,800 tokens of battle-proven prose. It now has two distilled siblings — a moderate set at 40% and an extra-lite set at 30% — built by one discipline: enumerate every hard signal, then cut only the prose around it. The signal table is executable: it lives in tests that fail if a distillation loses a sing...
KDCube Architecture: Trust, Isolation, and Data Boundaries
KDCube architecture maps trusted apps, tenant and user scope, storage isolation, runtime fences, and split code execution.
The KDCube Application Lifecycle: Load, Reload, Build, and Evict
How KDCube loads, reloads, predeploys authorized widget assets, and cuts over app generations without rewriting in-flight work.
KDCube Application Integrations: Provide, Consume, and Guard Every Surface
How KDCube apps provide and consume API, MCP, named-service, connected-account, Telegram, UI, event, and job surfaces.
Application Data in KDCube: Where State Lives and How It Moves
A map of KDCube app state: authorities, storage homes, scoped addresses, delivery lanes, public projections, and execution boundaries.