Skip to content

Releases: nphil/Cody

Cody v0.57.0

Choose a tag to compare

@github-actions github-actions released this 14 Oct 05:29

Cody v0.57.0

  • Side questions now live in the Side Bar ("This chat"), next to the separate
    "New chat". Typing /btw in the chat box opens it there.
  • The top bar shows live CPU and memory for each machine. Add machines (by
    ssh name) in Settings > System > Machines. The three token numbers moved
    into the session popover.
  • Scheduled messages: one slim bar above the chat box, tap to see the list.
  • Daily time limit (Settings > Preferences, off by default): counts only the
    time you actively use Cody, on all your devices together. A small circle in
    the chat box fills up; when it is full you get a calm notice, never a lock.
  • Claude API credits as backup (Settings > Providers > Anthropic): add an API
    key per Claude account. When every Claude plan hits its limit, the chat
    keeps going on the same Claude model with your API credits, and goes back to
    the plan when it resets. It never switches to another provider while a key
    has credit.
  • Removing or signing out of an account or provider now really removes it
    (fixes "Cody found no openrouter account matching that id").

Full Changelog: v0.56.0...v0.57.0

Cody v0.56.0

Choose a tag to compare

@github-actions github-actions released this 09 Oct 13:42

Release 0.56.0

Long unattended runs keep going overnight.

  • A chat whose run gets stuck is restarted by Cody. That covers a tool call
    that never answers, an engine that stops responding, or an hour with no
    progress. Cody then tells the agent what happened, so it checks what
    finished and carries on.
  • If a chat's engine crashes mid-run, Cody restarts it after 30 seconds.
  • If Cody's server or container restarts in the middle of a run, the run is
    picked up again when it comes back (if it was active in the last 6 hours).
  • At most 3 restarts per chat in 12 hours, then Cody stops and tells you. Every
    restart sends a push notification if notifications are set up.
    CODY_RUN_RECOVERY=0 turns all of this off.
  • Scheduled messages are no longer lost when they wait behind a long reply.
    The row says "waiting for the current reply to finish…", and the message is
    sent again if the engine or the server stops before reading it.
  • A chat can no longer split into two copies with an engine on each when its
    engine is replaced.
  • The server log now says why a running chat's engine was stopped.
  • Unraid: the template raises the container's process limit to 16384 (Docker's
    default is 2048, which long runs exceed). Add --pids-limit 16384 to Extra
    Parameters on an existing install; the container log warns when it is low.

Full Changelog: v0.55.0...v0.56.0

Cody v0.55.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 00:41

Release 0.55.0

Cody is now checked against omp 18.8.3, the latest engine release.

  • Chat names from omp 18.8 no longer show a broken box or a short code in
    front: omp's new "card" titles are shown as just the title.
  • Settings > Behavior > All settings works again in the container image. It
    had been coming up empty because of how the built server loaded omp's
    settings list; it now lists every setting, including 18.8's new title
    options.
  • The engine card in Settings > System now says "Built to v18.8.3".

Full Changelog: v0.54.0...v0.55.0

Cody v0.54.0

Choose a tag to compare

@github-actions github-actions released this 07 Oct 09:07

Release 0.54.0

Every device backup is one card and one compressed file.

  • One backup, one zip: Download all and Save to server each produce a
    single ZIP (Deflate, ZIP64 when needed) holding the files byte for byte
    plus SHA256SUMS and manifest.json. Partition dumps are mostly empty space
    and shrink a lot (a 220 MB test set became 21 MB). Opens with Windows,
    macOS, Android, unzip, Python and 7-Zip.
  • Save to server checks every file's SHA-256, packs one archive in the
    background, reads it back, then removes the uploaded pieces. The vault
    admits only saves it can finish and keeps a free-space floor while
    packing.
  • Sets group by when each read began, so a long read no longer starts a
    new card; agents can name a backup with set; a person can Combine a
    card with the older backup of the same device.
  • Choose what to back up: tick partitions for an EDL backup (All/None,
    search), or select files inside a card and Download/Save selected. Still
    one card and one zip.
  • Labels never claim more than the archive holds: an interrupted or
    trimmed backup reads "Incomplete backup", a chosen set "K of N
    partitions", in the card, the file name and manifest.json.

