Skip to content

feat(voice): optionally tell the agent a message was dictated - #32016

Merged
bolichen97 merged 1 commit into
mainfrom
pearcekieser/dictation-note-setting
Nov 10, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
pearcekieser/dictation-note-setting

Conversation

@Pearcekieser

@Pearcekieser Pearcekieser commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Let someone who dictates turn on a setting that tells the agent a message was dictated, so the agent reads transcription errors charitably.

A dictated message reaches the agent as plain text, indistinguishable from typing. Speech-to-text produces misheard words, odd punctuation and words in the wrong place, and the agent takes them literally: it acts on the wrong word or asks about an obvious transcription error.

Why it matters

People who dictate most of their messages hit this on nearly every turn. The agent already knows how to read a sloppy transcript generously; it just has no way to know the text was spoken.

Not a goal

  • Changing how dictated text is inserted, edited or shown in the composer.
  • Telling the agent about dictation on channels other than the dashboard composers (Slack voice notes, phone channels).
  • Hiding the note from the transcript or rendering it as a chip.
  • Recognising dictation in text that was pasted or typed from another dictation tool.
  • Tracking which words of a message were dictated. The record is per composer (see below).

What changed (motivation → approach → change)

A new checkbox, "Tell the agent this was dictated", sits under Settings → Voice → Fine-tuning. It is stored as stt.dictation_note, off by default. When it is on, a message that holds words the composer's dictation wrote ends with exactly one line, [This message was dictated. It may contain transcription errors, odd typos, misplaced words, or punctuation.]. A typed-only message and a slash command never get it.

The note is part of the message text, like the gateway's own provenance lines ([sent by session …]). A request flag the gateway appends for the agent only would have to ride the queue, a steer, the sub-agent hold, regenerate and resume, or lose the note. In the text it reaches the agent on every path.

The voice hook records that a composer holds dictated words whenever it writes them (streaming, batch, an off-screen delivery, a retried recording); the words themselves are never inspected. The record is keyed by session and composer, because the main chat, a split pane and a crew window each keep their own draft of a session. It lives in session storage (mc-dictated-drafts, at most 200 entries), so it survives a reload as long as the shortest-lived draft does. It never moves to a new chat that takes over text.

Each send and steer takes the record and decides the note. The command check runs on the finished outgoing text, after any quote, with the gateway's rule (starts with / after leading whitespace). A send that hands its text back (refused, failed, a returned steer, a cancelled queued card, the "not confirmed" restore strip) puts the record back from a flag it carries. Emptying the composer, a command or a discard clears it.

The rule is per composer, not per word: a composer counts as dictated from its first dictated word until it is sent or emptied, even if an edit deletes every dictated word. Per-span tracking needs a text model the composer lacks, and a hand-fixed message still started as speech; the module doc says so.

Where it lives:

  • Setting: src/kiro_crew/config/sections_stt.py, section_builders.py, and the STT config GET/PUT in src/kiro_crew/dashboard/handlers/core_stt_settings.py; regenerated config-baseline.json, the src/kiro_crew/docs/ registry and UI index, and the command palette registry, plus configuration.md. The checkbox is in website/src/pages/settings/SttSettings.tsx, with its label and description in every catalog under website/src/i18n/locales/.
  • Record and note: website/src/chat-core/composer/dictationProvenance.ts, with the note text in dictationNote.prompt.ts; marked from useComposerVoice.ts, appended in outgoingTurn.ts.
  • Send paths: website/src/pages/chat/page/composerSend.ts, busyTurnControls.ts and turnActions.ts for the main chat, with composerDrafts.ts clearing on an emptied composer and never moving it to a new chat; website/src/components/useChatPaneSend.ts and ChatPane.tsx for panes; website/src/pages/chat/crew-window/CrewChatWindow.tsx and crewWindowStore.ts for crew windows; website/src/hooks/useQueuedMessageActions.ts for a cancelled queued card.

Known limits, left for a follow-up:

  • The note path trims trailing whitespace from the outgoing text.
  • Words dictated while a new chat is being created move to it without the note, so a typed message there is never marked.

Backwards compatibility

