Skip to content

refactor: rename Ultra Mode to conductor mode - #36924

Merged
bolichen97 merged 1 commit into
mainfrom
refactor/rename-ultra-to-orchestrator-mode
Nov 14, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
refactor/rename-ultra-to-orchestrator-mode

Conversation

@bolichen97

@bolichen97 bolichen97 commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Every place a person reads the crew feature's name says conductor mode instead of Ultra Mode, and nothing an existing install saved stops working.

A maintainer ruling settled the feature's final name as conductor mode. Today the composer chip, the Sessions row tag, the Board panel, settings labels and search entries, gateway notices, agent prompts, skills, shipped docs and specs all still say Ultra Mode.

Why it matters

The old name is on every surface of a feature that is being launched. Each day it stays, more people, docs and saved prompts learn a name that is about to go away, and the code keeps naming one feature two ways.

Not a goal

  • Changing what conductor mode does, or how a run reports that it is done.
  • Renaming ids that never said "ultra": crew_mode, crew_root, dashboard.new_chat_crew_mode, agent.crew_mode_agent, the mc-preview-crew-mode flag, the crew view id.
  • Renaming the Claude "Ultracode" model-effort toggle, the retired ultra reply-verbosity level, or the glass ultrathin / ultrathick thicknesses. They are other features.
  • Editing existing decision entries, old RFCs, the task-spec archive or CHANGELOG.md.
  • Repositories outside this one.

What changed (motivation → approach → change)

People now see conductor mode wherever they saw Ultra Mode. It is written the way the dashboard writes "bots": "Conductor mode" at the start of a label or sentence, "conductor mode" inside one. Non-English catalogs keep the English name, written "Conductor mode" as they write "Bot". One mechanical rule set does the rename, so the code, the docs and the UI cannot drift apart.

Area What it says now
UI text, 13 locale catalogs, glossary conductor mode (chip, Sessions row tag, Board panel, welcome, notices, settings)
Code names ConductorModeCrewPanel, ConductorModeEffect, conductorModeEffect.ts, conductor_mode_* i18n keys, conductor-mode-* CSS classes, tokens and test ids, test names, capture harnesses, conductor_mode_shape() in tracing
Backend text gateway notices and errors, config labels and help, agent prompts, the goal-conductor skill, docstrings
Docs AGENTS.md, specs (crew-mode, metrics and others), architecture, guides, feature map, shipped user docs
Generated settings registry, UI index, guide plans, en-XA pseudolocale, config baseline, rebuilt by their generators
Decisions new entry docs/decisions/2026-11-13-the-crew-mode-feature-is-named-conductor-mode.md and its README row

The same swap reaches comments, strings and names in src/kiro_crew/agent_materialization, src/kiro_crew/agent_parts, src/kiro_crew/builtin_skills, src/kiro_crew/config, src/kiro_crew/context_assembly, src/kiro_crew/crew_log, src/kiro_crew/crew_mode.py, src/kiro_crew/crew_pause.py, src/kiro_crew/dashboard_agentic.py, src/kiro_crew/docs, src/kiro_crew/mcp_dashboard_caller_scope.py, src/kiro_crew/mcp_dashboard_session_runs.py, src/kiro_crew/mcp_tools, src/kiro_crew/security_posture_sinks_gateway.py, src/kiro_crew/slack, src/kiro_crew/tracing, and website/src/api, website/src/hooks, website/src/shell, website/src/store, website/src/styles and website/src/uiLocations; config-baseline.json is regenerated.

"Conductor" already names the agent role (kirocrew-conductor, conductor_close.py, the conductor-needs-you / conductor-status / conductor-view-* test ids). So every renamed code name carries a ConductorMode / conductor_mode / conductor-mode stem and never collides with them. Prose such as "the Ultra Mode conductor" is rewritten ("the conductor in conductor mode") rather than swapped.

Two labels keep Title Case because their sibling labels are Title Case: "Start New Chats in Conductor Mode" (settings) and "Traces: Conductor Mode Shape" (config).

