What belongs in this section?
Use it for runtime environment variables and similar configuration that should be applied through the dashboard restart flow.
Feature
Manage OpenClaw environment variables in the dashboard
Edit runtime variables from the dashboard and apply them through a managed restart instead of patching config by hand.
Environment settings are editable in the dashboard with row-based key/value controls. Save actions trigger a managed restart so your OpenClaw runtime picks up changes safely and predictably.
What you can do
- Add, edit, and remove environment variables in a structured UI.
- See unsaved-change state before applying updates.
- Use a controlled restart flow instead of ad-hoc shell edits.
- Keep runtime configuration changes readable for operators.
Real product screenshot
What you manage here
This view is for non-secret runtime configuration that belongs at the environment-variable level. You can update values, review pending changes, and apply them with a controlled restart.
That workflow keeps the configuration model readable for operators who want confidence about what changed and when it was rolled out.
- Where environment variables are edited
- What happens after save
- Which values belong here vs secret/provider flows
- How to validate a change after restart
Why this is easier than shell edits
Environment variables are easy to get wrong when the only interface is a shell or a scattered set of config files. A dashboard flow reduces that risk by showing the full change in one place.
You still control the exact values, but you do it with clearer visibility into save state, restart timing, and the runtime boundary the change affects.
FAQ
When should I use this page instead of provider-auth pages?
Use it for runtime configuration values. Use provider-auth pages and tutorials when the task is API key, OAuth, or provider-specific authentication.