Private projects, safe file tools, reusable flows, and a cleaner path from idea → working implementation.
Configure models, runtime behavior, voice, and system tools.
Primary OpenRouter credentials and default model.
Models used by prompt helpers and the optional browser-image sidecar.
Control probes, context, navigation, and ask-user timing.
Playback provider, voice, speed, and optional OpenRouter TTS.
Refresh model lists and check local runtime dependencies.
Replay onboarding without changing your saved projects.
Used for cost visibility, not for changing which model runs.
OpenRouter responses include usage/cost metadata, and generation stats can be queried later by generation ID. A separate OpenRouter key lets R3D3 keep pricing/account lookups isolated from the normal model-calling key.
OpenRouter notes that Management API keys are for administrative operations, while generation stats and response usage are used for model-cost auditing.
Open OpenRouter keys Open pricing docs
How each agent prompt is assembled before the model chooses a tool.
Pick a reusable specialty for Agent nodes. Keep the role broad; put task-specific instructions on the selected node.
Create safe source files, upload media, or add one subfolder level.