The new decision entry supersedes, in part, the 2026-10-29 entry that named the surfaces Ultra Mode, and the 2026-10-30 line that kept the word "conductor" out of user text, for the feature's own name only. The other entries written under the old name stay byte-identical, and the new entry says they apply to conductor mode.

After the change, git grep -i ultra finds only:

  • the Ultracode toggle, the retired ultra verbosity level and its ultra-brief change-card fixture, glass ultrathin / ultrathick, effort and quality test values, jev-ultrafast, a font name, plain English and Portuguese words, and false matches such as defaultRaf;
  • src/kiro_crew/_vendor/ (2 files);
  • old decision entries and their README rows, old RFCs and the RFC README, the task-spec archive, CHANGELOG.md;
  • the new decision entry, which names the old entries' files;
  • the allowlist below.

Allowlist (kept on purpose):

  • ultra_mode_only: the remote-dispatch refusal code. A conductor on another machine matches on it. The Python constant is now CONDUCTOR_MODE_ONLY, and the test that pins the code keeps its name.
  • ultra: the value of the kirocrew.crew.root_kind trace attribute, the trace kind behind trace.ultra, and the span names ultra round N / ultra outcome .... Exported traces carry them and saved trace queries filter on them.
  • telemetry.traces_ultra_mode: a saved config key, read as-is.
  • Ultra Mode in website/src/pages/chat/gatewayNotice.ts and one case in its test, so a transcript that stored the old agent-switch notice still renders as that notice.

Backwards compatibility

Compatible: no config key, localStorage key, saved setting, route or event a running install stores is renamed. The wire values, the saved config key and the stored notice wording above keep reading.

Reader: website/src/pages/chat/gatewayNotice.ts:agent_switch_blocked_crew_mode -- chat -- the regex matches both the "conductor mode" and the stored "Ultra Mode" wording; gatewayNotice.test.tsx covers both
Reader: src/kiro_crew/dashboard/handlers/remote_dispatch_routes.py:CONDUCTOR_MODE_ONLY -- crew page -- value stays ultra_mode_only; test_a_plain_owner_chat_is_refused_ultra_mode_only
Reader: src/kiro_crew/tracing/crew.py:ROOT_KIND_CONDUCTOR_MODE -- chat -- value stays ultra; test/tracing/test_tracing_runs.py
Reader: src/kiro_crew/tracing/provider.py:conductor_mode_shape -- chat -- still reads telemetry.traces_ultra_mode; test/tracing/test_tracing_work.py
Reader: website/src/components/commandPalette/settingsRegistry.gen.ts:developer.conductor-mode -- chat -- setting ids are slugs of the English label and are not stored; an old ?highlight=developer.ultra-mode link still opens the Feature Previews page, without the highlight
Reader: website/src/i18n/locales/.json:components.crewMode.conductor_mode_ -- chat -- keys ship inside the bundle; every caller is renamed in the same commit (npm run i18n:check)

Tests

Renamed tests keep their assertions; text assertions follow the new casing. gatewayNotice.test.tsx adds one case: a stored "Ultra Mode" agent-switch notice still resolves to the notice text.

Proof: not provable -- other: refactor (rename) PR with no behavior fix; the one behavior pin is a frontend test

Determinism (testing-conventions D12): the 9 renamed backend tests passed 20 of 20 runs at -n0, their files passed 10 of 10 at -n 4 (288 tests), and they passed in a shuffled order. gatewayNotice.test.tsx passed 20 of 20 runs, and the 7 changed frontend test files passed shuffled (335 tests).

Local runs on the reviewed patch: black (26.10.1), isort, flake8, mypy (4627 files), comment-history, brand name, file line cap, docs-lint, decision-ledger history, feature map, npm run i18n:check (diff-scoped), tsc, semgrep (0 findings), the flake-pattern ratchet, 197 related frontend test files and 274 related backend test files plus test/tracing. Two backend tests fail the same way on a clean origin/main checkout: test_find_ui_auto.py::test_the_generated_auto_tier_answers_labels_only_it_carries[continue with github...] and test/tracing/test_tracing_otlp.py::test_a_header_echoed_back_by_a_failure_reaches_no_log_record[library_error].

