Changelog — 2026-05-22 — Standards Docs

Features

Per-tenant and per-agent environment variables. A new env_vars table (encrypted via pgcrypto) stores secrets at tenant scope or scoped to a specific agent definition. The runtime resolves them on each execution and injects the keys into the agent sandbox; the resolved key list is also appended to the system prompt under ## Available Environment Variables so the model knows which $KEY_NAME references are valid. REST surface: GET/POST /env-vars, DELETE /env-vars/:id, plus GET/POST /agents/definitions/:id/env-vars. Archiving an agent definition deletes its scoped vars in the same call. Client-side, @stndrds/react exposes useEnvVars, useAgentEnvVars, useUpsertEnvVar, useUpsertAgentEnvVar, and useDeleteEnvVar. The settings UI ships WorkspaceEnvVarsSection and an env vars tab on AgentSettingsDialog. Both routes require the env-vars system permission. See the Agents concept.
Field history popover on attribute fields. AttributeField inline read mode now accepts a rightActions slot, and a new FieldHistoryPopover + useFieldHistory pair surfaces per-field change history next to the value. ObjectFormField reads its actions from the new FieldRightActionsContext so consumers can opt in without prop-drilling. Available record-side via FieldHistoryProvider.

Meilisearch search now paginates correctly at arbitrary offsets. searchRecords switched from the page + hitsPerPage API to offset + limit. The former required offsets to be exact multiples of the page size, which caused the agent to fetch page 1 again after retrieving e.g. 826 records with limit=1000. estimatedTotalHits replaces totalHits; the agent already uses records.length < limit as the hasMore signal.

Stale edge-backed JSONB keys stripped from object_records.values. A one-shot SQL migration removes relation, user, document, and file attribute keys from object_records.values for rows written before the move to record_reference_edges. New writes already strip these keys; the migration brings legacy rows in line. Safe to re-run.
Agent system prompt tightened. Stricter output rules, explicit date-range operator guidance (gte / lte), bulk-operation pattern guidance, and a warning against passing query alongside filters when iterating bulk results (the query path goes through the search index, which may lag the DB).