Compatible: the setting is new and off by default, so no message changes until someone turns it on.

Removes nothing: the PR adds a setting and a suffix; no key, path, validator or record is removed or narrowed.

Tests

  • dictationProvenance.test.ts pins the record's rules (per session and composer, taken by a send, cleared by an empty composer, kept across a reload) and the note (exact text, once, at the end, never on a command), and that the setting is read live from the shared STT config.
  • outgoingTurn.test.ts rows put the note at the very end of both texts, after session links and around a quote or expanded paste, on send and steer, without changing typedOnly. A command gets no note, a quoted message whose own text starts with a slash still gets one, and text that already ends with the note gets no second one.
  • useComposerVoiceDictationNote.test.tsx drives the voice hook: batch, streaming and off-screen deliveries mark the right session and composer, a slot switch keeps the mark where it was, and a discard or a hypothesis that retracts to nothing removes only the mark it set.
  • ChatPage.dictationNote.test.tsx covers the main composer: one note when dictated and on, none when typed or off, none on the next typed message, a refused send and a refused steer handing the words back and adding the note once on retry, typed text ending with the note line coming back whole, emptying the composer, a command sent from a dictated composer, a composer with no chat yet dropping its record once it shows a chat, a slot switch, and a new chat that takes over text entered while it was created, which starts unmarked while a dictated draft left behind keeps its note.
  • ChatPane.dictationNote.test.tsx covers the pane: send, steer, a steer demoted to the queue stashing its provenance, rebinding to another member, and words dictated into the main chat that do not mark a message typed in the pane for the same session. ChatPane.slashIntercept.test.tsx adds a /side that clears the mark.
  • CrewChatWindow.test.tsx covers a crew window: a dictated send ends with the note, a refused one comes back without it and the retry carries it once, and the next typed message carries nothing. crewWindowTranscript.test.ts checks that an off-screen delivery, including one into a rewind box, names the draft box it marks.
  • useQueuedMessageActions.test.tsx restores provenance from a stash hit and never infers it from a card's text.
  • SttSettings.surface.test.tsx checks the toggle lives under Fine-tuning, is off, and saves { dictation_note: true }.
  • test/test_stt_dictation_note.py covers the default, the loader's bool-only rule, and the PUT/GET round trip.

Determinism: every new test is synchronous or awaits a rendered state with waitFor; none sleeps, uses timers or depends on order. The new and touched vitest files (250 tests) passed 3 repeated runs and a --sequence.shuffle run; test_flake_pattern_ratchet.py passes.

Manual verification

A throwaway pod ran this branch's built dashboard against its own gateway, driven by Playwright in headless Chromium. That run was on an earlier version of the branch, before it was rebased onto current main and before the per-composer scope, the crew window, reload persistence and the command check were added. Those later changes are covered by the unit tests above, which ran on the final head. The microphone was a synthetic Web Audio stream with a recorder stub, because headless Chromium has no audio input. The recogniser was faked: batch transcription answered a fixed transcript, and the streaming socket sent scripted ready, partial, final and endpoint frames. Only the STT availability fields of the config read were overridden, because the pod has no speech model; the dictation_note value, settings writes, chat sends and the stored transcript were real. Results:

  • The setting is off on a fresh home and survives a reload once turned on.
  • Batch dictation sent by hand, an edited transcript, streaming dictation sent by hand and a streaming auto-submit each went out ending with one note.
  • A typed-only message and a dictated message with the setting off went out unchanged.
  • The gateway's stored user row carries the note.
  • Some of these sends met a busy session, and the gateway answered them as a queued send and a steer.

Local review: two model reviewers and a verifier ran four rounds on this branch. The fourth answered the CI findings on the create carry, and the fix for them was written in this session, not by a separate model-pinned repair agent. The GPT reviewer ran on gpt-5.6-sol because the profile's gpt-6.1-sol is not served on this account, so that lane ran at lower fidelity than the profile asks for.

Screenshots / video

The checkbox under Fine-tuning, on:

Settings → Voice → Fine-tuning with "Tell the agent this was dictated" switched on

A dictated message as sent and stored, with the note on its own line; the earlier message above it was sent with the setting off:

