Skip to content

Candor 6.1.0

Choose a tag to compare

@arunk3 arunk3 released this 14 Nov 21:40
· 3 commits to main since this release

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 (codemod items; approval-request, decision-review; Pro): ApprovalDecision is DecisionCard, in
    decision-review beside DecisionReview and DecisionBar, and approvalDecisionStrings is decisionCardStrings.
    Its props, its markup and data-slot="approval-decision" are unchanged, and it still takes a Decision.
    ApprovalRequest stays in approval-request. npx candor-ui@4 migrate items moves each import and renames its uses,
    <ApprovalDecision …> included.
  • decision-card-strings (codemod strings-keys; approval-request, decision-review; Pro): the approvalDecision
    strings are the decisionCard table, with the same keys and words. An override under approvalDecision isn't read.
    migrate strings-keys renames the table in a strings object written as a literal and lists one built at run time.
  • decision-bar-merged (codemod items; decision-bar, decision-review; Pro): the decision-bar item is gone.
    DecisionBar, decisionBarStrings and decisionBarChangeGuard are exported by decision-review, with the same props,
    strings and markup. DecisionBarAction and DecisionReviewAction are one type, DecisionAction. update --to 6.1.0 installs decision-review if you haven't got it, and keeps decision-bar's file as your own; migrate items
    points each import at decision-review and renames the action types. Delete decision-bar's file once nothing
    imports it.
  • review-ladder-removed (codemod items, which lists; review-ladder, permission-mode; Pro): ReviewLadder and
    ReviewLevel are removed. Draw your levels with PermissionMode: each level is one of your modes (its label,
    detail and locked), value is mode, onValueChange gets the mode's id, and label="Review level" names the
    control. PermissionMode's new label prop is the control's name in place of "Permission mode". migrate items
    lists each <ReviewLadder> and ReviewLevel import with this mapping. A ladder with no onValueChange becomes a
    PermissionMode with no onValueChange: the other modes say "Can’t be changed here", or pass locked with your
    reason. Delete review-ladder's file when you have moved.
  • review-ladder-strings (codemod strings-keys, which lists; review-ladder, permission-mode; Pro): the
    reviewLadder strings are gone. migrate strings-keys (and migrate 6.1.0) lists each override: the rungs' words
    are your modes' label and detail, and label is PermissionMode's label. Then delete them.
  • review-canvas-removed (codemod items, 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 items lists each <ReviewCanvas> and import. Delete review-canvas's file when you
    have moved.
  • review-canvas-strings (codemod strings-keys, which lists; review-canvas; Pro): the reviewCanvas strings are
    gone, and nothing reads them. migrate strings-keys lists each override; delete them.
  • usage-meter-variants (codemod items; usage-glance, usage-ring, usage-meters, portfolio-card; Pro):
    UsageGlance and UsageRing are UsageMeter's glance and ring variants, in usage-meters, with the props they took
    (period and href for a glance, estimateBasis for a ring, unknown and paused for every variant). They draw
    the same markup and data-slot values, with data-variant on the root. UsageMeters is unchanged. PortfolioCard
    draws its line with UsageMeter's glance, so it needs usage-meters in place of usage-glance. update --to 6.1.0
    installs usage-meters; migrate items writes <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 (codemod strings-keys; usage-glance, usage-ring, usage-meters; Pro): the usageGlance
    and usageRing tables are gone and their keys are in usageMeters. The glance's and ring's usedOfLimit is
    usedOfLimitWords, and the ring's estimateValue is estimateWithBasis; the bar's words don't change.
    migrate strings-keys moves 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 (codemod items; change-tree, change-diff; Pro): the change-tree item is gone.
    ChangeTree, ChangeTreeFile and changeTreeStrings are exported by change-diff, with the same props. migrate items moves 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 (codemod strings-keys; change-tree, change-diff; Pro): ChangeTree's chips read
    changeDiff.create, update and delete (the same words), and changeTree.create, update and delete are gone.
    migrate strings-keys moves an override of them to changeDiff where changeDiff doesn't set them, and lists it
    where it does.
  • away-digest-merged (codemod items, which lists; away-digest, digest, digest-email; Pro): AwayDigest and
    DigestItem are removed; Digest does the job. Draw a Digest with since, your heading as digest.title, the
    waiting items in needsYou, the failed ones in failed and the finished ones in done (a finished item's detail
    goes into its title, or is left out: DigestDone has none). onOpen(id) is unchanged. The since line reads "Since
    you were last here · 3 hours ago · 5 things", as AwayDigest's did. migrate items lists each <AwayDigest> and
    DigestItem with this mapping. Delete away-digest's file when you have moved.
  • away-digest-strings (codemod strings-keys; away-digest, digest; Pro): the awayDigest strings are gone.
    sinceLastHere is digest.since, failed is digest.failed and nothingHappened is digest.nothingSince, which
    migrate strings-keys moves. whileAway is your digest.title; the sections are headed by digest.needsYou
    ("Needs you") and digest.done ("What was done"); things is digest.total, which migrate strings-keys also
    moves, and group has no counterpart.
  • digest-open-rows (by hand; digest; Pro): Digest calls onOpen for a done or failed row without href too,
    not only a needs-you row, so with onOpen passed those rows are buttons. Give them an href, open them in onOpen
    by id, or leave onOpen out. DigestDone's by is optional, and a done row without it names no one: code that
    reads done.by needs a check, which the type check finds.
  • consolidation-motion (codemod tokens; usage-glance, usage-ring, approval-request, decision-review,
    review-ladder; Pro): --cd-motion-usage-glance-fill is --cd-motion-usage-meters-glance-fill and
    --cd-motion-usage-ring-fill is --cd-motion-usage-meters-ring-fill, each with its suffixes. DecisionCard's answer
    and its mark read --cd-motion-decision-review-card-outcome and -card-outcome-mark, where they read
    ApprovalRequest's outcome and outcome-mark, which ApprovalRequest keeps. --cd-motion-review-ladder-rung is
    gone. migrate tokens renames 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): MessageBlock gains table and
    quote, so a switch over a block's kind that ends in a never check fails the type check until it handles them
    or has a default. From 6.1 a minor may add a kind, and MessageBlock'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-run prints what 6.1 (and, from 5.4, 6.0) changes for the
    items in candor-lock.json, with the merges it would make, and writes nothing.
  • Update: npx candor-ui@4 update --to 6.1.0 updates 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.json as 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.0 runs 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.0 runs items, strings-keys and tokens for the entries on your
    installed items. Each lists what it couldn't change under "Left for you". --dry-run shows 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 --noEmit and your build, then your tests.
  • Verify: npx candor-ui@4 verify checks each installed file and its base copy against candor-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 when label is given. Its mode is the
    mode in force, as the app or the agent reports it. Without onValueChange it only shows the mode: the other modes
    are unavailable (aria-disabled, not disabled) and say "Can’t be changed here", the new
    permissionMode.readOnlyLocked. Pass locked for 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 takes unknown ("Not known yet", or "Not known yet, of {limit}", with no bar and never
    zero) and paused (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. usageMeters gains 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), and treeLabel, 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"), a failed section (DigestFailed) under a
    heading with a cross icon in the destructive tone, and at on needs-you, failed and done rows, drawn as relative
    times. digest gains since, failed, nothingSince and total.
  • DigestEmail writes the failed section; digestEmail.failed is added.
  • ShipReview's window doc no longer names a review level.
  • NavRail (KIT-369): NavItem and TabBarDestination are declared in app-layout; app-sidebar, tab-bar and
    nav-rail export them by name, so every import still works. Installing nav-rail no longer brings app-sidebar,
    person-menu or tab-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). sinceLastVisit and visit return { since, needsYou, done } in place of
    { since, items }, so the inbox route's digest field has that shape. No stored data changes.

