What's new in Hoplite

Meaningful features and fixes, in plain English. Open an update for the details.

  1. Features

    • The Mac app now picks up most updates without restarting 

      Hoplite for Mac downloads most updates in the background and reloads onto them when you step away, keeping your drafts and leaving local agents running. Updates that do need a restart install the next time you quit, and a small note in the sidebar appears only if one has waited a few days.

      By Bence Redmond

    • Private threads are now available in every organization: keep new threads private or make any thread you started private 

      Turn on Keep new threads private in your account settings, or choose Make private from a thread's actions menu. Private threads are visible only to you and stay out of other members' lists, search, notifications, and Slack status cards. Organization owners and admins can set New thread visibility to override members' defaults for new threads.

      By Odin Glynn-Martin

    • Agents in every organization can now schedule wakes for their thread, message other threads, and use the native Claude Code and Codex tool sets 

      Agents can schedule a delayed follow-up, create recurring wakes, and watch a command until it succeeds, each with visible status you can cancel. Threads can read and message other threads their owner can open. Anthropic and OpenAI models use Claude Code and Codex tool sets; models behind your own gateway keep the standard tools.

      By Odin Glynn-Martin

    Fixes

    • The desktop app no longer shows an error screen on every launch after you open a local thread 

      With a local thread open in a window tab, the desktop app showed "This page hit an error", and reloading or restarting showed it again. Local thread tabs now open normally.

      By Bence Redmond

    • Claude Fable 5.2 runs no longer fail partway through with an invalid request error 

      Some longer Claude Fable 5.2 runs, and runs that started while a workspace was still setting up, stopped with an invalid request error about earlier reasoning. Those requests now recover on the same model and the run continues.

      By Bence Redmond

    • On iPhone, messages in an open thread are fully readable again instead of washed out below the navigation bar 

      On iOS 26, every message in an open thread could appear faded into the page, in light and dark mode, which made replies hard to read. Threads now show their messages at full contrast. This fix is included in the next iOS app update.

      By Owais Korejo

  2. Features

    • Desktop app explains why local runs are unavailable and how to fix it 

      In the desktop app, the Local and Worktree options now say what is missing, such as Claude Code or Codex not being installed or signed in, and open Settings to fix it. Settings › Local agents shows each agent’s status, the Terminal command that fixes it, and a Re-check button. Local Claude Code runs start on Opus 5.5. Available as the desktop app updates.

      By Bence Redmond

    • Agents can answer with charts, diagrams and tables, right in the thread 

      Ask an agent to show its answer and it can reply with a page: a chart, heatmap, timeline, dependency graph, diagram, table or quick mockup, with hover details and controls such as sliders. The page appears in the thread in your current theme and opens full screen. Pages are only visible to people in your workspace, and they run isolated from your account.

      By Bence Redmond

    Fixes

    • Desktop Home tabs keep separate drafts and composer settings 

      Opening a Home tab starts with an empty composer instead of copying another tab’s draft. Returning to an existing Home restores its draft and composer settings, with the cursor at the end of the draft, so switching tabs no longer replaces work in progress.

      By Bence Redmond

    • Typing and switching tabs in the desktop app now respond faster 

      Typing and switching tabs in the desktop app do far less work. The message box no longer measures itself on every keystroke, shortcuts no longer scan the page as you type, and switching tabs no longer re-measures the tab strip before the new page appears. The message box also uses the system text cursor in Hoplite’s colour. Available as the desktop app updates.

      By Bence Redmond

  3. Features

    • Add preview models and replace retired defaults on custom gateways 

      For OpenAI-compatible gateways, add unlisted preview or beta models by ID, set their display name and capabilities, and verify them directly. Custom models stay saved when you refresh the provider catalog. If your default disappears, choose and verify a replacement before saving the refreshed list.

      By Bence Redmond

    • New threads start on the model your linked subscription includes 

      With Claude Code linked, new threads start on Opus 5.5. With only Codex linked they start on GPT-6 Astra, and with only xAI on Grok 4.7. Paid plans with nothing linked start on Opus 5.5. Until you pick your own favorites, the model picker stars Opus 5.5, GPT-6 Astra and GPT-6.1 Sol.

      By Bence Redmond

    Fixes

    • Threads requiring ChatGPT can start with an eligible organization subscription 

      An eligible organization ChatGPT subscription now lets you start or resume a thread that requires ChatGPT, even when personal accounts are disabled. These threads no longer incorrectly ask you to reconnect a personal subscription when an organization subscription is available.

      By Bence Redmond

    • In the Mac desktop app, Check for Updates now always answers: it shows that it is checking or downloading, brings back a ready update you dismissed, and lets you try again if a restart to update didn't happen. 

      Before, clicking Check for Updates could do nothing visible, and a restart to update that didn't go through blocked updating until you quit the app. Now every check ends with a clear result: up to date, the ready update, or what went wrong.

      By Bence Redmond

    • Repositories with environment-named Compose files such as docker-compose.dev.yml get the Docker runtime 

      Docker reprovision and new-thread runtime detection now recognize root Compose files like docker-compose.dev.yml or compose.local.yaml when they define services, and a requested verification script is still inspected past guard clauses that exit on a failed check. When reprovision finds no local Docker requirement, the agent reports whether the requested script was found and points to the project's Docker Compose setting. Repositories with no Docker signal stay on the default runtime.

      By Odin Glynn-Martin

    • Previews of apps that ask for a sign-in at their home page now open instead of loading forever 

      Apps that answered their home page with a sign-in challenge or refusal (HTTP 401 or 403) never counted as started, so Preview kept loading. They now open and show what the app sends. For HTTP Basic or Digest sign-in, your browser asks for credentials there, and agents no longer restart them.

      By Odin Glynn-Martin

    • Arabic and Hebrew messages read right to left 

      Paragraphs, lists, headings and table cells written in Arabic or Hebrew now read right to left, so English names and bold words inside them stay in the right order. The message box and thread titles follow the language you type in too.

      By Odin Glynn-Martin

    • Files the agent shares download with their real names 

      Downloading a file the agent shared now saves it under the file's own name and extension, such as clip.mp4 or report.zip. Before, the download was named after the agent's description of the file, so videos, archives, and documents often arrived without an extension and would not open on your device.

      By Odin Glynn-Martin

    • Supabase local stacks with custom auth email templates start in Docker Compose workspaces 

      supabase start no longer fails after migrations when a project sets custom auth email templates or multiline Edge Function secrets. The SELinux :z and :Z mount labels the Supabase CLI adds to these files are now accepted and ignored, so workspace files are never relabeled. Shared and slave mount propagation remain blocked.

      By Odin Glynn-Martin

    • Previews of projects on Vite 4 or older now open instead of waiting forever for the app to start 

      The preview checked whether an app was up with a request older Vite dev servers answer with a 404, so it kept waiting even though the app loaded in a browser. The check now requests the page the way a browser does, so these previews open once the dev server is ready.

      By Odin Glynn-Martin

  4. Features

    • In Paseo, Zed and other ACP clients, you can start a Hoplite session from any folder: when no project is linked to the folder, choose one from the session's Project picker next to the model. 

      Before, a session opened outside a repository linked to a Hoplite project failed with "No Hoplite project" unless you pinned one with --project. Hoplite also now recognizes more GitHub remotes, including addresses with a port or user name and SSH host aliases.

      By Bence Redmond

    • Agents in threads and swarms can merge and queue pull requests when you ask them to 

      Ask an agent to merge, queue, or dequeue its pull request, or to turn auto-merge on or off, and it acts once checks pass, review threads are resolved, and GitHub reports the pull request mergeable. Agents only do this when you tell them to. Branch protection and merge queues still apply, and agents cannot use admin overrides or jump the queue.

      By Odin Glynn-Martin

    • For organizations with GitCafe enabled, the agent can open pull requests on a connected GitCafe repository and follow their checks, reviews and CI. 

      In sandboxes that include GitCafe's command-line tool, threads on a GitCafe repository can open and update pull requests, read review comments and CI logs, and report when a pull request is ready. Merging stays with you.

      By Bence Redmond

    • For organizations connected to GitCafe, agents can edit a pull request's title, description and target branch. 

      Agents could open pull requests on GitCafe but not revise them. They can now update the title, description and target branch of an existing GitCafe pull request, as they already could on GitHub.

      By Bence Redmond

    • Paper is now available to every organization: connect it in organization integration settings so agents can open and edit your designs 

      Organization owners and admins can connect a shared Paper account under Settings, Integrations, Organization, Paper. Agents can then use Paper tools, threads show a Paper tab while agents work, and Paper file links in chat open there. Showing live designs inside chat responses is still limited to selected organizations.

      By Odin Glynn-Martin

    • Send messages while attachments are still uploading, and drop files anywhere on Home 

      You no longer wait for files to finish uploading before sending. Start a thread or send a reply right away, and it goes as soon as its attachments land. If one fails, nothing is sent and your draft stays. On Home, drop files anywhere on the page to attach them.

      By Bence Redmond

    Fixes

    • API keys and MCP clients can now download files a run attaches to a thread, using the id from the file's link in the messages 

      Downloading a run's shared file through the API previously returned not found, because its link carried an id the download route did not accept. GET /api/threads/{threadId}/attachments/{id} now accepts that id, and the MCP hoplite_call_api tool returns the bytes as base64 in 512 KiB chunks. Access is unchanged.

      By Bence Redmond

    • In Docker Compose workspaces, uv commands and Stop preview no longer fail on files Hoplite left owned by root. 

      Restored Docker Compose workspaces could carry cache and preview files that Hoplite had written as root, so every uv command failed to open its cache and stopping a preview failed with Permission denied. uv now uses a fresh cache that the workspace owns, Hoplite stops previews as the workspace user before archiving, and stopping a preview no longer fails on a leftover stop marker.

      By Odin Glynn-Martin

    • Switching between threads is faster, especially on slower computers 

      Your ten most recent threads now stay ready in the background, so opening one shows its messages without waiting on the server. Threads you switch back to after a few minutes reopen nearly as quickly as ones you just left, which matters most on computers with fewer cores or less memory.

    • For organizations with GitCafe enabled, the agent can push branches to a connected GitCafe repository instead of failing with a username prompt. 

      Pushes from a thread now use the workspace's GitCafe connection automatically, so you no longer need to export a bundle and push it yourself. The connection's token stays out of the repository configuration.

      By Bence Redmond

    • For organizations connected to GitCafe, agents commit in workspaces under the GitCafe account that owns the connection's access token. 

      Agent commits in GitCafe workspaces could fail because no author was set. They now use the account behind the connection's access token, and connecting checks that the token belongs to the username you enter.

      By Bence Redmond

    • For organizations with GitCafe enabled, threads can work across several repositories when one of them is on GitCafe, instead of failing to check out or attach the other repositories. 

      Additional repositories cloned into a thread, and repositories added during a thread, now work with GitCafe, and the agent can push from them. GitHub repositories in a thread whose main repository is on GitCafe also keep their access after the first hour.

      By Bence Redmond

    • For organizations with GitCafe enabled, a pull request opened on GitCafe from a thread's branch now appears on the thread, with its status, checks, and merge state, after the agent next pushes to that branch. 

      Hoplite links the thread to the one open GitCafe pull request from the thread's own repository whose head matches the pushed branch. Pull requests opened from forks are never linked, and pull requests you unlinked from a thread stay unlinked.

      By Bence Redmond

    • For organizations with GitCafe enabled, pull requests merged or closed on GitCafe now show as merged or closed in Hoplite, and threads that follow pull request activity are told about new reviews, comments and finished checks. 

      Previously a GitCafe pull request linked to a thread could stay open in Hoplite after it merged. Hoplite now receives signed GitCafe pull request events, so merges and closes show up and finished threads can be archived.

      By Bence Redmond

    • GitCafe repositories no longer disappear for workspaces using GitCafe. 

      Workspaces connected to GitCafe sometimes lost their GitCafe repositories in the sidebar, the new thread dialog, repository import and settings when a page loaded. They now stay visible whenever the workspace has a GitCafe connection.

      By Bence Redmond

    • For organizations connected to GitCafe, agents and projects can read repository files, project skills, repository settings, code search results and commits. 

      GitCafe rejected the branch format Hoplite sent, so file reads, tree listings, code search and commit lookups on GitCafe repositories failed. Hoplite now sends branches, tags and full commit hashes in the form GitCafe expects.

      By Bence Redmond

    • For organizations with GitCafe enabled, existing threads keep working after you rename or transfer a GitCafe repository and sync the connection. 

      Threads started before a GitCafe rename or transfer failed to commit, push or show their diff, saying the project had no repository. Syncing the GitCafe connection now moves those threads to the repository's new name, so they continue on their next message.

      By Bence Redmond

    • Settings changes apply instantly instead of waiting for the server 

      Switches, pickers, member roles, invitations, environment variables, skills, instructions and integration permissions now update the moment you change them, and stay usable while they save. Rapid changes save in order. If a save fails, the setting returns to its previous value and Hoplite explains what went wrong. Billing, new keys and sign-in steps still wait for confirmation.

    • Threads on a brand-new repository show their changes before the first push 

      When a thread starts on a repository that has nothing pushed yet, its changes panel now lists every file the agent created instead of staying empty. Once anything is pushed, changes are compared with the repository's base branch as before.

      By Odin Glynn-Martin

    • Agents no longer start an extra turn when a pull request closes mid-run 

      When an agent merged or closed a pull request near the end of a turn, it could start another turn by itself seconds later and spend credits you never asked for. A close during a turn now reaches only that turn. Closing a pull request while the thread is idle still wakes the agent.

      By Bence Redmond

    • A lost sandbox no longer rolls back your agent's recent edits 

      When a sandbox was lost mid-run, Hoplite restored a recovery snapshot that was often 15 minutes to over an hour old, so recent edits disappeared. The workspace now moves forward to the newest saved checkpoint of those edits when that cannot overwrite anything, usually losing only the last minute or two. Dependencies, build output and processes still come from the snapshot.

      By Odin Glynn-Martin

    • Opening a thread now puts your cursor in its message box 

      After you opened a thread from the sidebar, the threads list or the command palette, what you typed went to the list instead, and a message starting with "c" opened New Thread. Now typing goes straight into the message box. Moving through lists with the keyboard works as before, and phones and tablets keep their keyboard closed.

      By Bence Redmond

    • New versions of Hoplite no longer reload the page while you work 

      When we ship an update, an open Hoplite tab now waits until you switch away from it or leave it idle, then reloads once onto the new version. Clicking or navigating no longer triggers a reload, and a tab no longer reloads several times during one release. You can still apply an update straight away from its notice.

      By Bence Redmond

  5. Features

    • New threads open the moment you press Enter 

      Sending a prompt from Home or the new-thread dialog now opens the new thread straight away, with your prompt already in place, instead of keeping the previous screen up while the thread is saved and its page loads. If the thread can't be started, your prompt and attachments come back for you to retry.

      By Bence Redmond

    • Connect your Claude, ChatGPT or Grok subscription while setting up a new workspace 

      New sign-ups now get a step after GitHub to connect the Claude, ChatGPT or Grok subscriptions they already have, so agents can run on those plans from the first thread. Claude takes a token from claude setup-token; ChatGPT and Grok sign in with a one-time code. Every connection is optional, and you can add or change them later in Settings.

      By Bence Redmond

    • Ask your parent agent to switch a subagent’s model without starting over 

      For subagents started after this update, your parent agent can select another allowed model from the same provider at the next saved step, keeping the conversation and workspace. You can move ongoing work to a cheaper model without recreating the task. Subagents that inherit a subscription or connection model still use that model.

    • Refresh a custom endpoint’s models from Settings without reconnecting it. 

      Workspace owners and admins with custom model endpoints can refresh their available models from Settings → Models. Hoplite reuses the saved connection and credentials, so there’s no need to remove and re-add the endpoint. Existing model overrides are preserved for models that remain available.

      By Bence Redmond

    • Drag the sidebar's right edge to make it wider or narrower and it keeps that width; keep pulling it in to close it fully, and open it again from the button at the top left. 

      Resize the sidebar by dragging its edge or with the arrow keys once the edge has focus. It stops before its icons would be cut off; push past that point and hold, and it closes so pages run edge to edge. The close button now closes it fully too.

      By Owais Korejo

    Fixes

    • Let parent agents archive their child threads 

      Parent agents can archive the child threads they created without an API key. Thread tools also explain how to choose a different model when sending a follow-up message. Subscription and connection model restrictions still apply.

    • Create pull requests when repository commit hooks require unavailable tools 

      Creating a pull request could fail while saving your changes if a repository commit hook required tools unavailable in the workspace. Automatic commits now complete without running those hooks, so you can publish your changes for review.

      By Odin Glynn-Martin

    • Connecting an MCP client now reaches the consent screen after you sign in 

      When an MCP client sent you to Hoplite to approve access and you had to sign in first, signing in could drop you on your threads instead of the approval screen, so the client never connected. Signing in now returns you to the consent screen to finish connecting.

      By Bence Redmond

    • Attach files before starting a new thread 

      Uploading an attachment before sending the first message no longer fails with a thread-not-found error. Browser uploads and desktop attachment staging now work before the thread has been created.

      By Odin Glynn-Martin

    • Subagents retry empty model responses without requiring you to resume them 

      An empty model response no longer immediately stops a subagent and asks you to resume it. Hoplite retries automatically from saved progress. If repeated attempts still produce no usable response, the subagent stops and explains that the retry limit was reached.

  6. Features

    • Automation templates now arrive with their trigger set up, ready to save 

      New automation now offers a blank start or templates grouped by source, such as schedules, GitHub, Linear and Slack. Each template opens the editor with its trigger and instructions filled in, including new ones for reviewing pull requests, fixing failing CI and investigating flagged Slack messages. Templates for integrations you haven't connected link to their settings instead.

      By Bence Redmond

    • Threads running on Claude Code show its thinking while it works 

      When a thread runs on Claude Code, its reasoning now appears as a live thought while it works out what to do next, instead of a blank screen until the first reply or tool call. The thought clears as soon as the reply or tool activity starts.

      By Bence Redmond

    • Follow-up messages in threads with an existing workspace start responding sooner 

      When you send a follow-up in a thread whose cloud workspace already exists, Hoplite now wakes that workspace once instead of twice before the agent starts, so the reply typically begins about a second sooner. Follow-ups that already start from saved workspace context are unchanged.

      By Bence Redmond

    • Sign-up is shorter, and new workspaces pick a first agent task on Home 

      Onboarding now runs sign-in, a workspace name, then GitHub. The name comes prefilled with your company's name for a work email, or your own, so Continue or Skip keeps you moving while the workspace is created in the background. With a repository connected, the app then offers six first tasks, such as touring the codebase or fixing a real bug. Start one or several and Hoplite opens the first thread.

      By Bence Redmond

    • Team workspaces get three times the sandboxes and minute-level automations 

      Team workspaces now allow 150 concurrent sandboxes per seat, 500 new threads per hour, 100 active automations on schedules as often as every minute, and 500 iMessages per day. Existing Team subscriptions get the new limits automatically. Workspaces moving to Plus from now on run sandboxes up to 8 vCPU and 32 GiB RAM; workspaces already on Plus keep 16 vCPU and 64 GiB.

      By Bence Redmond

    Fixes

    • Ask to reconnect Claude when its sign-in stops working 

      When Anthropic stops accepting a connected Claude subscription's sign-in during a run, the run now stops right away and asks you to reconnect Claude in Settings → Models, instead of retrying for a few minutes and failing with a generic error.

      By Odin Glynn-Martin

    • Import thread history when personal skills cannot be added 

      Importing local conversations continues when your personal skill library is full or already contains a selected skill. The CLI reports which personal data was skipped and keeps discovery warnings in a scrollable details view so project choices stay visible.

      By Odin Glynn-Martin

    • Mac app messages show attached image previews instead of warning links 

      In the Mac app, screenshots and other images attached to messages appeared as links with a warning icon instead of a preview. They now load inline again, and clicking one opens the full-size viewer. The fix reaches the Mac app with its next update.

      By Bence Redmond

    • Resolve team invitations during signup to continue with Free 

      Choosing Free during signup now explains when members or pending invitations exceed its one-seat limit. You can remove extra members or cancel invitations and continue with Free instead of being left with a disabled button.

      By Odin Glynn-Martin

    • MCP tools stop failing after token refresh 

      Integrations connected through OAuth sign-in no longer fail tool calls or drop out mid-task when their access token renews in the background. Their tool names also stay the same across renewals, and agent steps no longer rebuild their setup after each renewal, so long tasks keep responding quickly.

      By Bence Redmond

    • Send follow-ups and attach files sooner after starting a thread 

      Starting a thread kept its composer waiting until the thread's title had been written, so a quick follow-up or attachment was held back for a few seconds. The title now arrives on its own once it is ready, and the composer is available as soon as the thread is created.

      By Bence Redmond

    • Reconnect Paper to view designs inside threads 

      Paper connections now request the permission needed to display designs inside threads. If Paper tools work but previews are denied, an organization admin can reconnect Paper in workspace integrations to authorize preview access. Available to organizations with Paper enabled.

      By Odin Glynn-Martin

    • Previews that redirect no longer read as broken after the agent starts them 

      Apps that redirect their home page outside the sandbox now count as running, and a failed check names the network error. When pausing the sandbox stops a server the agent started by hand, that port’s Preview tab says so and links to the managed preview when it is running.

      By Bence Redmond

    • Queued messages start promptly while Hoplite replaces its servers 

      While Hoplite replaced servers, a thread could stop picking up work, leaving your next message waiting until you sent another or a background check found it. Threads now retry and start queued messages on their own, and in-flight steps move to healthy servers right away. Runs blocked by a Claude spend limit or an unsupported model now fail within seconds.

      By Bence Redmond

    • Agents can share screenshots straight from their scratch folder 

      Screenshots and recordings the agent saves in its /tmp/verify scratch folder can now be shared in the thread directly. Before, sharing them failed, and agents often copied the files into your repository first to get them through.

      By Odin Glynn-Martin

    • Runs no longer stall for up to 20 minutes on an unresponsive sandbox 

      When a sandbox stopped responding while commands were still running on it, an agent run could wait up to 20 minutes before Hoplite moved its work to a fresh sandbox. Recovery now starts as soon as the sandbox is confirmed unresponsive, and later steps no longer recheck it. Recovery still depends on an available snapshot.

      By Bence Redmond

  7. Features

    • Choose which models your Cloudflare AI Gateway connection offers in workspace settings 

      When adding a Cloudflare AI Gateway, workspace admins can now list the provider/model ids it serves, such as Anthropic models, instead of one fixed model. Hoplite checks that each model can call tools before adding it. Available to workspaces with custom gateways enabled.

      By Bence Redmond

    • Pull requests and commits can belong to the person who started the thread 

      Commits can be authored as your linked GitHub account and pull requests opened as you via Hoplite, so reviewers see whose work it is. It is on by default for new workspaces; owners of existing workspaces can turn it on in workspace settings. Commits credit Hoplite as a co-author, which you can turn off in your profile. Automations still commit as Hoplite.

      By Bence Redmond

    • Retry every thread that stopped for credits from the Billing page 

      Threads that stopped when your workspace ran out of credits never restart on their own. Once runs can start again, owners and admins see how many stopped in the last 14 days and can retry them all after confirming.

      By Bence Redmond

    • Settings opens over your work, organized by Account, Agents, Project and Organization 

      Settings now opens as one large window over the page you were on, and closing it returns you there. Pages are grouped into Account, Agents, Project and Organization, with a project picker for project settings. Search finds individual settings and jumps straight to them. Every page has been redesigned, and existing settings links keep working.

      By Bence Redmond

    Fixes

    • Threads using a connected Claude subscription no longer fail when Claude works on a single turn for more than five minutes. 

      Long Claude turns were cut off at five minutes and retried from scratch until the run failed or was stopped. They now run until Claude finishes, within the step's normal time limit. A startup fault that occasionally made a Claude step wait a minute before retrying is also fixed.

      By Odin Glynn-Martin

    • Threads running on a Claude subscription no longer fail calling Hoplite's built-in tools 

      In threads paid by a connected Claude subscription, the agent sometimes called a Hoplite tool, such as workspace, subagent or thread management, by a name the session rejected, so the call failed with a missing-tool error. Those calls now reach Hoplite's tools.

      By Bence Redmond

    • The Mac installer uses standard compression that company antivirus scanners can inspect 

      Some company networks blocked the Hoplite for Mac download because their antivirus could not unpack its Apple-only compression. New installers use the standard compression most scanners read, so they no longer need an exception for that reason. The download is about 10% larger. Updates to installed apps are unchanged.

      By Bence Redmond

    • In the Mac app, choose to run cloud project threads on your Mac 

      New-thread composers in the Mac app again offer Cloud, Worktree, and Local. Cloud projects can run on your Mac through your installed Claude Code or Codex account, and unavailable locations explain what’s missing. The web app is unchanged.

      By Odin Glynn-Martin

    • The Mac app quits reliably and keeps local projects working 

      Quitting no longer hangs when the local agent stops responding: the app waits at most 30 seconds to pause local runs, then quits, and interrupted runs stay paused for you to resume. Opening a local project while cloud sync is still starting no longer shows an error page, and the model picker no longer reports Claude Code as missing after a restart.

      By Odin Glynn-Martin

    • Adding a suggested MCP server like Neon now opens ready to sign in 

      In project MCP settings, Add on a suggested or featured integration such as Neon, Stripe, Supabase or PostHog used to open an empty server form. It now fills in the provider's server address and sign-in method, so you only approve access in the provider's window. Suggestions that cannot be set up this way are no longer shown.

      By Bence Redmond

    • Slow-starting replies on organization model connections no longer fail with a generic error 

      Some organization model connections hold back their first response until a long reasoning turn has finished. Hoplite abandoned each attempt after two minutes, then showed a generic error. It now waits over four minutes per attempt on these connections. If a connection still never starts responding, the run reports that the AI provider is overloaded instead of showing a generic error.

      By Bence Redmond

    • Claude models through an OpenRouter connection now use prompt caching 

      Threads running a Claude model through your organization's OpenRouter connection were billed full input price on every step because no part of the prompt was cached. Hoplite now marks the stable instructions and recent conversation for caching, so repeated context costs less on your OpenRouter bill. Other gateway connections are unchanged.

      By Bence Redmond

    • Slack recognises the admin who connects it, even with a different email 

      Mentioning Hoplite in Slack no longer blocks the admin who connected it when their Slack and Hoplite emails differ. Connecting Slack now links the Slack account that approves it. If Slack was already connected, the admin reconnects once in Settings → Integrations → Slack, approving with their own Slack account. Unmatched accounts now get a reply naming the email checked and how to link or invite it.

      By Bence Redmond

    • In a subagent's tab, Stop, Resume and Start over now take effect instead of failing with “Couldn’t stop this subagent” 

      These controls were rejected every time, so a running subagent kept working after you pressed Stop and a failed one could not be recovered from its tab. Stop now ends a running subagent, Resume continues a stopped one from its last saved step, and Start over runs it again from the beginning.

      By Odin Glynn-Martin