What's new in Codron

EARLIER · page 4 of 5

1. v0.5.1Jun 11, 2026Telegram alerts stay in sync with the dashboard

   • · Answering a decision on the dashboard now updates its Telegram alert too: the option buttons disappear and the message flips to the same '✓ resolved' state you'd see after tapping a button in the chat, tagged '(from dashboard)'. Previously the phone kept showing a live-looking decision card for something you'd already handled at your desk. It's an in-place edit, not a new message; no extra ping for a choice you just made yourself.
2. v0.5.0Jun 11, 2026Google Antigravity engine support

   • · Google Antigravity (agy) joins Claude Code and OpenAI Codex as a third engine. Pick it as a project's master (or reviewer) from Settings → Engines or the per-project ENGINE card; cycles run through agy's headless mode with file tools enabled. Install via Google's official installer (the Engines row links the docs), sign in once by running agy in a terminal, and you're set. Timely if you're on Gemini CLI: it reaches end-of-life June 18 and agy is its successor.
   • · Antigravity model picks carry the reasoning tier in the name (e.g. 'gemini 3.1 pro · high'), exactly as agy exposes them, including the Claude and GPT-OSS models agy can route to. Heads-up on what this engine can't report yet: agy's print mode has no usage envelope, so these cycles show no token/cost figures and no live activity stream; the field report, diff chip, and confidence gate all work normally.
   • · The engagement/intel mode chip moved from its own header strip into the input rows (next to attach in the composer, next to send in intel) so the mode is visible exactly where you type, Claude Code style. The freed header row goes back to the activity stream.
   • · For followers: release notes now ship over RSS at codron.app/releases/feed.xml.
3. v0.4.0Jun 11, 2026Cross-project decision triage + one-click retry

   • · The home overview now leads with a NEEDS YOUR CALL section: every pending decision across all your projects, oldest first, answerable right there: option buttons, notes, and the multi-question form included. No more opening each project and scrolling its feed to find the amber card. Env-var requests link into the project instead, since those need the Variables tab filled before approving.
   • · One-click retry on a failed engagement. When the latest cycle fails, its card grows a retry button that re-queues the exact orders that cycle consumed and re-engages, replacing the old re-type → queue → engage three-step. Only the newest failure gets the button, so a retry can't replay stale orders over newer work.
   • · Engagement cards now show what actually changed: a diff chip on the meta line (e.g. '5 files +214 −18'), measured against the repo state before the cycle started. Works with auto-commit on or off; non-git projects simply don't show it.
   • · The empty feed finally tells you what to do: instead of 'no engagements yet' regardless of context, the copy now follows the project's state: wait (still scaffolding, ~1-3 min, updates live), watch (first cycle already running), or act (queue an order and press engage).
   • · Onboarding dead ends got exits. A failed engine install shows the exact manual npm command to run plus re-check; sign-in failures list concrete recovery steps; and the engine step explains why Continue is disabled instead of leaving a dead button.
   • · Billing hardening: if a card payment fails, the dashboard shows a fix-your-card banner (previously the first signal was a silent downgrade weeks later), and the plan flip after checkout now retries on transient errors so a paid account can't get stuck on Free.
   • · Dashboard worst-case staleness dropped from 20s to 5s when the realtime socket silently dies; a new escalation can't sit unseen.
   • · Fair-play note: the Free plan's 1-active-machine limit is now actually enforced at registration (it was UI-only before). Replacing a laptop still works; a machine that stops reporting frees its slot after 7 days.
4. v0.3.0Jun 10, 2026In-app git: a Source tab in the left panel

   • · New Source tab in the left panel (next to Timeline): see your project's git at a glance: current branch, ahead/behind the remote, the working-tree changes, and a commit-history rail that flags any commits not yet pushed. Pull / push / refresh are right there, with a 'pull before you push' nudge when the remote is ahead. Tuned for Codron's auto-commit model: it's view-and-sync, not a full SCM (no staging or commit UI; the agent owns commits). Desktop only; everything runs locally and nothing leaves your machine.
   • · The right panel's engagement / intel split is now a single mode chip (like Claude Code's mode picker) instead of two tabs: pick the mode, same two surfaces underneath, drafts preserved.
