Skip to content

Candor 5.2.0

Choose a tag to compare

@arunk3 arunk3 released this 13 Nov 21:07
· 7 commits to main since this release

Released 2026-11-13.

A minor, with CLI 3.2.0 and @candor-ui/react 5.2.0. Nothing a 5.1 app passes stops working; code that reads one of
the widened prop types (listed below) may need ?? undefined. The fixes 5.1's streams and reviews found: a Thread
that stays at the newest message (Storywrite's A-61), names from the app that read the right way round, and links
your router follows in the nav. One Pro item is new (use-focus-within), so the kit has 408 items: 74 free and 377
in Pro.

What to do: npx candor-ui@3 update --to 5.2.0 takes a 5.1 project to 5.2.0, with no codemod. If you use
@candor-ui/react, install 5.2.0, which carries the free fixes to Thread, Message and place(). The changes a 5.1
app sees, each with what to do:

  • Thread (free) stays at the newest message while its content lays out (KIT-295). Storywrite's A-61: "a Thread
    opened at its newest end stops following when its content grows just after the first draw", about 57 px short of
    the bottom in about 1 open in 4 in Chromium. In 5.1 any fall in scrollTop of more than 2 px unpinned the thread,
    and the browser's scroll anchoring makes one when content above the view changes size. In 5.2 the thread turns
    scroll anchoring off on its scroller while it follows (overflow-anchor: none), and back on once the reader scrolls
    up, so their place is kept. A fall in scrollTop counts as layout only up to how much the content's height, the
    view's height and the newest message's place changed since the last scroll or resize; the thread stays pinned and
    goes back to the bottom. Any larger fall is a scroll and unpins, while an agent streams too, whatever made it: a
    wheel, a touch, a key, the scrollbar, find in page, a screen reader, or your app through scrollerRef, as in 5.1.
    "Jump to latest" shows whenever the view is short of the bottom, not only once the reader has scrolled up. Nothing
    to do.
  • The Pro items' …Locked props and locked maps, and Inbox's and ApprovalQueue's defaultActiveId, accept null (KIT-282,
    KIT-291), as locked does since 5.1. For a …Locked prop or a locked value, null or left out is unlocked. For
    defaultActiveId, only null means "the list keeps the open row, with none at first"; left out, the list keeps no
    open row and marks none, as in 5.1. Code that passes them is unchanged. Code that reads one of these types into a
    string | undefined (ComponentProps<typeof Plan>["acceptLocked"]) fails the type check: add ?? undefined. The
    props:
    • RunEstimate's startLocked; PlanGate's upgradeLocked; DataControls' deleteAccountLocked,
      deleteHistoryLocked and exportLocked; SsoSetup's enforceLocked; AgentScreen's takeOverLocked; Plan's
      acceptLocked.
    • AccountState's actions[].locked.
    • The values of the locked maps on ArtifactToolbar, RestoreDialog, ReviewLadder and NotificationPreferences.
    • Inbox's and ApprovalQueue's defaultActiveId. Their selected behaves as in 5.1.
  • ApprovalQueue's (Pro) requester tile draws the name's first letter upper-cased, as a whole character, through
    the new initialOf in initials (KIT-285): an emoji or an Adlam letter is no longer cut in half, and a name that
    starts lower-case shows its capital. The tile still holds one letter.
  • ScopeBreadcrumb (Pro): a linked crumb opened with Ctrl, Cmd, Shift or Alt, or the middle button, follows the link
    and doesn't call onChange, as ScopeSwitcher's option does since 5.1 (KIT-269). A plain click calls onChange, as
    before.
  • AppSidebar, NavRail and TabBar (Pro) draw their in-app places through the app's link (LinkProvider, or
    CandorProvider's link), so your router's link handles them (KIT-268). With none set each draws the <a> it drew
    in 5.1. A plain click with onNavigate given calls it and the link doesn't navigate, as in 5.1; without
    onNavigate, your link navigates.

Translators: these keys are new. Until you translate them, each says its English words.

  • calendar.gridName ("{label}, {month}"), Calendar's grid name, which 5.1 joined with a typed ", " (KIT-271). The
    keys it read in 5.1 are still read, as its placeholders.
  • themeSetting.using ("Using {theme}"): with choices, a stored theme that isn't among them leaves the trigger
    reading "Choose a theme", and its description names the theme in force (KIT-292).

