Configure instance AI

​

Administrator: configure AI for the instance

Open Settings → Agents as an Instance Administrator. The workspace is split into three tabs so policy, runtime limits, governance, and usage are not mixed together. AI consumption is under Settings → Usage → AI. Select the timeframe there to compare usage with the preceding equal period and inspect tool, skill and plugin activity.

​

Global instructions

Configure global instructions under Settings → Agents → Instructions. Global instructions express stable organization-wide expectations, for example:

• use the tenant’s approved Components and plugins before ad-hoc alternatives;
• preserve backward compatibility for published Endpoints;
• redact customer identifiers from user-visible reports;
• validate changes in Sandbox before activation;
• return an operation identifier for production mutations.

The editor and runtime accept up to 12,000 characters per global instruction entry, preserving paragraphs and lists. Keep the text concise and policy-oriented. Product safety, authorization, approval rules, the current user’s explicit request, and exact execution results still take precedence.

​

Default plugins

Configure default plugins under Settings → Agents → Instructions. Select active registry plugins that should be available by default for AI work in the instance. Instance defaults and explicitly selected plugins remain subject to plugin status, capability policy, operation safety, permissions, and approval requirements. A disabled, deleted, unavailable, or policy-blocked plugin cannot become executable merely because it is configured as a default. Default plugin configuration accepts plugin IDs only. Put capability-specific guidance in an approved skill or package plugin. Use global instructions for organization-wide preferences, and keep tool schemas and authentication in the plugin definition. See Plugins for lifecycle, MCP synchronization, safety metadata, and attachment rules.

​

Runtime output limits

Configure the output ceiling under Settings → Agents → Runtime. The administrator can set the maximum output-token ceiling for AI execution from 10,240 to 128,000. This is an upper bound, not a target: individual models, tasks, and runtime policies can use less. Increasing the ceiling can help large code reviews or long structured deliverables, but it also increases latency and cost exposure. Prefer better task scope, references, and artifact workflows before raising it globally.

​

RevoEngine Docs preview

RevoEngine Docs is an opt-in preview under Settings → Agents → Runtime. It lets the Assistant search and read the current public product documentation. Use it when a task needs public documentation alongside the current instance configuration. Enable the preview when users need current official product guidance, design rationale, documented workflows, or citations. Documentation lookup can add several network calls and increase response latency. When the preview is disabled, documentation lookup is unavailable. The preview does not prove that a feature is deployed or permitted in the current instance. Exact contracts, permissions, and resource state still come from current platform tools. Public documentation queries must not contain private source code, records, identifiers, or credentials.

​

Other opt-in runtime features

The same Runtime tab exposes Programmatic Tool Calling and Studio sessions as separate previews. Programmatic Tool Calling lets supported AI workflows compose permitted tool calls with code; it does not grant new tool permissions. Studio sessions enables the shared draft, test and review workflow described in Studio sessions. These switches do not determine the stable status of Autonomous Agents. Enable only the workflow you intend to use and verify its prerequisites.

​

Memory policy

Configure memory under Settings → Agents → Memory policy. The tenant policy controls whether runtime recall is enabled, whether Agents can persist governed updates, and how much combined digest context can be supplied. The digest budget does not turn historical WORKSPACE records into an automatically recalled scope or replace the Autonomous Agent’s separate 20,000-token Memory field. Memory is selective. RevoEngine does not convert every answer, tool output, or conversation into durable memory. See Memory and workspaces.

​

Storage retention

Instance AI settings also define default retention for private database exports and Agent-created artifacts. Both accept 1–3,650 days. Expiration archives the file first; permanent removal remains governed by the instance garbage-collection policy. Use shorter retention for reproducible temporary exports and longer retention only when the artifact is required as durable operational evidence. An Agent can still select a more appropriate explicit lifecycle when policy and the Storage contract allow it.

​

AI security rules

Configure security guidance under Settings → Agents → Memory policy. Administrators can provide up to 8,000 characters of security guidance, selection terms, and blocked runtime tool names. Use this layer for tenant-wide restrictions such as credentials, customer data, regulated records, or forbidden external mutations. Security guidance complements—not replaces—roles, ACLs, service-account permissions, plugin safety metadata, and approval classification. Test both an allowed and a denied example after changing this configuration. Continue with assistant configuration.