Repository navigation
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 Candor's, installs the
item that takes over from one 6.1 removes, and keeps the removed item's file as your own. It writes
candor-lock.jsonas version 2 and a copy of each installed file in.candor/base/: commit both. - Migrate 6.0.0, if you are coming from 5.4:
npx candor-ui@4 migrate 6.0.0runs 6.0's codemods (data-types,
props,strings-keys,headings), as on Upgrading to 6.0. - Migrate 6.1.0:
npx candor-ui@4 migrate 6.1.0runsitems,strings-keysandtokensfor the entries on your
installed items. 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" above, then delete the
removed items' files once nothing imports them. - Type-check and build:
npx tsc --noEmitand your build, then your tests. - Verify:
npx candor-ui@4 verifychecks each installed file and its base copy againstcandor-lock.json,
without the network.
A project on 6.0.x has run 6.0's codemods, so it skips that step. Plain npx candor-ui@4 update on 6.0.x stays on 6.0
and says that 6.1.0 has breaking changes; --to 6.1.0 takes it there. A project before 5.4 takes Upgrading to
6.0's commands with CLI 3 first (npx candor-ui@3 update --to 5.4.0).
From now on run every command as npx candor-ui@4: CLI 3 can't read a version-2 lockfile.
Components (Pro)
- DecisionReview's page says which of its three components fits: one decision with two equal answers
(DecisionCard), a mixed queue reviewed one at a time (DecisionReview), or the bar that decides the item on screen
(DecisionBar). - PermissionMode gains
label, the control's name in place of "Permission mode", and
permissionMode.currentNamed("{label}: {mode}"), the compact button's name whenlabelis given. Itsmodeis the
mode in force, as the app or the agent reports it. WithoutonValueChangeit only shows the mode: the other modes
are unavailable (aria-disabled, notdisabled) and say "Can’t be changed here", the new
permissionMode.readOnlyLocked. Passlockedfor your own reason. - UsageMeter (
usage-meters): one usage against its limit as a bar (UsageMeters' card, the default), a one-line
glance or a ring. The bar takesunknown("Not known yet", or "Not known yet, of {limit}", with no bar and never
zero) andpaused(an icon and "Paused", or "Paused: {reason}"). A figure that isn't a finite number is drawn as not
known in all three, and in UsageMeters' cards.usageMetersgains 13 keys. - UsageMeter's ring fits its figure (KIT-366): the ring is 10rem across, or as wide as a narrower container, and
stays square. The figure is sized with the ring, 30px for a short figure at 10rem and smaller for a longer one, and
when one line would be too small its unit goes to a second line. A figure is never cut off, ellipsised or rounded to
fit. Nothing to do: a ring in a narrow column now fits it. - UsageMeter's ring measures its figure (KIT-375) once it is on screen, again when the figure changes and when the
fonts have loaded, so a figure in a narrower font is drawn larger and one in a wider font still fits. Nothing to do. - ChangeDiff takes
navigation="tree", which picks the file from a ChangeTree beside the diff (above it when the
item is narrower than 42rem), andtreeLabel, the tree's name. - Digest takes
since, drawn under the title as "Since you were last here", how long ago and how many things need
the person, failed or were done (digest.total, "{count} things"), afailedsection (DigestFailed) under a
heading with a cross icon in the destructive tone, andaton needs-you, failed and done rows, drawn as relative
times.digestgainssince,failed,nothingSinceandtotal. - DigestEmail writes the failed section;
digestEmail.failedis added. - ShipReview's
windowdoc no longer names a review level. - NavRail (KIT-369):
NavItemandTabBarDestinationare declared inapp-layout;app-sidebar,tab-barand
nav-railexport them by name, so every import still works. Installingnav-railno longer bringsapp-sidebar,
person-menuortab-bar. Nothing to do; a project that already has them keeps them.
Blocks (Premium)
- human-handoff (both versions): the inbox's "since your last visit" is a Digest titled "While you were away"
(humanHandoff.awayTitle).sinceLastVisitandvisitreturn{ since, needsYou, done }in place of
{ since, items }, so the inbox route'sdigestfield has that shape. No stored data changes.
New exports
DecisionCard,decisionCardStringsandDecisionAction(decision-review, Pro);DecisionBar,
decisionBarStringsanddecisionBarChangeGuardmove there.UsageMeter(usage-meters, Pro).DigestFailed(digest, Pro).ChangeTree,ChangeTreeFileandchangeTreeStringsmove tochange-diff(Pro).NavItemandTabBarDestinationare declared inapp-layoutand exported bynav-railtoo (Pro).- Removed:
ApprovalDecision,approvalDecisionStrings,DecisionReviewAction,DecisionBarAction,ReviewLadder,
reviewLadderStrings,ReviewLevel,ReviewCanvas,reviewCanvasStrings,UsageGlance,usageGlanceStrings,
UsageRing,usageRingStrings,AwayDigest,awayDigestStringsandDigestItem.
@candor-ui/react 6.1.0
The free items are unchanged but for these, and mcp-input's doc comments, which name DecisionCard.
- Model code is highlighted in its language (safe-markdown, payload):
markdownBlockskeeps a fence's language,
lower-cased, with common aliases mapped (pyis python,tsandtsxtypescript,jsandjsxjavascript,sh,
bashandzshshell,ymlyaml), for every language Payload highlights; one it doesn't is plain text with its
name as the title, as before. The caption names a recognised language once ("Python", not "Python · python"), and
keeps the fence's word for a dialect the label doesn't name ("TypeScript · tsx"). safe-markdown now installs with
highlight. - Payload names more languages (payload): its caption says "Go", "Rust", "Java", "Kotlin", "C", "C++", "C#" and
"JavaScript" where it upper-cased or capitalised the word ("GO", "CPP", "Csharp", "Javascript"), andshelland
zshread thepayload.shellstring ("Shell"), asbashandshdid. Nothing to do, unless a test or style
matches the old caption. - Tables in a model's text (chat, safe-markdown, message-content): a GFM pipe table becomes
{ kind: "table" }, a
header and rows of inline text cells with each column's alignment. MessageContent draws a<table>with column
headers in an area that scrolls sideways and takes focus, named by the newmessageContent.tablestring ("Table").
A table whose rows don't match its header stays a paragraph. It copies as a pipe table. Seemessage-block-kinds. - Quotes in a model's text (chat, safe-markdown, message-content):
>lines become{ kind: "quote" }, drawn as a
<blockquote>of paragraphs; one level, a deeper>is text. UndermarkdownBlocks(text, { breaks: true })a
quote keeps its line breaks, as a paragraph does (the block's optionalbreaks). It copies as>lines. See
message-block-kinds. - A switch over a block's kind needs a default (chat): MessageContent draws nothing for a kind it doesn't know, and
its copy leaves it out. - Streaming converts one message (use-candor-chat, claude-agent-sdk, ag-ui): while a reply streams, useCandorChat
converts only the messages that changed, and the Claude Agent SDK and AG-UI adapters read only the text that grew as
markdown. The output is the same. A Claude reply's citation markers pass over a table or a quote, as they pass over
code. Nothing to do.
Some DOM your CSS may match
- MessageContent: a model's pipe table was a
<p>of pipes; it is nowdiv[data-slot="message-table"][role="group"]
holding a<table>. Its>lines were a<p>without the>; they are nowblockquote[data-slot="message-quote"]
of<p>s. - Payload from a model's fence:
data-languageis the language's name (python,typescript,shell…) where it was
text, the label names it ("Python" where it said "Text"), the caption has no title beside a recognised language,
and the code is token spans. - UsageMeters: each card carries
data-slot="usage-meter",data-variant="bar", anddata-level,data-knownand
data-paused, as the glance and ring have them. The ring's box is@container aspect-square w-40 max-w-full(was
size-40), its centrepx-[18cqi](waspx-5), the figure's size an inlinefont-sizeincqi(wastext-3xl,
ortext-smwhen not known), and the ring's root gainsmin-w-0. - PortfolioCard's usage line gains
data-variant="glance". - ChangeDiff with
navigation="tree":data-slotchange-diff-body,change-diff-fileandchange-diff-tree.
Digest:digest-sinceanddigest-failed. - Payload: the caption's language name for
go,rust,java,kotlin,c,cpp,csharpandjavascriptis
the language's own ("Go", "C++", "C#", "JavaScript"…), andshellandzshread "Shell". - Digest: the failed section's heading carries an
svgicon andtext-destructive-textin place of
text-muted-foreground, and the since line ends "· 5 things" when there are rows. - PermissionMode with no
onValueChange: the modes other than the one in force carryaria-disabled="true",
data-lockedandaria-describedby, and a<p>under the list says "Can’t be changed here".
Docs and site
- App scaffolding: billing, team, admin, charts and layout are labelled "App scaffolding" (the screens every app
has, in Candor's theme, not agent surfaces) and listed after the agent groups in the docs,llms.txt, the skill and
the MCP. No item, tier or API changes. The site counts them on their own, not as agent components. - The home page leads with approvals and work surfaces, provenance in the type and the honesty rules; the item
counts are on the pricing cards.
CLI 4.0.0
- Run the CLI as
npx candor-ui@4. It works with Candor 5.4 and later; on an older projectupdate,addand
migratestop, change nothing and namenpx candor-ui@3 update --to 5.4.0(withmigrate 5.0.0from 4.x). CLI 3, 2
and 1 stay on npm. addandupdatekeep each installed file as Candor installed it in.candor/base/(<path>.base, beside
components.json;.candor/.ignorekeeps Tailwind out). Commit.candor/:updatemerges your changes against
these copies and needs only the release you update to from the registry. Don't edit them.candor-lock.jsonislockfileVersion: 2, recording each copy's hash. CLI 4 reads version 1 and rewrites it on the
firstaddorupdate. CLI 3 can't read version 2 ("candor-lock.json isn't a lockfile this version of candor-ui
reads."): from then on use@4.verifychecks your files and their base copies without the network;verify --remotealso checks the registry's
snapshots, as before.updatewithout--tostays before a minor with breaking changes, as before a major, and namesupdate --to <release> --dry-run.update --toprints the entries of items a release removes, installs the item that holds a
removed one's job (usage-glance 5.4.0 → 6.1.0: merged into usage-meters), keeps the old file as yours, and ends
naming the guide and eachmigrate <release>to run, oldest first.migrate 6.1.0runsitems,strings-keysandtokens. A stylesheet that sets
--cd-motion-approval-request-outcome(or-mark) gets a copy at--cd-motion-decision-review-card-outcome;
migrate 6.1.0makes only 6.1's token rows (migrate tokensby name makes 4.0's too).- A self-hosted registry serves
/r/v/<version>/breaking.jsonper release from 6.1, or a removed item's entry doesn't
print. updatealso writes the base copies of items already at the target that lack them. For a project an older CLI set
up,npx candor-ui@4 update --to <version> <items>, at the version they're at, writes their copies and moves
nothing;verifynames that command.migrate 6.1.0runs an entry's codemod where its old forms are in your source though the lockfile no longer records
the item (a removed item's kept file).- On a 6.1 project
theme checkreports a motion token 6.1 renamed as an error namingmigrate 6.1.0,
--cd-motion-review-ladder-rungas a warning, and--cd-motion-approval-request-outcomeset without
--cd-motion-decision-review-card-outcomeas a warning where the project hasdecision-review. The theme builder
reads an older file's names as 6.1 does. - "New strings to translate" no longer lists a table that moved into another item with its component.
updateprints 6.0's entries withnpx candor-ui@4 migrate ….
For maintainers
- The OrgSmith pack has left this repository (
packages/orgsmith, its test and its aliases); it lives in its own
private repository, which installs Candor as a buyer does. - Plans and reviews before 6.0 are in
internal/archive/, under the paths they had ininternal/. - The site, MCP and docs tests read the CLI's major from
packages/cli/package.jsonfor the install line they expect. npm run registryremoves an item's file frompublic/ronce registry.json no longer lists it, so a checkout that
built an earlier release doesn't serve a removed item.npm run test:browserrunstests/browser/usage-ring.mjs, the ring's figure checked in Chromium at 6, 8, 10 and
14rem, in both directions;--only usage-ringruns it alone.npm run release:checkis the quick run;npm run release:check -- --fulladds the browser, the shadcn
differential, the fresh apps and the upgrade steps, and is the run before RELEASING step 6.--quickstill works.- release:check runs independent steps side by side, prints each step's output whole with its time, and stops at the
first failure naming the step. npm run checkruns the source checks as one walker over one read of the sources;npm run check:<rule>runs one,
as before. A new rule,frozen-groups, fails a new file in billing, team, admin, charts or layout.npm run generateruns each generator once;npm run docsalone is unchanged.docs/RELEASING.mdis the steps a release needs; its history is ininternal/RELEASE-LOG.md.- CI's long jobs (on release pull requests, weekly and by hand) also run the snapshot store check, the pinned shadcn
differential, the Premium and monorepo fresh apps and the upgrade steps, with the store's token only where the store
is read.