5. v0.2.0Jun 10, 2026Per-project environment variables, agent env-requests, and Claude Fable 5

   • · New Variables tab on every project: edit that project's .env right in the app, Vercel-style: key/value rows with masked secrets, a per-field reveal, and inline add/remove. Values are written only to the local .env on this machine and never sync to the cloud; the key names are declared in the committed .env.example so a placeholder you add stays as a field even before you fill it in.
   • · The agent can now ask you for missing keys instead of guessing. When a cycle needs a value it doesn't have (an API key, a secret, or an id/URL you have to grab from a dashboard, e.g. a Stripe product id), it raises an 'env vars needed' card in the feed that lists each key with why it's needed and a how-to link. Fill them in the Variables tab, click continue, and the next cycle resumes with the values in place.
   • · Claude Fable 5 is selectable as a Claude Code model (Anthropic's public Mythos-class model, 1M-token context). It is NOT the default (Opus 4.8 stays the default since Fable costs more), so opt in per project or globally from Settings → Engines.
   • · Settings → Engines & Integrations cleanup: dropped the duplicate 'update → x' badge (the 'update to x' button already shows the version), removed the always-on 'update docs' link from manual integrations so a row only shows an action when there's actually one to take, and removed the Supabase CLI row since Supabase is handled through its MCP server.
6. v0.1.8Jun 9, 2026Telegram parity with the dashboard + agent reliability

   • · Telegram detail view now mirrors the dashboard: tap Send order to compose an order right in the chat (your next plain-text message becomes the order body), and the pause/resume buttons read as Disengage / Re-engage / Engage so the vocabulary stays the same on phone and web. Escalation and cycle-done alerts get an 'Open project' inline button so you can jump from a notification straight into the detail view.
   • · Note-style decisions in Telegram now accept a free-form reply: tap the note button and the bot waits for your next message as the answer, matching the dashboard textarea flow instead of requiring a slash command.
   • · Fixed P0: a state.json written by an older agent missing a newly-added metric field (e.g. lastEngagementSeconds) would crash-loop the whole agent on boot. Missing or non-numeric metrics now fill with 0 and the next engagement writes real values.
   • · Doc viewer reworked: the modal is wider and taller so long content isn't cramped, and you can edit references inline (briefing / plan / skill stay read-only; the agent rewrites those every cycle). Saving overwrites the file and queues a single cycle trigger, identical to adding a reference.
   • · FastAPI projects laid out as app/main.py or src/main.py are now correctly detected as backend tiers and started with 'uvicorn app.main:app'; previously they read as 'no backend tier detected' even though the code was fine.
   • · Settings → Notifications warns when Telegram has a token + chat id but the master toggle is off: in that state every automatic alert (escalations, cooldowns, cycle-done) is silently dropped while a test message still works, which previously made decision alerts look broken.
   • · The 'applying update' moment is on-brand now: instead of a native OS message box, restarting to apply an update paints a full-screen dark overlay with a spinner and relaunches.
   • · Activity panel current-task line no longer half-cuts wrapped Korean glyphs at the band edge.
7. v0.1.7Jun 5, 2026UI polish: outline buttons, in-app dialogs, briefing-free imports

   • · Import a project without writing a briefing. For an existing folder or a GitHub repo, leave the briefing empty and Codron just clones/registers it in standby, then waits for your first order; type a briefing and the button switches to 'Brief & engage' to start an engagement right away.
   • · Re-importing a GitHub repo you've already cloned no longer fails with 'clone target not empty'. If the folder is the same remote, Codron adopts it in place instead of refusing.
   • · Buttons are unified to one outline style across the whole app, and the OS confirm popups (the bare '확인 / 취소' box) are replaced with in-app dialogs that match the dark theme; project deletion and machine removal now ask inside the window.
   • · Fixes: the right-side activity panel no longer collapses to a sliver; the preview pane no longer jumps to a stale page when you press the mouse back/forward button; deleting a project whose folder was already removed now succeeds instead of erroring; 'Check for updates' is consistent between the app and engine cards, and a per-engine UPDATE button only appears when a newer version actually exists.
   • · Refreshed startup splash and assorted copy cleanup.
8. v0.1.6Jun 5, 2026Sign-in fix and Telegram lets you drive Codron from your phone.

   • · Fixed P0: sign-in on 0.1.5 failed with 'dashboard /auth/callback returned 405' right after OAuth approval. The desktop session bridge handler was removed in a cleanup that misread its purpose. Restored, with the docstring spelling out the desktop bridge is the sole caller so the same mistake doesn't recur.
   • · Telegram bot now takes inbound commands. /projects lists every project; tap a project to drill into a status detail with Pause, Resume, and Refresh inline buttons. Status icons match the dashboard so engaged, standby, stood-down, pinned, and accomplished read the same way on the phone.
   • · Type /order <project> on one line, then your instruction on the next line, to queue an order from your phone. If the project is paused, pinned, or done, the order also kicks the cycle so it actually runs. Running projects pick it up on the next cycle as before.
   • · /decisions in Telegram surfaces any unresolved decisions across all projects with the option buttons inline, useful for catching up after you missed an alert.
   • · Persistent bottom-bar keyboard in Telegram with Projects, Decisions, and Help shortcuts so you don't need to type slash commands.
   • · Site: shipped real Privacy Policy and Terms of Service pages under Viva Technologies Lab, LLC, and replaced the footer duplicates of the top nav with legal links and a Contact line.
9. v0.1.5Jun 3, 2026Per-project notifications, Expo/Flutter preview, and at-a-glance project status.

   • · Per-project Telegram notifications: mute alerts for a noisy project from its Settings tab or right when you create it, without touching your global Telegram setup.
   • · Mobile-app preview: Expo (React Native) and Flutter web builds now render in the preview pane, with a 'phone' button that shows a QR to open the running build on your device over the same wifi. Element-picking works on Expo; Flutter uses the canvas renderer so picking is preview-only there.
   • · Project status (engaged / standby / pinned / accomplished) now shows on the project page and next to the name in the top-bar switcher; no need to open the dropdown to check.
   • · Settings → Engines now checks for CLI updates: each installed engine shows 'up to date' or 'update available', and the Update button only stands out when a newer version actually exists.
   • · Fixed: after 0.1.4 set the default effort to xhigh, new cycles on an older Claude Code could fail with 'effort xhigh is invalid'. Effort now falls back to the best level your CLI supports instead of failing the run, and the default is back to high.
   • · Cleaner account menu: just Settings, Contact support, and Sign out. Plan & billing moved to a new Settings → Account tab.
   • · Quieter activity stream: filtered out the noisy 'system thinking_tokens' rows Claude Code emits on every reasoning tick.
10. v0.1.4Jun 1, 2026Settings reliability + per-CLI updates.

    • · Settings → Engines / Integrations now has an Update button on each installed CLI. npm-backed tools (Claude Code, Codex, Vercel) re-run their global install in place; manual-install tools open the upstream docs.
    • · Auto-save no longer hangs on 'saving…' if a save fails right after an app update. The default-engine card surfaces a one-click reload when this happens.
    • · Auto-update reliability: on boot, Codron clears the webview HTTP cache when the version changed since the previous launch, so a freshly-updated build can no longer be served the previous version's client chunks against the new server.
    • · The new-mission page no longer flashes a sanitized 'Server Components render' error when opened.