Caudra 0.2 Preview 5
View Markdown~700 tokens
- Configuration edits apply while Caudra runs.
- Global config files can read environment variables.
- Fewer questions about shell lines that set variables.
Important
After you update, restart running Caudra sessions so they pick up hot reload. Until every Caudra process that reads your config files runs Preview 5, keep
{env:NAME}out of them: older versions read it as literal text. Preview 5 does not upgrade the session database.
Configuration
Section titled “Configuration”- Edits apply while Caudra runs. The terminal UI watches its config files, skills, custom commands, and system prompt profiles, and applies an edit shortly after you save it. Permissions apply before the next tool call, MCP servers start, stop, and restart at once, and
[agent]settings apply from the next turn. Some changes still need/reloador a restart, and a footer line says which. Headless runs and ACP still read configuration once, at startup. See Hot reload. - Edits keep the prompt cache. Caudra keeps the tools and system prompt the model was shown until the cache is lost anyway, such as at a compaction or a model switch, and tells the model about the change in a short reminder meanwhile. Permissions and which tools can run follow your edit at once.
- Broken files fail safely, without dialogs. A config file that fails to load keeps its last valid version and shows a red chip in the status bar until it loads again. A broken
permissions.tomldenies every tool call until it loads again. Project permissions and MCP servers that need review show a chip that opens the review. - Environment variables in global config files. A string value in the global
caudra.toml,permissions.toml,mcp.toml,providers.toml, orworkcell.tomlcan contain{env:NAME}. Caudra fills it in from the process environment, or else from the global.env, so secrets can stay out of the file. An unset variable is an error that names the file, line, and variable. Project files under.caudra/cannot use references, andcaudra auth loginand/mcpkeep a reference in the file when they save it. See Environment variables.
Permissions
Section titled “Permissions”- Shell lines that set variables.
export,unset,declare,typeset,readonly,local, andsetno longer make a whole line unreadable, which allowed only "run once" or "no".unset FOO; set -euo pipefail; cargo testnow asks only aboutcargo test, with its usual scopes. Setting a variable or clearing one Bash itself reads, such asPATH, still counts as a command built at run time, and printing variables is treated likeprintenv.