ChatWalaʻau v0.90.0

This release adds one new feature to ChatWalaʻau: Declarative Agent Configuration.

Highlights

Declarative Agent Configuration (v0.90.0)

• Define agents in YAML, switch them at runtime. Describe an agent's persona, model selection, reasoning options, and output policy in a YAML file using the Microsoft Agent Framework declarative format (agent-framework-declarative), then switch the active agent from the web app -- no code change and no restart. A new robot icon in the sidebar footer (next to the File Explorer icon) opens a manager that lists the agents as a nested-folder tree; activating one rebuilds the agents with a blocking "rebuilding" indicator.
• The YAML is a specification; ChatWalaʻau owns construction. Fields ChatWalaʻau understands are mapped onto the real agent: instructions -> the agent persona (use =Identity or omit it to keep the global identity); model.id -> the preferred default model (the other configured models stay selectable, so the model picker never disappears); model.options.effort / verbosity -> reasoning effort and text verbosity; outputSchema -> a default JSON output schema. Credentials / connection in the YAML are never honored, and classic sampling parameters (temperature, top_p, ...) are rejected -- the supported models are reasoning-only.
• Applied as defaults, reflected in the UI, overridable per message. When you switch to an agent, the model picker, the reasoning-effort / verbosity controls, and the JSON-schema editor update to reflect it; its options take effect by default and you can still override any of them per message.
• Built-in CORE agent, byte-for-byte default. The standard ChatWalaʻau agent is registered as the built-in CORE agent and is active out of the box. With DECLARATIVE_AGENTS_DIR unset there are no custom agents and the runtime is exactly as before. Custom agents are discovered from DECLARATIVE_AGENTS_DIR (nested folders allowed) through a path-jailed loader.
• Validation with visible errors; warnings block activation. Each agent is validated on listing and activation: a malformed YAML or a rejected sampling parameter is a hard error, and an agent that maps with any warning (ignored connection/credentials, an unknown or invalid effort/verbosity value, or an unconfigured model.id) cannot be activated until the YAML is fixed -- the manager flags it, lists the warnings, and disables Activate. The active agent is also written to the log at startup and on every switch.
• Web-app only switching; API and Teams follow. The active agent is switched from the web app; the OpenAI-compatible API and Microsoft Teams always use whichever agent is currently active. The selection is in-memory only, so a restart re-initializes to the CORE agent.

Included in this release

This release includes implementation work from:

• v0.90.0 through v0.90.0

Notes

• No breaking changes. Declarative agent configuration is additive. With DECLARATIVE_AGENTS_DIR unset (the default) the only agent is the built-in CORE agent, which reproduces the previous behavior byte-for-byte; no removed or renamed endpoints, settings, or environment variables, and no data migration.
• Upgrade note (additive, non-breaking): one new backend dependency (agent-framework-declarative, used only to parse/validate YAML; the loader degrades gracefully if it is absent) and one new environment variable (DECLARATIVE_AGENTS_DIR, default empty). No new frontend dependency.
• Internal design management content and architecture control artifacts are intentionally omitted from this release note.

Installation

See the repository README for setup and usage instructions.

Version

• Release version: 0.90.0
• Previous release: 0.89.0