Skip to main content

Convex integration

Convex hosts the canonical transcript, Agent execution, Workflow/Workpool jobs, memory derivations, policies, private storage and reactive invalidation signals.

Additive installation​

The CLI's backend install --plan resolves the host's actual functions directory and composes Cortex tables, components, authentication and HTTP routes. Unrelated host content remains owned by the host. Ambiguous schema/config/route merges fail before applying an unsafe replacement.

Source installation, development registration, trusted grant provisioning and application metadata are separate steps. Use backend setup; an installed source tree alone does not establish a current actor grant, model qualification or published Agent.

Public and internal contracts​

Public runtime endpoints verify host identity, current grants and resource scope. Internal orchestration uses pinned authority references and fresh effect/delivery checks. Operator-only maintenance stays internal or behind fixed administrative transport; do not expose a native handler to make an app call succeed.

The client uses official Convex authentication. Subscriptions carry opaque change markers; protected payloads are fetched freshly through guarded operations. Server-derived authorization deadlines invalidate late delivery and private views.

Storage and lifecycle​

Private file bytes use authenticated owned HTTP actions rather than public storage URLs. Workflow stages and retained output survive application disconnect. Revocation, epochs and tombstones fence stale work before commits and delivery. Optional external graph projection remains controlled by the Convex outbox.

Generated bindings are versioned for clean offline package builds. Building/typechecking does not deploy a backend; deployment is an explicit operator operation against a selected target.