Configuration boundaries
AI OS configuration is divided by where a value is allowed to travel. Keep provider credentials and local paths in script-only local configuration; use browser-prefixed values only for settings that are safe to compile into the client bundle.
Configuration classes
Section titled “Configuration classes”| Class | Examples | Browser visible? |
|---|---|---|
| Public browser setup | Display preferences, setup defaults, extension visibility | Yes |
| Local host runtime | Scheduler, Dream, local data, and runtime provider settings | No |
| Private source credentials | Optional provider and collector credentials | No |
| Generated operator state | Local data, run state, caches, and logs | No |
Any variable with a VITE_ prefix can be bundled into browser code. Never use
that prefix for tokens, account credentials, private file paths, or provider
request material.
Local access default
Section titled “Local access default”Normal bun run dev startup derives the local all-access posture when it is
not explicitly set. This enables shipped local actions without requiring
legacy admin flags. Request checks, validation, redaction, timeouts, safe
errors, and path confinement remain in place.
Compatibility names
Section titled “Compatibility names”Some VITE_CLAUDE_OS_* browser settings remain because the current app was
built from an inherited starter. They are compatibility contracts, not the
current product identity. New host-owned script settings use AI_OS_* where a
canonical name exists.
Renaming a compatibility value requires an explicit migration with aliases, documentation, and tests.
Ports and surfaces
Section titled “Ports and surfaces”| Surface | Default local address | Purpose |
|---|---|---|
| AI OS dev app | http://127.0.0.1:5189 |
Local cockpit and guarded actions |
| Voice broker | http://127.0.0.1:8099 |
Optional local Hermes Voice broker |
| Docs dev site | Astro-selected local address | Public documentation authoring |
The product website, static demo, and documentation site have no access to local runtime configuration. They are independent public static builds.
Setup precedence
Section titled “Setup precedence”The browser setup wizard can use safe compiled defaults and then store the operator’s selections in browser storage. Script-only runtime configuration remains outside the wizard. A successful UI setup does not authenticate a provider or prove a local collector run.
For the optional OpenAI account path, use the dedicated subscription runtime guide rather than placing credentials in browser settings.