Repository navigation
Candor 5.4.0
Released 2026-11-13.
A minor, with CLI 3.3.1 and @candor-ui/react 5.4.0: the rows 5.3's streams and reviews left, made right. No item is
new, so the kit still has 420 items: 74 free and 389 in Pro. Nothing a 5.3 app passes stops working, and no
default text changes.
What to do: npx candor-ui@3 update --to 5.4.0 takes a 5.3 project to 5.4.0, with no codemod. If you use
@candor-ui/react, install 5.4.0, which carries the free fixes listed under it.
What Storywrite asked for (A-74 and A-80), and where each is:
- A-74 Plain type: the names that draw beside code now read
--cd-font-namein LogStream's writer column
(KIT-347), ChangeTree's file names (KIT-345) and, when you ask for it withtitleFont="name", CodeListing's title
(KIT-335). EntityChip and ChangeDiff have read it since 5.3.0. Unset, each draws as in 5.3, but for a title you
set totitleFont="name": with the token unset, it falls back to the monospace font, as the other names do. - A-80 Room for the app's own floating element: Thread's Jump to latest button sits
--cd-thread-jump-offset
higher (KIT-348). Unset, it sits where it did.
Components (Pro)
- TurnRequest (KIT-330):
taken, the app's word that the person has the screen now. It reads "You have the
screen. Hand it back when you're done." with Hand back (onHandBack), keeps what the agent won't do and whether it
sees the screen in view, and locks Take the screen saying why. It is never inferred from a press of Take, and focus
stays where it was. When the app clearstakenwith no report yet and focus was in the request, as after Hand
back, focus goes to the request's heading rather than falling to the page. - TurnRequest (KIT-341): a new request (new
why,todoor asking agent) is announced by its title once, when
focus is elsewhere and the request is shown; nothing on mount. The report's announcement is no longer made while
the request is hidden. A new asking agent (a newagent.id) is now a new request on its own, so with focus in the
request it also moves focus to the heading, as new words did in 5.3. - DecisionReview (KIT-333):
actionKeys, a key per action id that moves focus to that action's button; Enter or
Space then presses it. No key decides. The key is shown on the button and in itsaria-keyshortcuts("Plus" for
+). It is ignored in fields, with Ctrl, Alt or Meta, with Shift on a letter (a key typed with Shift, such as
?, works), after the app's handler callspreventDefaultand in the app's composite widgets; J, K and a key
already taken are ignored, with a development warning. The composite widgets it leaves keys to now
include a menubar, treegrid, toolbar and combobox (a button one too), for J, K and the arrows as well: 5.3 moved
between items on those keys there. - DecisionBar (KIT-342): a new title is announced only while the bar is shown, not under AppLayout's quick chat
or while the app hides it. (KIT-332):safeAreapads the bar's foot byenv(safe-area-inset-bottom)on top of its
ownpy-2, for the foot of a phone's screen when no TabBar is under it; apy-*orpb-*inclassNamereplaces
both. Left out, the HTML is 5.3's. - AgentScreen (KIT-340): the docs for
frameAt,markersandonFrameStaleChangesay a live frame with no
frameAtis never judged stale, so its markers stay shown and the callback says false. PassframeAtto have it
judged. The behaviour is 5.3's. - ChangeDiff (KIT-336): left to keep its own shown file, it keeps it by path, not by place in the list: a shorter
or reorderedfileskeeps the same file shown while it is there, and shows the first file when it isn't. 5.3 could
show nothing afterfilesgot shorter. (KIT-344): withselected, pressing a tab the app declined asks again on
the next press; 5.3 stayed silent until the shown file changed. - ChangeTree (KIT-345): file names draw in
--cd-font-namewhen you set it, so the tree matches ChangeDiff beside
it. Unset, nothing changes. - CodeListing (KIT-335):
titleFont="name"draws the title in--cd-font-name, and in the monospace font when
the token is unset, as the other names that read it do."body", the default, draws it as before. - LogStream (KIT-347): the writer beside each line draws in
--cd-font-namewhen you set it; the log text stays
monospace. Unset, nothing changes. - UsageMeters (KIT-337):
usageMeters.noLimit, a new opt-in key for a usage with no limit. Override it and
UsageMeters draws your words there in place ofnoCap's; left as it is, it draws "No cap on your plan." as in 5.3.
An override with the default's own words ("No limit set") can't be told from none, so it drawsnoCap's too.
In 6.0 the default moves to "No limit set", UsageRing's words. - UsageGlance, UsageMeters and UsageRing (KIT-343): past its limit, a meter reports
aria-valuenowat the limit,
not above it, and itsaria-valuetextsays the measured figure. UsageGlance and UsageRing said it already ("140 runs
of 100 runs"); UsageMeters now sets one past the limit ("140 / 100 runs"). Inside the limit the markup is 5.3's. - FreshnessStamp: a
readAtit can't read ("soon") says "Read time unknown" (itstimeUnknownkey) with no
date and notitle, where 5.3 threw a RangeError. - EmailLayout (KIT-339):
emailMarkup(node), new, writes an email's element tree to an HTML string with no
react-dom/server, so it runs in a route handler, a server action, a worker or the browser. It writes host
elements, text, fragments, a context provider's children and components without hooks,memoandforwardRef
ones included; anything else, such as a class or lazy component or one that uses hooks, throws an error naming it
rather than being left out.EmailLayouttakes optionalchildren, drawn in the document's<body>in place of
the notice's card; left out, ornull,undefinedor a boolean, the card is drawn. DigestEmail's
renderDigestEmailnow usesemailMarkuprather than a copy of it; its output is byte for byte 5.3's. - Names from the app have their direction controls neutralised in AppLayout's quick chat heading and region name
and inpanelLabelin the panel's names (KIT-331), and in ArtifactPanel's download items, NavRail's and TabBar's
counted names where the kit puts the label in (TabBar's own name,navRailTabs' defaultwaitingand
useNavRailTabs; an app's ownbadgeLabel, or what its ownwaitingreturns, is read as the app gives it, as in
5.3), SettingsLayout's select and the collapsed AppSidebar's person tooltip (KIT-327).
@candor-ui/react 5.4.0
- RelativeTime draws "Time not known" for a date it can't read (
"soon",new Date(NaN)) instead of throwing a
RangeError, with nodateTimeand notitle, from the new keyrelativeTime.unknown(KIT-334). The free Message
and ThreadEvent, and the Pro items that show a time through RelativeTime, draw it too.formatRelativereturns""for a date it
can't read, where it threw (or, withbare, returned "NaN seconds"). A valid date draws what it did. - Thread's Jump to latest button sits
--cd-thread-jump-offsethigher, a new token for an app with its own floating
element at the thread's foot (KIT-348). Unset, it sits where it did.
Nothing to do.
The new token
--cd-thread-jump-offset (KIT-348): how much higher Thread's Jump to latest button sits than its own place at the
thread's foot. It is 0px by default. Set it to a length on the thread or any element around it; it inherits.
--cd-font-name's description names every item that reads it, and says what Tailwind 4.0.0 to 4.0.14 draw for its
fallback: the theme's --font-mono as it was at build time, so CSS outside @theme that changes --font-mono isn't
followed there; set --cd-font-name too (DOC-17). From Tailwind 4.0.15 the fallback is font-mono's exactly.
New string keys
Translators: these keys are new. Until you translate them, each says its English words. No key read in 5.3 changed.
relativeTime:unknown("Time not known").usageMeters:noLimit("No limit set"), read only when your app overrides it; until 6.0,noCapis drawn
otherwise.turnRequest:taken,takenLockedandhandBack.
Some DOM your CSS may match
- Thread's Jump to latest wrapper keeps 5.3's classes and adds one,
mb-[var(--cd-thread-jump-offset,0px)]: a bottom
margin, which raises the absolutely placed wrapper. Unset, it is0px. - TurnRequest with
takenhas a new row,data-slot="turn-request-taken", anddata-phase="taken"on its root.
DecisionReview withactionKeysdraws each key in a<kbd data-slot="decision-review-action-key">on its button.
Without those props, the HTML is 5.3's but for React's generated ids, which can differ. - AppLayout's quick chat heading and its panel sheet's title draw the app's words in a
<bdi>. - ChangeTree's tree carries one more utility class (the font token). LogStream's writer
<bdi>and, with
titleFont="name", CodeListing's title<bdi>carryfont-[family-name:var(--cd-font-name,--theme(--font-mono))];
LogStream's writer is insidefont-monoas before.
Docs
- TurnRequest's example puts a line in the request's place after Not now and focuses it, so focus doesn't fall to the
page (DOC-16); it also showstakenwith Hand back. DecisionReview's example passesactionKeys. - Each item's install line names the CLI major,
npx candor-ui@3 add <name>, on the docs pages, incomponents.md,
llms-full.txtand the docs MCP'sget_component_docsandget_brief(CLI-53). - The upgrade guides' lines for keeping an older version installable name the CLI for each:
@1for 2.10.0,@2for
3.0.0 and 4.5.0 (SITE-37).
CLI 3.3.1
updatestops, naming the registry and changing nothing, when every item it asks for answers 404 and none of them
has a breaking entry of any kind, or when the registry's list of versions can't be read. Before, when every item
answered 404, it clearedcandor-lock.json(CLI-54). One 404 among items that answer is still a removal of that item.infoandsearchprintnpx candor-ui@3 add <name>(CLI-53).- A test keeps every
migrate <name>the CLI prints in step with its codemods (CLI-55).
For maintainers
release:checktakes its 5.x--fromlist fromtests/upgrade/5.0/fixture.json'salso(CLI-52), with 5.3.0
added, anddocs/RELEASING.mdsays so.tests/date-trap.tstraps every way a render could read the clock,new Date()as well asDate.now, for the five
clock-after-mount tests (HK-15).- Tests for React 19's ref cleanup through the merged refs:
merge-refs, and the free Popover, Composer and Thread
(HK-16). They found no bug. - The docs-snapshot test reads and hashes each blob once, not once per release that keeps it (HK-14): 1.6 s alone
to 0.2 s.
Upgrading from 5.3
Nothing to do. npx candor-ui@3 update --to 5.4.0.