Repository navigation
Releases
Candor 6.1.3
Released 2026-11-15.
With @candor-ui/react 6.1.3: numbered lists in model text keep their numbering. No CLI change.
@candor-ui/react 6.1.3
Only these free items change.
- Numbered lists in model text keep their numbering (safe-markdown, message-content). Blank lines between items
no longer end a list, numbered or bulleted, so the numbers go on. A fenced code block indented two columns or more
past an item is drawn inside that item, and the list goes on after it. A numbered list that starts at another
number, such as3.after a paragraph, is drawn from that number, and copying the message keeps the same numbers.
While a reply streams, a list doesn't restart and rejoin as a blank line or an item's code arrives. - A list block gains
start(its first number, left out when it is 1 or isn't a safe integer), and a block under an
item can be apayload. If you draw blocks yourself, set<ol start>fromstart, and give aswitchover a
nested block'skindadefaultbranch.
Candor 6.1.2
Released 2026-11-15.
With CLI 4.2.0 and @candor-ui/react 6.1.2: the registry serves only the current release, 6.0's codemods and the
Upgrading to 6.0 page are removed, and nested lists in model text are drawn nested.
CLI 4.2.0
update,addandmigratework with Candor 6.1 and later. 6.1 is the first release CLI 4 installs with a copy
of each file in.candor/base/, which is whatupdatemerges against now that the registry serves only the
current release. On a project before 6.1 they change nothing and say how to move on: commit, delete
candor-lock.json, run the codemods of the releases you crossed on your own code (with no lockfile, each runs all
of its release's), thennpx candor-ui@4 add <your items> --overwriteand take your edits back from git. An item
6.1 removed can't be added; Upgrading to 6.1 says what replaced it.- On a project on 6.1 or later but behind the current release, no command stops on an earlier version the registry
no longer serves.updatemerges against.candor/base/, and for an item without a usable copy stops before
changing anything and namesgit checkout -- .candor/baseornpx candor-ui@4 add <item> --latest --overwrite.
addnamesupdate, or--latest.infoshows the current page and says so.verify --remotechecks the items
at the current release and names the others as not checked.list --installed,theme check,add --dry-run's
preview andmigrate's list of new strings use.candor/base/where they can, and otherwise say why they can't
compare. migrateno longer has 6.0's codemods:data-types,propsandheadings, and 6.0's rows ofstrings-keys.
npx candor-ui@4.1 migrate 6.0.0runs them. 6.1's (items,strings-keys,tokens) stay.mcpanddoctorno longer mentionitem_changes, which the docs server no longer has.
Registry and site
- The registry serves only the current release.
/r/versions.jsonlists it;/r/v/<another version>/…answers 410
with a line namingnpx candor-ui@4 update, which merges against your project's.candor/base/and needs no
earlier version. If you install with shadcn from a versioned URL, use the current one. - The docs MCP server has twelve tools:
item_changesis gone, and a page asked for at another version is the
current one, which it says. - Upgrading to 6.0 is gone:
/upgrading-to-6and its.mdredirect to 6.0.0's section of this changelog. Upgrading to
6.1 stays as the list of 6.1's changes and their codemods. - The docs no longer have a version list: only the current release's are published.
@candor-ui/react 6.1.2
Only these free items change.
- Nested lists in model text (safe-markdown, message-content):
markdownBlocksreads an item indented two
columns or more past the item above it as nested in that item, ordered and unordered in each other, to four levels;
an item deeper than that is one more item of the fourth level, with its text kept. A tab counts as four columns. An
indented line that isn't an item continues its item, and after a blank line is a paragraph inside it. A list in a
quote is read as a list, and a quote whose lines include a list is split into paragraphs around it. Before 6.1.2 each of these was a flat item, or a paragraph after the list. MessageContent
draws what is under an item inside it, with hollow markers on a nested unordered list, and copies it as lines
indented by its marker's width a level. The Claude Agent SDK adapter places a citation after the deepest last item.
While a reply streams, an item is drawn at its own level from its marker on. - A list block gains
nested(what sits under each item) and a quote blocklists(which of its paragraphs is a
list); both are left out when there is nothing to put in them, so a flat list's block and markup are as before. If
you draw blocks yourself, drawnestedinside each item; left undrawn, the nested items are missing, not flattened. - Thread lands a tall new message at its start (thread): with
landNew="start", a new message taller than the
view, whether it arrives whole or grows there while it streams, stops the view at its start and the thread stops
following, so the opening of a long reply stays in view and Jump to latest shows; the reader's own message
(data-role="user") and anything shorter than the view are followed to the end. A reply that takes the place of a
placeholder row lands as a new message does. If you draw the reader's messages yourself rather than with Message,
mark themdata-role="user", or they can land too. The default,"end", follows as before. The newest message in a thread now carriesdata-newest, so you can find it without relying on Message's
data-slotanddata-role.
For maintainers
- A released version's files are held to
scripts/released.json(everypublic/rfile and docs page by hash),
written bynode scripts/released.mjs --writeat RELEASING step 6 and checked bygenerated.mjs --check. The
snapshot store in Vercel Blob, its scripts and workflow, and the upgrade fixtures and harness are gone. released.mjs --writewon't write over a record of the same dated version whose files differ (--forcedoes, for
a Release commit not yet merged), and--checkalso holds the record to the one taggedv<version>.release:checkwarns on a note marking wording only the owner gives in any file that ships or is served, and fails
on one under--fullor once the version is dated.
Candor 6.1.0
Released 2026-11-14.
One component per job, tables in model text, and upgrades that keep their own history. With CLI 4.0.0 and
@candor-ui/react 6.1.0.
Seven Pro items are folded into the items that do the same job: DecisionCard and DecisionBar join DecisionReview in
decision-review, PermissionMode takes ReviewLadder's place with your own levels, a docs example takes ReviewCanvas',
UsageMeter draws one usage as a bar, a glance or a ring in usage-meters, ChangeDiff picks its file from a tree, and
Digest says what happened since the last visit. This is the one minor release that breaks Pro items; each break has an
entry below, and CLI 4's codemods make most of the changes. Model text reads as it was written: a fenced block keeps
its language and is highlighted in it, a pipe table is a table and > lines are a quote, text only as always. CLI 4
keeps a copy of each file as Candor installed it in your project, so update merges against your own history. The
kit has 413 items, and Pro has 382 of them, the 76 free ones included.
Breaking
Each entry has its id in scripts/breaking.json (the same entries update --to 6.1.0 prints, and the Upgrading to
6.1 page lists), what changed, and what to do. Only
message-block-kinds is on free items.
decision-card(codemoditems; approval-request, decision-review; Pro): ApprovalDecision is DecisionCard, in
decision-reviewbeside DecisionReview and DecisionBar, andapprovalDecisionStringsisdecisionCardStrings.
Its props, its markup anddata-slot="approval-decision"are unchanged, and it still takes aDecision.
ApprovalRequest stays inapproval-request.npx candor-ui@4 migrate itemsmoves each import and renames its uses,
<ApprovalDecision …>included.decision-card-strings(codemodstrings-keys; approval-request, decision-review; Pro): theapprovalDecision
strings are thedecisionCardtable, with the same keys and words. An override underapprovalDecisionisn't read.
migrate strings-keysrenames the table in a strings object written as a literal and lists one built at run time.decision-bar-merged(codemoditems; decision-bar, decision-review; Pro): thedecision-baritem is gone.
DecisionBar,decisionBarStringsanddecisionBarChangeGuardare exported bydecision-review, with the same props,
strings and markup.DecisionBarActionandDecisionReviewActionare one type,DecisionAction.update --to 6.1.0installsdecision-reviewif you haven't got it, and keeps decision-bar's file as your own;migrate items
points each import atdecision-reviewand renames the action types. Delete decision-bar's file once nothing
imports it.review-ladder-removed(codemoditems, which lists; review-ladder, permission-mode; Pro): ReviewLadder and
ReviewLevelare removed. Draw your levels with PermissionMode: each level is one of yourmodes(itslabel,
detailandlocked),valueismode,onValueChangegets the mode's id, andlabel="Review level"names the
control. PermissionMode's newlabelprop is the control's name in place of "Permission mode".migrate items
lists each<ReviewLadder>andReviewLevelimport with this mapping. A ladder with noonValueChangebecomes a
PermissionMode with noonValueChange: the other modes say "Can’t be changed here", or passlockedwith your
reason. Delete review-ladder's file when you have moved.review-ladder-strings(codemodstrings-keys, which lists; review-ladder, permission-mode; Pro): the
reviewLadderstrings are gone.migrate strings-keys(andmigrate 6.1.0) lists each override: the rungs' words
are your modes'labelanddetail, andlabelis PermissionMode'slabel. Then delete them.review-canvas-removed(codemoditems, which lists; review-canvas; Pro): ReviewCanvas is removed.
ApprovalRequest's docs have "Approve with the evidence beside it", which composes Plan, LogStream, ChangeDiff,
BlastRadius, Reasoning and ApprovalRequest: copy it into your app, keeping its rule that a tab with nothing for the
chosen step says so.migrate itemslists each<ReviewCanvas>and import. Delete review-canvas's file when you
have moved.review-canvas-strings(codemodstrings-keys, which lists; review-canvas; Pro): thereviewCanvasstrings are
gone, and nothing reads them.migrate strings-keyslists each override; delete them.usage-meter-variants(codemoditems; usage-glance, usage-ring, usage-meters, portfolio-card; Pro):
UsageGlance and UsageRing are UsageMeter'sglanceandringvariants, inusage-meters, with the props they took
(periodandhreffor a glance,estimateBasisfor a ring,unknownandpausedfor every variant). They draw
the same markup anddata-slotvalues, withdata-varianton the root. UsageMeters is unchanged. PortfolioCard
draws its line with UsageMeter's glance, so it needsusage-metersin place ofusage-glance.update --to 6.1.0
installsusage-meters;migrate itemswrites<UsageGlance …>as<UsageMeter variant="glance" …>and
<UsageRing …>as<UsageMeter variant="ring" …>. A prop for another variant is ignored, with a warning in
development. Delete the two old files once nothing imports them.usage-meter-strings(codemodstrings-keys; usage-glance, usage-ring, usage-meters; Pro): theusageGlance
andusageRingtables are gone and their keys are inusageMeters. The glance's and ring'susedOfLimitis
usedOfLimitWords, and the ring'sestimateValueisestimateWithBasis; the bar's words don't change.
migrate strings-keysmoves each override, and where the glance and the ring worded a key differently it writes the
glance's and lists the ring's for you to choose.change-tree-merged(codemoditems; change-tree, change-diff; Pro): thechange-treeitem is gone.
ChangeTree,ChangeTreeFileandchangeTreeStringsare exported bychange-diff, with the same props.migrate itemsmoves the imports, and lists each file with a ChangeTree beside a ChangeDiff, which can become one
<ChangeDiff navigation="tree">by hand if you want.change-tree-strings(codemodstrings-keys; change-tree, change-diff; Pro): ChangeTree's chips read
changeDiff.create,updateanddelete(the same words), andchangeTree.create,updateanddeleteare gone.
migrate strings-keysmoves an override of them tochangeDiffwherechangeDiffdoesn't set them, and lists it
where it does.away-digest-merged(codemoditems, which lists; away-digest, digest, digest-email; Pro): AwayDigest and
DigestItemare removed; Digest does the job. Draw aDigestwithsince, your heading asdigest.title, the
waiting items inneedsYou, the failed ones infailedand the finished ones indone(a finished item'sdetail
goes into its title, or is left out:DigestDonehas none).onOpen(id)is unchanged. The since line reads "Since
you were last here · 3 hours ago · 5 things", as AwayDigest's did.migrate itemslists each<AwayDigest>and
DigestItemwith this mapping. Delete away-digest's file when you have moved.away-digest-strings(codemodstrings-keys; away-digest, digest; Pro): theawayDigeststrings are gone.
sinceLastHereisdigest.since,failedisdigest.failedandnothingHappenedisdigest.nothingSince, which
migrate strings-keysmoves.whileAwayis yourdigest.title; the sections are headed bydigest.needsYou
("Needs you") anddigest.done("What was done");thingsisdigest.total, whichmigrate strings-keysalso
moves, andgrouphas no counterpart.digest-open-rows(by hand; digest; Pro): Digest callsonOpenfor a done or failed row withouthreftoo,
not only a needs-you row, so withonOpenpassed those rows are buttons. Give them anhref, open them inonOpen
by id, or leaveonOpenout.DigestDone'sbyis optional, and a done row without it names no one: code that
readsdone.byneeds a check, which the type check finds.consolidation-motion(codemodtokens; usage-glance, usage-ring, approval-request, decision-review,
review-ladder; Pro):--cd-motion-usage-glance-fillis--cd-motion-usage-meters-glance-filland
--cd-motion-usage-ring-fillis--cd-motion-usage-meters-ring-fill, each with its suffixes. DecisionCard's answer
and its mark read--cd-motion-decision-review-card-outcomeand-card-outcome-mark, where they read
ApprovalRequest'soutcomeandoutcome-mark, which ApprovalRequest keeps.--cd-motion-review-ladder-rungis
gone.migrate tokensrenames the usage tokens, adds a DecisionCard declaration beside each approval-request
outcome one (keep the one you meant), and lists the ladder's as removed. Nothing fails to build.message-block-kinds(by hand; chat, safe-markdown, message-content; free):MessageBlockgainstableand
quote, so aswitchover a block'skindthat ends in anevercheck fails the type check until it handles them
or has a default. From 6.1 a minor may add a kind, andMessageBlock's doc comment says so. A model's pipe table now
draws as a table, its>lines as a quote, and a fence in a language Payload highlights is highlighted when
highlighting is on: check any CSS that matched those as paragraphs or plain code.
Upgrading from 5.4 and 6.0
Start from a committed tree, so you can see what each step changed. Then, from the app's folder (the one with
components.json):
- Look first:
npx candor-ui@4 update --to 6.1.0 --dry-runprints what 6.1 (and, from 5.4, 6.0) changes for the
items incandor-lock.json, with the merges it would make, and writes nothing. - Update:
npx candor-ui@4 update --to 6.1.0updates every item, merging your changes into Cand...
Candor 6.0.0
Released 2026-11-14.
A major release, with CLI 3.4.0 and @candor-ui/react 6.0.0: one way to say who, approvals that invent nothing, and
headings the free tier can follow. Who did something is one type, Actor, wherever Candor draws it;
ApprovalRequestData's onBehalfOf stays { name }, since it is always a person, the one an agent asked for. An
approval needn't be a deploy: its environment, production flag and build hash are optional, and Candor draws nothing
for one that is missing. HeadingScope and HeadingLevel are free, and the free items that draw a heading follow the
nearest scope, as the Pro items already do. Five things a minor couldn't change are put right: TypedText has one composition
prop, ColumnMapper's percent is the locale's, UsageMeters says "No limit set", a linked ScopeSwitcher or
ScopeBreadcrumb option calls onChange as every other Candor nav item does, and the nulls earlier minors let in are
recorded. CLI 3.4 runs the upgrade (npx candor-ui@3 update --to 6.0.0, then npx candor-ui@3 migrate 6.0.0). No
item is new; heading-level and heading-scope move to the free tier, so the kit has 420 items: 76 free and 389 in
Pro.
Upgrading from 5.x
Start from a committed tree, so you can see what each step changed. Then, from the app's folder (the one with
components.json):
- Look first:
npx candor-ui@3 update --to 6.0.0 --dry-runprints what 6.0 changes for the items in
candor-lock.json, and writes nothing. - Update:
npx candor-ui@3 update --to 6.0.0updates every item, merging your changes into Candor's asupdate
always has. - Migrate:
npx candor-ui@3 migrate 6.0.0runs each of 6.0's codemods that an entry on your installed items names,
in this order:data-types,props,strings-keys,headings. Each lists what it couldn't change under "Left for
you".--dry-runshows it first. - Finish by hand: make the changes the "Left for you" lines name and those marked "by hand" below.
- Check: type-check (
npx tsc --noEmit) and build, then run your tests.
A project still on 4.x goes to 5.0 first, with the same CLI: npx candor-ui@3 update --to 5.0.0, then
npx candor-ui@3 migrate 5.0.0 (Upgrading to 5.0), then the steps above. update --to 6.0.0 and migrate 6.0.0 on a
4.x project stop, change nothing and name them.
The codemods change your own files only: Candor's installed files come with the update, and in one you've changed,
what a codemod finds is listed. Strings you override are checked only where they are written as a strings object
Candor can see: on LocaleProvider or CandorProvider, in a CandorConfig, or typed StringOverrides. The type
check doesn't find an override of usageMeters.noCap, since StringOverrides takes any key: it still compiles and
isn't read, so migrate strings-keys is what moves it.
Each entry below has its id in scripts/breaking.json (the same entries update --to 6.0.0 prints, and the Upgrading
to 6.0 page lists), what changed, and what to do:
actor(codemoddata-types; work, digest, digest-email, change-list, decision-review, approval-request,
approval-queue, review-canvas, environment-promotion; Pro): who did something is one type,Actor
({ kind: "agent"; agent } | { kind: "person"; name }), fromlib/candor/work(KIT-346).DigestActor(Digest,
DigestEmail) andChangeListAuthor(ChangeList) were already that shape and are gone.ApprovalRequestData's
requester(ApprovalRequest, ApprovalQueue, ReviewCanvas, the approvals-inbox template, approve-from-anywhere and
approval-gated-change) was{ name }or{ agent }, andDecisionReviewItem'srequestera string or an
AgentIdentity; both take anActor. Each item draws what 5.4 drew for the same who.migrate data-typesmoves
each import of the old names toActorfromlib/candor/workand renames their uses (an import you aliased keeps
its local name). In a file that imports fromlib/candor/work, ApprovalRequest, ApprovalQueue or ReviewCanvas, it
writes a literalrequester: { name }or{ agent }as{ kind: "person", name }or{ kind: "agent", agent },
and lists every other requester there; in a file that imports DecisionReview, it lists each requester not written
with akind(a string or anAgentIdentityin 5.x). A requester built in a file that imports none of these isn't
seen. The type check finds the rest; a check like"agent" in requesterstill narrows anActor.
The Premium blocks' storedrequestercolumn is unchanged; requesters stored in your own database are data, so map
them to thekindshape where you read them. EnvironmentPromotion'srequestedBytakes anActorwithatas
well as{ name, at }(KIT-358), so code that reads it throughComponentPropsfails the type check at
requestedBy.name. No codemod lists it: by hand, read the name by its shape
("agent" in requestedBy ? requestedBy.agent.name : requestedBy.name).approval-optional(codemoddata-types; work, approval-request, approval-queue, review-canvas,
approvals-inbox; Pro and Premium):ApprovalRequestData'senvironment,productionandartifactHashare
optional, so an approval that isn't a deploy says nothing about an environment or a build (KIT-233). ApprovalRequest,
ApprovalQueue and ReviewCanvas draw nothing for a missing one: no Where line, no hash, no production warning, and
never "Non-production" for aproductionleft out. A request with all three draws as in 5.4.onApproveand
onRejecton ApprovalRequest and ReviewCanvas takehash: string | undefined,undefinedfor a request without a
hash.migrate data-typeslists each read of the three fields in a file that importsApprovalRequestData, and
eachonApproveoronRejecton ApprovalRequest or ReviewCanvas whose handler's first parameter is typedstring
(written inline, or as a function orconstin the same file), with its file and line (CLI-62). By hand: handle
undefinedthere, and where a handler passeshashon as astring; withstrictNullChecksthe type check finds
each.typed-text-as(codemodprops; typed-text; Pro): TypedText'sasis gone;render(since 5.1) chooses the
element (KIT-262).migrate propswritesas="h2"asrender={<h2 />}, keeping the other props, and lists anas
that isn't an element's name (as={tag}: passrender={<Tag />}) and a TypedText with bothasandrender.column-mapper-percent(codemodstrings-keys; column-mapper; Pro):{percent}incolumnMapper.percentSure
is the locale's percent, sign and all ("85%", "85 %" in French), and the default is "{percent} sure" (KIT-263). An
override that typed its own%would draw it twice.migrate strings-keystakes the%(and a space before it)
out where it follows{percent}, and lists an override it can't read or with%anywhere else. Translations stored
outside your source: take it out there.usage-meters-no-limit(codemodstrings-keys; usage-meters; Pro): UsageMeters says "No limit set"
(usageMeters.noLimit) for a usage with no limit, as UsageRing does, where it said "No cap on your plan."
(KIT-355).usageMeters.noCapis gone.migrate strings-keysmoves an override ofnoCaptonoLimit, and lists a
table that has both, for you to keep one. TranslatenoLimitif you hadn't.scope-link-click(codemodprops; scope-switcher, scope-breadcrumb; Pro): a plain click (or Enter) on an
option withhrefcallsonChangeinstead of following the link, as every other Candor nav item does; a click that
opens a new tab (a modifier key, or the middle button) follows the link and calls nothing (KIT-270). Choosing the
option already in place does neither, where 5.x followed its link. An app that passeshrefwith anonChangethat
only sets state stops going to the option's page.migrate propslists each ScopeSwitcher and ScopeBreadcrumb with
onChange; by hand, navigate inonChange(with your router), or leave outhrefwhere the option isn't a page of
its own.locked-null(by hand; command-palette, scope-switcher, scope-breadcrumb, settings-layout, dashboard-tile,
permission-mode, plan, tree, app-sidebar, nav-rail, tab-bar, know and the other items 5.1 to 5.3 widened;knowand
sliderare free): 5.1 to 5.3 widened these to acceptnull, which a minor shouldn't have done for code that reads
them, and 6.0 records it (KIT-281);know'slockedmap (ToolSetting.locked) acceptsnulltoo (KIT-294). 5.1:
thelockedfield ofPaletteItem,ScopeLevel,SettingsItem,DashboardTileView,PermissionModeOptionand
PlanAutonomyOption, thelockedprop of 28 components, and Tree'sonSelect's second parameter. 5.2: the
…Lockedprops of RunEstimate, PlanGate, DataControls, SsoSetup, AgentScreen and Plan, AccountState's
actions[].locked, thelockedmaps of ArtifactToolbar, RestoreDialog, ReviewLadder and NotificationPreferences,
and Inbox's and ApprovalQueue'sdefaultActiveId. 5.3: AppSidebar's, NavRail's and TabBar'sdefaultActiveId. Code
that reads one into astring | undefinedof its own fails the type check, as does a wrapper that types Tree's
onSelectas(id: string) => voidthroughComponentProps. No codemod: where you read one, write?? undefined
(nulland left out both mean unlocked), and type a TreeonSelectwrapper(id: string, node: TreeNode) => void.
Code that passes them is unchanged.heading-default-free(codemodheadings, which lists; heading-scope, heading-level, permission-prompt,
page-state, message-content, message, accordion; free):HeadingScopeandHeadingLevelare free (D109, D110).
PermissionPrompt, PageState (and ListStateView), AccordionTrigger and the headings in a model's message
(MessageContent, and Message through it) draw...
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 w...
Candor 5.3.0
Released 2026-11-13.
A minor, with CLI 3.3.0 and @candor-ui/react 5.3.0. New Pro items for decisions reviewed one at a time, usage at a
glance, changes read file by file, a periodic digest and an agent that asks for the screen, and the fixes 5.2 found.
Nothing a 5.2 app passes stops working; code that reads the nav items' defaultActiveId type may need ?? undefined
(below). Twelve Pro items are new, so the kit has 420 items: 74 free and 389 in Pro.
What to do: npx candor-ui@3 update --to 5.3.0 takes a 5.2 project to 5.3.0, with no codemod. If you use
@candor-ui/react, install 5.3.0, which carries the free fixes listed under it.
What Storywrite asked for (A-62 to A-78), and where each is:
- A-62 Focused review: DecisionReview, new. The keys move between items and never decide; the what-gets-checked
box isn't green unless the app reports a pass. - A-63 Turn request: TurnRequest, new, as a card or
variant="strip". - A-64 Guide overlay: AgentScreen's
markers, and ScreenGuide, new, for a question or a walk-through over them. - A-65 Driver signal and waiting: AgentScreen's
controlStyle="strip"andwaiting. - A-66 Budget pill: UsageGlance, new. A-67 Budget ring: UsageRing, new. Both take UsageMeters' levels, now in
the newusage-level. - A-68 Change reasons: ChangeDiff's
reasonsandfileName="entity", and ChangeList, new. - A-69 Activity filters: RunLog's
toolbarandstatusFilter. - A-70 Digest sections: Digest and DigestEmail, new.
- A-71 Project cap tile: PortfolioCard's
usageandaction. - A-72 Tabs as page navigation: PageTabs, new, a
navof links rather than a Tabs variation. - A-73 Change tree: ChangeTree, new, on Tree.
- A-74 Plain type: the token
--cd-font-name, read by ChangeDiff's file names and EntityChip. CodeListing's title is
drawn in the body font already, so it doesn't read the token. - A-75 Role words: RaciChips'
show="word". A-76 Plain scope: IntegrationConnect'sscopeIds="hidden". - A-77 Sticky decision bar: DecisionBar, new, and AppLayout's
bottomBar. - A-78 Thread list on a phone: SplitView's docs example now shows it (below).
New items (Pro)
Shell:
- DecisionBar (KIT-326): the decision for the item on screen, for AppLayout's
bottomBar. It names the item it
decides; whenitemIdchanges it locks its actions for half a second (changeGuard,decisionBarChangeGuard) and
announces the new title once; a destructive action says what can and can't be undone;locked, and each action's
locked, say why. - PageTabs (KIT-321): page navigation as a
navof links through the app's link render, the current page marked
aria-current="page". On a narrow width the row scrolls sideways with a fade at the edge that has more, and the
current tab is scrolled into view without moving focus.
Work:
- DecisionReview (KIT-308): a mixed queue of decisions, one at a time: "{position} of {total}", the kind (the app's
kinds), the outcome sentence (named as the agent's when an agent wrote it), the facts ("Not known" for null; money in
the app's currency), what gets checked (in future words; green only when the app reports a pass), what happens if you
stop (or "The app hasn't said what happens if you stop."), the actions, and the whole queue beside it. J, K and the
arrow keys move and focus the item's heading; no key decides. When the item shown changes, the actions lock for half
a second (changeGuard), as DecisionBar's do.currentIdwithonCurrentChange, or
defaultCurrentId(nullfor none at first). An approval reaches ApprovalRequest through thedetailrender prop. - TurnRequest (KIT-309): the agent asks the person to take the screen, for a sign-in, a one-time code or a check it
must not pass itself. It says why, what to do, what the app says the agent won't do meanwhile (wontDo, or that the
app hasn't said), and whether the agent can still see the screen (seesScreen, or that the app hasn't said). Take the screen, an
optional quieteralternativeand Not now sit side by side, none focused or pre-selected. After hand-back the
agent'sreportis shown as its words, not checked. Your app must stop the agent's input while the person has the
screen: Candor sends no input. - ScreenGuide (KIT-311): a question ("Which of these, 1 or 2?") or a walk-through (Step 2 of 4, Back, Next, the
steps) over AgentScreen's markers. Nothing is chosen for the person, and the step moves only on Back, Next or the
app's report. Pass it the samemarkersas AgentScreen: both number them throughnumberedMarkers. While
frameStale(from AgentScreen'sonFrameStaleChange) it says the markers may be out of date and locks the answers.
WithoutonAnswerthe answers are locked, and withoutonStepChangeBack and Next are, each saying why. - ChangeList (KIT-316): changes newest first, with who made each (an agent through its mark, or a person), when,
and lines added and removed when known; a choice of since the last review or everything. Without a recorded review
(lastReviewedAt) that choice is locked and says "No review recorded yet". - ChangeTree (KIT-322): changed files as a tree of folders, on Tree: a chip and the word for each change in
ChangeDiff's words (N New, C Changed, D Deleted; an unchanged file has a dot, not a letter), deleted files struck
through and still listed, the count of changes per folder, and a folder holding one folder joined to it in one row.
Its selection drives ChangeDiff (selected,onSelect).
Ops:
- UsageGlance (KIT-313): one usage as one line for a top bar's
end: "{used} of {limit}", a thin bar, the period in
your words (period), and the label as a link through your router (href). From 75 % the level is said in words
with an icon. No limit, no bar;unknownsays "Not known yet", never zero;paused(true, or your reason) is your
statement, never inferred from what's used. - UsageRing (KIT-314): one usage against its limit as a large ring: the figure, "of {limit}", "{percent} used"
(rounded down below 100), UsageMeters' levels, pending as a striped arc and may-exceed in words. The pace is your
usage'sestimate, a dashed inner arc said under the ring withestimateBasis(or that you gave none); the kit
computes no pace. Over the limit the ring is full and the words keep the measured figure. No limit, no ring;
unknownandpausedas UsageGlance.
Foundation:
usage-level(a lib item):usageLevel(usage)returns the ratio of used to limit, the level ("normal",
"warning"from 75 %,"danger"from 90 %) and its tone, with null for the ratio and level when there is no limit.
usageLevelThresholdsandusageLevelToneshold the numbers and colours. Safe on the server. UsageMeters reads its
levels from it and draws what it drew in 5.2.
Collaboration and admin:
- Digest (KIT-318): a periodic summary in sections in a fixed order: what needs you (each row a link, a button
throughonOpen, or text), health (a figure, a sparkline and its change against a named period), what was done (by
agent or person) and notes in the app's groups. A trend with fewer points thanminPoints(default 4) says "Not
enough data yet" with the count, never a flat line; a figure not known says "Not known" and the app's reason, never 0. - DigestEmail (KIT-319): the same
DigestDataas an email on EmailLayout's colours, server-safe (no"use client",
noreact-dom):DigestEmailas a whole document,renderDigestEmail(digest, options)for an HTML string, and
DigestEmailPreviewto show it on a page. Trends are in words, with no sparklines; links are the app's URLs.
It imports Digest's types only, so installingdigest-emailalso installsdigest.
Components (Pro)
- AgentScreen (KIT-310, KIT-312):
markers, numbered points in the frame's own pixels, drawn over the picture
where it is placed in the box (and as the box resizes), each with its number and label, and listed in text beside the
frame. While the frame is stale, lost or ended they're hidden, with "The markers are hidden: the picture may be out of
date."; with no frame, none.onFrameStaleChangetells the app when the picture becomes stale, lost or ended, and
current again. New exportsAgentScreenMarkerandnumberedMarkers.controlStyle="strip"says who
drives as a strip along the frame's top in the driver's colour, with the words in it, and outlines the frame to match;
forced colours use system colours.waiting(true, or the app's reason) draws "Waiting for you" beside the run's
state; it is a prop, not a newAgentScreenRunmember. - AppLayout (KIT-326):
bottomBar, pinned under the page indata-slot="app-layout-bottom-bar": a row just above
tabBarwhile the tab bar shows, otherwise the last row of the column beside the navigation. It takes its own room,
so nothing scrolls under it, and the page isn't remounted when it comes or goes; it is hidden while the quick chat is
over the page. Without it the markup is 5.2's. - ChangeDiff (KIT-315, KIT-322):
reasons(path to one line) draws "The agent's reason, not verified: …" above
that file's diff, as text.fileName="entity"names files by their entity in the tab and heading, with the path in
the accessible name and a tooltip.selected(a path) andonSelectlet the app, or a ChangeTree, hold the shown
file; withoutselectedit keeps its own, as in 5.2. - PortfolioCard (KIT-320):
usagedraws the workspace's usage against its own limit as UsageGlance's line, with
usageUnknown,usagePausedandusagePeriodas UsageGlance'sunknown,pausedandperiod;action
({ label, onClick }, the newPortfolioAction) is one button after the name's link. Withoutusageoraction,
the card is 5.2's. - RaciChips (KIT-324):
show="word"draws the ...
Candor 5.2.0
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 inscrollTopof 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 inscrollTopcounts 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 throughscrollerRef, 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'
…Lockedprops andlockedmaps, and Inbox's and ApprovalQueue'sdefaultActiveId, acceptnull(KIT-282,
KIT-291), aslockeddoes since 5.1. For a…Lockedprop or alockedvalue,nullor left out is unlocked. For
defaultActiveId, onlynullmeans "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'supgradeLocked; DataControls'deleteAccountLocked,
deleteHistoryLockedandexportLocked; SsoSetup'senforceLocked; AgentScreen'stakeOverLocked; Plan's
acceptLocked. - AccountState's
actions[].locked. - The values of the
lockedmaps on ArtifactToolbar, RestoreDialog, ReviewLadder and NotificationPreferences. - Inbox's and ApprovalQueue's
defaultActiveId. Theirselectedbehaves as in 5.1.
- RunEstimate's
- ApprovalQueue's (Pro) requester tile draws the name's first letter upper-cased, as a whole character, through
the newinitialOfininitials(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 callonChange, as ScopeSwitcher's option does since 5.1 (KIT-269). A plain click callsonChange, as
before. - AppSidebar, NavRail and TabBar (Pro) draw their in-app places through the app's link (
LinkProvider, or
CandorProvider'slink), so your router's link handles them (KIT-268). With none set each draws the<a>it drew
in 5.1. A plain click withonNavigategiven 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}"): withchoices, 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.basisandbasisand StatCard'sdelta.vsare each in a<bdi>. - Thread (free): while it follows the newest message, its scroller has
overflow-anchor: noneas an inline style,
which overrides anoverflow-anchoryour CSS sets there; it has none while the reader is scrolled up. - ThemeSetting (Pro): with a stored theme outside
choices, the trigger hasaria-describedbypointing at a hidden
element with thethemeSetting.usingwords. - 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.
lockedacceptsnullon everylockedprop, not on every item: in 5.1.0 the…Lockedprops
(acceptLocked,startLocked,upgradeLocked…), AccountState'sactions[].lockedand the record-typedlocked
maps still takestring | 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 astring | undefinedneeds?? undefined, and Tree's two-parameteronSelect
fails where a wrapper types it as(id: string) => voidthroughComponentProps<typeof Tree>(KIT-283). Lockedunder the app'sTooltipProvideropens its reason after the app'sdelayon 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:useFocusWithinand itsFocusWithintype (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'sautoFocus) 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
throughuseMergedRefs, 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
cacheComponentsno 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-widthand the push drawing fell back tomin(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...
Candor 5.1.0
Released 2026-11-13.
A minor, with CLI 3.1.0 and @candor-ui/react 5.1.0; nothing breaks a 5.0 project. The fixes 5.0 held back so its
breaks could be read on their own: focus that stays put, links your router follows, locked controls that say why, and
text that isn't joined in code. Six Pro items are new (link, merge-refs, use-settle, live-rows,
email-heading and user-message-actions), so the kit has 407 items: 74 free and 376 in Pro.
What to do: npx candor-ui@3 update --to 5.1.0 takes a 5.0 project to 5.1.0, with no codemod. If you use
@candor-ui/react, install 5.1.0, which carries the free fixes to Locked, Tooltip, ToolCall, Composer and
Progress. The changes a 5.0 app sees, each with what to do:
- Inbox and ApprovalQueue (Pro) keep their own selection when you pass
onSelectedChangewithoutselected: a
ticked item shows ticked, and the callback is still called. In 5.0 the tick never showed. Passselectedto hold the
selection yourself: once you have passed it, the list keeps none of its own, so clearing it toundefineddraws none,
as in 5.0. - ConfirmButton (Pro) stays armed for 6 seconds by default in English (4 in 5.0): left out,
armedForis long
enough to hear the armed announcement at a slow screen-reader rate and then press again, in whole seconds and never
under 4, and the announcement says how long. PassarmedFor={4000}to keep 5.0's window; a test that waited 4
seconds for it to disarm waits for the new window or setsarmedFor. - Six data types'
lockedfield acceptsnull(string | null | undefined):PaletteItem,ScopeLevel,
SettingsItem,DashboardTileView,PermissionModeOptionandPlanAutonomyOption. Code that builds them is
unchanged; code that reads one into astring | undefinedvariable fails the type check: add?? undefined. - Inside a
HeadingScope, some headings sit one level below it, as 5.0's rule says, where 5.0 ignored the scope:
the loading, empty and error heading of Inbox, SessionList, NotificationCenter, AgentRoster, ApprovalQueue,
TraceViewer, EvalScorecard, MembersTable, AuditLog and ResultTable; A2uiSurface's model headings; EmailPreview's
title; and AccessRequest's title, a<p>in 5.0, which is a heading inside a scope or with its newheadingLevel.
Outside a scope each draws what it drew in 5.0 (<h2>; A2uiSurface's levels; EmailPreview's<h3>; AccessRequest's
<p>). A test that found one of them by level inside a scope looks one below the scope, or passesheadingLevel; a
test that found AccessRequest's title as text inside a scope finds it by roleheading. - A stacked Carousel (Pro) changes slide on a finger or pen swipe only: a mouse drag over a slide selects its text.
The slide change a person makes is announced ("2 of 3",carousel.slideOf).
Translators: these keys are new. Until you translate them, each says its English words.
graphView.putBack;modelKey.saving;dockWindow.goToWindowandgoToWindowTitle.board.unplaced(one and other) andboard.columns;dataTable.sortCleared.usageMeters.amount,usedOfLimit,limitAfter,unitAfterandwithPending. The keys UsageMeters read in 5.0
are still read.runTree.readoutStatusandreadoutJoin.from,afterandverdictNoteare still read, as their placeholders.- The Premium templates' strings that held " · " (
agentOpsConsole.topLineandtopLineStopped,
approvalsInbox.owner,member,ruleHeading,waitingLineandrequestDescription,
supportCopilot.threadCustomerLineanddraftCardHeader) take{separator}, the locale's separator, in its place;
agentOpsConsole.startedByandapprovalsInbox.appliedByno longer hold it, since the template joins them. An
override that kept its own " · " instartedByorappliedByshows it twice: take it out.
Some DOM your own CSS or tests may match has changed:
- FilterChips (Pro): a chip's label and its value are each in their own
<bdi>. - Board (Pro): the scrolling region keeps the board's
labeland the group of columns inside it is named
"Columns of {label}"; the region's description says how many cards are in no column. - EmailPreview (Pro): the title carries
data-slot="email-heading", drawn by the newemail-headingpart. - SheetContent (Pro) carries
data-edge(top,right,bottomorleft, flipped for RTL). - CardDeck (Pro): the hint is clipped while hidden, not
invisible, so a screen reader's browse mode finds it. - Inbox and ApprovalQueue (Pro): the rows' list carries
data-slot="live-rows", drawn by the newlive-rowspart. - A stacked Carousel (Pro): the slides' row is
aria-live="off"("polite"in 5.0), andCarouselStatushas no
aria-live, since the carousel says a slide change the person makes once itself, through Candor's announcer. A test
that asserted either live region checks the status's text, or the announcement, instead. A sliding carousel's are
unchanged. - ToolCall and SearchTrace: a row that finishes with nothing to show while focus is on it keeps its locked button
until focus leaves; then it is text, as in 5.0.
Corrected in the 5.0 upgrade notes
scripts/breaking.json's 5.0.0 entries, the Upgrading to 5.0 page
and what update prints going to 5.1.0 or later say these now. update --to 5.0.0 reads the 5.0.0 snapshot, frozen as
released, so it prints the old text; the page says so. The 5.0.0 section below is left as it was released.
heading-default(CLI-36): the free PermissionPrompt draws<h2>by default since 5.0 and reads no
HeadingScope: passheadingLevel={3}to keep 4.x's<h3>.HeadingScopeis named as Pro.strings-separator(CLI-34):Formatterhas two new members,separatorandjoin, so an object you build as a
Formatteryourself (a test double foruseFormat) fails the type check until it adds them.locked-not-disabled(CLI-40): the reasons the waiting controls give are 50 newlocked…keys, on 31 items,
which a translated app says in English until it translates them; the entry lists them.strings-sentences' list of
new keys addsclarifyingQuestions.before.props-active-id-nav(CLI-35): its search finds SettingsLayout'sactive=too.- The migration lines of the ten entries with a codemod name
npx candor-ui@3 migrate, as the codemod lines do,
so a project withcandor-ui@2installed doesn't run CLI 2 (CLI-37).
New items (Pro)
link:LinkProvider,useLink,LinkRenderandLinkRenderProps. Set how Candor's items draw an address in
the app (a Next or TanStackLink) once, or throughCandorProvider's newlinkprop, and SessionList,
ScopeBreadcrumb, ScopeSwitcher, PersonMenu (Help), NotificationCenter, NeedsYouLine, ScoreRing, PortfolioCard,
DetailsList and BoardCard draw their in-app links with your router. With none set each draws the<a>it drew in
5.0. Downloads and links to other sites stay<a>.merge-refs:mergeRefsanduseMergedRefs, one callback ref from an app's ref and an item's own. Tabs uses it.use-settle:useSettle, which calls back once a value has stopped changing for a set time. PlanPicker and
ScheduleEditor use it, with their 5.0 timings.live-rows:LiveRows, the rows of a list whose data changes under the person, as Inbox and ApprovalQueue draw
them (both now draw through it; the rows' list gainsdata-slot="live-rows", listed below).email-heading:EmailHeading, EmailPreview's title at the level the page'sHeadingScopegives it; a client
part, soEmailPreview,EmailLayoutandrenderEmailstay free of"use client".user-message-actions:UserMessageActions, Copy and Edit and send again on the person's own message, placed in
Message'smeta. Edit hands the app the message's words throughonEdit; what the person sends is a new message, and
this one stays in the thread, so the app keeps the versions. Copy appears whentextis given, and Edit when both
textandonEditare.
Components
New, additive props (Pro):
- ThemeSetting:
choices, the looks to offer, all four by default;choices={["system", "light", "dark"]}leaves
out High contrast. A stored value outside the list shows as nothing chosen. defaultActiveIdon SessionList, SidePanel, AppSidebar, TabBar, NavRail, AgentRoster, Inbox, ApprovalQueue, Plan,
RunTree, VersionHistory, GraphView and Tree;defaultSelectedon DataTable, DocumentViewer and the four charts;
defaultOpenon RestoreDialog and ReportReply (KIT-236). Where the item had no state of its own, it keeps one only
when the default is given; an item given neither draws as in 5.0, except Inbox and ApprovalQueue, listed above. An
app that holds the selection itself, withundefinedas none, sees none when it clears it. A chart's
defaultSelectedand Tree'sdefaultActiveIdtakenullto keep the selection with none at first. DataTable keeps
its own selection withoutonSelectedChange, as in 5.0; withonSelectedChangeand noselected, pass
defaultSelected(an emptySetfor none) to have it tick the rows a person selects.- Inbox takes
activeIdand marks the item open beside it (KIT-234). - AccessRequest takes
headingLevel(KIT-252).useHeadingScope(), fromheading-scope, gives the nearest
HeadingScope's level, orundefinedoutside one. - DataTable: a column with
sortable: falsehas no sort button, noaria-sortand no place in the stacked sort control
(KIT-221). - Tree's
onSelectpasses the node as its second argument, as the tree drew it, loaded children included;
onSelect={(id) => …}still type-checks (KIT-239). - TypedText takes
render, which wins overas(KIT-238). - DateRangeField takes
name(hidden inputs{name}.fromand{name}.to) anderror, as Date...
Candor 5.0.0
Released 2026-11-13.
A major release, with CLI 3.0.0 and @candor-ui/react 5.0.0: one heading outline, one name per idea, and strings a
translation can reach. Every item that draws a heading takes headingLevel (1 to 6) and, without it, draws one level
below the nearest HeadingScope, else <h2>, so a page's outline skips no level; dialogs, sheets, drawers, settings
sections and dashboard tiles set the scope. The nav items' selected item is activeId, Tree's and EnvironmentBand's
onSelect passes an id, and an accessible name is label. The " · " between parts is one string,
locale.separator, and sentences that were joined in code are one string each with {placeholders}. The six data
types are MessageData, ToolCallData and so on, as @candor-ui/react already named them, and the English exports
kept for compatibility are gone. CLI 3.0 runs the upgrade (npx candor-ui@3 update --to 5.0.0, then npx candor-ui@3 migrate 5.0.0) and no longer takes a 3.x project, which keeps CLI 2. heading-level and heading-scope
are new, so the kit has 401 items: 74 free and 370 in Pro.
Upgrading from 4.x
Start from a committed tree, so you can see what each step changed. Then, from the app's folder (the one with
components.json):
- Look first:
npx candor-ui@3 update --to 5.0.0 --dry-runprints what 5.0 changes for the items in
candor-lock.json, and writes nothing. - Update:
npx candor-ui@3 update --to 5.0.0updates every item, merging your changes into Candor's asupdate
always has. - Migrate:
npx candor-ui@3 migrate 5.0.0runs each of 5.0's codemods that an entry on your installed items names,
in this order:types-data,props,strings-keys,headings. Each lists what it couldn't change under "Left for
you".--dry-runshows it first. - Finish and check: make the changes the "Left for you" lines name and those marked "by hand" below, then
type-check (npx tsc --noEmit) and build.
migrate parses your source with the project's TypeScript or, on TypeScript 7 (which has no JavaScript API) or with none, with the TypeScript 5 that CLI 3 brings, so there is nothing to install for the run. Strings you override are checked only
where they are written as a strings object Candor can see: on LocaleProvider or CandorProvider, in a
CandorConfig, or typed StringOverrides. The type check doesn't find an override of a key 5.0 removes, since
StringOverrides takes any key: it still compiles and isn't read, so migrate strings-keys is what moves or lists it.
Every change, by its id in scripts/breaking.json (the same entries update --to 5.0.0 prints, and the Upgrading to
5.0 page lists):
types-data(codemodtypes-data):MessageandToolCall(lib/candor/chat),ApprovalRequestand
ResultTable(lib/candor/work),Finding(lib/candor/data) andRunReceipt(lib/candor/ops) areMessageData,
ToolCallData,ApprovalRequestData,ResultTableData,FindingDataandRunReceiptData, the names
@candor-ui/reactalready used. No alias is kept. The codemod renames each import and its uses; an import you
aliased keeps your local name. Imports from@candor-ui/reactdon't change.heading-default(codemodheadings, which lists): withoutheadingLevel, an item's top heading is one level
below the nearestHeadingScope, else<h2>, and its sub-headings sit below it. Most items that drew<h3>or
<h4>now draw<h2>outside a scope; they look the same. DialogContent, SheetContent, DrawerContent,
AlertDialogContent, SettingsSection, DashboardTile, ArtifactPanel, AppLayout's chat, a floating DockWindow,
ReportSheet and ReportSection put their content in a scope, so a Candor item inside draws one level lower than
before. ReportSheet's cover, a fixed<h1>in 4.x, is<h2>: passheadingLevel={1}where a ReportSheet is the
whole page. The free PermissionPrompt draws<h2>(was<h3>) and reads no scope. PageHeader stays<h1>,
AccountState (a whole page) keeps its<h1>, EmailPreview keeps<h3>, and RestoreDialog's "not undone"
heading keeps<h3>, under the dialog's<h2>title. The codemod lists each use without
headingLevelwith the level it drew in 4.x, and changes nothing: where a page or a test needs that level, pass
headingLevel={n}, or wrap a section in<HeadingScope level={n}>(lib/candor/heading-scope).heading-level-type(no codemod: nothing to change):headingLevelisHeadingLevel(1 to 6) on every item,
where DataTable, ReorderableList, Board and BoardCard, NarrativeBlock, PortfolioCard, MonitorCard, DashboardTile and
EnvironmentList took2 | 3 | 4 | 5 | 6. A level you pass still type-checks. Where you type a level of your own,
importHeadingLevelfrom lib/candor/heading-level (layout/headingstill exports it).props-active-id-nav(codemodprops): TabBar's and NavRail'scurrent, AppSidebar'sactiveNavand
SettingsLayout'sactiveareactiveId, with the same value. Stepper's, PlanPicker's and InlineSuggestion's
currentmean something else and stay.props-label-name(codemodprops): SettingsLayout's and DocumentViewer'stitle, their accessible name, which
isn't drawn, islabel;titleis Candor's word for a heading that is drawn.props-popup-class(codemodprops): PersonMenu's and ScopeSwitcher'slayerClassprop, the classes for the
menu's popup, ispopupClassName.on-select-id(by hand): Tree's and EnvironmentBand'sonSelectpasses the id of the node or environment, not
the object. WriteonSelect={(id) => …}and look it up by id where the handler needs it.migrate propslists each
onSelecton them, and the type check finds a handler that still takes the object.strings-compat-exports(codemodstrings-keys):statusLabel(lib/candor/status),environmentLabel
(lib/candor/team),approvalStateLabel(approval-request),reviewLevels(review-ladder) andstandardCards
(standard-cards), English only, are removed. The codemod rewritesstandardCardsused inside a component toconst standardCards = useStandardCards()at its top, and lists the others, andstandardCardsused outside a component,
with what to use:useStatusLabel()(label("running")); EnvironmentBand'sproductionandnonProduction
strings joined withuseFormat().join;useStrings("approvalRequest", approvalRequestStrings);
useStrings("reviewLadder", reviewLadderStrings). SessionList'sstatusLabelprop is a different thing and stays.chart-strings(codemodstrings-keys):barChart.byCategory,lineChart.over,lineChart.chartValuesand
heatmap.heatmap, unread since 4.2, are removed. An override of one still compiles and draws nothing; the codemod
deletes it.strings-separator(codemodstrings-keys): the " · " between parts is one string,strings.locale.separator,
read throughuseFormat().separatoranduseFormat().join. The keys that held it are removed:
message.metaSeparator,payload.titleSeparator,permissionPrompt.scopeSeparator,reasoning.summarySeparator,
composer.hintSeparator,searchTrace.domainSeparator,changeSetReview.hintSeparator,taskTray.countSeparator,
workflowEditor.hintSeparatorandmarkSeparator, andreviewQueue.hintSeparator. The codemod moves an override
of one tolocale.separator; where two give different values, it lists them for you to choose.subscoreCard.separator
andtableScrubberMap.kindSeparator(", ") are removed too: those lists follow the locale's list format, and the
codemod lists an override of either. These strings no longer hold the mark, since Candor joins the parts:
integrationConnect.connectedSince("since {when}") andcheckedAt("checked {when}"),
subscriptionStatus.cardExpires("expires {expires}"),membersTable.invitedBy("Invited by {name}", with the new
expiresIn),awayDigest.group("{label}"),blastRadius.group("{noun}s"),escalation.sentLineand
acknowledged,environmentPromotion.requestedBy,promotedanddeclined(each without{when}),
taskTray.started("started"),clarifyingQuestions.progress("question {step} of {total}", with the new
before),agentRoster.failed("{count} failed") andcolumnMapper.suggested("Suggested", with the new
percentSure, "{percent}% sure"). Four that held it between parts are removed, their parts joined by Candor:
reconcileTable.summary(openCount,resolvedCount,matchedCount),evalScorecard.passedFailed
(passedCount,failedCount),reviewQueue.progress(position, "{position} of {total}", andgradedCount) and
dataTable.aggregateLine, which has nothing to translate; the codemod lists an override of one with the keys that
say it now. An override of a kept string that kept its own " · " shows it twice. One that kept a placeholder
Candor no longer fills ({when},{count},{status},{expires}or{percent}) shows it as written:{when}
on screen. The codemod lists an override that still has either: take it out.strings-sentences(codemodstrings-keys, which lists): sentences built by joining strings and numbers in
code are one string each with{placeholders}, or are parts Candor joins with the separator. The removed keys, and
what says them now:scheduleEditor.announceNext(announceRule,announceRuleAlone);dataRetention.policy
(policyVersion,policyChanged);subscriptionStatus.price(pricePerSeat,priceTotal);inviteChooser.from
(fromName,expiresIn);dualListbox.addedandremoved(addedNowandremovedNow, "Added 3 to Members, which
now holds 5.") andtotal;subscoreCard.outOf100(scoreOutOf, "{score} / {max}");freshnessStamp.stampOverdue
(overdue);memoryManager.summary(inferredCount);blastRadius.reach(`reachChang...
Candor 4.5.0
Released 2026-11-12.
A minor, with CLI 2.3.1 and @candor-ui/react 4.5.0; nothing breaks. Steps and conditions dragged into place in
WorkflowEditor's graph, by pointer, keyboard or touch; heading levels on seven items, so they fit under a page's own
headings; the fixes 4.4's reviews found, in the kit, the motion system and the docs MCP; and the fixes the Fable review
of 4.3.0 and 4.4.0 found. The kit has 399 items: 74 free and 368 in Pro.
What to do: npx candor-ui@2 update takes a 4.4 project to 4.5.0, with no codemod. If you use @candor-ui/react,
install 4.5.0, which carries the free fixes to Button, Locked and Progress. Three changes a 4.4 app sees, each
with what to do:
- MonitorCard (Pro) without
onTogglesays "On" or "Off" in words (span[data-slot=monitor-on], the new strings
monitorCard.isOnandisOff) in place of a switch that did nothing when pressed. An unavailable monitor keeps its
switch, locked with the reason. PassonTogglewhere the person can turn the monitor on or off; a test that found
the switch on a card withoutonToggleshould find the words. - DriftChange (Pro) keeps its actions locked once Adopt or Revert has finished, saying "Waiting for the change to
update." (the new stringdriftChange.waitUpdate), until itsstatusleaves"open"or a new change arrives; then
it announces the outcome. Setstatusto"adopted"or"reverted"whenonAdoptoronReverthas done its work;
an app that never sets it leaves the actions locked. - PersonMenu's avatar (Pro) is named after the initials it shows, then its 4.4 name: "PS, Priya Shah, account
menu", through the new stringpersonMenu.withInitials("{initials}, {label}"), so its name starts with what can
be seen. A test that found the avatar by its name should look for the new one; the row form is unchanged.
Translators: these keys are new. Until you translate them, each says its English words, except where noted.
scheduleEditor.announceRuleandannounceRuleAlone, the announcement once the person stops changing the rule.
An app that translated 4.4'sannounceNextand not these still hears its own words, joined as 4.4 joined them.
announceNextis no longer read otherwise; 5.0 removes it.settingsLayout.contentLabel("{item} settings"), the open section's region name. An app that translated
SettingsLayout's other strings and not this one gets 4.4's name, the item's own label.personMenu.withInitials;monitorCard.isOnandisOff;driftChange.waitUpdateandrevertUndo;
modelKey.cancelLocked;permissionMode.changingLocked;linkPreview.userinfo;dateField.readingWithProblem.sessionList.contextWordsandcontextKindShown;cardDeck.dismissedNext,keysMoveDismiss,keysMoveand
keysDismiss;dataTable.sortBy,notSorted,order,ascending,descendingandsortFirst.- IntegrationConnect's hold:
integrationConnect.waitingTitle,waitingNote,blockedTitle,blockedNote,
approveWho,approveWhere,blockedWhat,unblocker,askedAt,holdCheckedAt,checkAgain,checking,
waitCheck,checkFailedandback. - The workflow graph's move:
graphView.places, andworkflowEditor.move,moveNode,moveHint,cancelMove,
cancelMoveNode,triggerFixed,placeAt,placeHere,pickedUpandputBack.
Some DOM your own CSS or tests may match has changed:
- SettingsLayout's open section (Pro) is a region named "{item} settings" ("Members settings"), no longer the item's
label alone, so it no longer shares "Members" with MembersTable's section. A test that found the region by the item's
label should use the new name. - PermissionMode (Pro), while a change of mode is on its way, keeps the other modes focusable,
aria-disabledin
Lockedwith the reason "Changing the mode" (permissionMode.changingLocked), notdisabled, and focus stays where
it was. A test that expected them disabled should checkaria-disabled="true". - CardDeck (Pro) lists its keys in
aria-keyshortcutsand describes them in[data-slot=card-deck-hint], shown
while the stack has keyboard focus. Once the app has taken a dismissed card out, it announces "{card} dismissed.
{next}, 2 of 5" once, in place of "{card} dismissed". A test expecting the shorter announcement should expect the
sentence. Backspace still dismisses. - AppLayout's app frame (Pro) draws no
<header>when there is nobrand, notopand no menu button; the
banner's row collapses. A test that expected an empty banner landmark there should expect none. Locked(free), without a reason, hands back the control as it is: it no longer gives it an id or a tooltip
trigger's attributes and handlers, so an app's ownTooltipTriggerround it finds the app'sTooltip. Locked's
tooltip now sits beside the control rather than round it.lockedimports@base-ui/react/tooltip. EachLocked
also has its own tooltip provider, on yourTooltipProvider's timing, so moving from one locked control to the next
waits the provider'sdelayagain rather than opening at once within itstimeout. Nothing to change in the app; a
test that expected the next locked control's tooltip at once should wait for it.- LinkPreview (Pro) shows the scheme and host the browser goes to: lower-cased, an international name as its
punycode, without a user name or password. An address that carries one has a note under it,
[data-slot=link-preview-userinfo](linkPreview.userinfo). A test that matched the address as written should
match the host as the browser reads it. - DataTable's stacked form (Pro) has
[data-slot=data-table-sort]above its cards whenever it has rows. - ReorderableList's drag ghost (Pro),
[data-slot=reorderable-list-ghost], and GraphView's new one are drawn
throughLayerPortal, at the end of<body>(or in the layer host inside another library's dialog), so inside a
Dialog or Sheet the ghost sits beside the pointer and isn't cut off by the window. A test that looked for the ghost
inside the list should look indocument. - Tabs (Pro) leave
data-tab-valueoff a tab whose value is an object or a function, where 4.4 wrote "[object
Object]"; strings, numbers, booleans,nulland bigints keep it. - Added attributes, with nothing to do: LineChart's plot carries
data-plot-dir="ltr"; GraphView's node buttons, and
the backdrops of Dialog, AlertDialog, Sheet and Drawer, carry their moment's motion chain in their ownstyle, with
the caller's style merged over it; DriftChange's Revert confirmation has[data-slot=drift-change-revert-undo].
New items (Pro)
@candor/initials, a lib item:initialsOf(name, locale?), the first letter of each of a name's first two
words, upper-cased inlocale("ilker" is "İ" in Turkish, "I" in English). Left out, the letters are upper-cased the
same in every language, so the server and the browser agree. PersonMenu and Board import it, so installing Board no
longer brings in PersonMenu;person-menustill exportsinitialsOffor apps that import it from there.
Components
- WorkflowEditor (Pro): steps and conditions move in the graph view. Drag one with a mouse or pen to a place
between two nodes or into a branch, or press the Move button on its card under the graph: the arrow keys choose a
place, Enter drops it there and Escape puts it back, each step said; on a touch screen, tap a place, or Cancel. The
layout stays automatic. A move is marked "Moved by you" and Undo takes it back. The trigger always comes first, and
its Move button says so. Escape during a move or a drag doesn't close a Dialog or Sheet the editor is in. - GraphView (Pro) takes
places, a function giving the places a node can go (GraphViewPlace, in the layout's
layer and slot),onPlace(a drop) andmoving(a keyboard move the app draws). While a move is on, each place is a
button named by its place, out of the tab order. After a drop the nodes that moved slide, asettlemoment in the
move family. Withoutplacesa graph draws as before, so Plan, RunTree and Diagram are unchanged. headingLevel(Pro) on ReorderableList (its group heads, default 4), Board (its column heads, default 4),
BoardCard (one below its board's heads; used alone, 5), DataTable (its title, default 3; the stacked form's group
heads and cards below it), ApprovalDecision (1 to 6, default 3), MonitorCard (default 3) and EnvironmentList
(default 3), so each fits under a page's own headings. ApprovalRequest and PortfolioCard already had it. The defaults
are 4.4's levels, so nothing a 4.4 page draws changes.- IntegrationConnect (Pro) takes
hold(IntegrationHold,"waiting"or"blocked"),onCheckAgainand
onBack, as EnvironmentConnect does: who has to approve the app, where and when it was asked and checked, or whose
policy blocks it and who can unblock it. Withoutholdnothing changes; once connected,holdis ignored. The names
in a hold are another tenant's text, neutralised and drawn in a<bdi>. - SessionList (Pro):
contextKind="visible"prints the context's kind before its chip ("Approval · Quote over
$50k"); the default,"name", reads it in the chip's name only, as in 4.4. - ScheduleEditor and SessionList (Pro) build their sentences from strings with placeholders (
announceRule,
announceRuleAlone,contextWords), not by joining words in code, so a translation can order them. - DataTable (Pro):
stackBelowis measured before the first paint, so a phone never draws the wide table first;
server-rendered HTML shows the wide table until it hydrates. The stacked form has a Sort by control (a column, or Not
sorted) and Ascending and Descending above the cards: the same sort as the column heads, asked of the server in
server mode and kept when the table widens. Nothing is chosen until the person chooses...