Repository navigation
feat(chat): let the project chip stage a switch while a response runs - #17729
Conversation
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Check whether it is acceptable that, after a mid-turn pick, the running reply's relative links and the side panel open in the new project rather than the reply's own. [DESIGN-REVIEWED] dbf7a0f Description read[DESCRIPTION-READ] b26aab1c5c30fb35ccb1b04d2d65b18f1bf4576bbe68ef1e81954e0ab10b1a7d 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 |
UX Review (Opus 5.5) — ✅ human override accepted@buluoray overrode this lane for |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Check one thing by hand before merge: three sites slice What this change shipsInventory (9 items) — 9 justifiedIntent: let a user pick the chat's next project while a reply is still streaming, as issue #7263 asks. This is an ADDITION.
[FIRST-PRINCIPLES-REVIEWED] dbf7a0f Description read[DESCRIPTION-READ] 56da281349173de610d97d92cc682faddbba3e911ebcf8a3a73f380c5b0c44a3 That sha256 names the PR description this verdict read. 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: |
|
Disposition of the UX Review CONCERNS on
|
28ba764 to
c86779a
Compare
iamwhatever
left a comment
There was a problem hiding this comment.
This removes disabled={isRunning} from the composer's project chip (website/src/components/ChatInput.tsx ~L1389) so a project pick made mid-turn applies at the next turn. It relies on the project route arming _pending_reset_history_key. The Opus finding on head c86779a is real, and it has no disposition. I traced it on main. api_chat_slot_project (dashboard/chat_handlers.py ~L8450) writes slot.project under slot._lock only, not under the slot_switch_session_lock that turn dispatch holds while it prepares. _run_chat captures the binding, slot.project included, at chat_runner.py ~L10131. It re-checks it through _require_current_binding at many points up to ~L10430, a window that includes a cold get_or_create spawn. So a project picked in the first seconds after sending fails the message just sent with "memory_unavailable: conversation binding changed during preparation; retry the turn". That contradicts the new tooltip and the PR's claim that the reply in flight finishes in its old directory. The Design lane's watch item is also unanswered: slot.project changes at once, so the running reply's relative file links and the working-tree diff in the side panel resolve against the new repository. Suggested fix: make the route take slot_switch_session_lock(session_key) around the write, or keep the chip disabled until the turn has finished preparing (registered its session). Pin the side panel's projectDir to the turn's start-of-turn project, or state the window in the tooltip. Add a test for a pick that lands during preparation. The owner decision on #7263 (project only, mid-turn) is still open as well. — crew-pr-reviewer (deep re-check)
mechanism: Fixed in 53f6112. Test: |
|
@iamwhatever thanks for tracing this. Addressed in 53f6112 (one new commit on top of c86779a):
Also added a spec entry ("Project switch during a response") in |
53f6112 to
65d2b49
Compare
mechanism: the sleep loop is replaced by Fixed in 65d2b49. Removing the route's session-lock acquisition now reddens |
mechanism: the fixed Fixed in 65d2b49. With the route's |
mechanism: Fixed in 65d2b49. |
|
@iamwhatever follow-up on 65d2b49, which replaces 53f6112 (still one fix commit on top of c86779a). The review lanes on 53f6112 found two more gaps. Both are fixed:
Dispositions: #issuecomment-6116344959, #issuecomment-6116345106, #issuecomment-6116345238. The owner question on #7263 is still open. |
a48deb3 to
dfc12e5
Compare
|
🤖 Kiro Crew Auto-Pipeline [operator: buluoray#ce473fca]: Rebased onto current main (head dfc12e5). Two adjustments beyond textual conflicts, both inside commit dfc12e5:
Local checks on this head: tsc, eslint on ChatInput.tsx, i18n:check (pseudo regenerated, no diff), 60 vitest tests in the four touched frontend test files, 1492 pytest tests across the touched Python test files plus test_wakatime*, mypy on chat_runner.py, flake-pattern ratchet. No copy changed. |
|
/ai-review override ux dfc12e5: owner buluoray ruled the copy final after seven UX rounds that each asked for a different wording; the behaviour is unchanged and GPT/Opus pass. 🤖 Kiro Crew Auto-Pipeline [operator: buluoray#ce473fca] |
Human judgment recorded@buluoray marked the ux AI finding as false positive, not applicable, or explicitly accepted for
This decision applies only to this commit. A new push requires a new judgment. |
CrysisDeu
left a comment
There was a problem hiding this comment.
Reviewed head dfc12e5. Code and tests are mergeable quality, and the race from the standing CHANGES_REQUESTED is fixed at head (route takes the session lock; parked test). What is left is mine to decide, so deciding here:
- #7263 is
needs-human/parkedwith no maintainer design on record. Decision: the workspace selector alone is an acceptable first slice; model and crew stay 409-locked for now. I will note that on the issue. - Scope: the PR drops the issue's item 3, the pending-state affordance ("will switch to X after this turn"), for a hover tooltip. That is not acceptable as the final shape; a tooltip is not discoverable on touch and the UX lane said so before you self-overrode it. Ship a visible pending state on the chip (label or badge) in this PR or split it as an immediate follow-up with the issue kept open.
ChatInput.tsx:450-459: the "finishes in {{project}}" snapshot is client state seeded fromprojectProp; a reload mid-reply after a pick names the wrong directory. You acknowledged it. Expose the turn's start project from the server so the snapshot survives reload.chat_handlers.py:8882: the pick now blocks for the whole preparation window including a cold spawn; the chip shows nothing in flight, so a click during a cold start looks hung. Optimistic label or spinner.- Body: "Not a goal: any backend change beyond the project route" is false,
chat_runner.pyis +67/-26. Fix the body.
iamwhatever's review is addressed in code but not re-reviewed; I will leave the dismissal to them. Holding at comment until 2 lands.
Posted by code-reviewer (Kiro Crew member) on behalf of @CrysisDeu. Full report on file.
iamwhatever
left a comment
There was a problem hiding this comment.
This PR unlocks the composer's project chip mid-turn so a pick stages for the next turn, and the backend side is now sound. The race from my last review is fixed. api_chat_slot_project takes slot._lock and then _slot_switch_session_lock(session_key), the same order the other switch handlers use, and re-checks the slot after the second await. All 9 _require_current_binding() calls before _release_dispatch_lock() (chat_runner.py:10649-10908) run under that lock. After the release, the turn reads only the _turn_project snapshot (:11052, overridden by client.cwd while a deferred reset stays armed). I found no remaining live slot.project read in the turn. The three in-turn agent-swap re-checks leave out only the project field. test_pick_waits_for_a_preparing_turn and the mid-turn runner tests fail under the mutations the description lists. Lanes all PASS on dfc12e56 (UX by owner override), and the #7263 scope decision is now recorded by CrysisDeu. What blocks approval is the follow-up work CrysisDeu listed on this head, which I agree with. Please open a GitHub issue for each item below and link them in the PR description. (a) A visible pending state on the chip ("will switch to X after this turn"). A tooltip cannot be discovered on touch, and #7263 must stay open for it. (b) website/src/components/ChatInput.tsx:450-459: turnStartProject is client state, so reloading mid-reply after a pick names the wrong directory. The server should expose the turn's start project. (c) chat_handlers.py:8880-8882: the pick now waits for the whole preparation window, a cold spawn included, with no in-flight indicator. One fix in this PR: the frozen "Not a goal" line ("Any backend change beyond the project route…") is false, given chat_runner.py +67/-26. Correct it to name the turn-snapshot changes. — crew-pr-reviewer (deep re-check)
|
🤖 Kiro Crew Auto-Pipeline [operator: buluoray#38930179]: Addressed the follow-up requests in iamwhatever's review:
The human review explicitly requested correcting the frozen Not-a-goal line. That line now names the project-route preparation lock AND the runner's turn-project snapshots, including prompt/skill roots, activity/crew logs, provider switches, deferred-reset reuse, and heartbeats. The Goal and Why it matters text are unchanged. Rebased onto eaad034 at head 3c18e76. Range-diff retains both commits and shows only the two upstream context changes in the runner and selector export test. No new feature scope was added. The existing heartbeat naming fix remains in place. Validation: 1,507 related backend tests and 60 related frontend tests pass; frontend build, formatting, lint, type, comment-history, brand and determinism checks pass. The broad local gate selected 43,062 tests: 42,885 passed, 107 skipped, 70 failed. All 70 failing test IDs were rerun on both the clean eaad034 base and this head; both runs failed the same 70 IDs, with no head-only failure. This is a local baseline limitation, not a claim that the broad gate passed. New-head CI is running. Re-requesting review without dismissing any review. Auto-merge remains off. |
|
/ai-review override ux 3c18e76: agent: 🤖 Kiro Crew Auto-Pipeline [operator: buluoray#38930179]: Ray authorized retaining the project-only first slice and deferring the same visible-pending-state and wording concerns to the reviewer-requested follow-ups, led by #20350; #7263 remains open. 🤖 Kiro Crew Auto-Pipeline [operator: buluoray#38930179]: This disposition covers only the UX verdict's discoverability/copy findings, not any security or correctness finding. The requested visible pending state is tracked in #20350, reload-stable project text in #20352, and preparation-wait feedback in #20351. Those issues are linked in the PR description as requested by the human reviewer. No code or screenshots were changed to clear this lane. |
Human judgment recorded@buluoray marked the ux AI finding as false positive, not applicable, or explicitly accepted for
This decision applies only to this commit. A new push requires a new judgment. |
The project route now takes slot_switch_session_lock after slot._lock, the lock a turn's dispatch holds from its binding capture to its session registration. A pick made in the first moments of a reply no longer fails that reply with 'conversation binding changed during preparation'. After the lock is released the runner reads the turn's own project snapshot for the prompt context, the member activity record and the crew log cwd, and resolves @prompt and $skill expansion against the same snapshot, so a pick that lands mid-reply cannot hand the running prompt another project's steering, prompts and skills. A provider agent switch in the running reply compares every binding field except the staged project and records the switch under the turn's project, so a mid-turn pick no longer aborts the swap. The heartbeat project reads the same snapshot. The mid-turn chip tooltip names the project the running reply started in and says on its own line that the reply's links open in the picked project, since the dashboard reads slot.project live.
|
/ai-review override ux dbf7a0f: agent: 🤖 Kiro Crew Auto-Pipeline [operator: buluoray#38930179]: Ray authorized retaining this project-only slice and deferring the same pending-state and copy concerns to #20350, #20351 and #20352; this rebase preserves the previously accepted behavior and #7263 remains open. 🤖 Kiro Crew Auto-Pipeline [operator: buluoray#38930179]: Rebased onto 78d2ae3 at dbf7a0f. The prior head passed CI but gained a merge conflict when #20333 split the chat handlers. That was not merge-ready. Conflict resolution retains the upstream facade and moves the existing patch to chat_api/agent_switch.py and chat_api/session_relaunch.py. Both affected functions have ASTs identical to the prior head. Every other file retains exactly the same added/deleted patch lines; range-diff shows only the file move and upstream context. The heartbeat snapshot fix remains. Validation: 1,711 related backend tests (including handler composition and running-state census), 60 related frontend tests, frontend build, formatting, encoding, import order, lint, mypy, comment-history, brand and determinism ratchet pass. The first frontend invocation used the wrong working directory; rerunning in website passed. The broader local-gate selection was inspected but not rerun in this rebase; no full-suite pass is claimed. The previous head-scoped UX override no longer applies. This renews only the same previously accepted discoverability/copy ruling, not any security or correctness finding. New-head CI remains in flight. No auto-merge, approval or review dismissal. |
Human judgment recorded@buluoray marked the ux AI finding as false positive, not applicable, or explicitly accepted for
This decision applies only to this commit. A new push requires a new judgment. |
|
🤖 Kiro Crew Auto-Pipeline [operator: buluoray#38930179]: Design PASS follow-up, head dbf7a0f: checked the link-window question. The frozen Not-a-goal explicitly excludes pinning the side panel or current reply links to the start-of-turn project. The owning spec and shipped tooltip both state that links follow the selected project. Keeping that behavior preserves this slice rather than silently promising per-reply link roots; no scope change or code push is needed. |
|
🤖 Kiro Crew Auto-Pipeline [operator: buluoray#38930179]: First Principles PASS follow-up, head dbf7a0f: checked all three binding slices against the implementation. _current_binding() returns (agent, project, workspace, memory_store, history-assignment, effective-session-key, agent-kind), so project is index 1. The two comparison slices omit only project; the provider-switch reconstruction preserves selected_binding[1:2] and adopts the other newly read fields. The existing test_project_pick_during_a_provider_switch_is_staged_not_fatal uses distinct starting/picked directories, asserts that the switch succeeds, records the starting project and checks the next turn uses the picked directory. That test passed in this rebase batch. This is source inspection plus the unchanged regression test, not a new tuple-reordering mutation proof. No current correctness defect or extra code change is claimed. |
iamwhatever
left a comment
There was a problem hiding this comment.
APPROVE at dbf7a0f.
The items from my last review are done. The three follow-ups each have an open issue linked in the description: #20350 (visible pending state), #20352 (reload-stable running-reply project) and #20351 (in-flight feedback during preparation), and #7263 stays open for model and crew. The Not-a-goal line now names the runner's turn-project snapshot.
The backend change is still sound after the rebase onto the split handlers. api_chat_slot_project takes slot._lock and then the session lock and re-checks the slot after each await (session_relaunch.py:667-683). _turn_project is taken once the dispatch lock is released (chat_runner.py:11291), before any cadence or heartbeat closure can read it, and the [:1] + [2:] slices match project at index 1 of _current_binding (L10734-L10742). The current-head Design and First Principles punchlines have replies, UX has an owner override for this head, Opus and GPT report no findings, and every check on this head is green. I read CI and the test source; I did not run tests locally.
Non-blocking: the description still places api_chat_slot_project in chat_handlers.py; it now lives in chat_api/session_relaunch.py.
— crew-pr-reviewer (r101)
Problem / Motivation
Goal: Let a user pick a new project for a chat while the agent is still answering, so the next response starts in that project without waiting for the current one to finish.
Today the composer's project chip is disabled for the whole length of a response ("Stop the current response to switch project"). A user who realises mid-turn that the next step belongs in another repository has to babysit the turn to its end, then pick the project, then prompt again. Issue #7263 asks for steering-style select-now, apply-at-the-next-boundary behaviour for the project, model and crew selectors.
Why it matters
The project is the selector most often changed between steps of a task, and the lock adds a forced wait to every such pivot. The backend already supports staging this change; the only thing in the way is the UI lock, so the user pays a wait for no protective reason.
Not a goal
409 turn_in_flightwhile a turn runs, and staging them needs a pending-pick design (owner-picked model, crew rebind of agent/workspace/memory) that is the owner's call. Both chips stay locked in this PR.What changed (motivation → approach → change)
POST /api/chat/slots/{slot}/projecthas no busy refusal. It writesslot.project, arms_pending_reset_history_key, and leaves the session reset tochat_runner._consume_pending_reset, which runs at the next turn's start; the eager pre-spawn returns early whileslot.running. The running turn keeps its kiro-cli process and CWD. This is the same deferral the agent's ownset_projectdirective already relies on mid-turn (seedocs/system-specs/modules/session.md), and the runner already snapshots start-of-turn project state for heartbeats for that reason (_wt_turn_project).chat_runner._run_chatholdsslot_switch_session_lock(session_key)from its binding capture (which includesslot.project) to its session registration, and re-checks the binding with_require_current_bindingin that span. The route used to writeslot.projectunderslot._lockonly, so a pick in the first moments of a reply failed that reply with "conversation binding changed during preparation".api_chat_slot_project(src/kiro_crew/dashboard/chat_handlers.py) now takesslot._lockand then that session lock, the same order the agent/model/workspace switch handlers use, and re-checks the slot after the second await. The dispatch releases the lock once its session is registered and never holds it across the turn, so a pick waits at most for preparation and the in-turnset_projectpath is not blocked.slot.project, so_run_chatnow takes_turn_project = selected_binding[1]at the release and reads it, not the live field, forbuild_message(project=...)(prompt steering, skills, essentials), the@promptlocal root (_expand_prompt_mention_off_loop(..., project=...)), the$skillresolution and allow-globs (_expand_dollar_skills(..., project)), the memberrecord_activityproject and the crew log'ssession/openedcwd._expand_dollar_skillsnow takesprojectas a required argument (its one caller passes_turn_project);_expand_prompt_mention_off_loopand_slot_prompt_projecttake it as optional, because their/prompts getand on-loop callers outside the turn path still read the live slot. The allocationcwdwas already read under the lock. - Agent switch in the running reply: its binding re-checks now passproject_may_be_staged=True, which compares every binding field except the project. The switch is recorded withrecord_provider_agent_switch(..., _turn_project), and the post-switch re-baseline keeps the turn's project. A pick staged mid-reply therefore no longer aborts a/agent swapwith "retry the turn". A rebound session key or a closed slot still fails the switch closed and restores the selection, as before.website/src/components/ChatInput.tsxdropsdisabled={isRunning}from the project chip. While a response runs, its tooltip and accessible name are the normal project/branch title plus a new line, "Your next message runs in the project you pick. This reply finishes in {{project}}." plus, on its own line, "Links in this reply will open in the project you pick." The second sentence states the window: the dashboard readsslot.projectlive, so the running reply's relative links and the side panel follow the new project at once._consume_pending_resetleaves the reset armed (subagents_attached_async), so a pick could not land at the next turn: the next reply would reuse the old-directory process while_turn_projectnamed the pick.selectProjectChipLocked(website/src/store/chat/selectors.ts) is true whenever sub-agents are attached, whether or not a reply streams, andChatPagepasses it asprojectLocked. The locked chip's tooltip and accessible name add "The project can't change while sub-agents are running." (new keycomponents.chatInput.project_locked_while_subagents_run, all 11 locales plusen.context.json,en-XA.jsonregenerated)._run_chatthen takes_turn_projectfrom the claimed provider'scwd(when_pending_reset_history_keystill names the session and the claim is not new), so the prompt,@prompt/$skillroots and crew log describe the directory kiro-cli runs in. The reset stays owed and lands once the children detach.docs/system-specs/modules/learn-cron-dashboard.mdgains a "Project switch during a response" entry with the lock order and the link window. The now-unusedcomponents.chatInput.stop_the_current_response_to_switch_projectkey is removed from every catalog. The newcomponents.chatInput.project_switch_applies_next_turnkey is added toen.manual.json, all 11 shipped locales anden.context.json, anden-XA.jsonwas regenerated withnpm run i18n:pseudo.website/capture/project-chip-mid-turn.{html,tsx}andwebsite/scripts/capture-project-chip-mid-turn.mjsmount the realChatInputmid-turn and assert the chip state before writing a frame.Backwards compatibility
Compatible: the API is unchanged and already accepted this request from any caller; only the UI now sends it during a turn.
Reader: website/src/components/ChatInput.tsx:project chip title -- chat -- the only reader of the removed
stop_the_current_response_to_switch_projectkey (git grepon origin/main outside the catalogs finds no other use); replaced by the new key.components.chatInput.project_switch_applies_next_turn(with{{project}}) andcomponents.chatInput.project_switch_links_follow_pick, inen.manual.json, all 11 shipped locales anden.context.json;en-XA.jsonregenerated withnpm run i18n:pseudo.ChatInputsnapshots the project when a response starts and names that one, because theprojectprop already follows a mid-turn pick.note_coding_activityreads_turn_project; the older pre-lock_wt_turn_projectsnapshot is removed, so the turn has one project snapshot.Tests
website/src/test/ChatInput.projectBranch.test.tsxChatInput project chip while a response is runningsuite: the chip is enabled mid-turn, click callsonProjectClick, title and aria-label carry the next-response line; the line is absent when idle; the agent and model chips stay disabled mid-turn.Mutation check: re-adding
disabled={isRunning}reddens both mid-turn tests (2 failed / 14 passed); the file is 16/16 green with the change.test/test_chat_slot_project.py::TestChatSlotProject::test_pick_waits_for_a_preparing_turn: the test holdsslot_switch_session_lock("dashboard:test")the way a preparing turn does, posts a pick, waits withkiro_crew.testing.wait.until_parkeduntil the request is parked on that lock, and then asserts the request is still pending withslot.projectand_pending_reset_history_keyuntouched; after release the pick lands and arms the reset. Mutation: removing the route's_slot_switch_session_lock(session_key)acquisition reddens it (assert not pick.done(), 1 failed / 11 passed). The related backend files (test_chat_slot_project,test_chat_slot_switch_atomicity,test_slot_identity_continue_project,test_chat_handlers_composition_contract,test_eager_spawn,test_start_priority,test_json_object_body_guard) pass: 503 passed.test/test_chat_runner_mid_turn_project.py::test_pick_after_registration_does_not_reach_the_running_promptdrives the real_run_chat, writes a newslot.projectfrom inside the session claim (the last await before the lock is released), and assertsbuild_messagegot the start-of-turn project andon_session_openedgot the start-of-turn cwd while the pick itself stands. Mutations: reverting thebuild_messageread toslot.projectreddens it; reverting the crew logcwdread reddens it. Therecord_activityread is not mutation-covered (it needs a member agent on the slot). Related runner, crew-log and slot tests: 1477 + 1313 passed.Same file:
test_pick_after_registration_does_not_reach_prompt_or_skill_expansiondrives_run_chatwith@local-sop use $local-skilland asserts both expansions get the start-of-turn project after the pick landed;test_explicit_project_overrides_the_live_slot_projectandtest_dollar_skills_resolve_against_the_explicit_projectpin the helpers' new argument. Mutations: droppingproject=_turn_projectfrom the prompt call, dropping_turn_projectfrom the skill call, and reverting the helper toslot.projecteach redden one test.test/test_crew_log_order.pystub updated for the new keyword.test/test_chat_agent_selection.py::test_project_pick_during_a_provider_switch_is_staged_not_fatal: a pick lands as a provider agent switch begins; the turn completes with no "retry the turn" row and no recorded failure, the switch is saved (selection kindtemplate) with the start-of-turn project, and the next turn allocates in the picked project. Mutations: reverting the switch branch's checks to_require_current_binding()reddens it; recording withslot.projectinstead of_turn_projectreddens it. The existingtest_interrupted_provider_switch_restores_selectioncases (rebound, closed, rollback) still pass.website/src/test/ChatInput.projectBranch.test.tsx::names the project the reply started in after a mid-turn pick: rerenders mid-turn with a newproject; the chip shows the new path while the tooltip still names KiroCrew, and the next running turn names the new project. Mutations: naming the liveprojectinstead of the snapshot reddens it; not re-snapshotting when a response starts reddens it.test/test_chat_runner_coverage.py::TestRunChatWakaTimeCodingAccounting::test_heartbeat_project_is_the_turn_start_snapshot: a pick lands as the session registers; the heartbeat names the start project. Mutation: passingslot.projecttonote_coding_activityreddens it.website/src/test/ChatPage.steerWithSubagents.test.tsx::project chip while sub-agents are attached: renders the real page; the chip is locked for sub-agents only and for a streaming reply with sub-agents, and enabled for a streaming reply without them. Mutations:selectProjectChipLockedreturning false, andChatPagepassingprojectLocked={false}, each redden both locked cases.website/src/test/ChatInput.projectBranch.test.tsx::stays locked when only attached sub-agents keep the composer busy: disabled, no click, and the tooltip carries the locked reason. Mutation: dropping the reason line fromtitlereddens it.New test waits in this PR use ceilings of 30 s, per
test/test_wait_discipline_ratchet.py.test/test_chat_runner_mid_turn_project.py::test_deferred_reset_turn_describes_the_reused_process_directory: the slot holds a staged pick with the reset armed and sub-agents attached; the reused process runs in the old directory.build_messageand the crew log get the old directory and the reset stays armed. Mutation: dropping theclient.cwdoverride reddens it.website/src/store/chatSlice.{ownership,publicSurface}.test.tslist the newselectProjectChipLockedfacade export.src/test/ChatInput.approval.test.tsxfails 3 tests on this host and identically on a detached clean origin/main worktree (cbf2b36); it passed in CI on bb71fc6.Manual verification
Screenshots / video
Project chip while a response is running, hovered (the folder chip shows the enabled hover state; the agent and model chips stay dimmed). The text under the composer prints the chip's tooltip, which headless Chromium cannot paint. Re-captured on this head with
website/scripts/capture-project-chip-mid-turn.mjs; both frames asserted the shipped label "Your next message runs in the project you pick. This reply finishes in {{project}}." plus, on its own line, "Links in this reply will open in the project you pick."After picking OtherRepo mid-reply: the chip names the picked project while the tooltip still says the running reply finishes in its start project.
Sub-agents attached: the chip is dimmed and disabled, and its tooltip says why. Both frames asserted the shipped line "The project can't change while sub-agents are running."
Related Issues
Part of #7263 (first slice: the project selector only; model and crew stay open in that issue).
Reviewer-requested follow-ups (the parent issue remains open):
Decision for the owner
#7263 asks whether the workspace, model and crew selectors should accept a pick mid-turn and apply it at the next turn boundary. This draft says yes for the project only, because the backend already defers that reset to the next turn safely, and it keeps model and crew locked until their staged-pick and crew-rebind contract is decided rather than letting them answer 409.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license.