Local review in slices

The diff is 1.1 MB, over the 1 MB limit at which the AI review lanes fail closed. It was reviewed locally on this head in five slices, each by the model-pinned GPT and Opus lanes with the CI contract prompts:

Slice Files GPT Opus
1. Python source, shipped docs, specs, docs src/kiro_crew/**, docs/**, AGENTS.md, config-baseline.json (397 KB) PASS, no findings PASS, 3 Low (a UI-path label's casing, the decision entry's kept-values list, "conductor mode ... conductor" wording): fixed
2. Website source outside i18n and tests components, pages, lib, styles, capture (147 KB) PASS, no findings PASS, 3 Low (comment and capture-title casing): fixed
3. i18n catalogs and data 13 catalogs, glossary, plural keys, context (412 KB) PASS, no findings PASS, 1 Low (a hint naming the section label in lower case): fixed; 1 pre-existing note (the glossary lists the term twice, as main did) left
4. Tests backend and frontend tests (156 KB) PASS, no findings PASS, 2 Low (a See what ... looks like regex that could no longer match, so the check was vacuous; heading-comment casing and ruler width): fixed
5. Rename completeness, whole tree git grep for leftovers, every new name against its definition and imports, collisions with existing conductor names, interim-name check PASS, no findings PASS, 1 Low (old setting ids in ?highlight= links and stored cards): rebutted, neither id has a card write path (resolve_setting refuses both with no_write_path), and an old link still opens the right page

The four slice diffs sum to the whole diff (190 files, 1,111,772 bytes). After the fixes, one GPT and one Opus verifier checked the fix delta on this head: both PASS, no findings.

Manual verification

I built the SPA before and after the change and loaded it gateway-free (dark theme, English): a conductor chat with the Board open at 1400 px and 390 px, and a new chat with the chip pressed at 1400, 390 and 320 px. The chip is 141 px wide (it was 109 px), the Sessions row tag fits beside the time, the footer mark fits, and the Board tab still reads "Board". The welcome title stays on one line at 390 px and wraps cleanly onto two lines at 320 px.

Screenshots / video

Before and after: composer chip, Sessions row tag, footer mark

Board open, and the welcome at 390 px and 320 px

Board open after the rename

Welcome at 390 px

Welcome at 320 px

Related Issues

Closes #36869

Waiting for a maintainer (human-only):

  • recorded-decisions-are-not-regressions: the new decision entry supersedes part of two recorded decisions, so this gate blocks by design (docs/decisions/README.md rule 3) until a maintainer restates the ruling on this PR.
  • Sensitive Change Review: src/kiro_crew/security_posture_sinks_gateway.py changes (one description string), so it needs the reasoned approval of a maintainer.
  • The merge approval of a maintainer.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners November 13, 2026 23:19
@bolichen97
bolichen97 requested a review from CrysisDeu November 13, 2026 23:19
@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Sensitive Change Review

Sensitive files changed:

  • src/kiro_crew/security_posture_sinks_gateway.py

  • @KiroCrewCaptain: missing the ## Sensitive change review heading

How to clear this check:

  1. The PR author posts the template below as a PR comment, with
    every field filled (N/A needs a reason). Keep the
    Head commit line: it must name the current head SHA.
  2. The check turns green within a minute, with no push.
  3. A new push resets this check: post it again for the new head.

Only the author's comment counts this way. A reviewer can instead
paste the filled template into an "Approve" review on this head.
Merging still needs a reviewer's approval.

## Sensitive change review
- Head commit: 3503e0f44781c3f6627976d583a8828bdc44c9fa
- What rule changed:
- Before -> after (what was allowed/blocked, now):
- Worst case if wrong (breaks commands / leaks secret / locks user out):
- Evidence checked (which sandbox result proves it):
- No regression:
  - Tools still work (which tools/commands were run, result):
  - Backward compatible (old config / old data / old callers still work, how checked):
  - Existing tests (which suites passed on this head):
- How to undo:

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 13, 2026
@bolichen97
bolichen97 enabled auto-merge (squash) November 13, 2026 23:20
@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 3503e0f44781c3f6627976d583a8828bdc44c9fa — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing blocks. Every item is the rename. Issue #36869 and the maintainer-signed decision entry are the source for it. The values an install has already saved keep their old spelling on purpose.

What this change ships

Inventory (10 items) — 10 justified

Intent: people see the crew feature under its final name, conductor mode, and nothing an existing install saved stops working. This is a FIX: a relabel.

  1. The composer chip, Sessions row tag, Board panel, welcome text and settings labels now say "conductor mode" — justified
  2. The 13 non-English catalogs show "Conductor mode" untranslated, the way they show "Bot" — justified
  3. Gateway notices, errors, config help, agent prompts and the goal-conductor skill text say conductor mode — justified
  4. A settings search link with the old id opens the page without the highlight — justified
  5. Code names, i18n keys, CSS classes and test ids use the conductor_mode stem — justified
  6. A stored "Ultra Mode" agent-switch notice still renders as that notice — justified
  7. The values ultra_mode_only and ultra, the ultra span names and telemetry.traces_ultra_mode keep their spelling — justified
  8. AGENTS.md, specs, guides and shipped user docs use the new name — justified
  9. A new decision entry replaces parts of the 2026-10-29 and 2026-10-30 entries — justified
  10. The settings registry, UI index, pseudolocale and config baseline are regenerated — justified

[FIRST-PRINCIPLES-REVIEWED] 3503e0f

Description read

[DESCRIPTION-READ] 1a3df101b2ef0a2d22b378fbc190ef6044cd8be49063fb049b8fdb0a9caebc7c

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ human override accepted

Reviewed 3503e0f44781c3f6627976d583a8828bdc44c9fa — this comment is updated in place on each push.

Human judgment by @bolichen97 overrides the Opus 5.5 finding for 3503e0f44781c3f6627976d583a8828bdc44c9fa; the recorded reason is authoritative for this commit.

[OPUS-OVERRIDE] 3503e0f

Verdict recorded from an authorized human decision for commit 3503e0f44781c3f6627976d583a8828bdc44c9fa.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 3503e0f44781c3f6627976d583a8828bdc44c9fa false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 3503e0f44781c3f6627976d583a8828bdc44c9fa and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 3503e0f

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 3503e0f44781c3f6627976d583a8828bdc44c9fa false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Nov 13, 2026
@bolichen97 bolichen97 changed the title refactor: rename Ultra Mode to Orchestrator Mode refactor: rename Ultra Mode to conductor mode Nov 14, 2026
@bolichen97
bolichen97 force-pushed the refactor/rename-ultra-to-orchestrator-mode branch from 3c4b8e6 to 54a2f62 Compare November 14, 2026 01:23
@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 14, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

The title and the Goal: line now use the final product name, conductor mode, at a maintainer's request. The goal is otherwise unchanged.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 14, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override design 54a2f62 not-applicable: agent: owner-authorized (maintainer ruling): diff is a mechanical rename over the lane size limit; reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override ux 54a2f62 not-applicable: agent: owner-authorized (maintainer ruling): diff is a mechanical rename over the lane size limit; reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a not-applicable release (class not-applicable) for the design AI finding on 54a2f621f76337c0a76d122a6c7800a1e68317f4.

agent: owner-authorized (maintainer ruling): diff is a mechanical rename over the lane size limit; reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a not-applicable release (class not-applicable) for the ux AI finding on 54a2f621f76337c0a76d122a6c7800a1e68317f4.

agent: owner-authorized (maintainer ruling): diff is a mechanical rename over the lane size limit; reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ human override accepted

@bolichen97 overrode this lane for 3503e0f44781c3f6627976d583a8828bdc44c9fa via /ai-review override (this commit only).

@github-actions

github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ human override accepted

@bolichen97 overrode this lane for 3503e0f44781c3f6627976d583a8828bdc44c9fa via /ai-review override (this commit only).

@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override gpt 54a2f62 not-applicable: agent: owner-authorized (maintainer ruling): the blocking finding is the by-design recorded-decisions gate on the new superseding decision entry; the diff is a mechanical rename reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a not-applicable release (class not-applicable) for the gpt AI finding on 54a2f621f76337c0a76d122a6c7800a1e68317f4.

agent: owner-authorized (maintainer ruling): the blocking finding is the by-design recorded-decisions gate on the new superseding decision entry; the diff is a mechanical rename reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

This decision applies only to this commit. A new push requires a new judgment.

@bolichen97
bolichen97 force-pushed the refactor/rename-ultra-to-orchestrator-mode branch from 54a2f62 to 29534d3 Compare November 14, 2026 01:48
The crew feature's final product name is conductor mode. Every
user-facing place that said Ultra Mode says conductor mode: UI strings
in all locales (kept untranslated), settings labels and their generated
search entries, gateway notices, agent prompts and skills, shipped docs,
specs and the feature map. Code names that carried the old name
(components, CSS classes and tokens, test ids, i18n keys, tests, capture
harnesses) follow it, with a ConductorMode / conductor_mode /
conductor-mode stem so they never collide with the existing conductor
agent-role names.

Saved state keeps working: ids that never said ultra stay (crew_mode,
dashboard.new_chat_crew_mode, mc-preview-crew-mode), the ultra_mode_only
refusal code and the ultra root_kind trace value keep their spelling, and
a transcript that stored the old agent-switch notice still renders as
that notice. A new decision entry records the rename and maps the
earlier entries to the new name; those entries stay as written.
@bolichen97
bolichen97 force-pushed the refactor/rename-ultra-to-orchestrator-mode branch from 29534d3 to 3503e0f Compare November 14, 2026 02:51
@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override design 3503e0f not-applicable: agent: owner-authorized (maintainer ruling): diff is a mechanical rename over the lane size limit; reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override ux 3503e0f not-applicable: agent: owner-authorized (maintainer ruling): diff is a mechanical rename over the lane size limit; reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a not-applicable release (class not-applicable) for the design AI finding on 3503e0f44781c3f6627976d583a8828bdc44c9fa.

agent: owner-authorized (maintainer ruling): diff is a mechanical rename over the lane size limit; reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded, but the following reviewer lane(s) could not be re-run automatically: Design Review. Re-run the lane's latest workflow run for 3503e0f44781c3f6627976d583a8828bdc44c9fa manually from the Actions tab.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a not-applicable release (class not-applicable) for the ux AI finding on 3503e0f44781c3f6627976d583a8828bdc44c9fa.

agent: owner-authorized (maintainer ruling): diff is a mechanical rename over the lane size limit; reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

This decision applies only to this commit. A new push requires a new judgment.

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded, but the following reviewer lane(s) could not be re-run automatically: UX Review. Re-run the lane's latest workflow run for 3503e0f44781c3f6627976d583a8828bdc44c9fa manually from the Actions tab.

@bolichen97

Copy link
Copy Markdown
Contributor Author

/ai-review override fable 3503e0f not-applicable: agent: owner-authorized (maintainer ruling): the blocking finding is the by-design recorded-decisions gate on the new superseding decision entry; the diff is a mechanical rename reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

@github-actions

Copy link
Copy Markdown
Contributor

Human judgment recorded

@bolichen97 recorded a not-applicable release (class not-applicable) for the fable AI finding on 3503e0f44781c3f6627976d583a8828bdc44c9fa.

agent: owner-authorized (maintainer ruling): the blocking finding is the by-design recorded-decisions gate on the new superseding decision entry; the diff is a mechanical rename reviewed locally in slices by GPT and Opus, no open findings; evidence in the PR body

This decision applies only to this commit. A new push requires a new judgment.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 14, 2026

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed head 3503e0f. The rename is complete. No removed Python symbol is still referenced in src, test or website. The i18n keys map one to one from ultra_* to conductor_mode_* in the catalogs compared, with no placeholder drift. Every renamed CSS class, token and test id has a definition. Test case counts are the same before and after, with no assertion dropped. A merge with current main is clean and leaves no old name outside the documented allowlist.
Done well: the values running installs already hold keep their spelling, and each has a comment saying why. These are the ultra_mode_only refusal code, the ultra trace kind, the span names and telemetry.traces_ultra_mode. The gatewayNotice regex also accepts both wordings, with a test for each.
Optional:

  • test/test_session_control_crew.py:653 compares against crew.CONDUCTOR_MODE_ONLY, so it would still pass if the wire value changed. Asserting the literal "ultra_mode_only" would make the backwards-compatibility claim hold.
  • The decision entry supersedes two recorded decisions. A short PR comment from the deciding maintainer that states the ruling, cited from the entry, would give it a clear record.
  • Open PRs #36830, #23512, #31518 and #37044 add new "Ultra Mode" text. #23512 also asserts the old aria-label. These authors will need to rebase onto the new name after this lands.

@bolichen97
bolichen97 merged commit 176820c into main Nov 14, 2026
101 of 107 checks passed
@bolichen97
bolichen97 deleted the refactor/rename-ultra-to-orchestrator-mode branch November 14, 2026 04:30
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 14, 2026
buluoray added a commit that referenced this pull request Nov 15, 2026
The crew feature's final product name is conductor mode. Every
user-facing place that said Ultra Mode says conductor mode: UI strings
in all locales (kept untranslated), settings labels and their generated
search entries, gateway notices, agent prompts and skills, shipped docs,
specs and the feature map. Code names that carried the old name
(components, CSS classes and tokens, test ids, i18n keys, tests, capture
harnesses) follow it, with a ConductorMode / conductor_mode /
conductor-mode stem so they never collide with the existing conductor
agent-role names.

Saved state keeps working: ids that never said ultra stay (crew_mode,
dashboard.new_chat_crew_mode, mc-preview-crew-mode), the ultra_mode_only
refusal code and the ultra root_kind trace value keep their spelling, and
a transcript that stored the old agent-switch notice still renders as
that notice. A new decision entry records the rename and maps the
earlier entries to the new name; those entries stay as written.

Hand-resolved backport; original author: Bolin Chen.

(cherry picked from commit 176820c)
buluoray added a commit that referenced this pull request Nov 15, 2026
…ename

The rename changes the text of the two conductor agent specs and of
_CONDUCTOR_SYSTEM_PROMPT. Main re-pinned the same pins in #36924, but
release/0.13.0 builds those specs from its own prompts, so its digests
differ from main's. Only kirocrew-conductor.json and
kirocrew-ledger-conductor.json change; every other pinned spec keeps its
bytes.
buluoray added a commit that referenced this pull request Nov 15, 2026
The crew feature's final product name is conductor mode. Every
user-facing place that said Ultra Mode says conductor mode: UI strings
in all locales (kept untranslated), settings labels and their generated
search entries, gateway notices, agent prompts and skills, shipped docs,
specs and the feature map. Code names that carried the old name
(components, CSS classes and tokens, test ids, i18n keys, tests, capture
harnesses) follow it, with a ConductorMode / conductor_mode /
conductor-mode stem so they never collide with the existing conductor
agent-role names.

Saved state keeps working: ids that never said ultra stay (crew_mode,
dashboard.new_chat_crew_mode, mc-preview-crew-mode), the ultra_mode_only
refusal code and the ultra root_kind trace value keep their spelling, and
a transcript that stored the old agent-switch notice still renders as
that notice. A new decision entry records the rename and maps the
earlier entries to the new name; those entries stay as written.

Hand-resolved backport; original author: Bolin Chen.

(cherry picked from commit 176820c)
buluoray added a commit that referenced this pull request Nov 15, 2026
…ename

The rename changes the text of the two conductor agent specs and of
_CONDUCTOR_SYSTEM_PROMPT. Main re-pinned the same pins in #36924, but
release/0.13.0 builds those specs from its own prompts, so its digests
differ from main's. Only kirocrew-conductor.json and
kirocrew-ledger-conductor.json change; every other pinned spec keeps its
bytes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename Ultra Mode to conductor mode across the product

2 participants