Full Changelog: v0.53.0...v0.54.0

Cody v0.53.0

Choose a tag to compare

@github-actions github-actions released this 07 Oct 01:56

Release 0.53.0

Devices panel: one card per job, backups as sets, and a safe way to keep them.

  • Activity tells a task as one card: "Back up partitions · 47 of 58 · about
    3 min left", one progress bar, the item in flight, Details and Cancel. A
    finished job becomes one line in History, grouped by device and day.
  • What needs you comes first (countdowns, the device trust question,
    failures); a failure stays until you press "Got it".
  • Logs, hashes, ids and raw results moved into one detail sheet; the panel
    itself no longer has scroll boxes inside it.
  • Files & backups shows one card per set ("58 files · 2.1 GB · all
    verified") with partition names, filter and sort past ten files, and a
    per-file menu.
  • Download all: one ZIP (ZIP64 when needed) with the files unchanged plus
    SHA256SUMS and manifest.json.
  • Save to server: streamed upload in pieces that resumes after a dropped
    connection; the server re-reads every file and checks its SHA-256 before
    the folder appears, with manifest.json and SHA256SUMS. Agents get
    device_artifacts_save and device_artifacts_status.
  • Removing a file is locked while its set is being saved or zipped, and a
    cancelled transfer says so instead of vanishing.

Full Changelog: v0.52.0...v0.53.0

Cody v0.52.0

Choose a tag to compare

@github-actions github-actions released this 07 Oct 00:09

Built for omp 18.7, plus per-device trust and scheduled sending.

New with omp 18.7

  • Side questions: type /btw , or use "Ask a side question" while
    the agent is working. The answer streams into its own panel and never
    enters the chat; follow-ups, Cancel, Copy and history are kept per chat.
  • Goals are now the engine's own: /goal [--budget 200k] shows a
    Goal panel with tokens used against the budget, time, Pause, Resume and
    Drop. "Keep working automatically" lets the agent continue toward the goal
    by itself (saved for every chat).
  • Stop gives queued messages back: anything you sent during a run that the
    agent had not read yet returns to the message box instead of running
    after you pressed Stop.
  • Fork from here on any reply, and Duplicate chat in a chat's menu and in
    the command palette.
  • Slow mode in the model menu (low-priority lane on Claude subscriptions,
    flex tier on OpenAI), and a plain line in the usage popup when an account
    is over its limit and on a slower or wrap-up allowance.
  • A chat whose saved model no longer exists opens with a notice and a model
    picker instead of failing to start; the message you sent waits and is
    delivered once you pick. omp 18.7 refuses to reopen such chats on its own.
  • models.yml editor: model kind (image, speech, embedding, judge, ...), the
    runner APIs that serve them, and per-provider/model stored Responses
    chaining.
  • Fixed for 18.7: new chats showed "(no messages)" in the sidebar and never
    got an automatic name, and a pop-up repeated the engine's internal tool
    list every time a chat started. Only MCP tool changes raise a pop-up now.
  • New engine settings labelled: terminal-only display options are chipped,
    and the subagent completion-estimate setting notes that it never runs in
    Cody. Verified against omp 18.7.0.

Devices and scheduling

  • One question per device, in the chat: Allow or Deny, with "Remember this
    device". It replaces the shell-access switch, per-operation approvals and
    typed override codes. Forget it from the device card or Settings.
  • Scheduled send: the Send button's arrow sends now, when the chat's model
    quota resets, or at a time you pick. Agents can schedule messages too.

Smaller image

  • The container no longer ships the 730 MB web build cache it never used,
    so the image is about 0.7 GB smaller on disk.

Full Changelog: v0.51.0...v0.52.0

Cody v0.51.0

Choose a tag to compare

@github-actions github-actions released this 04 Oct 23:54

Release 0.51.0

Device panel: quiet, grouped, and approve-then-send.

  • Routine agent device commands (getvar, getprop, reads) no longer raise a
    pop-up each. Pop-ups only appear when something needs your approval, a long
    or bulk job (flash, backup, transfer, >15 s) finishes, or something fails or
    is cancelled. Bursts of failures fold into one pop-up plus a summary.
  • The Devices panel groups a burst of agent commands into one expandable entry
    ("Agent ran 7 fastboot commands · 7 ok"); anything waiting for you is listed
    first, and flashes/backups keep their own card.
  • Approve first, send later: the approval card names the device and offers
    "When to send" (right away, 10, 20, 30 or 60 s). After approval a countdown
    with a Cancel button runs; nothing is sent until it ends. The approval is
    single-use, expires 10 s after the countdown, and is refused if the device
    left or its USB identity changed. Agents may suggest a wait
    (options.sendDelaySeconds, 1-300 s); your choice wins.
  • A waiting approval cancelled by the system (device unplugged, page closed)
    now says why instead of vanishing.

Full Changelog: v0.50.0...v0.51.0

Cody v0.50.0

Choose a tag to compare

@github-actions github-actions released this 04 Oct 19:55

Back up and flash Qualcomm devices in emergency download mode (EDL) from the tablet.

  • Detects a Qualcomm device in emergency mode (USB 05c6:9008), reads its chip serial, hardware id and key hash, and sends the loader you choose after you confirm it.
  • Reads the partition tables and storage size, checks that the tables fit the measured disk, and backs up any partition or the whole user area with checksums.
  • Flash a partition from a file or erase one: Cody saves and verifies a copy first, writes in blocks you can cancel, reads back to verify, and says plainly when a write may have happened but could not be verified.
  • Back up a whole unit as a set and restore it onto the same unit only (serial, key hash, storage and disk id must match), partition tables last.
  • Start-up and identity partitions need an extra typed confirmation; the eMMC boot areas and RPMB are never written.
  • Every copy that justifies a write is read twice and must match; reads that do not line up with what the device actually sent are refused.

Tested against a simulated device only; real-hardware checks are listed in docs/hardware-checklist.md.

Full Changelog: v0.49.0...v0.50.0

Cody v0.49.0

Choose a tag to compare

@github-actions github-actions released this 04 Oct 12:43

Flash and manage hardware from the tablet the way a PC would, plus chat notifications.

Phone and tablet notifications

  • Cody can send a push notification to your ntfy server when a chat needs you.

Hardware flashing (PC parity)

  • ESP chips: erase the whole chip (after saving a restorable backup, including zero-offset chips such as ESP32-S3/C3) and read eFuses.
  • Fastboot: large images are split into sparse pieces automatically; full-package update (update/flashall) with the package's own requirements checked, and stage.
  • DFU: plain DFU 1.1 downloads with a backup first, DfuSe leave and USB reset. A device that leaves the bus as expected is a finished, unverified write, never a silent success.
  • Android (adb): install apps (never replaces an installed app unless you approve it, typed confirmation, staging cleaned up even on failure or cancel), root/unroot, switch to TCP/IP or USB-only (Wireless debugging is checked too), and wait for a device.
  • Every one of these asks first, says honestly what it could and could not verify, and can be cancelled at any time.

Full Changelog: v0.48.0...v0.49.0

Cody v0.48.0

Choose a tag to compare

@github-actions github-actions released this 03 Oct 20:37

Release 0.48.0

Port forwarding from a tablet, and a calmer Devices panel.

  • adb forward and adb reverse work from the browser, through Cody's server.
    Forward listens on the Cody machine's loopback and tunnels each connection
    to the device; reverse lets the device reach a service on the Cody machine.
    Each rule is a confirmed operation with bounded quotas and credit-based flow
    control, and it is torn down on cancel, unplug, a lost relay or page
    replacement. Port rules, shells, pulls and terminals share one ADB
    connection and lease.
  • The Devices panel is reorganised as connect -> device -> that mode's
    actions: one "Add a device" card, one card per device with its mode
    (ADB, recovery, sideload, fastboot, DFU, serial, ESP, Bluetooth) and tabs
    for only the actions that mode supports. Touch targets are 44 px or more,
    laid out for tablet portrait and landscape. Every existing action stays
    reachable; protocol and confirmation logic are unchanged.
  • docs/hardware-parity.md lists every adb, fastboot, esptool, dfu-util and
    mtkclient command with the Cody action and the test that exercises it.
    MediaTek preloader/BROM support is not implemented yet.
  • docs/release.md records the v0.47.0 release-job runner fault and its
    recovery.

Full Changelog: v0.47.0...v0.48.0