Skip to content

v0.1.128

Choose a tag to compare

@github-actions github-actions released this 28 Oct 04:41
· 326 commits to master since this release

Highlights

  • macOS builds are signed and notarized. Release builds are now signed with a Developer ID (RICHE VENTURES, INC.) and notarized by Apple, so Gatekeeper treats Verde like any other downloaded app. Privacy permissions such as Documents access now carry over to the next update instead of being asked for again after every update. The signature changes from ad-hoc to Developer ID with this release, so macOS asks one last time after you install it (6fbf95e).
  • macOS asks for folder access during setup. A new first-run step asks for Documents, Desktop and Downloads access and has a shortcut to Full Disk Access. Existing users see it once too. Until now the first prompt often came from the background daemon while nobody was at the Mac. The macOS prompts also say why Verde is asking (17d0384).
  • Browsing folders can no longer freeze the daemon. If a workspace lived in a macOS-protected folder and a privacy prompt went unanswered, browsing folders (for example the iPhone Add workspace browser) could hang the whole daemon. Verde now works out browse roots without opening workspace folders, runs at most 2 folder-browse requests at a time and answers extras with "busy", and the desktop reports "daemon busy" instead of starting a second daemon (b73e485).
  • Scheduled tasks. Ask a chat or the Companion to run a prompt later: once, every N minutes, or daily at a set time on chosen weekdays. A task can post into an existing chat or start a new one, and it reports back to the Companion. You can manage tasks from the Companion on desktop, iOS and Android, from verde schedule, or through MCP tools any agent can use (eccdafa).
  • Use a workspace on another machine. Run on now finds machines that already have the workspace, or a checkout of the same git repo ("Same origin · Use it"). It can also set the workspace up on another machine from a card in the chat, using a remote folder picker. Pairing is easier too: nearby Tailscale machines connect by approval, a Pairing link fills in the whole form from one paste, and one Settings switch makes this desktop reachable (3ca89b8, 972747d, ede22f7, 9c23f68, 8eb3911, 560ac14, e8ab3d5, 4c39a0f, 82d5ee3).

macOS

  • Developer ID signing and notarization: the release jobs sign the app and the DMG with the Developer ID identity, then notarize and staple both. Forks without the signing secrets still get ad-hoc builds (6fbf95e).
  • Folder access step: a macOS-only first-run dialog after the provider and MCP steps. It has one row per protected folder (Allow, its status, and Open Settings if access was denied), an "Allow all" button that shows the prompts one at a time, and an "Open Full Disk Access" shortcut. Checks run in the background, so a pending prompt never freezes the window or blocks quitting. Done or Skip is remembered. The app's Info.plist now explains every prompt it can raise: Documents, Desktop, Downloads, network, and removable volumes (17d0384).