Some DOM your own CSS or tests may match has changed:

  • Names from the app drawn inside Candor's words have their direction controls marked, listed below; where the
    text read the same, it still does. DetailsList's row label is in a <bdi> inside its <dt>; ScoreRing's
    delta.vs, projection.basis and basis and StatCard's delta.vs are each in a <bdi>.
  • Thread (free): while it follows the newest message, its scroller has overflow-anchor: none as an inline style,
    which overrides an overflow-anchor your CSS sets there; it has none while the reader is scrolled up.
  • ThemeSetting (Pro): with a stored theme outside choices, the trigger has aria-describedby pointing at a hidden
    element with the themeSetting.using words.
  • ColumnMapper (Pro): the gap after a field's icon is a layout gap, not a typed space, so the text has no leading
    space (KIT-274).

Corrected in the 5.1.0 notes

The 5.1.0 section below is left as it was released.

  • locked accepts null on every locked prop, not on every item: in 5.1.0 the …Locked props
    (acceptLocked, startLocked, upgradeLocked …), AccountState's actions[].locked and the record-typed locked
    maps still take string | undefined (KIT-282). 5.2 widens them, listed above.
  • The widened types break code that reads a prop's type, not only the six data types: ComponentProps<typeof ConfirmButton>["locked"] read into a string | undefined needs ?? undefined, and Tree's two-parameter onSelect
    fails where a wrapper types it as (id: string) => void through ComponentProps<typeof Tree> (KIT-283).
  • Locked under the app's TooltipProvider opens its reason after the app's delay on hover, where 5.0's own
    provider gave none; only moving between locked controls inside the delay group skips it (KIT-289).

New items (Pro)

  • use-focus-within: useFocusWithin and its FocusWithin type (KIT-276). It tracks whether focus is inside an
    element, so an item moves focus only when focus is in it, or on its control that was just removed, and announces
    otherwise; a target held for the next render is dropped once the person moves focus out. Focus already inside when
    it mounts (a control's autoFocus) counts. NeedsYouLine, ModelKey, DriftChange, EnvironmentConnect and
    IntegrationConnect use it in place of their own checks; NeedsYouLine now keeps focus for any control in the line, not
    only Retry.

Components

Names from the app, a model or another person (KIT-266, KIT-267, KIT-277, KIT-284): drawn inside Candor's words or in
an accessible name, their direction controls are neutralised, so a name can't turn the sentence round it. Message
(free): the author's and agent's names in its aria-label. Shell and agents: DockWindow's title (Float, Go to window,
Bring back, Move and the floating line), MembersTable's environments in roleOn. Data, reports, charts and evals: Tree,
ReconcileTable, DataTable (its stacked name, agentPending and agentInputs), RunEstimate, EvalScorecard,
SubscoreCard, ScoreRing, StatCard, ReportSheet, DetailsList, BoardCard, ReorderableList, ColumnMapper, DataImport,
ImportReview, and the select hint of BarChart, LineChart, DonutChart and Heatmap. Work, collaboration, knowledge, admin
and billing: ApprovalRequest, Plan, ShipReview, RunRecovery, ExtractionReview, InlineSuggestion, CodeListing,
CodeEditor, CompareSlider, DocumentViewer, DocumentProgressQueue, AgentScreen, EnvironmentPromotion, HoldToConfirm,
Proposal, RestoreDialog, RunHeartbeat, SteerComposer, UndoWindow, WorkflowEditor, AccessRequest, CommentThread,
Escalation, HandoffCard, Presence, RaciChips, Diagram, ConfidenceMark, KnowledgeSources, MemoryManager, MemoryMode,
MemoryUsed, ApiKeys, DataControls, DeviceSessions, ScheduleList, Webhooks, EnvironmentConnect, IntegrationConnect,
SsoSetup, SetupChecklist, StepUpDialog, ProfileSettings, PlanGate, PlanPicker, DowngradeImpact and SubscriptionStatus.

The rest, by item:

  • Dialog, DropdownMenu, AlertDialog, MaskedInput, FloatLabelInput, Command and TabsList merge your ref with their own
    through useMergedRefs, as Tabs does since 5.1: an object ref and a callback ref both get the element, and a new
    callback ref takes over from the old one, where TabsList kept the first ref an app passed (KIT-265).
  • RunEstimate and ScheduleEditor read the clock after they mount, never while they render, so a Next 16 prerender with
    cacheComponents no longer fails on an unstable value (KIT-298). The server's HTML has no time left on RunEstimate
    and no next runs on ScheduleEditor; both appear once the page has mounted, before it paints, as RunEstimate's time
    left and ScheduleEditor's runs already did after hydration.
  • SheetContent: a sheet opened from another gives the outer sheet's width back when it closes, where 5.1 removed
    --cd-sheet-width and the push drawing fell back to min(75vw, 24rem) (KIT-290).
  • The Premium templates' server stores type no " · " into the labels they build: the approvals inbox names the
    customer in a refund's title, and the support copilot's store returns the parts its pages join with the locale's
    separator (KIT-275).

