Glossary
A reusable configuration: model, system prompt, tools, skills, MCP servers. Versioned. See Concepts → Agent and Configuration → Agent.
API key
Section titled “API key”Bearer token used to authenticate REST API and CLI calls. Created on the Console API Keys page. See REST API → Authentication.
Built-in toolset
Section titled “Built-in toolset”The shipped set of tools (bash, read, write, edit, glob, grep, web_fetch, web_search) referenced as agent_toolset_20260401. See Skills & Tools → Built-in tools.
Container
Section titled “Container”A Cloudflare Container instance, one per session, used to execute tools that need a real OS. Defined by the Environment. See Self-host → Overview.
DefaultHarness
Section titled “DefaultHarness”The shipped harness implementation, built on the ai SDK. Lives in apps/agent/src/harness/default.ts. See Concepts → Harness.
Durable Object (DO)
Section titled “Durable Object (DO)”Cloudflare primitive providing strong consistency and per-key state. openma uses SESSION_DO (per-session SQLite event log) and SANDBOX (per-session Container).
Environment
Section titled “Environment”Sandbox configuration: packages, network rules, base image. See Concepts → Environment.
Event log
Section titled “Event log”Append-only sequence of events for a session. Stored in SESSION_DO’s SQLite. The source of truth.
Harness
Section titled “Harness”The agent loop. Ships as DefaultHarness; pluggable via HarnessInterface. See Concepts → Harness.
Hosted
Section titled “Hosted”Refers to the openma SaaS at openma.dev, as opposed to self-host.
Integration
Section titled “Integration”A way to publish an agent into a third-party platform (Linear, GitHub, Slack). See Concepts → Integration and Custom Integrations.
IntegrationProvider
Section titled “IntegrationProvider”The interface every integration implements. Defined in packages/integrations-core/src/provider.ts. See Custom Integrations.
Model Context Protocol — open standard for connecting language models to tools. openma auto-generates mcp_<server>_<tool> for any registered MCP server. See Skills & Tools → MCP servers.
Memory store
Section titled “Memory store”Per-agent semantic memory backed by Vectorize + Workers AI embeddings. See Concepts → Memory Store.
Model card
Section titled “Model card”Bring-your-own-model config: provider, base URL, API key (Vault-backed), allowed models. See Reference → Model Cards.
Outbound proxy
Section titled “Outbound proxy”The egress proxy through which all sandbox HTTPS requests flow. Injects Vault credentials per-host so the model never sees raw secrets. See Concepts → Vault.
Publication
Section titled “Publication”A binding that says “this agent serves this workspace via this integration with these scopes.” See Console → Connect Integrations.
Self-host
Section titled “Self-host”Running openma on your own Cloudflare account, as opposed to the hosted SaaS.
Service binding
Section titled “Service binding”Cloudflare primitive for Worker-to-Worker calls without leaving the data plane. openma uses them for main → integrations, main → agent, etc.
Session
Section titled “Session”A single conversation, durable and resumable. See Concepts → Session.
Server-Sent Events. The transport for /v1/sessions/:id/events. See REST API → Stream session events.
Reusable prompt fragment + reference files mounted into the sandbox. See Concepts → Skill and Skills & Tools → Custom skills.
Tenant
Section titled “Tenant”A unit of multi-tenancy in openma. Created automatically on first user sign-in. See Self-host → Operations → Multi-tenancy.
Anything the model can call. Built-in, custom, or MCP-generated. See Concepts → Tool.
Trajectory
Section titled “Trajectory”The full record of a session’s events as a typed sequence. See docs/trajectory-v1-spec.md in the repo for the internal spec.
A credential store. Bound to specific hosts; injected by the outbound proxy. See Concepts → Vault.
Vectorize
Section titled “Vectorize”Cloudflare’s managed vector index. openma uses it to back Memory Stores.
Workers AI
Section titled “Workers AI”Cloudflare’s managed model service. openma uses it for memory embeddings (not for the agent loop itself — that goes through your configured Model Card).
Workspace bucket
Section titled “Workspace bucket”R2 bucket holding session-scoped files (/home/user/files/...).