Multi-machine and remote runtimes

  • Same repository, different machines: each machine's daemon now records every checkout's git origin and shares it with clients. SSH and HTTPS forms of the same remote count as one repository. Workspaces that already existed have their origins filled in in the background when the daemon starts, without delaying startup (3ca89b8, 9c23f68).
  • Attach a folder as a workspace: a new daemon request attaches a folder on the target machine after checking that it is inside the allowed roots and has the expected origin. If that folder already belongs to a workspace there, the two are linked so chats and files address the same workspace from either side (972747d).
  • Run on, with setup: Run on now groups machines into three tiers: machines that already have the workspace, machines with a checkout of the same origin (one click to use it), and "Set up on …" for the rest. If a send fails because the repository isn't bound on that machine, a setup card replaces the error and your draft is kept. The card offers Use it, Pick folder… (browse the remote machine) and Cancel. Devices without write access are told that setup needs a Full device or the owner (ede22f7).
  • Setup card fixes: Cancel no longer crashes the app, a failure message no longer covers the card's buttons, and an older machine now says "'s Verde can't set up workspaces yet. Update Verde on " instead of "could not be reached". The remote folder picker won't offer the home folder itself as a workspace (8eb3911).
  • Clearer remote send errors: a remote chat that can't start now says "The selected repository is not bound on this runtime" instead of a generic "could not start". Sends that hit a busy connection (for example during a heartbeat or token refresh) retry for up to 15 s instead of failing (560ac14).
  • Pair by approval: Add connection lists Verde machines on your tailnet. Connect sends a request that the other desktop shows as " () wants to connect", with a match code and a permission preset. Allow finishes the pairing with no further clicks. Add connection now lists, in order: Nearby machines, Verde Cloud (no machine needed), Pairing link, and SSH under Advanced. Developer status text and raw URLs are gone from the Connect step (e8ab3d5).
  • One-paste pairing link: paste the link first and both machine names fill in from the link host and this computer's hostname. A link that already carries the grant starts the exchange right away. Agents can pair machines for you: verde-daemon pair create --link-host prints the link, and verde runtime pair plus the pair_runtime / runtime_pair_status MCP tools run the same visible wizard (4c39a0f).
  • Remote access switch: Settings → Connections → Remote access makes this desktop reachable over Tailscale Serve, with no commands to run. The card shows "Reachable at https://….ts.net", or the one thing in the way and how to fix it. Turning it off removes only Verde's own gateway and Serve mapping. An existing gateway for the same data is reused instead of starting a second one, and phone pairing uses this address automatically (82d5ee3).
  • Verde Cloud accounts: Settings → Connections shows one card per account with its machines inside, instead of one connection per machine. You sign in once per account, a single assigned machine connects on its own after the first sign-in, and the composer's runtime picker shows " · ", including machines not linked yet. Existing connections and the chats pinned to them keep working with no migration (2d601eb).
  • Provider sign-in on remote machines: installing and signing in to a provider CLI now runs in a terminal on the remote machine (Verde Cloud, paired, or SSH) without tying up chat. The provider dialog and Settings → Connections show the real sign-in status for Codex, Claude and Cursor, and the setup terminal font shrinks so QR codes and links fit (9422b82).
  • Connection logging: the desktop logs each settled connection state once (no secrets), so a reconnect loop leaves a trace. A 5xx from the server while connecting a device now reads as "server unavailable" instead of offline (fd6bde5).

Scheduled tasks

  • The daemon runs scheduled tasks: a prompt sent into an existing chat, or into a new chat with a chosen provider and model. A task can run once, every N minutes, or daily at a local time on chosen weekdays. Due tasks fire within 15 s. If the chat is busy the prompt steers or queues, new chats report back to their parent (such as the Companion), and a task missed while the machine was off runs once when it comes back (eccdafa).
  • Where to manage them: a Scheduled view in the desktop Companion panel (toggle, run now, delete, details), a Scheduled list with a New/Edit form in the Android and iOS Companion sheet, verde schedule list|add|enable|disable|remove|run, and MCP tools for any agent. The Companion creates a task itself when you ask for something later or on a schedule. The CLI reference and Companion docs cover it (eccdafa).

