Short, dated notes on what just landed in the platform — one capability per entry.
Search covers titles, summaries, tags and full article text.
An agent writes Python; the code posts a file to Slack, sends an email, saves a memory. That code runs in a sealed sandbox — yet the call reaches the real service, under the real user, with real consent checks. The trick is a relay: the request rides KDCube's durable message lane to the service's home process and the answer rides back.
The ReAct agent writes Python; the code posts a file to Slack, sends an email, saves a memory. That code runs in a sealed sandbox — yet the call reaches the real service, under the real user, with real consent checks. The trick is a relay: the request rides KDCube's durable message lane to the service's home process and the answer rides back.
A tool call leaves the process — a subprocess, a sandboxed container, a remote task. What must follow it is not the infrastructure but the situation: who is asking, which app is acting, what the call may touch. KDCube packs that situation into one JSON-safe room, ships it across the boundary, and rebuilds everything else from descriptors on the other side.
An external agent has no chat turn — yet it must attach a file to an email, post one to Slack, and pull attachments out. KDCube gives it a waiting room: signed upload slots into a staging area inbound, signed download URLs outbound. Bytes travel over plain HTTP; tool calls stay JSON.
The platform keeps every durable user choice in one home — a per-user, per-app, per-key record store — under one contract: the admin's config grants the space; the user chooses within it . Every turn runs from the intersection.
KDCube users can now give their own scripts, agents, and DevOps jobs a bounded way to call KDCube — a short-lived bearer token scoped server-side by resource_grants . The automation acts as a delegated client while KDCube projects the approving user as the grantor.
App content was visible to humans, invisible to crawlers — SPA shells with no title, body, or structured data. This entry records the new public content surface: an app declares an alias and publishes items into a registry; the platform serves crawlable pages, JSON-LD, canonical/OG metadata, and a per-alias sitemap.xml — runtime-updated, no rebuilds — and...
Field notes from making a KDCube named service — conversations ( conv ) — usable by Claude Code as an external agent over the managed named_services MCP surface. What bit us once a real agent started calling it: binary files returned as base64 blew the model's context, so they now come back as a short-lived download link ; and refs had to be made self-con...
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...
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_<id> ; platform authority, economics, and identity-family are projected only through sele...