v0.25.0 — Desktop app: Tools, Maturity, Onboarding & MCP

Four more screens for the Chimera Desktop app — each grounded in real backend data, and the terminal stays sovereign (every app feature has a CLI equivalent; the desktop is an opt-in [desktop] extra).

Added

• Tools — lists every tool the agent can actually call (built from the same registry the agent uses), each with its parameters and honest capability tags (network / read / write / exec / side-effect) derived from the governance sets. No invented "origin" — there is no such field.
• Maturity — the agent's coverage scorecard by surface (fusion, evolution, governance, memory, benchmarks, resilience, interop) with the weakest surface highlighted. Honest in every deployment: live from the test suite in a source checkout, a shipped snapshot (labeled "as of vX") for a pip install, or an honest empty state — never a false all-Alpha card. Shows coverage/evidence presence (a test with that stem exists), not performance numbers.
• Onboarding — the app now boots without a provider key and opens a first-run setup screen: paste an OpenRouter key → save → live-test it (a real minimal call, so "verified — it works" is never faked; presence ≠ authentication) → pick a model. chimera app no longer hard-exits without a key; the other CLI commands stay strict.
• MCP / Integrations — MCP servers become a real, persisted capability instead of Python-only wiring: chimera mcp add/list/remove/test (CLI is the source of truth, .chimera/mcp.json), a screen to configure + live-test them (a "connected · N tools" badge appears only after a real stdio connect), and opt-in autoload (CHIMERA_MCP_AUTOLOAD) to make their tools callable by the agent. MCP output is untrusted — taint-tracked by governance.

All four ship in the wheel (pip install 'chimera-agent[desktop]' → chimera app), in 7 UI languages, behind a same-origin bearer guard and localhost bind.

Full changelog: https://github.com/brcampidelli/chimera-agent/blob/main/CHANGELOG.md