Companion (desktop)

  • Expand to full size: a header button grows the Companion over the whole workspace area, edge to edge like a maximized pane, with a centered reading column. Conversation text and the composer now use the chat fonts and sizes (af9beba, 6ad7afa).
  • Crew: collapsed to a one-line summary by default. It opens itself when a chat needs you, and a manual collapse sticks until the next time something does. Chats that need you and running chats come first, and finished ones fold into an "N done" row with Clear done. When expanded, the crew sits in its own column (c0ec41f).
  • Smoother and faster: replies stream in smoothly like chat threads, and a long history now takes about 0.1 ms per frame to draw instead of about 17 ms. The composer border is crisp and matches the chat composer (c0ec41f, 0a2368f).
  • Steer while it works: pressing Enter while the Companion is working steers its running turn, as in chats (or queues the message for providers that can't steer). Before, the message was refused and stayed in the draft. Steers show as your own bubble labeled "You · steering" (ccfc9b4, 502202f).
  • Close conversations: the menu has "Close this conversation", and each remembered conversation has an ×. Closed conversations are archived, not deleted, and don't show up as ordinary sidebar chats. A conversation that hasn't started yet can be dismissed too (be4a187, 0bf8dde).
  • Stays out of the way: opening a chat, terminal or new thread from the sidebar minimizes the Companion instead of opening behind it. Companion conversations started from a phone no longer open as desktop chat panes or appear under Open in the sidebar (1fd41d3, 1a2b083).
  • Messages from other devices: Live voice transcripts and other lines saved by your phone now appear in the Companion panel (03f7bd0).

Live voice

  • Live voice on Linux: hands-free, two-way voice with the Companion on the desktop, ported from the phone apps. It uses PipeWire with echo cancellation, so you can talk over it without headphones. If no echo-cancelled audio arrives, it falls back to half-duplex. It supports OpenAI Realtime, xAI and Gemini Live. Ctrl+Alt+Space (or prefix Shift+Space) starts or ends a call and Ctrl+Alt+M mutes. Clicking the speaking Companion interrupts it, and the transcript is saved to the Companion chat. macOS and Windows are not supported yet (2072dab, 2326014).
  • Call pill: a floating pill with the Companion, a level meter, and settings, captions, mute and end buttons. A captions card shows the last two lines. The settings popover picks the voice provider and voice and restarts a running call. The shortcut now starts a call without opening the Companion panel (a1add89).
  • Voice by voice: asking the Companion something during a call steers its running turn instead of waiting for it to finish. Saying "stop" or "cancel that" stops it (ccfc9b4).
  • Transcripts: voice lines show as conversation turns ("You · voice" bubbles and " · voice" replies, with the phone apps' waveform icon) instead of system rows, and this also fixes transcripts saved from phones. Finished exchanges are saved about 1.5 s after they end instead of every 2 minutes. Waveform icons no longer draw over the header when scrolled (71543e2, 616f7d0).

Companion and mobile (iOS and Android)

  • Live voice call pill on phones: a Live call on iOS and Android now shows as a pill floating over the Companion conversation, matching the desktop: the Companion, dots that rise with whoever is talking, and settings, captions, mute and end buttons, with a captions card underneath. Tapping it opens a full view with a large orb and the conversation in large type; the chevron goes back to the pill. A failed call still shows why (5a64719).
  • Lowercase name: the iOS and Android apps write the product name as "verde" everywhere you see it: app names, permission prompts, notifications and errors (6886ff7).
  • Photos: the iOS attach menu's Photos item now opens the photo picker instead of just closing the menu. Photos can be up to 700 KiB each at up to 2048 px, up from 160 KiB, and four photos always fit in one message. Android adds multi-picked photos one at a time (f7f3b71, f1d42e7, c717823).
  • iOS transcript scrolling: the transcript stays on the newest message while diff cards and images finish loading, instead of ending in blank space, and it no longer jumps around when the composer resizes (6f2c3c5, f1d42e7).
  • Rename fix: renaming a chat with history no longer fails with "The runtime rejected the request" (963d2cb).
  • New-chat defaults follow the desktop: the New chat sheet starts with the desktop's new-chat provider and model, and a model you pick for a new phone or web chat is remembered on the desktop (1d53d1e).

Desktop

  • Waiting on agents: a bar above the composer lists the subagents and linked chats a turn is waiting on, with View and dismiss. Sidebar rows read "Waiting · N agents", the side-panel toggle shows an agent count, and the stream header says "Waiting on N agents" once the provider goes quiet (43ef148).
  • Mouse back/forward: mouse side buttons move back and forward through the workspaces and chats you've visited. The browser pane keeps those buttons for page history. You can rebind them in Settings → Workspace → Back & forward or under keybinds.navigation, and Go Back / Go Forward are in the command palette (a1caeac).
  • Lone panes: a pane alone in its view fills the workspace edge to edge with a thin focus line, and its border lines up with the window and sidebar edges. The zoom button is hidden when there is nothing to hide (c55f9f9, 6079860, 511afe0).
  • Keyboard commit dialog: the commit sheet and the "Commit & push to ?" confirmation can be used entirely from the keyboard, with Tab order, arrows through files and hunks, and a focus ring after keyboard input (3ef9aac).
  • Provider updates: a newer provider CLI is announced in a dismissible toast (" update available") (06e410e).
  • Build status in the sidebar: a chat whose agent is waiting for or running a build shows "Waiting · build" or "Building" (03e4610).

Settings and Connections

  • Connections page redesign: Remote access and Paired devices are separate cards. Each device is one row ("Full access · Last seen 10 h ago") with a Details disclosure and a Revoke button that asks you to confirm. Runtime rows show just the main action. Expanding a row lists repositories, providers and tools with one Install / Sign in button each, and IDs, endpoints and setup commands sit behind Details. Green now means only connected, signed in or ready, amber means a problem you can fix, and red means a failure. Text wraps or truncates at any width, and Tab order follows the layout (e7cf9d5).
  • GitHub on remote machines: a "Tools on this runtime" section shows GitHub CLI status on the remote machine. "Install & sign in" installs gh without root and checks its checksum, then signs in with a device code in the same dialog. The one-time code appears at the top, and "Copy code & open GitHub" copies it and opens the GitHub device page. Sign-in no longer gets stuck on gh's "Press Enter" prompt, and the clipboard warning on headless machines is gone (264a75d, 8aa9a7a, 7649b5d).
  • Install, then sign in: when an install finishes and the CLI is signed out, the dialog offers "Sign in to " right away. The footer button changes as you go (Copy code, Done, Check again), and Back / Not now / Escape return you to where you started (8aa9a7a).
  • Onboarding: a new "Connect an AI provider" dialog covers installing, signing in and updating, with readiness rechecks and full keyboard access (9422b82).

Providers

  • Muse workflows: background workflows a Muse turn launches now keep running and deliver their results to the chat, instead of being stopped when the turn ends with an empty answer. Each workflow shows as one row with agent progress. Tool rows no longer say "Cursor tool" for every provider (1558460).
  • Defaults match each CLI: for new users the built-in models now follow each CLI: Claude default (Opus 5.5) instead of Fable 5.1 1M, Codex gpt-6.1-sol, Cursor auto, Grok default. Reasoning effort is left to each model's own default. Model-less turns from phones and web use the desktop's new-chat model (1d53d1e).
  • Codex: GPT-6.1 Terra is in the model list (042cec3).
  • Status and detection: fixed provider readiness checks failing with invalid_params, and updated provider CLI detection, version and sign-in checks (9422b82).

Daemon and reliability

  • Folder browsing fix: browse roots now come from stored paths, and only the folder you are browsing is opened. At most 2 folder-browse or attach requests run at once, and extras get an immediate "busy". The desktop sees that reply as "daemon present but busy" instead of starting a duplicate daemon and failing after 5 s (b73e485).
  • Build leases for agents: verde lease run takes its lease straight from the daemon and no longer keeps its own queue, which could leave agents waiting on each other for up to an hour while no lease was held. Stopping it ends the command's whole process group and releases the lease at once. Rerun messages say how many files changed (9422b82, 03e4610).

Website and docs

  • New homepage headline ("All your coding agents. Anywhere you work."), screenshots of the current UI in 14 themes, a gallery viewer that plays short feature clips, and App Store / Google Play "coming soon" badges. The homepage copy is shorter and simpler for first-time visitors, and the tiling section is gone (4b9bdf5, c397d11, dc3ac73, 91ed671, aaf5f93, b5418f5, 4df0af4).
  • New and rewritten docs: multi-machine workspaces, remote runtimes, remote access and pairing (with a "Pairing by approval" section), desktop Live voice, and scheduled tasks (560ac14, 2d601eb, e8ab3d5, 2072dab, eccdafa).

Build and release

  • macOS release jobs sign with Developer ID, notarize and staple the app and DMG (6fbf95e).
  • mise run stage-remote-access stages verde-server, verde-web and the web assets next to the dev build, so the Remote access switch works in dev builds (1d1ee86).
  • Release and Linux install script updates (9422b82).