KDCube

Our Journal

Short, dated notes on capabilities that just landed in the platform.

25 articles · latest 2026-06-30

Search covers titles, summaries, tags and full article text.

Named services can now leave KDCube through a delegated MCP connector

The same named-service realm an in-platform agent reads internally, a user's own external agent can now read too — through one guarded MCP door, scoped to exactly what the user consented to. The durable memory realm ( mem ) is live today; task and cnv are the same pattern, not yet on MCP. This is the payoff of "portable memory": build the realm once, and ...

named-servicesmcpdelegated-credentialportable-memoryagent-portable-realms
2026-06-30

Connecting A Telegram Channel To KDCube Through Connection Hub

Field notes on the Telegram channel integration for KDCube Companion: a Telegram webhook for messages, a Telegram Mini App for UI, and Connection Hub linking the Telegram actor to a KDCube platform identity through an explicit edge. The Telegram actor stays telegram_ ; platform authority, economics, and identity-family are projected only through select...

connection-hubtelegrammini-appconnection-edgeidentity-family
2026-06-30

Find a realm by its name, not its address

The named-services discovery service is the registry that lets a consumer find and reach a namespace published by another app — by namespace, not by hardcoded address . An owner app publishes its complete current provider registry; consumers resolve an eligible provider for each request, across app packages.

named-servicesdiscoveryecosystemresolve-by-namespacecurrent-registry
2026-06-26

What the agent always sees: a live map of its workspace

The native KDCube ReAct Agent gets a live map of its disposable, distributed workspace: what is local now and what survives as a durable ref, so it can read, pull, or checkout by intent.

react-agentworkspacedistributed-runtimelive-viewread-pull-checkout
2026-06-22
← Newer21–25 of 25Older →