Repository navigation
feat(crew): let a mate pin its own agent harness - #25485
Conversation
Design Review (Opus 5.5) — ✅ PASS (a BLOCK with no Trigger and no Outcome does not block)Design-level review of Design-Verdict: PASS cannot evaluate: missing screenshot of the new "Agent harness" row, its picker, and the "can't start" notice on the crewmate profile's Settings page; the evidence list has no image or recording for this revision. BlockersThe new crewmate profile surface has no rendered evidence Notes
[DESIGN-REVIEWED] 22e4978 Description read[DESCRIPTION-READ] 8cc1aff1a7d4cb58bb9b446570e1c8d31ac5a5ede53d86ac60cf2ed5c8986624 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing blocks. The pin is opt-in: an empty pin inherits What this change shipsInventory (10 items) — 10 justifiedIntent: let one crewmate run on a different agent harness, with that harness's models, without moving every other crewmate. ADDITION.
[FIRST-PRINCIPLES-REVIEWED] 22e4978 Description read[DESCRIPTION-READ] 3b7acf998b6380a89e018ccaf5552e72e408edce91d13f94f1f8b5de06f2052f That sha256 names the PR description this verdict read. Recompute it with |
UX Review (Opus 5.5) — ✅ PASS (a BLOCK with no Trigger and no Outcome does not block)UX-level review of UX-Verdict: PASS cannot evaluate: missing screenshots of every new control. No blind read ran because the PR attaches no image, so nobody has checked whether a first-time user understands the Agent harness row, its picker or its notices. Evidence gaps
Notes
[UX-REVIEWED] 22e4978 Description read[DESCRIPTION-READ] 6fba66ff0372b7e9e5698fe6fda647d23d0b7844fe031e73184b1c19429f4542 That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
bolichen97
left a comment
There was a problem hiding this comment.
Thanks for scoping the re-port down to crewmates and folding in the call-site guard test. The shape is right: the pin is one more tier in select_provider_backend, the empty value inherits through the same path as today, and the save path refuses a pin or model the gateway cannot run.
Requesting changes at 91d3767 for two blocking items and two smaller ones:
- Fail-closed pin vs harness-parity H3.
CrewBackendPin.resolve()raises inside the one selection gate, while H3 indocs/system-specs/modules/harness-parity.mdstill says an unselectable persisted backend never raises and degrades to the Kiro floor with a logged reason. Failing closed is a reasonable product choice here, but it has to be recorded: either add the exception to H3 with a test that pins it, or keep the gate non-raising and refuse earlier, outside it. This PR changes neither the spec nor the gate contract test. - SAST (Semgrep) is red on
test/test_crewmate_harness.py:34and:42: both autouse fixtures patch through the sharedmonkeypatch, so any test that callsmonkeypatch.undo()lifts them. Request_floor_monkeypatchinstead. - After a harness pick, the next model pick is pushed to the live slot, which still runs the old harness, so a model only the new harness serves comes back as a 400 even though the record saved it. Skip the live push when the pinned harness differs from the live session's.
- UX: "Harness" with the hint "The agent harness ... run on" explains the word with itself. The Settings tab already says "Agent harness"; a hint that says what changes in plain words would help. Please also attach a screenshot of the new Feature Previews card, which the UX lane could not see.
Non-blocking: crewmate_harness._LABELS duplicates names tool_gate already holds for three ids; consider calling label_for for all of them so there is one map.
Checked at this head: diff of the gate, loader, worker, policy, slot_model and model_switch paths; the profile Settings save flow; harness-parity.md and crew-mode.md; the Semgrep log; overlap with the older attempts in this area. Backend and frontend test shards were still pending when I looked.
91d3767 to
f86314a
Compare
|
The evidence gaps and notes are addressed in the same head. The description now shows the Feature Previews card (light and dark), every harness by its readable name on Settings > Agent Harness and on first-run setup, and refreshed profile shots. Inherited always says what it runs on, through a new Follow-up in d67dc12: a model or reasoning-effort pick saved for the next session now gets its own notice ("Saved. {name}'s next session uses this model." / "… uses this reasoning effort."), new keys These copy and UI changes were made by the author directly, not by a model-pinned delegate. |
f86314a to
bdb5df5
Compare
|
|
@bolichen97 thanks for the review. All four items are addressed at bdb5df5 (replies on each thread). On the non-blocking label map: |
bolichen97
left a comment
There was a problem hiding this comment.
Thanks for the quick turnaround. At bdb5df5 the four points from my last review are addressed: H3 now defers to the new H17 row with tests that pin the pre-gate refusal and a gate that never raises, the autouse fixtures use _floor_monkeypatch (SAST is green), the profile picker no longer gets a 400 after a harness switch, and the copy reads "Agent harness" with a plain hint. The design is good to go from my side.
Still requesting changes for three items at this head:
crewmate_worker_backendchanged from takingAgentConfigto taking the whole config plus the crewmate, butsubagent_manager/run_turn.py:317-321still passes.agentand no crewmate.getattr(AgentConfig, "agent")isNone, somember_acp_backendreads as empty and the crewmate's pin is never consulted on that path. Before this PR the same call returned the member backend. Please pass the loaded config andcrew_for_member_id(...), and treatCrewmateHarnessUnavailableas a refusal there. A test on that call site would catch the signature drift.- The
next_sessionshortcut inslot_model.py(and the same one inslot_effort.py) answers 200 for any model or effort pick on a crewmate session whose configured harness differs from the live one. Only the profile page saves the record first; the composer and keyboard pickers post to the same route, read nothing fromnext_session, and show a pick that was stored nowhere. The shortcut also returns before_model_rejected_reason, so an invalid id gets 200. Please scope it to the profile save (for example an explicit request flag), refuse other callers with a 409 naming the pending harness change, and validate against the configured harness in both cases. - Backend shards 2 and 5 (Linux) and 5 (Windows) are red.
test_backends_vocabulary_family.py::test_no_product_module_but_the_facade_imports_an_ownerfails becausecrewmate_harness.pyimportsACP_BACKENDS_MATE_WORKER_KITfromagent_sdk.backends_membersinstead of theagent_sdk.backendsfacade. Shard 2 also failstest_slot_reset_interleaving_seam.py::test_switch_blocks_until_reloads_serialized_teardown_completes("switch never completed after reload released the locks"); this PR adds work to the sameapi_chat_slot_modelpath, so please check whether it is related before rerunning.
Checked at this head: range-diff against 91d3767, the H3 and H17 rows, the test fixtures, slot_model.py, slot_effort.py, mate_worker.py, every crewmate_worker_backend caller, the profile settings save flow, and the failing job logs.
bdb5df5 to
d67dc12
Compare
|
|
…tion (H17) A mate's own agents.<name>.acp_backend pin that cannot start refuses that mate's sessions before the selection gate instead of degrading to kiro. Add it to the harness-parity review rule as the one H1/H3 exception, with what stays flagged. The H17 spec row lands with the code in #25485.
|
Rebased onto main #25798 is now |
95115e5 to
75d017d
Compare
bolichen97
left a comment
There was a problem hiding this comment.
Re-reviewed at 75d017d. I read the full range-diff from d3b7302.
Fixed since my last review: unrelated edits to a crewmate whose stored harness cannot start. judges_a_model_edit now skips an inherit value and a value equal to the stored one unless the harness moves, and it is applied in the pre-lock probe and in the locked check for both model and worker_model. The new tests cover a re-sent model, worker_model and both, and also check that a harness move still judges unchanged pins. That clears the red item from my previous review. I also checked that the editor sends acp_backend only when the harness row itself is picked, so a re-sent unstartable pin does not hit harness_pin_rejected on an ordinary save.
Still blocking: the Opus finding on this head is valid. CrewBackendPin.resolve maps a stored kiro pin with backend_from_stored and returns ACP_BACKEND_KIRO as is. The Kiro CLI choice that main now moves onto KAS once v3 is confirmed (kiro_cli_pick_backend, applied in _read_backend_choice) is never applied to the crewmate pin. So a crewmate pinned to Kiro CLI keeps the v2 launch while the same spelling in agent.acp_backend runs on KAS, and agent.member_acp_backend = "kiro" is always remapped to KAS. Details inline.
Still open, not a code defect: the base harness-parity rule on main has no H17 exception yet. The companion rule PR carries it and should land first.
This replaces my earlier change requests. Once the pin follows the Kiro CLI mapping and the AI lanes and readiness pass on the new head, I expect to approve.
75d017d to
8f2bdde
Compare
Also in this push: rebased onto main |
|
bolichen97
left a comment
There was a problem hiding this comment.
Re-review at 1acd024cd6ceb0690247109db42897c55f3341bb (range-diff from 75d017de86644a9f8f6a8d72ffcc88553a4fa225).
The blocking finding from my last review is fixed. CrewBackendPin.resolve now sends a stored kiro pin through kiro_cli_pick_backend() when agent.kas_bundle is off, the same way _read_backend_choice reads a stored agent.acp_backend. Both construction sites (crewmate_pin_for and pinned_entitlement_backend) pass kas_bundle, the display path in agent_catalog._session_backend reads the resolved harness, and the new TestAKiroPinOnAV3KiroCli tests plus the H17 row cover both routes. The other hunks in the range-diff (dormant DM model and effort clearing on a harness save, the autocompact backend lookup passing crew_backend, docs) read clean. No new blocking findings from me.
What still blocks approval at this head:
- The branch conflicts with main again, in
website/src/i18n/en.context.jsonand the locale catalogs. Please rebase. - CI is still running.
- The Opus lane blocks on the H17 exception being absent from the base harness-parity rule. That rule change is #25798, and it needs to land first.
Non-blocking, from the Design lane: the crewmate worker registry lives only in process memory, so a worker resumed after a gateway restart follows the member route rather than the pin. Worth a sentence in H17 or a follow-up.
I will re-check once the rebased head is green.
|
Rebased onto main #25091 also grew Local gate: generated files clean, i18n (vitest + |
bolichen97
left a comment
There was a problem hiding this comment.
Re-review at 2bdd6e5 (range-diff against 1acd024).
The new head changes look correct. models_route now takes the request query mapping, so only a present backend key asks for a harness; the handler passes request.query and the tests cover an empty value, an unselectable harness and no query. The other code edits are comment and naming tidy-ups, and the locale and context JSON edits are the conflict resolution plus the same three harness strings. No new findings.
This branch conflicts with main again: the generated ui-index.generated.json under the docs package changed on main after your rebase (the Sprites and boxd session environments change). Please rebase onto current main and regenerate that index file. Once the branch is clean and the checks are green, the remaining gate is the harness parity rule change in the companion spec PR, which needs to land first.
|
Rebased onto main The PR now has two commits:
Local gate: generated files clean, i18n, tsc, members/settings vitest, targeted pytest (8,064 subagent and related tests; the one failure, |
|
|
Rebased onto main
Frontend Tests (1) on Local gate: generated files clean, |
bolichen97
left a comment
There was a problem hiding this comment.
Re-review at f4d84c6 (range-diff against 2bdd6e5 and 4e49af7).
The new commits look correct and I have no new findings.
- The harness save now refuses with 409
crewmate_harness_busywhen the mate has more than one live DM chat, before any teardown, so the nested reload that could post a false notice and then answer 409 cannot start. check_member_approval_moderuns the same compare-and-set aspersist_member_configunder the config lock, and its mutate returns None, soupdate_config_lockedskips the write. An approval conflict is now refused before the chat is reloaded; the in-hook write still checks again.- Moving the usage row into
usage_row.pybroketest_usage_turns.py::TestWriteSiteStamping::test_subagent_completion_stamps_the_dispatching_appat 4e49af7 (the source pin only readrun.pyandrun_*.py). The test now readsusage_row.pyas well, and it passes locally at this head, together withtest_crewmate_harness.py,test_spawn_crewmate_worker.py,test_mate_worker_dispatch.pyandtest_turn_duration_recorded.py.
CI note: at 4e49af7, three backend failures (test_dir_fd_create_race_ratchet.py, test_security_gate_liveness.py line budget, test_subagent_prompt_hooks.py watchdog) also fail on the base commit. They still fail locally at this head, whose base predates the main fix for them. Rebasing onto current main should clear them; the branch merges cleanly with it.
Merge order is unchanged: this PR should land after the companion rule change for the H17 exception.
A crewmate can name the agent harness its chat and the worker sessions it opens run on (agents.<name>.acp_backend), beside the model it already pins. Unset inherits agent.member_acp_backend exactly as before. The pin is a tier of the one selection gate (members.select_provider_backend), below an explicit spawn_run(backend=...) and above the member route, and every caller passes it. A pinned harness this gateway cannot start refuses the session with crewmate_harness_unavailable instead of falling back to kiro-cli. The model and worker_model pins are judged against the pinned harness at save time. The dashboard shows a Harness row on the crewmate's profile Settings page, behind a Settings > Developer > Feature Previews switch, and scopes the Model list to the picked harness. The pin is read only through the owner-only GET /api/agents/resolved-model; GET /api/agents leaves it out. Re-port of #11324 onto current main, scoped to crewmates. Co-authored-by: Akim Akimov <9255+Zedmor@users.noreply.github.com>
…stay under the line cap main took subagent_manager/run_turn.py to 2,030 lines, over the 2,000-line cap, so any change to it fails check_file_line_cap. Move the body of _run_inner_impl's nested _persist_usage_row into a sibling module, subagent_manager/usage_row.py, and call it from the nested function. No behaviour change: the moved body reads time, asyncio, logger and provider_fallback_active from kiro_crew.subagent at call time, the namespace _run_inner_impl runs on, so existing patches still reach it.
bolichen97
left a comment
There was a problem hiding this comment.
Approving at head 22e4978.
Gates checked at this head: label readiness: passed; every check green or skipped, none red or pending; Design, First Principles, UX, Opus and GPT review lanes all PASS; Sensitive Change Review green; mergeable with no conflict; base is main; no other human change request.
Every hunk of the diff (87 files) was read across our review rounds. This head is a rebase of f4d84c6: range-diff shows both commits unchanged and the whole-PR patch-id is identical, so nothing new needed reading. Areas covered:
- Crewmate harness pin and its pre-gate check (new
crewmate_harness.py,policy.pybackend selection, config apply rebuild on anacp_backendedit, member dispatch gates). - Crew editor save path in
crew_update.pyandcrew_records.py, including the approval-mode compare-and-set run before the chat reload, which only adds a refusal and never widens one. - DM chat and crewmate worker refusal when a pinned harness cannot start (fails closed, no fallback to another harness), plus slot model, effort and session create paths.
- Harness-parity spec H17 row and crew-mode docs, matching the H17 rule now on main.
- The
usage_rowmove out ofrun_turn.pyinto its own module (refactor, no behavior change). - Tests (new harness, dispatch, live model switch and spawn tests), locales and generated settings and UI index files, and the crew profile settings page.
Security checklist answered at this head: no change to auth or owner checks, no new unvalidated external input (the pin is checked against the selectable harness set), no trust boundary or sandbox change, approval mode handling only gets stricter, no secret handling.
This approval replaces our earlier request for changes. The findings from that round (the multi-chat harness save and the missing H17 rule) are fixed in this head and in the companion spec change that has merged.
Problem / Motivation
Goal: A crewmate can run on its own agent harness, with that harness's models, chosen in its profile settings.
Today every crewmate's chat runs on one install-wide setting,
agent.member_acp_backend. A crewmate can pin a model and an effort, but not the harness under them, so two crewmates cannot run on different harnesses, and choosing one for a single crewmate moves all of them.Why it matters
Harnesses differ in model catalog, cost, provider and capability. A developer who wants one crewmate on Claude Code and the rest on KAS has to switch every crewmate today. A per-crewmate pin moves just that crewmate, with a model list that matches what its harness can run, and keeps everything else on the defaults.
Not a goal
ACP_BACKENDS_MEMBER_DISPATCH,ACP_BACKENDS_MATE_WORKER_KIT) are unchanged.What changed (motivation → approach → change)
A crewmate record gains
acp_backend, stored next to itsmodelandworker_model. It usesagent.acp_backend's spelling (kiro,kas,claude, ...), and empty inherits. No second model field: the existing pins are reused and judged against the pinned harness.members.select_provider_backendtakes the pin ascrew_backend, one more tier of the one gate:spawn_run(backend=)wins, then the pin, then the member route. Every caller passes it ascrewmate_backend_pin(...)orNone, and a test fails on one that does not.crewmate_harness.crewmate_for_sessionfinds the crewmate from the session key alone: its DM thread, or its own worker (the worker registry records whose worker it is).CrewmateHarnessUnavailable(crewmate_harness_unavailable) before any process exists. It never falls back to kiro-cli (#21910). The refusal is a check BEFORE the selection gate (crewmate_backend_pinreturns aStartableCrewPin), so the gate itself still never raises (H3);harness-parity.mdrecords the exception as H17. Display reads usecrewmate_stored_pin, which never raises. An explicitspawn_run(backend=)override outranks the pin, so the pin is not checked then.PUT /api/agents/{name}takesacp_backendonly as""or a startable harness, and refuses amodel/worker_modelthe pinned harness cannot run, including stored ones when the harness changes.GET /api/agents/resolved-modelreturns the pin, plusinherited_harness(what clearing it would run).GET /api/agentsleaves it out.GET /api/models?backend=lists one harness's models.acp_backendreloads its live DM chat through the existingreload_slot_session(the tab's Reload), clears the slot's own model and effort overrides and rebuilds the provider factory, in one step under the slot and session locks; the record is written only after the old process is down. The transcript and resume pointer stay, so the next message starts on the new harness with the conversation replayed by the existing provider-switch path. While a turn or its sub-agents run, the save is refused with a 409crewmate_harness_busythat names the mate and says to wait or stop it, and nothing is written. Model and effort picks therefore always reach a session on the saved harness.subagent_manager/run_turn.py) is judged on the mate's pin, then the member route; an unstartable pin refuses the run.crewmate_worker_backendtakes the whole config and raises on a config section.acpBackendName,crewmate_harness.harness_label), so OpenAI Codex, OpenCode, Pi, goose, DeepSeek Harness and GitHub Copilot CLI no longer show as their raw ids, here and on Settings > Agent Harness and first-run setup.The developer gate is a Feature Previews switch because the Developer Mode switch was removed (
docs/request-for-change/rfc-developer-tools-in-settings.md, accepted; #24810). The row is on the profile Settings page, next to the existing Model and Worker model rows, because #25091 folded the crew editor's Advanced section away.A saved pin rebuilds the provider factory, from the editor or from a
config.jsonedit (session_parts/config_apply.py). The member operating-mode block, the cold-slot readouts,set_model, slash-command checks andkirocrew agent update --modelall read the pin through the same helpers. Specs, the user docs and the 12 catalogs plusen-XAare updated.Where it lives: the pin and its helpers in
src/kiro_crew/crewmate_harness.py; the field inconfig/sections_session.pyandconfig/loader_pipeline.py; the gate tier inmembers_parts/member_sessions.py(re-exported bymembers.py), its factory call inconfig/loader_config.py; the worker backend inmate_worker.py; the dispatch block incontext.pyandcontext_assembly/member_gates.py; save and readout indashboard/agent_admin/crew_update.pyandcrew_records.py; the CLI check incli_commands_agent.py; the flag inwebsite/src/utils/previewFlags.ts; the harness names inwebsite/src/api/acpBackend.tsandwebsite/src/i18n/glossary.json; the client calls inwebsite/src/api/client/agents.tsandchatSlotSettings.ts; the copy inwebsite/src/i18n/locales/*.json; docs insrc/kiro_crew/docs/configuration.mdand the regenerated settings and UI indexes.Re-port of #11324 by @Zedmor onto current main, scoped to crewmates. Zedmor is credited as co-author on the commit. The call-site guard test and keeping the field out of
GET /api/agentscome from #16200.Second commit: main's #25122 and #25127 took
subagent_manager/run_turn.pyto 2,030 lines, over the 2,000-line cap, so the 9-line worker change above failscheck_file_line_cap. The second commit is a behaviour-free move: the body of_run_inner_impl's nested_persist_usage_rowgoes tosubagent_manager/usage_row.pyand the nested function calls it, which putsrun_turn.pyat 1,993 lines. The moved body readstime,asyncio,loggerandprovider_fallback_activefromkiro_crew.subagentat call time, the namespace_run_inner_implruns on, so existing patches still reach it;test_turn_duration_recorded.py's per-file persist-site count andrun_turn's field list move with it.Backwards compatibility
Compatible: the field is new and defaults to
"", which inheritsagent.member_acp_backendthrough the same code path as before; no stored value, endpoint or response field that works today changes meaning.Removes nothing: the diff adds a field, a request key, two response keys on an owner-only readout, a query parameter and a preview flag; every existing value keeps its answer.
Tests
test/test_crewmate_harness.py: gate precedence (override > pin > member route),kiroas a real pin, fail-closed refusal with the crewmate and value named, which session keys take the pin (DM in three spellings, worker, forgotten worker, others), the worker backend, the dispatch block, config round-trip, save validation and no partial write, model judged against the pending and the stored pin, owner readout and its non-owner absence, roster exclusion, hot reload on anagents.*.acp_backendedit, and an AST scan that fails on anyselect_provider_backend(call withoutcrew_backend.test/test_crewmate_harness.py::TestThePreGateCheckand::TestSelectionGate::test_the_gate_never_raises_for_a_crew_pin: the refusal happens before the gate, and the gate never raises (H17).test/test_agent_execution_catalog.py: the catalog answers for a mate whose pin cannot start.test/test_crewmate_harness.py::TestAHarnessChangeReloadsTheLiveChat: a harness change reloads an idle live DM chat (process torn down, overrides cleared, transcript and resume kept), an unchanged harness reloads nothing, a running turn or running sub-agents get the 409 with nothing written, and a mate with no live chat is a plain save.test/test_spawn_crewmate_worker.py: a worker run is judged on the member route when unpinned, on the pin when pinned, and is refused on an unstartable pin.website/src/pages/members/CrewProfileSettings.test.tsx: the row is hidden with the preview off; Inherited names what it resolves to; a harness the worker cannot start says so; a pick saves the harness with a model reset and touches no thread; the Model list comes from the pinned harness; a harness that cannot start shows its reason.src/api/acpBackend.test.ts,AgentBackendTab*.test.tsx,KiroPrerequisiteGate.agent*.test.tsx,McpTab.wholeServerDeny.test.tsx: expectations follow the readable harness names.acp_backendwithheld),select_provider_backendcall assertions,API_KEY_ORDERinwebsite/src/test/ApiClient.refactor.surface.test.ts,config-baseline.json,settingsRegistry.gen.ts.Proof: not provable -- other: feature PR; new behaviour has no pre-existing implementation to revert against
Manual verification
Local: the prepare-pr gate floor. On this round, after re-syncing onto main, 3,798 related backend tests and the profile, settings and i18n frontend suites pass. Earlier, the scoped backend suite showed 26 failures that fail the same way on a clean worktree of the base (
c6789799df), from this host's environment (symlink-loop and launch-record tests). This round,test_app_agent_launch_copy.py::...[opted-out]fails the same way on a clean worktree of main. The Electron tests needwebsite/electron/node_modules, which this worktree does not have; this PR changes no Electron code. Both are left to CI.The rendered profile was checked with a capture script against the built dashboard and stubbed API (the screenshots below), asserting the PUT body, the scoped model list, the named unavailable harness and its button, and Inherited's hint while pinned. The Feature Previews card, Settings > Agent Harness and first-run setup were captured from the real components behind stubbed APIs, asserting each harness's readable name.
Screenshots / video
The Feature Previews switch that turns the feature on (light and dark):
The Agent harness row on a mate's profile Settings page, with the preview on (light and dark):
The Agent harness picker: Inherited names what it runs on, and a harness the mate's workers cannot start on says so before it is picked.
After picking Claude Code: the save puts the model back to Inherited and says when it applies.
Pinned to Claude Code, the Model page lists Claude Code's own models.
A pinned harness that can't start, named rather than shown as its id, with the way out inside the notice.
The button opens the picker: Inherited says it follows the crew default, and the pinned harness says only that it can't start here.
A harness change while the mate is mid-reply is refused, names the mate and says what to do; the pick is put back:
With the preview off there is no Agent harness row.
Every harness by its readable name on Settings > Agent Harness:
And on first-run setup's Use other coding agents:
Related Issues
Part of #21910
Part of #12451
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)