What's new in Codron

EARLIER · page 3 of 11

1. v0.20.3Sep 11, 2026Bring your own CLI tools, and alerts on Discord, Slack or your phone

   • · Settings now lets you add the command line tools you actually use, beyond the four that ship built in. Pick a preset (AWS, Azure, Fly.io, Railway, Cloudflare Wrangler, Netlify, Stripe, Docker, Terraform, kubectl) or describe any other tool yourself: which command it runs, how to tell whether you are signed in, how to sign in and out, and how to install it here. Codron then installs it, signs you in, and shows its version and sign in state the same way it does for GitHub or Vercel.
   • · Your list of tools follows your account across machines, while installed and signed in state is checked on the machine you are sitting at. So the same tool can read ready on one machine and not installed on another, which is what you want to know before sending a run there. Adding tools is included with Pro.
   • · Notifications are no longer Telegram only. Add a Discord or Slack webhook, an ntfy topic for phone push, or any webhook URL of your own, and the same alerts (a decision waiting for you, a long cooldown, a finished engagement) arrive there with a link back to the dashboard. Each channel has a test button that sends exactly what real alerts look like. Replying and approving still happen in the dashboard or in Telegram.
   • · Turning notifications off for one project now silences every channel for it, not just Telegram.
   • · The Codron version and the check for updates button moved to Settings, Machines, next to each machine's agent version, which is also where the version in the account menu now takes you. The optional ngrok token folds away once it is saved.
   • · The project list on the overview is quieter. The redundant project count line is gone, search and the status filter sit on one row, and a project shows what it is working on only while it is actually working. Finished and idle projects are a compact two lines.
2. v0.20.2Sep 11, 2026Manage a project across your machines, and safer project deletion

   • · Settings now lists every machine that holds a checkout of a project, with its folder path, whether it is online, which one you are sitting at, and where the last run happened. Pick a machine and send Run or Pause; an offline machine keeps the request until it reconnects. Results and review history stay the same on every machine, while local chat sessions, environment values, and uncommitted files stay where they are.
   • · Codron finds a project's folder on the current machine by its own project identity, so a renamed folder is still recognized and a different project with the same folder name is not. Imported repositories outside the Codron folder are found again through the path that machine registered.
   • · Deleting a project now tells you up front what will happen on this machine. Folder deletion is offered only for folders Codron manages, disabled buttons explain why, and other machines that still hold the folder are named. A folder that belongs to a different project, and the Codron folder itself, are never touched. Deletions that cannot apply now report an error instead of appearing to run forever.
   • · A checkout left on another machine no longer recreates a project you deleted. That machine keeps its copy on disk, stops syncing, and pauses instead of starting new work.
   • · The desktop companion keeps its last known project status while a refresh is retried, says when it is updating, and comes back on its own after sleep, window focus, or a dropped connection. Project tabs now fit a single row that scrolls sideways in narrow windows.
3. v0.20.1Sep 11, 2026Balanced companion sizes and continuous Robo Cat animations

   • · Robo Cat and Sprout now have comparable body heights across the collection, website previews, and desktop companion, while keeping each character's proportions.
   • · Picking up and dragging a companion leaves room for its movement, so its body and tail stay inside the display area while swaying and settling.
   • · Robo Cat's resting, working, input, and review reactions now move forward and back through continuous loops. Repeated endpoint frames are removed, and the review loop keeps the folder visible. Reduced-motion and hidden-window pauses still apply.
4. v0.20.0Sep 10, 2026Smoother companions, playful pick-up reactions, and Sprout

   • · Companions have their own Settings tab, with an on/off toggle, a character collection, purchase restoration, and a mystery slot for the next arrival. Robo Cat remains free.
   • · Meet Sprout, a new pixel dragon for your desktop. Buy it once for $4.99 USD through Stripe and choose it on any machine signed into the same Codron account. No Pro subscription required; AI usage and future characters are separate.
   • · Idle motion follows a longer continuous loop with eased turns. Hold a companion to lift it, drag to make it sway, and release to let it settle. The dashboard and minimized desktop window share the same reactions and reduced-motion support.
   • · Purchases are verified on the server, kept separate from subscription permissions, and restored from your account. Duplicate checkout requests reuse the same session; full refunds remove access. See codron.app/companions for previews and purchase terms.
5. v0.19.1Sep 10, 2026Easier project variables, smoother team handoffs, and companion fixes

   • · Browse project environment variables by key, with search and a project list that stays usable as you add projects. Inspect each source file, explicitly reveal or copy a value, and choose which value to reuse in this machine's keyring before saving.
   • · The desktop companion keeps moving while projects need input or results await review. Review animations repeat smoothly, while hidden windows and reduced-motion preferences still pause playback.
   • · Team workspace now sits alongside Results, Preview, and Chat in a single group with matching button heights and a layout that fits narrow windows.
   • · Manage invitations directly from the team workspace. Shareable invitation links remain accessible when clipboard access fails, accepting an invitation opens the team workspace, and sign-in preserves links to specific results. Clearer discussion and request-queue links explain where requested changes go next.
6. v0.19.0Sep 10, 2026Live project companion, clearer reviews, and CLI usage visibility

   • · The desktop companion now follows your own projects across all machines. Input requests take priority, followed by results that need review and active work. Click it to see project details, or minimize Codron to keep the character on your desktop and click it to return. Turn it off in Settings to minimize normally.
   • · Review several results at once with Accept selected. Request changes uses the same wording across project and team views and queues a linked revision for a future run. Team discussions have a clearer composer, member attribution, and direct navigation from each project.
   • · Team workspaces require the project owner to have Pro; invited members can participate on Free.
   • · Usage shows subscription limits and reset times reported by supported local Codex and Claude CLIs, plus recent session context when available. Unavailable data stays unknown. Session panels show the model that actually ran.
   • · Overview uses more of the available width, with clearer project summaries, filters, results, usage and drafts. Settings can inspect environment keys by project and reuse existing values for new projects; CLI updates and sign-ins can run independently per engine.