A transcript where the last user message ends with the dictation note

Related Issues

Fixes #32015

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

@Pearcekieser
Pearcekieser requested review from a team and KiroCrewCaptain as code owners November 7, 2026 03:00
@github-actions github-actions Bot added merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 7, 2026
@Pearcekieser
Pearcekieser force-pushed the pearcekieser/dictation-note-setting branch from bb899d9 to 50ab995 Compare November 7, 2026 04:30
@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 7, 2026
@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of fa16558b289fee08908454edcba2bea5e0e0e845 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: the setting is opt-in and off by default, and the description explains why the note goes in the message text instead of a request flag.

Notes

  • The note is saved in the message itself, so session titles, summaries, memory extraction and history search will all read it. Turning the setting off later does not remove it from messages already sent. Consider having the parts that derive titles and summaries strip this exact line.

[DESIGN-REVIEWED] fa16558

Description read

[DESCRIPTION-READ] 2cd9aee2f0e372c018fb50ca779656c9725d8cc9abff630455ebd55e82ff06e5

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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of fa16558b289fee08908454edcba2bea5e0e0e845 — 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. The new setting is off by default, so nobody's messages change unless they turn it on. Each part of the change has a real problem to solve, code that uses it, and no existing mechanism that already does it.

What this change ships

Inventory (7 items) — 7 justified

Intent: a person who dictates wants the agent to read speech-to-text errors generously instead of literally. This is an ADDITION.

  1. New checkbox "Tell the agent this was dictated" under Settings → Voice → Fine-tuning, off by default — justified
  2. When it is on, a message holding dictated words ends with one note line, which also shows in the transcript — justified
  3. New config key stt.dictation_note, read and saved through the STT config GET/PUT — justified
  4. Slash commands never get the note, so it cannot become part of a command's arguments — justified
  5. A refused or failed send, a returned steer, or a cancelled queued card keeps its "dictated" mark when the text comes back — justified
  6. The "dictated" mark is kept per composer (main chat, split pane, crew window) in session storage, so it survives a reload — justified
  7. The note is never added twice to text that already ends with it — justified

[FIRST-PRINCIPLES-REVIEWED] fa16558

Description read

[DESCRIPTION-READ] e7d325f8ab49b2c2960cc65a098db77fb90bb08c8bfbf74146ece7e465fdc8c8

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 7, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS

UX-level review of fa16558b289fee08908454edcba2bea5e0e0e845 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

Nothing blocks. The blind reader understood the new "Tell the agent this was dictated" toggle and said they would use it. It matches the toggles beside it under Fine-tuning. Both of its states (setting on, note in a sent message) appear in screenshots.

Notes

  • When the reader saw "[This message was dictated…]" in their own chat bubble, they were "surprised… as if I had typed it." The hint "the note shows in the transcript too" says this, but it sits behind the (i) icon. Move "Also shows in your sent message." into the visible label row, so people know about the note before they turn the toggle on.

[UX-REVIEWED] fa16558

Description read

[DESCRIPTION-READ] fd473e142be6e88b0b7cb8771b4eb0a26850eca97f297f70bd96962d4c754266

That sha256 names everything this verdict read: the PR description, plus the 5 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 .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

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

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] fa16558

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

@github-actions

github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

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

Review details

No findings.

[OPUS-REVIEWED] fa16558

Verdict parsed from the review's SHA-scoped output markers for commit fa16558b289fee08908454edcba2bea5e0e0e845.

False positive or not applicable? A repository writer can comment:
/ai-review override fable fa16558b289fee08908454edcba2bea5e0e0e845 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 7, 2026
@Pearcekieser
Pearcekieser force-pushed the pearcekieser/dictation-note-setting branch from 50ab995 to 93eeb97 Compare November 8, 2026 01:45
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 8, 2026
@Pearcekieser
Pearcekieser force-pushed the pearcekieser/dictation-note-setting branch from 93eeb97 to 3ddbb5c Compare November 8, 2026 03:00
@Pearcekieser

