v21.3.0 — the simplification release

AgentQon gets out of your way.

Two connection kinds, total

The Connections form now offers exactly two kinds: a local model server (your machine, no API key) or an API key (BYOK) connection to any provider or gateway. Either kind can use any address — a local address like 127.0.0.1 is accepted for both. The old kind-based rejections (URL_POLICY: private_endpoint when a gateway-kind connection pointed at your own machine) are gone: locality is derived from the address itself. The protections that matter are unchanged — cloud-metadata addresses are always blocked, public endpoints still require https, credentials never travel inside URLs.

Budgets leave the interface

No budget pickers in chat, no budget field on the mission form, and no mission can fail with a budget error. You describe the job; it runs. Spend is still recorded as plain accounting. (One fixed, generous internal ceiling remains — invisible and not user-settable — purely so a stuck loop cannot drain an API key.)

Forms fold away

The custom-agent form stays collapsed until you add or edit an agent, and folds back after saving. The mission form leads with just the task and Run; secondary fields live under a collapsed "More options".

Verification

Full suites before staging: unit 204 passed, integration 143 passed, pack gate PASS.