amadan
The console's own config should be settable through a carlos verb, not root env edits Feature Request open
Migrated from github.com/carlosframework/platform issue #368, opened 2026-08-29. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".
Still outstanding: The console's own config should be settable through a carlos verb rather than root env edits.
---
Filed per the platform-first rule, from setting CONSOLEHOMEREGION on the tito console (2026-08-29). carlos env set reaches every activator-run app's bundle, but the console's OWN knobs (CONSOLEHOMEREGION, CONSOLE_DB, retention, …) live only in a hand unit's root env file — so console configuration is an SSM/root edit plus a restart, invisible to the audit trail every app-config write gets.
The ask: a carlos console set <VAR>=<value> (or fold the console's own vars into the existing config door with an owner gate), delivered however the console prefers, with the same refusal-before-write and audit posture as carlos env set. Secrets-class vars (CARLOSRELEASEKEY etc.) can stay deliberately out.
🤖 Generated with Claude Code