Pearcekieser commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in config-baseline.json, docs/feature-map/README.md, docs/system-specs/modules/config.md, src/kiro_crew/config/section_builders.py, src/kiro_crew/docs/configuration.md, the settings registry files, all 12 locale catalogs, CrewChatWindow.tsx, crewWindowStore.ts and CrewChatWindow.test.tsx since this head went green (fe2d88c -> fcfba68); CI re-running.

@github-actions github-actions Bot added readiness: checking Automated validation is still running merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: passed Eligible automated validation passed for the current revision labels Nov 8, 2026
@Pearcekieser

Pearcekieser commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor Author
  • span=6f7a45e828e6 Persisted provenance outlives evicted drafts and marks typed-only messages

Rebutted: disproportionate remedy, as the Opus 5.5 adjudication on 93eeb97 ruled (DOWNGRADE F1, reason=disproportionate-remedy).
The case needs all of: the opt-in stt.dictation_note setting on (off by default), a dictated pane or crew-window draft dropped by the 256 KiB byte cap or the 50-entry cap, and a reload of the tab.
The effect is one visible line on the next message sent from that composer, saying it may contain transcription errors. Nothing is lost or exposed.
It clears itself: that send takes the record through takeDictated, so later messages carry no note.
The fix would couple draft-store eviction to the provenance store in both the pane and the crew-window hydration paths, a permanent cost for a rare, self-clearing effect.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 8, 2026
@Pearcekieser
Pearcekieser force-pushed the pearcekieser/dictation-note-setting branch from 3ddbb5c to 04cec85 Compare November 8, 2026 03:45
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

@bolichen97 thanks for the review.

issue: withDictationNote parses text with a regex

Fixed locally in 72cd65bc28: the line is now const body = text.trimEnd(). That was the only regex in the new product code. The 65 tests in dictationProvenance.test.ts, outgoingTurn.test.ts and ChatPage.dictationNote.test.tsx pass. I will push it together with the rebase below.

note (non-blocking): the App chunk over its budget

I built both trees with vite build --mode analyze. The merge base f08ae0d builds App at 2,253,662 B, already 862 B over the 2200 KB ceiling with none of this PR's code; that is issue #33668. This PR adds 961 B on top, for 2,254,623 B. Those bytes are dictationProvenance.ts and the note text: the voice hook and every composer send path call them, and those modules load with the chat route, so there is no lazy boundary to move them behind. The re-measure in #33669 (2311 KB from that same 2,253,662 B) covers both. This PR will wait for that fix to land on main, rebase onto it, and push then. No CHUNK_BUDGETS change goes into this PR.

@Pearcekieser
Pearcekieser force-pushed the pearcekieser/dictation-note-setting branch from 8901908 to 2c9354a Compare November 9, 2026 05:15
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

@bolichen97 the trimEnd() fix is now on the PR head, 2c9354a, rebased onto main after #33665 raised the App ceiling to 2311 KB. A local analyze build of this head passes check-bundle-size.mjs with every chunk within budget. Could you re-review when CI settles?

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 9, 2026
@Pearcekieser
Pearcekieser force-pushed the pearcekieser/dictation-note-setting branch from 2c9354a to f5761cd Compare November 9, 2026 06:15
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Nov 9, 2026
@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • span=b9b08523ab39 Dictated retry after a failed create from the welcome composer loses the note

Rebutted: not reachable, same finding and same evidence as disposition 6730219469 on feb9de5; the code is unchanged since.
With no active chat, ChatPage.tsx:1157 renders ChatEmptyState, which has no composer and no voice hook. The only main composer mounts in ComposerDockView, whose activeSlot prop is typed string (line 95) and passed as slotKey.
So the voice hook never writes a dictation record under the null key on this page, and takeDictated(null) in composerSend.ts is always false. The null key in dictationProvenance.ts is defensive, never written by the main page.
The only sends that reach the !uiSlot arm are autoSendRef retries sent as optionText, which carry no dictated words.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author

/ai-review override fable f5761cd false-positive: agent: same unreachable path as the override on feb9de5. With no active chat ChatPage renders ChatEmptyState, which has no composer, so no dictation record exists under the null key. Evidence in disposition comment 6733795183.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Human judgment recorded

