Better adapter switch

Strong +1 on the pain — I hit this every time a new adapter version drops or I want to A/B Claude vs Codex vs Hermes across a whole company. Two ways to think about it:

Today's workaround (not great, but unblocks): the agent PATCH endpoint takes adapterConfig, so you can script bulk changes via the API. Roughly:

bash list agents, then PATCH each curl -s "$BASE/api/companies/$COMPANYID/agents" -H "Authorization: Bearer $TOKEN" \ | jq -r '.items[].id' \ | xargs -I{} curl -X PATCH "$BASE/api/agents/{}" \ -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \ -d '{"adapter":"claudelocal","adapterConfig":{...}}'

Keeps you out of the UI but obviously doesn't scale to "I want this in the product."

What "better" would look like in the UI — curious what shape you'd actually want; a few options I can think of:

Multi-select in the agents list → "Switch adapter…" → pick adapter + base config, applied as a bulk patch. Company-level default adapter with a checkbox per agent for "follow company default," so changing one setting cascades. Adapter "presets" you can save and apply across agents (e.g. "Claude w/ skip-permissions + persistent memory").

Which of those would actually solve your case? If it's (1), that's probably the smallest landable change. (2) is the more opinionated product move and would also fix the "I onboarded ten agents and they all drifted to slightly different configs" problem. Worth knowing your real-world scenario before pushing this upstream.