7. v0.18.1Sep 10, 2026The companion character preview now ships in the desktop app

   • · The companion character introduced in 0.18.0 now appears in the packaged desktop app, at the lower right of the window, instead of only in development builds. Drag it to move it, click it to pick a motion, pause or replay, hide it, or reset its position. Placement is remembered on this machine and stays inside the window when it resizes, and the reduced-motion setting shows a still pose.
   • · This is still a visual preview. Its motions are chosen by hand and are not yet connected to live agent state, and character purchases are not included. No database migrations or execution engine changes in this release.
8. v0.18.0Sep 9, 2026A clearer Overview and a renewed Codron website

   • · Overview now places projects and decisions beside recent results and usage on wide screens. Empty, loading, and error states keep their space, while smaller windows use a single column. Results and drafts expand when you need more.
   • · Selection controls now share one visual language across machine and status filters, result views, usage periods, project navigation, engine settings, and team reviews. Pointer, disabled, and keyboard-focus states are more consistent throughout the dashboard.
   • · The English and Korean website has a new product walkthrough with interactive populated and empty Overview examples, concise workflow guidance, and mobile navigation. Language switching preserves your page and no longer changes preference during link prefetching.
   • · A companion character preview introduces the next direction for Codron. The original character and basic reactions are planned to be free. The draggable animation study remains development-only; live agent reactions and character purchases are not included in this desktop release.
9. v0.17.0Sep 9, 2026Shared requests, result reviews, and confirmed automation pause

   • · Team workspace brings shared requests and result discussions together. Add completion criteria, preserve drafts, review the original request beside its result, and queue a linked change request without starting an engine.
   • · Owners can accept results, reopen reviews, or request revisions. Results show bounded Git evidence and recorded execution details; accepting a result remains separate from merging code.
   • · The project panel groups activity into expandable session cards with a routing summary. Request history separates saving, intake, observed output, and recorded results, while returning projects open Results first.
   • · Request reservations and owner-controlled machine assignment are enabled after every registered project runner has updated to 0.17.0 or later. Offline runners also need updating or retirement. Attachments stay on their originating desktop, and reserved work remains on its current machine.
   • · Pause waits for the tracked automation cycle and its CLI process tree to stop. Reset preserves task files until that confirmation, and an uncertain stop holds the project for inspection. The watchdog no longer frees a still-running cycle for a duplicate start.
   • · This release uses the project owner's runners. Team members can submit and review work; execution with each member's own engine, isolated task worktrees, automatic handoff, and a merge queue are still planned.
10. v0.16.0Sep 7, 2026session lanes route orders across warm sessions by difficulty, Claude Fable 5.1 and GPT-6 Astra land in every picker

    • · Smart routing now keeps SESSION LANES instead of one master session. A lane is a named CLI session pinned to one model: the haiku classifier reads each order batch, decides whether it continues an existing lane's topic (or touches files that lane already knows) or opens a new one with a 2-4 word label, and sizes it. Trivial orders run sonnet-5 at medium, moderate ones sonnet-5 at high (new), complex or ambiguous ones run your master engine. Similar orders keep landing on the same warm transcript, so the prompt cache stays hot and the session doesn't re-read the repo; when a topic outgrows its tier it continues on a fresh lane on the heavier model with the previous lane's file list handed over. Before this, a routed sonnet order overwrote the single session slot and the next mission cycle on opus started cold, which threw away exactly the context the routing was meant to protect. Four lanes per project, least recently used retires, the mission's main lane never does. Execution is still one cycle at a time per project; lanes are about context and cost, not parallel edits.
    • · The right panel has a SESSIONS section under the activity stream: one row per lane with its label, model and effort (colored by tier), consecutive cycles, orders consumed, tokens, dollars, and last use. The lane the running cycle is on pulses; expand a row to see the files that session touched. With a single main lane and nothing routed the section folds to one line. The activity stream footer now shows what the in-flight cycle actually runs on (lane, engine, model, effort, and the classifier's trivial/moderate/complex verdict with resume or fresh); the agent stamps this before the engine spawns, where before the footer had nothing to read until the cycle ended. Feed cards gained a per-cycle dollar figure and a model/effort chip, so a sonnet cycle and an opus cycle read differently at a glance.
    • · Claude Fable 5.1 (claude-fable-5-1, GA 2026-09-01) and GPT-6 Astra (gpt-6-astra, 2026-09-03) are in every model picker (settings, per-project engine, /new, and the session/scratch chat picker), with their effort tiers (Astra goes to ultra). Defaults are unchanged: opus-5 at xhigh and gpt-5.6-sol at high. Both new models are the premium tier at double the price, so they stay a deliberate pick rather than what an unattended multi-cycle loop spends on by default. gpt-5.4-mini left the pickers (retired 2026-08-31, Codex upgrades it to luna on its own).
    • · Both new models need a newer CLI than many desks have installed (Claude Code 2.1.251+, Codex CLI 0.153+), and both CLIs reject an unknown model only after the spawn, as a 400 that used to pin the project STUCK on every cycle with the reason buried in the stderr tail. The engines now recognize that rejection, run the cycle once on the model's fallback (fable-5.1 falls to fable-5, astra to gpt-5.6-sol), and post a line in the activity stream telling you to run claude update or codex update. The fallback is remembered per agent process so later cycles skip the doomed probe, and the engagement record stores the model that actually ran. The settings dropdown shows the version requirement under the model.