Developer surface

APIs, packs, exports, and agent-facing tools.

The API

The app speaks an open workflow protocol on the wire — runs, events, capabilities — plus host-extension REST routes for app features. Capability discovery tells clients exactly what this deployment supports; nothing is advertised that is not honored.

Packs

Functionality ships as packs: node packs (workflow steps), agent packs (personas), artifact-type packs, workflow chains, and connection packs. Packs are versioned, signed, and installable from the marketplace.

MCP and external agents

An inbound tool server lets external AI clients — IDEs, desktop assistants — call selected capabilities as typed tools with per-user authorization. Documentation search, notebooks, and app-builder controls are exposed this way.

Exports and portability

What you build leaves with you: workflows export as portable definitions, the app builder emits real source code, documents export to standard formats, and data export covers your workspace’s records. Portability is a design rule, not an afterthought.