CLI release notes: formats
Every Candle CLI release note carries a Formats line. It says whether the release changes anything the CLI keeps on disk (vault.enc, tee-wallets.enc, the files beside the vault, config.json, and the names it stores secrets under) and whether an older CLI still reads what this one writes. Check it before you run two CLI versions against one vault, restore a backup on an older machine, or pin a bot to an older release.
The full notes for each release are on its GitHub release (releases through 0.12.0 are in candledottv/agentic). This page keeps the Formats lines together, newest first.
An Unreleased entry can also carry a Waits marker, for a release that needs API routes production does not serve yet: Waits: promote <sha>, with the full commit that adds those routes, or Waits: <YYYY-MM-DDTHH:MMZ>. Write it in the version’s entry (- 0.13.31: ... Waits: promote <sha>. **Formats:** none) or in packages/cli/release-gates.json as { "0.13.31": "Waits: promote <sha>" }; the same file next to packages/sdk and packages/mcp gates those packages. Until that commit is in production (an ancestor of alpha) or that time has passed, the npm publish skips with skipped (waits: promote <sha>) and asks for no approval. It runs on the first staging push after the promote that touches packages/sdk, packages/mcp or packages/cli, for example the change that deletes the met gate. A release with no marker, or a met one, publishes as before.
Unreleased
Section titled “Unreleased”- 0.13.46:
candle tee rebindstops and reports when an approved owner confirm is refused, instead of sending a request that asks for a second approval (BE-4315). Against an API before BE-4315, which uses the approval and then asks for the wallets’ owner signatures, it stops withREBIND_CONFIRM_SPENTand says not to run it again until the API carries the fix (each run would spend another approval). Against a current API the signatures are asked for before the approval, so one approval finishes the rebind; if a wallet’s owner changes while the approval is pending, it stops withREBIND_OWNERS_CHANGED(the approval was not used) and a re-run covers the current owners. Nothing changes in either stop. This version also carries 0.13.39 to 0.13.45. Waits: 2026-11-24T09:00Z. Formats: none. No change to anything the CLI keeps on disk. - 0.13.45:
candle agent positionslabels a Hyperliquid spot holdingHyperliquid spot(symbol, amount and value; no P&L, the route serves none for it) and--jsonpasses itsvenue: "hyperliquid"through;candle agent recordprints aSpot P&L includes Hyperliquid spotline (realized, unrealized, fees, volume, trades, and the unpriced, sold-beyond-tracked and partial notes) when the record carrieshyperliquidSpot, BE-4222. An answer without them prints exactly as before. This version also carries 0.13.39 to 0.13.44. Waits: 2026-11-24T09:00Z. Formats: none. No change to anything the CLI keeps on disk. - 0.13.44: the bundled
candle mcpserver (MCP 0.10.43) offers the four Hyperliquid spot tools,candle_perps_spot_markets,candle_perps_spot_balances,candle_perps_spot_orderandcandle_perps_spot_cancel(BE-4217). The order and cancel are checked against the machine’s own read of Hyperliquid’s spot metadata before anything is signed, and use the key’s EVM TEE wallet only.--read-onlyleaves them out; the core classifies the order and cancel as perps cards and the two reads as reads. This version also carries 0.13.39 to 0.13.43. Waits: 2026-11-24T09:00Z. Formats: none. No change to anything the CLI keeps on disk. - 0.13.43: help text and README only:
TEE_LAUNCH_BUYS_ENABLEDis on by default and a server turns TEE launch buys off withTEE_LAUNCH_BUYS_ENABLED=0, BE-3982. No code change. This version also carries the 0.13.42 perps spot--hide, the 0.13.41telegram:notifychange, the 0.13.40 quote launch and the 0.13.39 perps summary. Waits: 2026-11-23T09:00Z. Formats: none. - 0.13.42:
candle perps spot buyandsellaccept--hide(BE-4215). It keeps the order’s fills out of the public activity stream, as--hidedoes on perps. The CLI refuses to sign a hidden spot build without ahide: trueecho (HIDE_NOT_CONFIRMED, exit 1). Needs an API with spothide(BE-4215). This version also carries 0.13.39 to 0.13.41. Waits: 2026-11-24T09:00Z. Formats: none. No change to anything the CLI keeps on disk. - 0.13.41:
telegram:notifyis held by every key (BE-4185): the API grants it at check time whatever a key was minted with, socandle keys listreads a key that stored it beside a preset as that preset (Write, not custom), and the README no longer calls the scope named-only.--scopes telegram:notifyis still accepted and changes nothing. This version also carries 0.13.39 and 0.13.40. Waits: 2026-11-23T09:00Z. Formats: none. No change to anything the CLI keeps on disk. - 0.13.40:
candle launch --quote <mint>launches against a Solana token that is not a listed pair (BE-3633): the mint is sent as the quote asset, case intact, and the server admits and sizes the curve from its own reads (--checkshows the same answer) and refuses by name. No--buyon a new-quote launch yet: the CLI refuses it before any request; buy the token withcandle swapafter it lands. A Hood quote and a symbol that is not a listed pair still refuse (QUOTE_LAUNCH_UNAVAILABLE). Needs an API with the new-quote launch. Formats: none. No change to anything the CLI keeps on disk. - 0.13.39:
candle agent <profile-id|slug> --perps [--window all|24h|7d|30d]prints a published agent’s Hyperliquid perps summary for the window, the figures its agent page shows: P&L and its parts, volume (builder-dex fills included), fees to volume, rounds closed, win rate, largest win and loss, highest and average leverage (rounds with leverage not recorded left out), liquidations and max drawdown, each with its formula (BE-3775). No key is read or sent;--jsonprints the route body. Needs an API with the perps summary read. Waits: 2026-11-23T09:00Z. Formats: none. No change to anything the CLI keeps on disk. - 0.13.38: README only: the npm page now describes
candle perps market <coin> --agents, BE-4059. No code change. This version also carries the perps--hidesupport from 0.13.36. Waits: promote ba1be9ffa03a841c058bf72d6b9ffd270b0552be. Formats: none. - 0.13.37: the CLI release is built with Bun 1.4.0 (it was 1.3.14), the first Bun with the Postgres auto-pipelining fix (oven-sh/bun#33627), BE-4095. Under Node, the width estimate now counts a decomposed voiced kana mark (U+3099, U+309A) as zero columns, so a table lines up the way Bun 1.4 measures it. Formats: none. No change to
vault.enc,tee-wallets.enc,config.jsonor the secret store. - 0.13.36:
candle perps open,close,modifyandtpslaccept--hide(BE-3996, #4033). It keeps the order’s fills out of the public activity stream. For TP/SL it applies to newly attached protection. The CLI refuses to sign a hidden order build without ahide: trueecho (HIDE_NOT_CONFIRMED, exit 1). Needs an API with perpshide(#3935). Waits: promote ba1be9ffa03a841c058bf72d6b9ffd270b0552be. Formats: none. - 0.13.35:
candle agent record <profile-id> [--cursor <cursor>] [--json]reads a published agent’s public measured record: spot swaps and certified closed Hyperliquid rounds together, newest first, with entry and exit, largest size, recorded leverage, fees, funding, net P&L and ROE (BE-3754, #3921).--cursorpages older rows. No key is read or sent, and a field that was not recorded is shown as unknown, never zero. Ships with SDK 0.6.29 (getAgentRecord) and MCP 0.10.40 (candle_get_agent_record). Formats: no change to anything the CLI keeps on disk. - 0.13.34:
candle token exit <token>reads where a holder of a Candle Hood launch stands if it does not migrate, and--recover [--amount],--enter-recoveryand--claim-teamrun the exit through Candle with the embedded Hood wallet, after the API’s dry run (--dry-runstops there; exit 5 on a decline, 1 partial, 3 indeterminate), BE-3794.candle portfoliomarks Hood positions in Recovery, pending rescue or rescued. Formats: no change to anything the CLI keeps on disk. - 0.13.33:
candle perps risk|account|positions|watchread a wallet Hyperliquid reports as a unified account through the unified path while the server’s unified-accounts switch is on (BE-3860, #4006): balances and holds from unified spot clearing, positions from every perp dex, and Hyperliquid’s unified account ratio as the margin ratio (Unified ratio and dexes rows).candle perps setupadmits a unified account only while the switch is on. A wallet that is not unified, a switch that is off, or an older API answers exactly as before. Needs an API with the unified-accounts switch on. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store. - 0.13.33 (also):
candle perps market <coin> --agentsreads one Hyperliquid perp market,dex:COINincluded, with its public figures, the last 24 hours of funding, and Candle’s public agents in it (BE-3777).candle launch --quote <symbol|address> --checkchecks a featured symbol or token address before an image exists, printing admission checks and named refusals; existing fixed pairs keep their figures and--quote-assetremains supported (BE-3633, #4000). Formats: none. No change to anything the CLI keeps on disk. - 0.13.32:
candle perps activity [--wallet <tee>]lists the wallet’s resting Hyperliquid orders across the default perp dex and every builder-deployed dex (each row names its dex) plus withdrawals still in flight (account:read, reads only), andcandle perps thresholds --key <prefix|label>shows a key’s stored risk thresholds and perps limits with the device token, BE-3758 (#3925). Formats: none. - 0.13.31:
candle perps transfer --to-dex <dex> <amount>,--from-dex <dex> <amount>|--allandcandle perps transfer status <id>move USDC between the key’s own Hyperliquid main perps and a builder dex (perps:write, destination fixed to the wallet itself, checked before signing), BE-3765 (#3928).--to-spotand--from-spotare refused.candle perps withdrawnow sweeps releasable builder-dex USDC before withdrawing. Needs an API with the transfer routes. Formats: none - 0.13.30 (also):
candle perps spot markets|balances|buy|sell|canceltrades Hyperliquid spot from the key’s EVM TEE wallet, BE-3771 (#3936). Formats: no change to anything the CLI keeps on disk. - 0.13.30:
candle perpsaccepts builder-deployed (HIP-3) Hyperliquid markets nameddex:COIN(xyz:TSLA), BE-3755 (#3924). The name is checked locally (dex of 1-12 letters and digits, a colon, a coin of 1-20) before any request;candle perps markets --dex <dex>lists a builder dex, and previews show the market’s terms (dex, oracle, deployer, margin mode, collateral, fee multiple, a warning above 2x). Main-exchange names are unchanged. Needs an API with builder-dex support. This release also carries the BE-3756candle agent roundandcandle agent positions --orders. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store. - 0.13.29:
candle swap --hidekeeps one token buy or sell out of the public activity stream (BE-3673). The flag is sent only when set, on the build or one-shot request, and the CLI refuses to sign or execute unless the API echoeshide: true: an API that predates the flag or has it off, or that ignores it, ends inHIDE_NOT_CONFIRMEDand exit 1, never a public order reported as hidden. A base-asset swap, a bridge and--dry-runrefuse--hide. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store. - 0.13.29:
candle keys create --scopes telegram:notifyis accepted: the CLI’s scope list now carriestelegram:notify(BE-3720), so a key can be minted for the API’s client Telegram notifications. It is named-only: no default,--accesspreset or omitted--scopesever includes it. Formats: none. No change to anything the CLI keeps on disk. - 0.13.28:
candle launch --hidekeeps the launch and its dev buy out of the public activity stream; the body carrieshide: trueonly when the flag is set, and a dry run, build or embedded pre-check without the API’shide: trueecho is refused (HIDE_NOT_CONFIRMED) before anything is signed. The creator wallet stays public on chain. Formats: none. - 0.13.28: the rent-floor refusals on
candle vault transferandcandle vault fund(TRANSFER_INSUFFICIENT_FUNDS) and the payerInsufficientFundsForRentpreflight refusal (TRANSFER_REJECTED) suggested a--maxflag that does not exist;vault transfernow says--amount max, andvault fund, which takes no max, no longer offers to empty the key (BE-3680). Suggestion text only; codes, exits anddetailsare unchanged. Formats: none. No change to anything the CLI keeps on disk. - 0.13.27:
candle launch --image <path> --dry-run(and--banner <file>) checks the file and uploads nothing (BE-2668, R21). The API checks it throughPOST /uploads/agent-image?dryRun=true, which hosts nothing, and the launch dry run is sent withimageChecked/bannerCheckedin place of a URL; the result reportsimageCheckedand noimageUrl. A real launch still uploads before its confirm. Formats: none. No change to anything the CLI keeps on disk. - 0.13.27:
candle launch statusprintsquoteAssetfromquoteMint, plusquote paused,quote splitand a blocked-launch line from the newquoteStateonGET /launch/status/:id(BE-3631);candle fees claimshows a Hood claim’sOutcomeand thegas_estimate_unavailablereason, and refuses to sign a non-Solana claim.candle vault transferandvault fundon Solana refuse a send that would leave the payer with more than zero but less than the rent floor (TRANSFER_INSUFFICIENT_FUNDS; for a SOL send, names the largest amount that leaves the floor after the fee if that amount is greater than zero; otherwise, or for a token send, asks you to fund the key with SOL first), and a send the RPC refuses at preflight isTRANSFER_REJECTED(exit 1, nothing broadcast) instead ofSubmitted. Formats: none. No change to anything the CLI keeps on disk. - 0.13.26:
candle transfersends from the embedded wallet through the existingPOST /agent/transferon Solana and Hood, the rail MCPcandle_transferuses (it used to refuse the embedded wallet):--tois a plain address, the key needstransfer:write, and Candle signs.--client-id(or an id the CLI picks and prints) goes out asclientTransferId: a repeat of a sent transfer replays its answer, a repeat that may have landed is refused, andcandle transfer status <id>reads it. ATRANSFER_FAILEDexits 3 and names the id. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store. candle swapon a Hood TEE payer previews before it builds (BE-3369, on the BE-3367 and BE-3368 server routes): a run that stops at the quote (no--yes, a decline, too little gas, a held wallet) holds nothing, and a quote that moved before the confirmed build isQUOTE_MOVEDwith nothing held. Newcandle swap cancel --operation <id>releases a Hood TEE trade, swap or Hood-origin bridge operation this key opened and never signed a leg of (exit 0), refuses with exit 3 when a leg may have been signed, and exits 1 on any other refusal. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.candle swap --dry-runcovers Hood TEE swaps and all eight SOL/USDC and ETH/USDG bridge pairs (BE-3363): read-only previews of fee, legs, gas, route and destination, with no build and no lock. It now also refuses--wait. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.candle tee checkchecks each TEE wallet on its own chain, so a healthy Hood wallet passesactiveinstead of failingCHAIN_MISMATCHagainst a Solana operation (BE-3359). New--chain solana|hoodchecks every wallet against one chain.--signskips a Hood wallet (because: "hood") and builds nothing;tee checktakes no Hood wallet lock. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.candle swap ... --waiton a Hood TEE swap follows the trade and fee legs for up to ten minutes and prints the same response ascandle swap status --operation <id>, which now takes--waittoo: exit 0 completed, 1 failed, 3 partial, unresolved or timed out (BE-3360). Where--waitdoes not apply (an embedded wallet, a Solana same-chain swap) theUSAGEmessage namescandle swap status --operation <id>andcandle swap status <client-trade-id>. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.candle doctorreportsDevice token beside signeras information, not a warning: the row is a pass (ok), its note under the list is a note, and it no longer counts in the warnings tally. The detail still says what holding both allows and what to do on an owner or a trading machine.tee signer newstill warns. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.- 0.13.25:
candle wallet close-emptyon the embedded wallet needsswap:writeortransfer:write(it neededtransfer:write), so aswap:writekey can recover rent. Against the current API, re-runningcandle wallet close-empty --client-trade-id <id>to read arecoveringjob now fails with 503LAUNCH_DISABLEDwhileAGENT_TRADING_ENABLEDis off, with 403 for a test key or a keydeniedthe embedded wallet, or withJOB_NOT_FOUNDfor a different key than the one that started the run. No new flag. Formats: none. - 0.13.20: an uncertain Hood leg is reported as
LEG_UNCONFIRMED(exit 3) with the leg’s exact hash, “do not repeat this trade” and the--kind tradestatus command; a revert says so (BE-3072).No leg landed.is nowNo leg is confirmed yet.andLanded:isConfirmed:. JSON keeps the server’s recovery evidence. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store. - 0.13.19:
candle tee check <wallet>... [--label-prefix <p>] [--sign]andcandle swap --dry-run(BE-2934).tee checkreports per-check results for each TEE wallet (payable membership, record parity with the swap’s listing, this machine’s signer) without spending;--signalso builds, spend-checks, relay-signs and simulates a tiny quote, never broadcasting.swap --dry-runstops after the quote and spend check on a Solana TEE payer and never signs, sends, prompts or saves an operation. Formats: no change tovault.enc,tee-wallets.enc,config.jsonor the secret store. candle transfer --client-id <id>andcandle transfer status <id>(BE-2673): a client id names a linked-origin transfer, so a retry of one already built or sent is refused withIDEMPOTENCY_CONFLICTnaming it instead of sending twice, and the status read returnsbuilt,expired,submittedwith its signature,unconfirmed(may still land; check the chain orcandle activitybefore using a new client id), orfailedby the transfer id or the client id (kept 24 hours by the API). New API routeGET /api/v1/agent/transfer/:id;POST /transfer/buildtakes an optionalclientTransferId. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.candle vault fundandcandle vault transferrefuse a retired TEE wallet (demoted and swept) as the destination withTEE_WALLET_STOPPED, before any request or signature (BE-2678). A retired address is never refunded.- 0.13.18: a Solana TEE launch with launch rules and a first buy (
candle launch --wallet <tee> --buy <amount>with--open-in,--max-buy-per-wallet,--allowlistor--dev-buy-max) signs again (BE-2899). 0.13.17 refused it before signing with “leg 1 is not one curve swap”, because the API puts the creator’sregister_buyer(no proof) ahead of the curve swap in the first-buy leg. The pre-sign check now reads that one instruction on a launch with rules only: this wallet as the buyer, the same pool as the swap, and its 82-byte tally’s rent counted in “Most this wallet can lose”. Aregister_buyeron a launch without rules, one with a proof, a second swap or any other instruction is still refused, and nothing is signed. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store. candle wallets allowlist [--all]prints the account’s withdrawal allowlist (BE-2672): each approved address’s id, chain, address and label, the same rowscandle transfer --to <allowlist label>resolves by. Any key reads it;--alladds removed rows. Approving an address stays with the owner, in the agent console’s Wallets tab; an acting key can revoke one, a read-only key cannot. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.candle keys create --no-storecreates and prints a key without saving it as the profile’s working key, even when the profile has none (BE-2700). The profile’s existing key, prefix and scopes are left untouched.--jsonreturns the one-time key withstored: false; skipping storage intentionally exits 0. The default still stores only when no working key exists. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.candle wallet close-empty --previewprints what would close and closes nothing (BE-2694, R59): under--jsonthe whole preview (accounts, totals, fee, skipped rows) is one JSON document on stdout withstatus: "preview"; without--jsonthe same lines a prompt would show, then the JSON result. No prompt, nothing signed, and a named--client-trade-idis not looked up. Run headless without--yesor--preview, theCONFIRMATION_REQUIREDrefusal (exit 1) now carries that same preview underdetails, so a script learns what would close instead of a bare code. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.candle launchtakes launch rules on Solana (BE-2794), where the API hasCURVE_LAUNCH_RULES_ENABLEDon:--open-in <duration>,--max-buy-per-wallet <amount>with--cap-window <duration>,--allowlist <path>with--allowlist-window <duration>, and--dev-buy-max <amount>. Durations are seconds or90m,6h,2d; amounts are whole quote units, sent as the request’s nestedlaunchRulesin raw units. Each value is checked before any request with the API’s bounds and words (the open at most 7 days away, each window at most 24 hours, the list 1 to 4,096 wallets), and--dry-runprints a Launch rules block from the API’s answer. A server with the switch off answersLAUNCH_RULES_DISABLED. The bundled MCP’scandle_launch_tokenandcandle_launch_and_seedtake the samelaunchRulesobject in seconds and raw units. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store.- 0.13.13: TEE launch by key scope (BE-2724, BE-2752): where the API has
TEE_LAUNCH_BY_SCOPE_ENABLEDon, a key’slaunch:writeis enough to launch from the TEE wallets bound to it, and the owner’sallowLaunchis no longer enforced.candle wallets allow-launchanddisallow-launchare deprecated. When the preview saysenforced: falsethey print one stderr line, “this server does not enforce allowLaunch”, and go on:allow-launchsaves the value and exits 0;disallow-launchsaves it, prints the server’sALLOW_LAUNCH_NOT_ENFORCEDmessage and exits 1, since no launch was stopped (pause the key withcandle keys stop, move it to Read, or rebind the wallet).candle tee rebindnow warns for every moved wallet when the target key lackslaunch:write, instead of only for wallets withallowLaunch.candle launch --checkreportsteeLaunchByScope. A TEE launch with a first buy also needsswap:writethere; without it the API answersSCOPE_MISSING. A CLI that predates this release keeps working against such a server, because the API servesallowLaunch: trueon TEE rows. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store. candle accounts createis retired (BE-2746). The command and the server routes behind it are gone: its server switch was never set, so production never served it, and staging answeredACCOUNTS_ROUTES_OFF. The test fleet is minted by the reviewed owner script (BE-2627). Formats: no change tovault.enc,tee-wallets.encor the secret store. A profile an older CLI wrote withapiKeyItemis still read, and still refused for ordinary authentication withACCOUNTS_FLEET_RUNNER_REQUIRED.
0.13.23
Section titled “0.13.23”- The macOS release ships the signed
candle-enclave.apphelper for Touch ID on Apple silicon Macs and Intel Macs with a T2 chip. The helper deliberately omits the associated-domain entitlement: synced passkeys remain unavailable, andvault factor add passkeyrefuses withVAULT_FACTOR_UNSUPPORTED_ON_PLATFORMexplaining that omission. No new commands or flags. The npm package ships no native helper; use the macOS release, or install the matching signed bundle and setCANDLE_ENCLAVE_HELPER. See Factors.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.13.22
Section titled “0.13.22”- Enabled the signed macOS helper release policy after Apple’s developer enrolment approval. This version reached npm, but its native helper release failed; use 0.13.23 for Touch ID.
CANDLE_API_KEY_FILEforcandleandcandle mcp(BE-3165): an absolute path to an external API-key file, used instead ofCANDLE_API_KEYorCANDLE_AGENT_API_KEY. A nonblank file path with either nonblank raw key refuses withAPI_KEY_SOURCE_CONFLICT. The file must be a regular file owned by the effective user, mode 0400 or 0600, with no final symlink, at most 4096 bytes and one printable ASCII token with an optional final newline. Unsupported platforms, unreadable files and invalid files refuse withAPI_KEY_FILE_UNSUPPORTED,API_KEY_FILE_UNREADABLEandAPI_KEY_FILE_INVALID; there is no fallback. The key is read once at startup, so restartcandle mcpafter rotating the file. Formats: none. No change tovault.enc,tee-wallets.enc,config.jsonor the secret store; the file is never imported into a profile or credential store.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.13.21
Section titled “0.13.21”candle swap receipt <hash>or--client-swap-id <id>re-reads a one-shot swap’s settlement without resending. The JSON answer preserves receipt state and recovery guidance; a human line marks a Relay refund, fallback refund or failure. Poll no faster than every 15 seconds. See the CLI reference.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.13.14
Section titled “0.13.14”- The first credential or signer write on a fresh box (
candle tee signer new,candle auth login,candle keys createand the rest) creates the config directory at mode 0700 instead of failing withUnexpected error: ENOENT ... credentials.enc.lock. An existing directory is left as it is. A directory the CLI cannot create or write isCONFIG_DIR_UNWRITABLE(exit 1), with the path and errno indetailsunder--jsonand aFix:line (BE-2712). candle doctor’sConfig directoryrow checks the directory itself: PASS when it exists and can be written, WARN when it does not exist yet but can be created (the first write creates it), FAIL with the errno and aFix:line when it cannot be created or written. Doctor never creates it (BE-2712).
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.13.11
Section titled “0.13.11”candle feessays who can claim: a claimable Solana row reads “claimable by this key” (reason: claimable_by_key), andclaimable_via_web_sessionexplains that the fees go to the account’s web wallet, which a signed-in session claims (BE-2598).candle launchnames the launching wallet as the default fee wallet where the API hasLAUNCH_FEE_WALLET_FROM_LAUNCHERon (the server switch ships off): a Solana launch without--fee-walletearns to the wallet that launches it (the TEE, linked or embedded wallet), and the preview, the confirm quote and--checksay “the launching wallet”. Against a server without it they keep the account-wallet words. The stderr warning for a defaulted fee wallet names both possibilities, since it prints before any request (BE-2599).- New MCP tool
candle_atomic_launch_dry_run(read-only), reachable throughcandle mcp(BE-1851). Bundled MCP 0.10.29.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.13.10
Section titled “0.13.10”candle vault demotetakes several addresses, or--all --empty(every Solana TEE wallet with nothing left to sweep), under one unlock and one typedconfirm(--yesskips it); a failure does not stop the rest, and--jsonwrites one document withwallets[]andsummary(BE-2597).candle launch status <id> [--wait]reads a launch’s status, and with--waitfollows it to the end (BE-2573).candle launchon Solana warns on stderr when no--fee-walletis given and the launch’s curve and pool fees default to the account wallet; dry runs and--checkkeep their ordinary info line. The opt-in--require-fee-walletrefuses the launch (exit 2, before any request) when no--fee-walletis given (BE-2572).candle tee signer newtakes--no-wait(exit 0 once the request is pending) and, with--json, emits newline-delimited events:pendingwith the approval code and URL at once, then the result. A retry re-attaches to the same live request. Newcandle tee signer status --key <prefix|label>reads the signer state once without requesting anything (BE-2570).candle swap --jsonand the trade results share one result shape (W2) (BE-2569).candle transferfrom a TEE wallet can send to an address on the account’s withdrawal allowlist, by label, id or address, where the server hasTEE_WITHDRAWALS_ENABLEDon (the switch ships off) (BE-2601, BE-2600).candle vault transferSOLmaxsends the balance minus the exact fee and leaves no fee dust (BE-2596).
Formats: a key signer entry in config.json can carry pendingRequest (the API it was made on, the approval code, the verification URLs and the expiry: public approval facts, never a key) while a signer request is pending, so a later signer status or retry can resume it. An older CLI ignores the field. No change to vault.enc, tee-wallets.enc or the secret store.
Unreleased (not a release)
Section titled “Unreleased (not a release)”-
candle vault promote --from <cold label>now asks you to confirm promoting a new TEE wallet with the named pinned vault, on both Solana and Hood. The prompt no longer says it will sweep funds; promotion moves no funds (BE-2679). -
candle tuilaunches Candle Harness: it looks forcandle-harnesson PATH first, thencandle-tuifor older installs. If neither is installed, it links to Candle Harness releases. Help now uses the Candle Harness name (BE-2853). -
New
candle wallets authorizegives agents access to the account’s embedded wallets without creating a key. The grant needs your browser, so it opens the Agents page’s grant step (/agents?authorize=1); with an API key on the profile it waits until every embedded wallet is delegated (--timeout, 600 seconds by default;--no-waitstops after opening), and an account already delegated is told so with no page opened.candle doctor,candle walletsandcandle launch --checkname it when a wallet is not delegated (BE-2698). -
Retired TEE wallets (demoted, then swept) no longer clutter the lists.
vault listhides them unless--all, says how many it hid, and gains a LIFECYCLE column;--jsonaddshiddenRetired, and hidden wallets are not read for--balances.vault rename(single and--pairs-from) now renames a retired TEE wallet’s vault entry, which neither it nortee renamecould do before.wallets --allincludes disabled linked wallets, which stay hidden by default. -
candle token edit <mint>sets Candle’s copy of a token’s description and its four links as the token’s creator, with the launch flags--description,--website,--x,--telegramand--discord;--clear <field>removes one, and fields not named keep their value. Name, symbol and image cannot be changed, and nothing is written on chain. It needs alaunch:writekey from the account that launched the token, runs the account guard, and sends an Idempotency-Key (exit 3 when the outcome is unknown).candle token history <mint>lists the token’s edits, newest first, and sends no key; with a section it stays the About section history. A deployment accepts edits only onceTOKEN_METADATA_EDIT_ENABLEDis on; until theneditanswersMETADATA_EDIT_DISABLED. -
candle scan <contract address>prints the token card for one contract, as a Quant group gets it: market, the all-time high since launch, bundles, snipers, insiders, fresh wallets, wallet age, tracked wallets in the last hour, the same-name leader, forensics coverage and the Candle page, each figure with its source and a dash where there is none. The chain is read from the address unless--chainnames it. No key needed and none sent. Reads the public card route, which a deployment serves only onceTOKEN_CARD_ENABLEDis on; until then the command answersTOKEN_CARD_DISABLED. -
candle token events <mint>lists one token’s signals, callouts and tracked-wallet trades, one event per line: time, kind, name or short address (with the wallet’s kind), action and size, sells withWorLwhen known.--kind,--since,--limitfilter (--kindlocally, the page keeps its cursor),--beforecontinues a page. No key needed; a configured key is sent so group names follow its tier. Reads the public events route, which a deployment serves only onceTOKEN_EVENTS_ENABLEDis on; until then the command answersTOKEN_EVENTS_DISABLED. -
A new profile created by
auth loginneeds--api-url(orCANDLE_API_URL, or a prompt at a terminal). It no longer inherits another profile’s host, a leftoverconfig.jsonapiUrl, or the production default. The host is printed before the device code. -
auth loginends with the minted key’s embedded wallet denied unless--embedded-wallet allowis confirmed at a terminal, matchingkeys create. The approval page still starts its switch on, so the key can exist allowed for the moments between approval and the correction (the CLI cannot ask the page for deny). If the denial cannot be confirmed,auth loginrevokes the key, stores nothing and exits 1; if that revoke also fails it names the key to deny or revoke. -
New
candle token about|claim|section set|section restore|history|flagread and edit a token’s About page. Writes need a key grantedtoken-pages:writethroughkeys create --scopesand the account’s own 0.5% of supply; the creator proof is a message signed on your own machine. The server switches ship off. -
New
candle accounts create --env staging --name <fleet-name>creates a staging test member for the funded test fleet with no browser, from the identity key in the login keychain itemcandle-fleet-<env>-<name>-soland a key signer the owner sealed beforehand. macOS only, at a terminal, under the fleet runner lock. The API key is stored by the owner’s hash-pinned reviewed sibling incandle-fleet-<env>-<name>-apikey, never by the CLI. Production is refused. Retired in the next release (BE-2746).
Formats: a profile written by accounts create carries apiKeyItem, the name of the keychain item holding its API key (never the key). It is a public fleet record, not an ordinary authenticated CLI profile: ACCOUNTS_FLEET_RUNNER_REQUIRED refuses credential resolution (including doctor), even with an exported credential. Account-create section 6 and fleet R9.3 confine reads to the reviewed runner; general profile use needs a separate custody decision, so the section 5 example’s doctor suggestion is not supported. --use selects the record only. JSON success names credentialAccess: "fleet-runner-only". An older CLI ignores the field. No change to vault.enc, tee-wallets.enc or the secret store.
0.12.0
Section titled “0.12.0”- The final CLI release published from
candledottv/agentic. Later releases are published and signed incandledottv/cli, and from this version oncandle updateandcandle doctorlook for them there. Until the first release there exists,candle updatesays so, exits 0 and leaves this version installed; it never falls back tocandledottv/agentic. Releases through 0.12.0 stay where they are, andcandle update --to cli-v<version>still finds each one in the repository it came from. Homebrew and npm keep updating throughbrew upgrade candleandnpm i -g @candledottv/cli@latest. - No other change from 0.11.41.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.41
Section titled “0.11.41”- Preparation for moving CLI releases to their own repository. Releases through 0.12.0 are published and signed in
candledottv/agentic, as every release so far has been; later releases will be published and signed incandledottv/cli. This release knows both, and checks every release against the one repository its version comes from. Nothing moves yet:candle update,candle doctorand the installer still readcandledottv/agentic. candle update --toand the installer’s--totake only a release tag such ascli-v0.11.39, because the version in the tag decides where that release is looked up and whose signature it must carry. Anything else exits 2 (the installer exits 1) before a download.candle updaterefuses a release manifest that names a version released from the other repository, or a pinned manifest that describes a different tag than the one asked for, withMANIFEST_INVALIDand nothing downloaded.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.39
Section titled “0.11.39”- No change to the CLI’s behaviour: 0.11.38 as published on npm, released again so the GitHub release and the Homebrew tap carry it. The 0.11.38 release build in
candledottv/agenticfailed on a test that needs the unpublished TUI package; that test now skips where the TUI is absent.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.38
Section titled “0.11.38”candle launchtakes the same launch inputs as the HTTP API.--modenames the experimental Solana curvesexp-a,exp-b,exp-candexp-custom;exp-customtakes--curve-v <V> --curve-g <G>, and--creator-fee-bps 100|200adds an extra creator fee on anexp-mode. The local dev-buy check applies theexp-rule (at most 0.5 SOL or 2,000,000 CNDL, or 10% of the threshold when that is lower).- Pool choices at graduation, Solana only:
--pool-fee 25|50|100, an anti-snipe fall with--pool-fee-from <bps> --pool-fee-minutes <min>(at most 2500 bps over at most 30 minutes),--pool-open legacy|curve_priceon preset tiers and--exp-pool-shape floor|full_rangeonexp-curves. Bad combinations exit 2 before any request, and a Hood launch refuses them. Omitted, nothing is sent and the pool is today’s. candle launch --dry-runsends the launch’s body to Candle’s dry run (the atomic dry run with--buyon Solana) and prints the preview: the curve’s terms, the first buy’s share, the fees, how the pool opens at graduation and the dev-buy ceiling. It claims, builds, signs and records nothing. With--imageit still uploads the file, which is public and permanent.- Compact help that fits the terminal’s width, and global
--plainand--no-color(alsoCANDLE_PLAIN,NO_COLOR, CI and dumb terminals). Results,--jsonoutput and errors are undecorated.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.37
Section titled “0.11.37”- Hyperliquid:
candle perps withdrawno longer reads Relay’s request record (GET /requests/v3) before signing. Relay now refuses that read without a Relay key, so 0.11.36 refused every withdrawal with “Relay’s record of the request could not be read (HTTP 400)” and nothing signed. The recipient check is the build’sto, which must still be one of this key’s own wallets on the chain asked for; the command makes no call toapi.relay.link. Withdrawals stay switched off on the server.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.36
Section titled “0.11.36”- Banners from a local file.
candle image upload <path> --bannerhosts a wide image uncropped (wider than 1.5:1, for example 2171x724) and prints the URL to pass asbannerUrl; a square image is refused as a banner withBANNER_WRONG_SHAPE.candle launch --banner <file|URL>uploads a banner file the same way, or passes anhttps://URL through, on Solana and Hood TEE launches; the result reportsbannerUrl. Both uploads happen before the confirm prompt and are public and permanent. The server side is on staging first and on alpha with the next promote. - A Solana TEE
candle launch --buygoes through the atomic launch route, so the launch and the first buy fit Solana’s packet size. The CLI relay-signs both legs, saves the bundle before submitting, and never sends a leg itself. - An unset TEE spend limit (raw cap or USD
txLimit) means no limit on every TEE spend path.candle doctor, the key access screen and help say so, and no longer warn that transfers, LP deposits and launches need a cap. A configured limit, zero included, still binds. - Hyperliquid:
candle perps deposit --no-submitasks the server for a preview that holds nothing (no wallet lock, no USD reservation); against an API without previews it says it built for real and names the operation and when it releases the wallet.candle perps withdrawsigns the NonceMapping against Relay’s order id (relayOrderId). Withdrawals stay switched off on the server. - Hyperliquid wording from the 2026-10-20 mainnet test: perps help puts the deposit before
candle perps setup, names how to get an EVM TEE wallet onto a key, and sends realized P&L readers tocandle pnl --profile <name>; every--to-keypromote confirmation says the rebind does not move the wallet’s signer. - Solana LP transactions use a finalized blockhash, matching the send preflight, and a failed send simulation prints the RPC message, the simulation error and the last 20 log lines.
candle keysuses one set of capability words for custom access summaries and key details. No displayed string changes.- Preview: the Candle core and TUI gain Quant (the signals data source and the Quant preset) in the Agents tab.
@candledottv/tuiis still not published.
Formats: the core can write <config dir>/core/<profile>/agents.json (0600), the Agents tab’s agent profiles. An older CLI ignores it. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.35 (2026-10-20)
Section titled “0.11.35 (2026-10-20)”- A documented safeguard changed: no prompt asks for the last six characters of an address any more.
candle tee enable,candle tee sweep(Solana and Hood),candle vault demote,candle vault promote(--from,--in-placeand a resumed promote, Solana and Hood),candle vault export-key, the account step ofcandle vault restore --phrase, and the account and server-destination checkscandle tee status --verifyand a promote resume run before adopting a grant now print the address in full on its own line, in groups of four, and askType confirm to <what it does>:(for exampleType confirm to sweep everything to <address>:,Type confirm to promote <address>:,Type confirm to export the key for <address>:). The word is trimmed and compared without case; anything else, the old six characters included, refuses with nothing done and no retry, under the same codes as before (DESTINATION_NOT_CONFIRMED,VAULT_NOT_CONFIRMED; restore’s account step still records no exposure, exits 3 withEXPOSURE_ACCOUNT_MISMATCHand namescandle vault reconcile-exposure). This is the shapevault transfer,vault fundandexternal sweeptook in 0.11.19. Everything else is unchanged: the unlock still comes first, there is still no--yeswhere there was none, a terminal is still required, and every refusal before the unlock and every server-state check still runs.candle vault promote-batchstill names destinations aslabel (…last6), as a display label only. - The Candle core’s transfer approval (
cards.approveon atransfercard, which the TUI sends) checks the typedconfirmalone. Itsconfirm.lastSixfield is ignored, a wrong answer never withdraws the card, and the journal’scard.approvedrow recordsconfirm: { typed: true }. The TUI’s transfer flow drops its last-six step: the confirm step shows the address in fours under “Check this address against where you got it.”
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.34 (2026-10-20)
Section titled “0.11.34 (2026-10-20)”- Hood TEE launches are no longer refused. The signing check on the
createCurveleg pinned a stale selector, so everycandle launchfrom a Hood TEE wallet stopped with “The createCurve leg does not match what this operation confirmed” before anything was signed. It now pins the launch stack v2 factory’s selector (0x7cf8ad31). - Preview:
candle core serve,candle core mcpandcandle tui, withPROFILE_CORE_OWNEDdispatch guarding core-owned profiles.@candledottv/tuiis not published, socandle tuianswersTUI_NOT_INSTALLEDunless a checkout’scandle-tuiis on PATH. The core holds a profile’s trading credentials only once a view moves them there by turning trading on in the Candle TUI. candle keys listnames a custom key’s Read and LP access in its Access column (Read, Launch, Trade, LP), and lists any scope no word covers, where it used to leaveaccount:readandlp:writeout.candle wallet close-empty --wallet <tee address|label>closes a Solana TEE wallet’s empty token accounts and returns their rent to that same wallet, where it used to refuse and point atcandle tee sweep. It needsswap:write, so a Write key can clean up the TEE wallet it trades from. Candle builds the close transactions; the CLI refuses any that is notCloseAccountalone, with the wallet as fee payer, rent destination and owner, over the accounts the preview showed, before the key signer approves each one; Candle then sends the whole batch. A close the chain has not settled yet printsrecoveringand exits 3, and re-running with the same--client-trade-idreads it again without sending anything. The server routes are off on a deployment untilAGENT_TEE_CLOSE_EMPTY_ENABLEDis on. The embedded wallet’s close (--wallet embedded, its address, or no--wallet) is unchanged.
Formats: the core can write an encrypted credential slot at <config dir>/core/<profile>/slot.enc. Only when a profile is moved to the core (trading turned on from the Candle TUI), it writes that slot, sets coreOwned: true on the profile in config.json, deletes the profile’s Write key, device token and signer items from the plain secret store, and can store a Read key in their place. An older CLI ignores coreOwned and lacks the PROFILE_CORE_OWNED guard; it finds only the Read key (or no key if none was stored), cannot read the core-only slot and does not regain the trading credentials. No change to the vault.enc or tee-wallets.enc formats.
0.11.33 (2026-10-18)
Section titled “0.11.33 (2026-10-18)”- Hyperliquid risk and visibility:
candle perps account,candle perps risk,candle perps watchandcandle perps thresholds(show, set, clear), plus the liquidation distance, funding and risk level incandle perps positionsand a perps section incandle portfolio. They read Hyperliquid directly from this machine. - Hyperliquid history and markets:
candle perps fillsandcandle perps fundingpage the wallet’s history from Hyperliquid;candle perps markets,market,bookandcandlesread market data with a key of any scope. - Hyperliquid management:
candle perps modify,margin,tpsl,schedule-cancel,flatten,reduce-onlyandclose --pct. candle keys create --access trade-perpsmints a key with exactlyaccount:readandperps:write.candle perps openandclosesend aclientId, so a retry returns the original order instead of placing a second one; a conflicting reuse isPERPS_CLIENT_ID_CONFLICT. Setup refuses an account that is not in standard mode (PERPS_ACCOUNT_MODE).- The CLI checks every fee-bearing Hyperliquid order against Candle’s builder pinned in the release, and every withdrawal against the pins recorded from live Relay quotes (
CANDLE_PERPS_WITHDRAW_PINSstill overrides them for one machine). Withdrawals stay switched off on the server.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.32 (2026-10-17)
Section titled “0.11.32 (2026-10-17)”- New
candle perps withdraw <amount> --to solana|hoodbrings USDC from the key’s Hyperliquid account back to the key’s own Solana or Hood wallet through Relay, andcandle perps withdraw status <id>follows one. It needs the opt-inperps:withdrawscope and is confirmed at the terminal (there is no--yes). The command is in this release. The routes it calls reached production in the 2026-10-18 promotion and are switched off there (PERPS_WITHDRAW_DISABLED). - Touch ID fixes from the hardware run:
vault status --unlockwith Touch ID or a synced passkey now works with stdout redirected (a passphrase or PIN prompt still refuses without a terminal); a system-cancelled Touch ID prompt says so and suggests retrying with the Terminal window in front. vault transferandvault fundrefuse before the confirm, withTRANSFER_INSUFFICIENT_FUNDS, when the wallet cannot cover the amount, the fee and any rent. A send that no status read found is reported as most likely dropped, and--jsonaddsseen.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.31 (2026-10-17)
Section titled “0.11.31 (2026-10-17)”- The Hood signing checks no longer accept the retired Uniswap v2 router; a leg that names it is refused. No change to any command.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.30 (2026-10-16)
Section titled “0.11.30 (2026-10-16)”- More checks before signing for TEE wallets: a Hood launch or trade fee leg must pay the treasury the pinned splitter factory names on chain, read over your RPC; a Hood launch’s buy leg must go to the curve its own
createCurvecreated, for exactly the confirmed amount; and each Hyperliquid take-profit or stop-loss leg must sit within the allowed slippage of its trigger price.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.29 (2026-10-16)
Section titled “0.11.29 (2026-10-16)”- The CLI checks what it signs before it signs it (external report SEC-001 to SEC-009).
candle signshows any change of control (owner, delegate, close authority, program assignment) and refuses it withSIGN_CONTROL_CHANGE,--yesincluded. Solana TEE transfers, swaps, bridges and perps deposits are decoded and simulated before signing and held to the confirmed amounts and destination. Hood launch, swap and trade legs are decoded and pinned to the expected contracts, amounts and recipient. Hyperliquid orders must carry the coin’s asset index and stay near Hyperliquid’s mid. A key signer’s hash is derived locally (KEY_SIGNER_UNVERIFIEDwhen the server disagrees), only https or loopback http links are opened in a browser, and a request carrying a key or device token never follows a cross-origin redirect. candle launchon Hood without--buyplanscreateCurveonly, and Solana swaps on TEE wallets always read the RPC.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.28 (2026-10-15)
Section titled “0.11.28 (2026-10-15)”candle mcpruns@candledottv/mcp0.10.16: the launch tools take launcher-chosen curves (mode: "exp-custom"withcurve: { virtualQuote, threshold }). No change to any other command.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.27 (2026-10-15)
Section titled “0.11.27 (2026-10-15)”- New
candle agent profile show|setreads or edits the agent’s public page with its own key, andcandle agent post create|delete|listpublishes, deletes and reads its posts. candle mcpgainscandle_vamp_candidates,candle_update_profile,candle_create_post,candle_delete_postandcandle_list_agent_posts, from@candledottv/mcp0.10.15;--read-onlynow pins eight keyless tools.- A token trade whose trade leg landed but whose later step failed exits 3 and keeps its stage and signature, so it is not retried as a new trade.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.26 (2026-10-13)
Section titled “0.11.26 (2026-10-13)”- New
candle stakereads eligible Solana wallets’ CNDL, sCNDL, withdrawals and rewards, withstake add,stake remove,stake finishandstake claimfor the writes (swap:write).candle mcpgains the five staking tools andcandle_list_agents.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.25 (2026-10-12)
Section titled “0.11.25 (2026-10-12)”candle mcpcan launch with an image file: the connector it runs is the one in@candledottv/mcp0.10.12. SetCANDLE_IMAGE_DIRto an absolute directory path in the environmentcandle mcpstarts with, andcandle_launch_tokenandcandle_launch_and_seedacceptimagePath, an absolute path to a PNG, JPEG, GIF or WebP file of at most 10MB inside that directory. The connector uploads the file and launches with the URL that comes back. The upload is public and permanent, on a dry run too. A path outside the directory is refused, and so is a link inside it that leads outside. With the variable unset nothing changes: the tools takeimageUrlonly and the connector reads no image file.candle mcppasses the variable through untouched. No change to any other command.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.24 (2026-10-12)
Section titled “0.11.24 (2026-10-12)”candle launch --image <path>launches with an image file on this machine. The CLI uploads the file to Candle, then makes the launch with the URL that comes back;--jsonreports it asimageUrl. Pass--imageor--image-url, never both. The file must be a PNG, JPEG, GIF or WebP of at most 10MB, and the type is read from its first bytes, not its name: anything else is refused before any request (IMAGE_TYPE_UNSUPPORTED,IMAGE_TOO_LARGE,IMAGE_UNREADABLE). The upload happens before the confirm prompt and cannot be undone: the file becomes public and permanent, with any metadata it carries, even if you then decline or the launch fails. It runs once, before the launch id is claimed, so a failed upload leaves the id unused, and re-running a launch that already started uploads nothing.- New
candle image upload <path>does only the upload and prints the hostedhttps://URL, for a launch made somewhere else: the SDK, the REST routes, or a connector. It needs a key withlaunch:write, spends no funds, and does not count against the daily launch cap; the plan’s uploads-per-minute limit applies, and the route’sRATE_LIMITEDandUPLOAD_INVALIDcome back as sent. candle launch --image-urlwith anything but anhttps://URL is now refused on this machine, with a message naming--image. It used to reach the server and come back asVALIDATION_FAILED.- No route is new: both commands use
POST /api/v1/uploads/agent-image, which the API already serves.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.23 (2026-10-11)
Section titled “0.11.23 (2026-10-11)”- New
candle feeslists the creator fees your launched tokens can pay, andcandle fees claim <mint> [--dry-run]claims one token’s to the wallet fixed at launch (there is no destination option).candle mcpgainscandle_get_feesandcandle_claim_fees, from@candledottv/mcp0.10.11. The server keeps the claim off until Candle enables it, and answersLAUNCH_DISABLEDmeanwhile; the list works now.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.22 (2026-10-11)
Section titled “0.11.22 (2026-10-11)”candle mcpnow acceptsbucket=finalstretchincandle_get_feed: the connector it runs is the one in@candledottv/mcp0.10.10. The API serves that bucket only where it is switched on; elsewhere the request is refused as an unknown bucket, andbluechipstill answers. No change to any other command.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.21 (2026-10-10)
Section titled “0.11.21 (2026-10-10)”candle tee rename <label|address|id> <new-label>renames a TEE wallet on both sides: the label Candle holds and, when the wallet’s key is in this vault, the vault entry.candle tee rename --pairs-from <file>does 1–256 of them from the file shapevault rename --pairs-fromtakes, with--dry-run. Owner only (the device token). One server call renames every row, all or nothing, then one vault commit; the vault is unlocked once, only when a named TEE wallet may be in it. New labels follow the same rule on both sides: at most 64 characters, no edge whitespace, never trimmed. If the vault write fails after the server accepted, the command prints address-keyed rows to re-run.vault renamestill refuses a TEE wallet, and its refusal now namestee rename. Needs an API that hasPOST /api/v1/agent/linked-wallets/rename; against one that does not, it reportsTEE_RENAME_UNSUPPORTEDand changes nothing. It refuses an older whole-file copy of the vault before the server is called unless--accept-older-copy, treats a legacyember-hotwallet as a TEE wallet, and prints the address-keyed re-run rows when the rename request gets no answer.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store. A rename that reaches the vault rewrites the encrypted index once and advances its generation once; older CLIs still read it. A label in tee-wallets.enc is not changed.
0.11.20 (2026-10-10)
Section titled “0.11.20 (2026-10-10)”candle vault rename --pairs-from <file>renames 1–256 vault or external keys with one unlock and one commit. Supply<label|address|id> <new-label>lines or CSV columnsfrom,to; blank lines and#comments are skipped. Every finding refuses the whole file before any write; swaps inside the batch work.--dry-rununlocks and prints the plan without writing, and--jsonreturns the renamed rows. Single and batch rename now refuse new labels longer than 64 characters or with edge whitespace, without trimming; existing longer labels remain usable targets. TEE wallets are still refused byvault rename.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store. A rename rewrites the encrypted index once and advances its generation once; older CLIs still read it.
0.11.19 (2026-10-10)
Section titled “0.11.19 (2026-10-10)”- A documented safeguard changed: a vault send now asks for one verification, not two.
candle vault transfer,candle vault fundandcandle external sweepno longer ask you to type the destination’s last six characters, and no longer present your factor (passphrase, security key, Touch ID or passkey) a second time before signing. The unlock is the one verification, and its Touch ID reason, passkey line and security-key line now name the send (send <amount> <asset> to <destination>). After the decoded display the destination is printed in full in groups of four, and you typeconfirm(trimmed, any case); anything else ends the command withDESTINATION_NOT_CONFIRMEDand nothing signed. There is still no--yes, a terminal is still required, and on Hood the chain id, the pending nonce and a promoted wallet’s operation lock are still read again after the confirmation and before the signature. The last-six prompts onvault promote,vault export-key,tee resolveand the Hood promote and enable paths are unchanged.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.18 (2026-10-06)
Section titled “0.11.18 (2026-10-06)”- Agent key levels are named Read, Write and Withdraw everywhere the CLI shows or asks for one.
candle keyshelp and the commands the CLI suggests use--access read|write|withdraw. The old spellingsread-write,transferandread-write-transferstill work and mint exactly the same scopes. Stored scopes, preset ids and error codes are unchanged. candle vault demoteunlocks the vault once, for Solana and Hood TEE wallets alike, and runs the disable and the sweep against that one open vault; it used to ask three times. Inside demote, the standaloneRecover the funds: candle tee sweep ...hint is gone; demote printsSweeping remaining funds to <destination>...just before the sweep. A Solana wallet holding 0 SOL and no token accounts skips the sweep and saysNothing to sweep: 0 SOL, 0 token accounts., with nothing signed. A bad--rpc-urlis refused before the unlock. The disable still runs before anything is signed, and the emergency-sweep rules are unchanged.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.17 (2026-10-05)
Section titled “0.11.17 (2026-10-05)”candle launch --wallet <tee> --buy <amount>makes the first buy at launch, from the same TEE wallet. The amount is in whole units of the quote asset, converted ascandle swap --amountis (SOL, USDC or CNDL on Solana; ETH on Hood). On Solana the buy rides in the launch transaction; on Hood it is Candle’s own curve buy, signed as the last leg after the curve and the fee, and the CLI signs it only when it pays this launch’s curve exactly that amount. The preview names the buy before you confirm. Without--buythe launch is unchanged. It needs a server withTEE_LAUNCH_BUYS_ENABLEDon, which is off by default: until then Candle refuses the buy, and the CLI says so (VALIDATION_FAILED, naming the flag, with nothing built or signed) and suggests launching without--buyand buying withcandle swap.candle wallets allow-launch <wallet>...lets TEE wallets pay for a launch, whichcandle launchneeds, andcandle wallets disallow-launch <wallet>...stops them. They take the selectorswallets trusttakes (a label, address, id, orprefix*) and the device token, never an API key. The screen shows each wallet’s label, address and bound key before you typeconfirm;disallow-launch --yesskips the confirm. A wallet that is not a TEE wallet is named and left alone. They need an API with the allow-launch preview; an older one answersALLOW_LAUNCH_UNSUPPORTEDand nothing changes.candle launch’sLAUNCH_NOT_ALLOWEDmessage now names the command instead of the raw endpoint.candle plansandcandle launch --helpsay which launch paths need a plan. The two launch rows read “Launch from a linked or TEE wallet (self-signed)” and “Atomic launch: launch + 1–4 first buys in one bundle”, and the note under the table says every plan, Free included, can launch from its embedded wallet with an optional dev buy (same transaction on Solana; best-effort follow-up on Hood) (the headless launch: MCPcandle_launch_and_seed, SDKlaunch()).candle launchitself is unchanged: it is the TEE-wallet path and needs Pro or Max.candle swapfrom the embedded wallet now swaps between base assets on one chain (SOL, USDC and CNDL on Solana; ETH and USDG on Hood). It shows the quote and asks before anything is sent, as a token trade does: Candle builds the swap and holds it, and the CLI submits that stored plan once you confirm. It used to refuse a base pair from the embedded wallet withPAIR_UNSUPPORTED. A server that cannot hold an embedded swap for confirmation answersEMBEDDED_PAYER_UNSUPPORTEDand nothing is built. When the outcome is uncertain, the CLI prints the known hashes and says not to retry under a new id.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.16 (2026-10-03)
Section titled “0.11.16 (2026-10-03)”- A project
.envno longer configures the CLI. The compiled binary ignores.envandbunfig.toml; exportCANDLE_*variables or store settings in a profile. candle doctortells an owner profile from a bot profile.API key valid (launch:write)is renamedAPI key valid, and in the bot roleLaunch wallet delegatedis renamedEmbedded wallet.--jsonrows have stable ids, and the role and provenance fields are additive. A paused profile fails the Trade path check.candle portfolio <filter>shows only the wallets whose label or address contains the filter, in every group: vault, external, TEE and embedded, on both chains. The rule isvault list’s: a case-insensitive substring, no glob. Vault and external keys the filter leaves out are never sent to your RPC, so a few wallets out of a large vault read in a few requests where the whole vault can be rate-limited on the public endpoint. Subtotals and the total are for the matched wallets, the first line says how many matched, and--jsongainsfilter,matchedandwallets. No match prints one line and exits 0 when the list and the reads were whole.candle portfoliokeeps a cut-off wallet list partial on its own. Filtering out a wallet Candle could not read, or an LP position it could not read, no longer makes the result look complete, and no match says when the list was only part of the account. Against an older API that does not say whether the list was cut off, that partial answer stays partial instead of being reported complete.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.15 (2026-10-03)
Section titled “0.11.15 (2026-10-03)”candle plansprints the plans the API serves (GET /api/v1/agent/plans): each plan’s monthly price, agent trade fee and Hyperliquid perps builder fee, the limits a new key gets, and one row per capability, such as buying or selling tokens not launched on Candle, self-launch, linked wallets and limit orders. Every number is the server’s. It needs no key and sends none;--jsonis the server’s body. Against a server without the table it says so and exits 1.candle swap,candle launchandcandle perpshelp say what each plan can do: any plan can sell a token it holds, buying a token not launched on Candle and launching from a TEE wallet need Pro or Max, and every plan except Max pays the perps builder fee. They point atcandle plansfor the rates in force rather than naming them.candle mcpgainscandle_get_plans, and--read-onlypins six keyless tools.candle pnlreads the one P&L (see the 2026-10-02 entries in the partner API changelog):Totalis the console’s figure, to the cent.candle pnl --profileprints a Hyperliquid block: realized gross, funding, fees and net for the key’s bound EVM TEE wallets since their current binding, kept apart from the spot total.candle perps deposit <amount> <SOL|USDC|ETH|USDG>moves USDC onto the key’s Hyperliquid account through Relay, paid from the key’s Solana TEE wallet (SOL or USDC) or Hood TEE wallet (ETH or USDG);--to <evm tee>picks the account when the key has more than one.candle perps deposit status <id>follows one. It needsswap:writeand a raw cap on the asset, takes no Candle fee and is mainnet only. There was no withdrawal in this release;candle perps withdrawarrived in 0.11.32. Those routes reached production in the 2026-10-18 promotion, switched off (PERPS_WITHDRAW_DISABLED).candle mcpgainscandle_perps_deposit.
Formats: no change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.14 (2026-10-02)
Section titled “0.11.14 (2026-10-02)”- Hyperliquid perpetuals:
candle perps setup|open|close|cancel|orders|positions|leverage, from the EVM TEE wallet bound to the key. The key needs theperps:writescope, which is opt-in.setupapproves Candle’s builder fee once (0.1% on Free, Believer and Pro; none on Max).open <coin> <long|short> <size>trades at market, or as a limit with--price, with optional--tpand--sl;close <coin>closes reduce-only. Candle builds each action within the key’s limits; the CLI recomputes its hash and checks the action type and Candle’s builder before anything is signed, then submits the signed action to Hyperliquid itself.CANDLE_HYPERLIQUID_BUILDERpins the builder andCANDLE_HYPERLIQUID_NETWORK=testnettrades testnet. Depositing to Hyperliquid from the CLI is not in this release.candle mcpgains the matchingcandle_perps_*tools. candle portfolioshows Hood: the account’s Hood TEE and embedded wallets (ETH, USDG and tokens, from Candle) and EVM vault keys (ETH and USDG, over your own Hood RPC:--evm-rpc-url, elseCANDLE_EVM_RPC_URL, else the built-in Hood RPC). ACHAINcolumn,chainon every wallet and holding in--json, subtotals per group and per chain, and--chain solana|hoodto show one. An unpriced Hood token shows why. An EVM RPC that is not Hood is refused withEVM_CHAIN_MISMATCH. Against a server that does not send Hood wallets yet, the output is Solana only.candle pnlshows a Solana block, a Hood block and the combined figure, and aCHAINcolumn on positions.candle pnl --profiledoes the same frompnl.byChainand lists each paying wallet with its chain.- Solana
tee sweepandvault demoteread, simulate and confirm against one finalized RPC context, so a load-balanced RPC can no longer size a transfer from a newer state and simulate it against an older one. A transaction the RPC rejects before broadcast is reported as rejected and not broadcast (broadcast: falsein--json) instead of “may still land”, and the sweep carries on with the other accounts; it stops after a third rejection and lists what it did not attempt.--jsongainscontextFloorSlotand an optionalsloton each receipt.
Formats: a sweep receipt in tee-wallets.enc can carry an optional slot; older CLIs ignore it. No change to vault.enc, config.json or the secret store.
0.11.13 (2026-10-02)
Section titled “0.11.13 (2026-10-02)”candle mcp(the MCP server this CLI bundles) gainscandle_get_portfolio: balances and prices for the account’s embedded and TEE wallets on Solana and on Hood. Vault and external wallets stay oncandle portfolio, which reads them over your own RPC. The same server’scandle_get_profile_pnlnow describes per-chain P&L:chainon each open position and wallet row, andpnl.byChainwith each chain’s own figures. This is the portfolio command surface from #1538. A server that predates it omitshood,chainandbyChain.- Two other bundled-server text changes landed after 0.11.12 and ship in this binary. They are already on the standalone
@candledottv/mcpnpm package:candle_get_profile_pnldescribespnl.byWallet(#1501, MCP 0.10.3), andcandle_token_forensicssays a Hood token Candle did not launch names its launch account for pons.family and pools.trade, with no record of earlier coins (#1537, included in MCP 0.10.4).
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.12 (2026-09-30)
Section titled “0.11.12 (2026-09-30)”- Bridging between Solana and Hood in
candle swap: a TEE wallet swaps a base asset on one chain for a base asset on the other (SOL or USDC on Solana, ETH or USDG on Hood), through Relay, into the same key’s TEE wallet on the other chain. No Candle fee.--to <tee>picks the destination when the key has more than one on that chain,candle swap status <id> --waitfollows a bridge until it fills, refunds or fails, andtee sweeprefuses a wallet while a bridge from or to it is still open. Vault to vault isvault fund, thencandle swapacross, thentee sweep. vault promote --to-keyandtee rebindreport trade readiness by the rule the server uses: only a cap of zero stops an asset, and a missing cap or transaction limit is unlimited, so a key with no caps no longer warns that it cannot trade. A Hood wallet is checked against its ETH and USDG caps.candle mcp(the MCP server the CLI runs) now describesclientSwapIdon the swap tool as a durable idempotency key. A retry of the same request with the same id, amount and slippage replays the stored result instead of swapping again, so after a timeout an agent retries with the same id rather than stopping. A confirmed first leg of a bridge is replayed with its hash and is not run a second time.
Formats: a swap’s local operation record (the file candle swap status reads) can carry an optional bridge field for a bridge; older CLIs ignore it. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.11 (2026-09-28)
Section titled “0.11.11 (2026-09-28)”- Only the limits a key’s owner set apply. A TEE trade or swap needs neither a per-asset cap nor a USD transaction limit; a missing one is unlimited, and a limit that is set still binds.
candle doctorand the swap readiness checks follow the same rule. - The automatic stop after five consecutive buys of the same token is removed. Trade-rate, failed-sell and owner-set loss limits stay.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.10 (2026-09-26)
Section titled “0.11.10 (2026-09-26)”- Key signers:
candle tee signer new,keys signer approve,keys signer move, andvault promote --to-keyandtee rebindonto a key that has a signer. See Key signers. - Hood TEE wallets in the CLI: EVM promote, fund, sweep, demote and
swapon Hood. See Hood TEE wallets. candle keys accesschanges a key’s access level in place.- A default Solana RPC, a per-profile RPC setting, and a prompt when the public RPC rate-limits you.
- A key can hold up to 1,000 wallets (the Max plan’s linked-wallet cap), read from the server, and a rebind that adds no wallet is never refused for size.
candle wallet close-emptycloses the embedded wallet’s empty token accounts and reclaims their rent.
Formats:
vault.encversion 4, one way. A vault moves to version 4 on the write that creates its first Hood TEE wallet (an EVM promote, orvault restore --phrase --evm-tee-countof 1 or more), and never moves back. 0.11.9 and every older CLI refuse a version 4 vault withVAULT_VERSION_UNSUPPORTED. A vault with no Hood TEE wallet keeps its version 2 or 3 header byte for byte and still opens in older CLIs. Before creating a Hood TEE wallet, update every machine that opens that vault or its backups.- New file
vault.evm-record.sealedbeside the vault, and<copy>.evm-record.sealedbeside a backup. Older CLIs do not read it or copy it. config.jsongainskeySigners(the key-signer index and pins) andpublicRpcNotice. Older CLIs ignore both and keep them when they write the file.- Secret store: new refs
key_signer_<prefix>_<spkiSha256>. Older CLIs ignore them. A wallet owned by a key signer trades only from a CLI that has this release: an older CLI looks only for the wallet’s ownwallet_signer_<id>, and atee rebindorkeys signer moveonto a key signer deletes that slot once the move is read back. tee-wallets.encis unchanged.
0.11.9 (2026-09-24)
Section titled “0.11.9 (2026-09-24)”EVM vault keys (vault new-key --chain evm, vault transfer on Hood or any EVM chain), and tee rebind pointers.
Formats: no version change. EVM keys are new entries in the existing version 2 and 3 index, which already allowed them, so older CLIs open the vault. Older CLIs predate the check that stops Solana-only commands from being pointed at an EVM key, so run commands that name an EVM key only from 0.11.9 or later. tee-wallets.enc, config.json and the secret store are unchanged.
0.11.8 (2026-09-24)
Section titled “0.11.8 (2026-09-24)”candle transfer, keys create --access, wallets trust, and a security key can authorize adding another factor.
Formats: none. No change to vault.enc, tee-wallets.enc, config.json or the secret store.
0.11.7 (2026-09-24)
Section titled “0.11.7 (2026-09-24)”candle lp, portfolio and pnl with LP valuation, vault promote --to-key, and vault transfer from a promoted wallet.
Formats: tee-wallets.enc sweep records can now have kind lp-close, an addition. Older CLIs open the file and carry the record through unchanged; how they display an lp-close record has not been checked. vault.enc, config.json and the secret store are unchanged.
0.11.6 (2026-09-23)
Section titled “0.11.6 (2026-09-23)”The unlock menu, tee rebind, the promote confirmation, and security keys in sealed backups.
Formats:
- The vault’s state file (
vault.state.json) gains four optional backup fields that tie a backup to the factors it was made with. An older CLI keeps them, but its ownvault backupdoes not update them, so after an older CLI’s backupvault statusstops naming which keys the last backup carries. Nothing is lost. - A sealed backup copy now keeps security-key envelopes as well as the passphrase. The copy’s version is unchanged, and older CLIs already open a vault with security-key envelopes.
vault.encitself,tee-wallets.enc,config.jsonand the secret store are unchanged.
0.11.5 (2026-09-22)
Section titled “0.11.5 (2026-09-22)”vault list, vault promote-batch, and a working install for GitHub CLI users.
Formats: none. promote-batch writes the same index fields a single promote does.
0.11.4 (2026-09-21)
Section titled “0.11.4 (2026-09-21)”vault rename, the label uniqueness guard, and the backup transcript.
Formats: none. A rename rewrites an existing label field; the version is unchanged.
Before 0.11.4
Section titled “Before 0.11.4”vault.enc version 3 (the external branch, for candle external and candle sign) predates 0.11.4. A CLI from before it refuses a version 3 vault with VAULT_VERSION_UNSUPPORTED; a vault that never used the external branch stays version 2.