@Pearcekieser recorded a false-positive release (class false-positive) for the fable AI finding on f5761cded69a8eab32585559abe6527b7702d7ef.

agent: same unreachable path as the override on feb9de5. With no active chat ChatPage renders ChatEmptyState, which has no composer, so no dictation record exists under the null key. Evidence in disposition comment 6733795183.

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

@github-actions github-actions Bot added merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 9, 2026
Add stt.dictation_note, an off-by-default checkbox under Settings, Voice,
Fine-tuning ("Tell the agent this was dictated"). When it is on, a message
that holds dictated words ends with one line telling the agent it may
contain transcription errors. Typed-only messages never get it.

The Voice atom records which session's composer or parked draft received
spoken words. Each send path (main chat send and steer, pane send and
steer) takes that record when it consumes the composer, and every path
that hands the text back (a refused or failed send, a returned steer, a
cancelled queued card) puts it back. Emptying the composer clears it, and
a discarded dictation takes back the mark it set.

The note is part of the message text, like the gateway's own provenance
lines, so it reaches the agent on every later path (queue, steer,
regenerate, resume) and the transcript shows what the agent was told.
@Pearcekieser
Pearcekieser force-pushed the pearcekieser/dictation-note-setting branch from f5761cd to fa16558 Compare November 10, 2026 00:45
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: passed Eligible automated validation passed for the current revision merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention labels Nov 10, 2026
@KiroCrewCaptain

Copy link
Copy Markdown
Collaborator

Thanks for this. The review on this head found no blocking problems. Two things still need a maintainer before this can merge:

  1. The PR adds a row to docs/feature-map/README.md that describes the new feature. A maintainer needs to agree to that row. A review bot cannot approve it.
  2. The change request from bolichen97 on 8901908 is fixed on this head: withDictationNote now uses text.trimEnd() at dictationProvenance.ts:163, and no new regex was added. GitHub still shows the request as open until it is re-reviewed or dismissed.

What the review checked on fa16558: the setting stt.dictation_note is off by default, the PUT handler accepts only a bool, and a non-bool value in config.json loads as off. Every send, steer, queue and hand-back path on the main page, the split pane and the crew window takes the dictation mark when the composer is sent, and puts it back when a send is handed back. The command check runs on the final message with the same rule the gateway uses, so /goal clear gets no note but a quoted message that starts with a slash does. PR Readiness passed on this head, and every review lane passed.

Done well: the code never guesses from the words whether a message was dictated, so typed text that happens to end with the note line comes back unchanged. A test checks exactly this.

Optional:

  • Port the "emptying the composer forgets the dictation" test from ChatPage.dictationNote.test.tsx to ChatPane.dictationNote.test.tsx and CrewChatWindow.test.tsx. Today no test fails if the pane or crew window stops clearing the mark, and that is the one case where a typed message would get the note.
  • The setting help says the note shows in the transcript. Session summaries and titles also read it as part of the user's words. One line under Known limits in the PR body would cover it.
  • When a note comes back as plain text (a queued steer cancelled on the main page, or up-arrow recall), dictating more and sending adds a second note. This only affects how the message looks.

@bolichen97 bolichen97 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approve on fa16558. I read the whole diff (2844 lines). Both points from our change request are fixed. This fixes #32015.

  • Regex: withDictationNote now uses text.trimEnd(). I searched the diff and found no replace(/, new RegExp, re.compile or other regex literal in product code.
  • Bundle: Bundle Size Gate passes on this head. The App chunk is 2,296.43 kB, within its budget.
  • The setting stt.dictation_note is off by default. The PUT accepts only a real boolean, the same as dictation_panel next to it.
  • Provenance is per session and per composer scope (main page, pane, crew-window draft and rewind box). It is never guessed from the text. Every hand-back path (refused send, steer, queued-card cancel, delivery-unconfirmed restore) puts the record back and restores the note-free text.
  • The note is never added to a command (isCommandText), and withDictationNote is idempotent.
  • All 97 checks are green, and nobody else has an open change request.

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.

Voice: optionally tell the agent a message was dictated

3 participants