New exports

  • DecisionCard, decisionCardStrings and DecisionAction (decision-review, Pro); DecisionBar,
    decisionBarStrings and decisionBarChangeGuard move there.
  • UsageMeter (usage-meters, Pro).
  • DigestFailed (digest, Pro).
  • ChangeTree, ChangeTreeFile and changeTreeStrings move to change-diff (Pro).
  • NavItem and TabBarDestination are declared in app-layout and exported by nav-rail too (Pro).
  • Removed: ApprovalDecision, approvalDecisionStrings, DecisionReviewAction, DecisionBarAction, ReviewLadder,
    reviewLadderStrings, ReviewLevel, ReviewCanvas, reviewCanvasStrings, UsageGlance, usageGlanceStrings,
    UsageRing, usageRingStrings, AwayDigest, awayDigestStrings and DigestItem.

@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): markdownBlocks keeps a fence's language,
    lower-cased, with common aliases mapped (py is python, ts and tsx typescript, js and jsx javascript, sh,
    bash and zsh shell, yml yaml), 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"), and shell and
    zsh read the payload.shell string ("Shell"), as bash and sh did. 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 new messageContent.table string ("Table").
    A table whose rows don't match its header stays a paragraph. It copies as a pipe table. See message-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. Under markdownBlocks(text, { breaks: true }) a
    quote keeps its line breaks, as a paragraph does (the block's optional breaks). 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 now div[data-slot="message-table"][role="group"]
    holding a <table>. Its > lines were a <p> without the >; they are now blockquote[data-slot="message-quote"]
    of <p>s.
  • Payload from a model's fence: data-language is 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", and data-level, data-known and
    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 centre px-[18cqi] (was px-5), the figure's size an inline font-size in cqi (was text-3xl,
    or text-sm when not known), and the ring's root gains min-w-0.
  • PortfolioCard's usage line gains data-variant="glance".
  • ChangeDiff with navigation="tree": data-slot change-diff-body, change-diff-file and change-diff-tree.
    Digest: digest-since and digest-failed.
  • Payload: the caption's language name for go, rust, java, kotlin, c, cpp, csharp and javascript is
    the language's own ("Go", "C++", "C#", "JavaScript"…), and shell and zsh read "Shell".
  • Digest: the failed section's heading carries an svg icon and text-destructive-text in 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 carry aria-disabled="true",
    data-locked and aria-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 project update, add and
    migrate stop, change nothing and name npx candor-ui@3 update --to 5.4.0 (with migrate 5.0.0 from 4.x). CLI 3, 2
    and 1 stay on npm.
  • add and update keep each installed file as Candor installed it in .candor/base/ (<path>.base, beside
    components.json; .candor/.ignore keeps Tailwind out). Commit .candor/: update merges your changes against
    these copies and needs only the release you update to from the registry. Don't edit them.
  • candor-lock.json is lockfileVersion: 2, recording each copy's hash. CLI 4 reads version 1 and rewrites it on the
    first add or update. 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.
  • verify checks your files and their base copies without the network; verify --remote also checks the registry's
    snapshots, as before.
  • update without --to stays before a minor with breaking changes, as before a major, and names update --to <release> --dry-run. update --to prints 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 each migrate <release> to run, oldest first.
  • migrate 6.1.0 runs items, strings-keys and tokens. A stylesheet that sets
    --cd-motion-approval-request-outcome (or -mark) gets a copy at --cd-motion-decision-review-card-outcome;
    migrate 6.1.0 makes only 6.1's token rows (migrate tokens by name makes 4.0's too).
  • A self-hosted registry serves /r/v/<version>/breaking.json per release from 6.1, or a removed item's entry doesn't
    print.
  • update also 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; verify names that command.
  • migrate 6.1.0 runs 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 check reports a motion token 6.1 renamed as an error naming migrate 6.1.0,
    --cd-motion-review-ladder-rung as a warning, and --cd-motion-approval-request-outcome set without
    --cd-motion-decision-review-card-outcome as a warning where the project has decision-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.
  • update prints 6.0's entries with npx 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 in internal/.
  • The site, MCP and docs tests read the CLI's major from packages/cli/package.json for the install line they expect.
  • npm run registry removes an item's file from public/r once registry.json no longer lists it, so a checkout that
    built an earlier release doesn't serve a removed item.
  • npm run test:browser runs tests/browser/usage-ring.mjs, the ring's figure checked in Chromium at 6, 8, 10 and
    14rem, in both directions; --only usage-ring runs it alone.
  • npm run release:check is the quick run; npm run release:check -- --full adds the browser, the shadcn
    differential, the fresh apps and the upgrade steps, and is the run before RELEASING step 6. --quick still 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 check runs 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 generate runs each generator once; npm run docs alone is unchanged.
  • docs/RELEASING.md is the steps a release needs; its history is in internal/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.