Configuration Overview
All configuration lives in .agent-settings.yml. The canonical, richly
commented template is
src/config/agent-settings.template.yml;
the installer renders it into your project (or user-global) settings.
# .agent-settings.yml (excerpt)profile: id: developerdiscipline_profile: autopersonal: autonomy: autoquality: local_auto_run: falseLayered merge (lowest → highest precedence)
Section titled “Layered merge (lowest → highest precedence)”- Package defaults (the template).
~/.event4u/agent-config/agent-settings.yml— user-global, whitelist-filtered to six DX keys (name,ide,rule_loading_tier,personal.bot_icon,personal.autonomy,telegraph.speak_scope).<repo-root>/.agent-settings.yml.- Intermediate-directory settings.
<CWD>/.agent-settings.yml— deepest wins.
Project-local always beats user-global.
Two ways to write it
Section titled “Two ways to write it”- The GUI —
agent-config config(orsettings) opens a local settings editor (loopback-bound, two-phase commit, comment-preserving merge). - Hand-editing the YAML directly — skips validation and locking, so prefer the GUI for anything non-trivial.
Validation & sync
Section titled “Validation & sync”agent-config settings:check— validate against the settings contract (read-only).agent-config settings:sync— additively merge new template keys into your file.agent-config validate— drift gate suitable for CI.
The schema
(src/scripts/schemas/agent-settings.schema.json)
is deliberately permissive (additionalProperties: true) and only enum-guards
the value-bearing keys that historically collided.
- Settings Reference — the key groups.
- Profiles — the four profile concepts, disambiguated.