Set environment variables during Agent creation
Environment variables are name/value configuration for a new Agent. Use them only for non-sensitive service URLs, project identifiers, and feature flags. Enter them in the additional environment variables section of the Agent creation form.
Use them for endpoints and settings the environment must read, including a local LLM endpoint verified during creation. Manage provider API keys and shared credentials through Credentials; copying them into several Agents' variables makes rotation and auditing difficult.
Add variables to a new Agent
- Open Agent → Add New Member and configure basic information and models.
- Expand the additional environment variables section near the bottom of the creation form.
- Select the add-variable action.
- Enter the variable name in KEY_NAME and its setting in the value field, then complete creation review.
Names must start with an uppercase letter or _, followed only by uppercase letters, digits, or _, such as ACME_PROJECT_ID or INTERNAL_API_URL. Values cannot consist only of whitespace.
The creation flow passes custom variables to Agent configuration. Users cannot override reserved platform keys such as AGENT_ID, organization identifiers, Gateway tokens, and internal API URLs. Selecting a local LLM sets OLLAMA_HOST from its connection information.
Verify after creation
Run a small test and verify the needed setting was read and the external connection works. This guide does not provide a procedure for editing existing Agents' variables. Do not call unexposed management APIs or pass secrets to bypass missing UI.
Keep passwords, API keys, access tokens, MFA and recovery codes, customer originals, bulk personal data, and shared provider credentials out of custom variables. Do not copy secrets already written in Chat, Task comments, or workspace instructions.
Variables configure behavior; they do not replace instructions. Put role rules in SOUL.md and tool conventions in TOOLS.md.
The current Portal exposes these fields for new Agent creation only. For an existing Agent, use the organization's approved creation or operational process to update its configuration.