@candor-ui/react 5.2.0

  • Thread stays at the newest message while its content lays out, and "Jump to latest" shows whenever the view is short
    of the bottom (KIT-295, above).
  • Message marks the direction controls in the names in its aria-label (KIT-277).
  • place() (locale) reads only a placeholder the nodes hold themselves, so a translation holding {constructor} or
    {toString} draws it as written, where 5.1 drew a function and threw (KIT-286).
  • mcpInputView and mcpInputResponses (mcp-input) fill a placeholder in their words only from the values they were
    given, so a translation holding {constructor} or {toString} draws it as written, where 5.1 drew a function's
    source (KIT-297).
  • Locked's doc says when its reason opens: under the app's TooltipProvider, on hover after that provider's delay;
    with none, at once; on a press, at once (KIT-289).

Nothing to do.

CLI 3.2.0

  • update says when package.json lists a package below an updated item's new range, with the command to install it,
    and leaves package.json as it is ("lucide-react has ^1.60.0 in package.json; thread 5.2.0 needs ^1.67.0. Run
    npm install lucide-react@^1.67.0."). A package inside or above the range gets no line, and one that two items name
    is named once, at the higher range. A workspace: or file: specifier is named as not compared (CLI-45).
  • Every command migrate and theme print, and the theme usage line, names npx candor-ui@3: migrate's "Not
    run" line, usage, strings-keys' line on a spread and its pointers to update and add; theme check's fix for a
    renamed token, its file and motion hints and its pointers to update and init; theme apply's and theme from's
    lines, so a project with candor-ui@2 installed doesn't run CLI 2 (CLI-43).
  • The new string keys update and migrate strings-keys list count a key renamed inside a namespace as moved, not new
    (CLI-46).

Docs and the docs MCP

  • The docs MCP's theme_check names npx candor-ui@3 migrate tokens for a renamed token (CLI-43).
  • SubscoreCard's doc names FindingData (KIT-272). DocumentViewer's example shows defaultSelected and RestoreDialog's
    shows defaultOpen (KIT-273). Thread's scrollerRef doc says scrolling it up stops the thread following.
  • The upgrade page's 4.0 command names npx candor-ui@2 update --to 4.0.0.

For maintainers

  • release:check runs an upgrade check from 5.0.0 and from 5.1.0 to this version, on the 5.x fixture
    (tests/upgrade/5.0 and its also), and runs migrate only when a breaking entry is crossed (CLI-44). The 4.5 and
    5.x steps run within 5.x; at another major one step fails and says where to add that major's upgrade steps.
  • check:motion: the calm/none rule needs [data-motion="calm"] and [data-motion="none"], and their descendants, in
    a :not(…), each compared whole (MOT-66); a negated container query doesn't allow a loop (MOT-67); an @ease value
    it can't read fails on either line (MOT-68); a loop needs its running state on every selector of a list.
  • layers.mjs fails for an engine named in CANDOR_LAYER_BROWSERS or --browsers that doesn't start; one of the
    default three that won't start here is still skipped with a line, and on CI any fails (KIT-287).
  • candorItemsOf (scripts/page-items.mjs) reads imports from the syntax tree, so a path in a comment or a string
    isn't listed (KIT-288).
  • A kit test checks that every data-slot an item draws is in the token manifest (KIT-280).
  • tests/browser/thread-follow.mjs opens a thread 20 times in Chromium with A-61's late change and checks each ends at
    the bottom, and that PageUp with focus on body, a text fragment (find in page's scroll) and scrollIntoView unpin
    it, with no streaming and while a token arrives every 30 ms; npm run test:browser runs it after the hosted demos.
  • The OrgSmith pack's package.json and a committed package-lock.json list the packages its Candor items import, and
    npm run candor puts both files back after add, so a later npm install keeps them (ARCH-39).
  • The short real-time sleeps left in the tests wait on fake timers (HK-9), and tests that type a bidi control use a
    \u escape (HK-10).