New In Hoplite

Coding agents can explicitly enable autofix for a linked GitHub pull request without changing project or organization defaults. Activation is confirmed before the agent reports success. Requests to monitor comments remain separate from permission to make automatic fixes.

By Odin Glynn-Martin

Select multiple threads and right-click to turn auto-fix on or off for their linked pull requests. Threads without a pull request are skipped, and auto-merge settings stay unchanged. Workspace permissions and billing restrictions still apply.

By Odin Glynn-Martin

Every plan lists the same rows for seats, included usage and concurrent sessions per seat, so the differences line up at a glance. A paused workspace reopens on the plan it was on, and the footer states the price for your chosen seats and billing period before you check out in Stripe or confirm a change.

By Bence Redmond

For organizations in the first-message rollout, Hoplite starts finding reusable project context while accepting your message and uses recent repository updates to avoid an extra GitHub lookup. Changed or unavailable context still falls back to the live workspace before tools run.

By Bence Redmond

Open the Text size section under Appearance to choose Small, Default, Large, or Extra large. Changes apply immediately across Hoplite and stay saved on this device after a reload. Default keeps the existing display-aware sizing, and the section can be collapsed when you're done.

By Odin Glynn-Martin

Confirmations name the action and show exactly what they affect. The command palette groups and highlights results, keyboard shortcuts show what applies to the current page, the setup checklist sits in the sidebar and counts as done after four steps, and feedback opens from a button beside your account.

Ask Hoplite in Slack to enable autofix for a coding thread or its linked pull request. Hoplite can activate the CI and review fix loop and confirm its state without asking the coding thread to change settings. Your existing permissions and access requirements still apply.

By Odin Glynn-Martin

Connecting an app, signing in to the Hoplite CLI, and accepting a workspace invitation now use one wide panel centred on screen: Hoplite and the other side on the left, what it gets on the right. A long permission list scrolls inside the panel, so Allow and Deny stay in view. Phones keep a single column.

By Bence Redmond

After importing local history, opening your threads in the browser no longer closes the CLI. Import errors and manual browser links remain visible until you choose to exit. Sign-in instructions explain when to return to the terminal; Windows continues to support onboarding and handoff, while the coding-agent terminal remains available on macOS and Linux.

By Odin Glynn-Martin

The Hoplite CLI listed separate 1M context entries, such as Claude Haiku 5.5 (1M context), next to their base models. It now shows one row per model, as the web app does, and the base model uses its long context window automatically. A request for a model the provider does not serve now fails right away instead of retrying for several minutes.

Once the download infrastructure update is applied, versioned CLI downloads cannot be replaced or deleted by a release publisher. Existing download links keep their original files, while the latest-version pointer can still advance normally.

By Odin Glynn-Martin

The activity dropdown no longer leaves a large empty gap after the timer, keeping its arrow close to the action label as the run progresses.

By Odin Glynn-Martin

The demo's PostHog settings now start with a redacted example instead of a token-shaped value. Editing and saving the example keeps the same masked display without including an underlying authentication value.

By Odin Glynn-Martin

First messages that reuse cached repository context prepare independent work together, reducing the wait before the model starts without changing its instructions or available tools.

By Bence Redmond

For organizations in the first-message dispatch canary, newer work on unrelated branches no longer prevents agents from reusing verified project instructions from recent main history. Instructions and configuration are still checked, and uncertain results fall back to fresh workspace context.

By Bence Redmond

Threads on Haiku 5.5 reported that the context limit was reached at about 50,000 tokens, even though the model showed a 1M window, and selecting its 1M version failed outright. On paid plans, both now run up to the full window and summarize history only as it nears that limit. Calls above 100,000 input tokens are billed at the long-context rate.

Delegating several Linear issues at once no longer requires a new mention when a request hits a temporary processing problem. Each delegation retries independently with backoff and keeps the same Hoplite thread. If processing still cannot succeed, Hoplite reports the error in Linear.

By Odin Glynn-Martin

When developer login is enabled, the local API accepts direct connections only from the same machine. Standalone previews also stay local. Managed preview workflows remain available, while normal deployments keep their existing network listener.

By Odin Glynn-Martin

Public preview visitors can no longer use developer shortcuts to sign in. Authorized sandbox QA sessions remain available, and local development shortcuts are unchanged.

By Odin Glynn-Martin

The model dropdown keeps descriptions, speed, intelligence and context limits without displaying token prices. Subscription and connected-account labels remain available, so you can still see which account a model uses.

By Odin Glynn-Martin

Changing the model in an existing thread used to warn that all previous context would be compacted, even though most switches keep the full history. In the web app, the warning now appears only when the thread no longer fits the new model's context window, and it says why: the transcript will be summarized before your next message.

The copied onboarding command starts the installed Hoplite CLI directly, so another same-named program on your machine won't be selected instead. The same setup command continues to work across supported operating systems.

By Odin Glynn-Martin

Starter threads use a repository-backed project instead of an empty default project. If a starter request fails, onboarding stops retrying automatically and lets you retry deliberately, preventing repeated conflict errors during setup.

By Odin Glynn-Martin

The Preview tab keeps its port number on the same text baseline as the label, so the number no longer appears to float above it.

By Odin Glynn-Martin

Repository guidance is now presented as clearly labeled reference data. Local coding conventions remain available, with explicit boundaries against overriding your request or granting additional permissions.

By Odin Glynn-Martin

Older supported OpenAI models share the project's initial prompt cache routing, while later steps keep thread-specific routing. Cache controls now follow the resolved provider model, helping supported models reuse shared instructions without changing prompts or reasoning settings.

By Bence Redmond

The synchronization service uses updated address parsing dependencies. This maintenance update takes effect with the next service deployment and preserves existing synchronization behavior.

By Odin Glynn-Martin

Workspace preparation now keeps the thread branch available as the upstream branch after fetching it, so resumed sessions can finish their steps even when the workspace was cloned from a different branch.

The managed browser command interface now rejects attempts to switch to another browser session or control sessions outside the task. Normal preview browsing, screenshots, recordings, and page inspection remain available.

By Odin Glynn-Martin

Standard and 1M-context versions now share one model choice in the new-thread dialog. Eligible credit- and provider-key-backed runs use the larger context automatically; subscription-backed runs retain their supported limits. Organization model restrictions also apply to automatic long context. Existing selections and favorites keep working, and provider usage still determines the billed tier.

By Odin Glynn-Martin

The galloping horse now sits vertically aligned with the working status label in thread conversations.

By Odin Glynn-Martin

The working indicator displays one horse pose at a time, preventing flashes from neighboring animation frames. Playback preserves the original artwork and honors reduced-motion settings, including changes made while the app is open.

By Bence Redmond, Odin Glynn-Martin

Auto fix appears between divider lines, matching the New messages marker. Expand it to inspect each fix pass while keeping the pass count and current status visible.

By Odin Glynn-Martin

Starting or resuming a repository thread checks both branches together and downloads changed branches in one transfer, reducing repeated work before the agent starts. Your local changes remain intact, and the agent can still inspect files while workspace setup runs in the background.

By Odin Glynn-Martin

See which projects, members, or invitations prevent a switch to Free and remove them directly in the billing dialog. Each removal requires confirmation, and connected GitHub repositories stay untouched. The dialog checks the limits again before enabling the downgrade.

By Bence Redmond

Each sandbox size has a fixed hourly price, from $0.08 for X Small to $1.50 for X Large, billed per second while running, idle time included. Sizes give 4 GiB per vCPU; unsized sandboxes are Medium, and Plus allows up to 32 GiB. Sandboxes burst to their size and step up a size after running out of memory. Cost counts toward usage credits and spend limits. Only new sandboxes are billed.

By Bence Redmond

Muse Spark 1.3 is no longer offered, and Free-plan requests no longer use Meta's Contributor route. Threads and projects that had Muse Spark selected now use GLM 5.3 Flash, and earlier Muse Spark usage keeps its original rates.

By Odin Glynn-Martin

When you return to a thread, whether from another thread or from another tab or app, a "New" divider now sits above the first reply or teammate message that arrived while you were away, and the thread opens with it in view. Your own messages never count. Leaving and coming back with nothing new clears it, and so does reloading the page.

By Odin Glynn-Martin

When a plan or trial ends, you can still open threads, diffs, pull requests and settings instead of a blocking screen. A banner at the top names the end date and resumes the plan in one click; members are pointed to an owner. Starting new agent work stays off until the plan resumes. Integration sign-in results now show a clear page with a way back to Hoplite.

Track workspace and platform-console spend, export usage and explore member and project breakdowns on Plus. Plus also gets Team's sandbox sizes, concurrency and automation limits. The plans retain their separate prices and included credit allowances.

By Bence Redmond

CLI sign-in, password reset, invitations, two-factor, app approval, and error pages use one clear panel in light and dark themes. Two-factor accepts a pasted code and explains a wrong code on the page. App approval opens on its own page and shows the workspace and account it will use. Error pages show a reference you can copy for support.

By Bence Redmond

The tool output condenser saves context automatically on the free plan. Upgrading turns it off and reveals the setting, so you can choose whether to use it on a paid plan. The experimental badge has been removed.

By Odin Glynn-Martin

The task bar no longer shifts to the right on desktop. Its header and expanded checklist use consistent spacing, and long task summaries leave room for the progress count and expand control.

By Odin Glynn-Martin

For customers included in Hoplite's Attio integration, one rejected customer update no longer stops later customers from syncing. The rejected record is reported and retried on a later refresh after its data is corrected.

Agents can recover a completed browser download when its initial event is missed. Downloads verify that the new file exists before reporting success, so an older file cannot hide a failed download. Available in sandboxes using the updated browser image.

By Odin Glynn-Martin

When browser code throws an unusual value, error reports retain its type and available stack so support can distinguish failures and find their origin. Reports continue to exclude arbitrary customer payloads.

By Odin Glynn-Martin

Organizations enabled for Claude Code can start unattended runs again. Sessions now use a supported permission setting while retaining restrictions on the tools they can call. The engine remains available only to enabled organizations.

The live working indicator and activity dropdown now use the same font, size, and weight as the completed Worked for message. Status text stays consistent as an agent finishes, in both light and dark mode.

By Odin Glynn-Martin

Clicking an archive or another file that cannot be previewed downloads it to your device. The file preview also has a clearly labelled download button and shows the file size when available, so saving a file no longer requires opening a raw file tab.

By Odin Glynn-Martin

After the worker update deploys, agents inspecting their tools will see the available commands for reading files, editing code, and continuing running commands. This helps delegated tasks find existing workspace access and continue their work instead of incorrectly reporting that it is unavailable.

By Odin Glynn-Martin

For organizations in the first-message dispatch canary, agents can reuse verified project instructions after unrelated source updates instead of waiting for a workspace to start. Changes to instructions or configuration still require fresh context, and every planned action waits for the current checkout to be verified.

By Bence Redmond

When a cloud goal is not met yet and Hoplite keeps working, the thread now shows a quiet "Goal not met, continuing" divider instead of a chat bubble attributed to you, and the continuation no longer appears in the queued messages panel. The agent now receives the continuation the way its own tooling sends it, as an instruction from the harness rather than something you typed.

By Odin Glynn-Martin

A new goal appears once as your message and the agent starts on it, or once the current run finishes. Pausing or deleting from the goal bar leaves the chat untouched, and resuming shows a short divider. Typing /goal on its own still answers with the current status.

By Odin Glynn-Martin

Each run a goal queues uses the same model, reasoning effort, and speed as the run that started or resumed the goal, including resumes from the goal bar. Previously, a goal started at max effort continued at medium.

By Odin Glynn-Martin

GPT exploration agents using inline delegation can read repository instructions and run workspace commands instead of reporting missing tools. Their nested tool calls remain scoped to the delegated agent, without access to parent-only platform controls.

By Odin Glynn-Martin

See which linked pull requests are still waiting without opening GitHub or hovering each number. The clock’s label distinguishes running CI from the merge queue, and disappears once the pull request settles.

By Odin Glynn-Martin

When you interrupt an active cloud run to send a queued message, the agent retains the work it completed since your previous message. Follow-up prompts can continue from those results even when the interrupted run’s conversation record is still being saved.

By Odin Glynn-Martin

After the worker update deploys, refreshed agent workspace hooks separate co-author credit from merge commit titles. This keeps the title readable and lets Git recognize the co-author trailer. Existing repository hooks and the option to disable co-author credit continue to work.

By Odin Glynn-Martin

Ongoing model text stays inside the working accordion while the agent decides its next step, so it no longer appears as a reply and jumps into the activity history. Open the accordion to read it live. Confirmed replies appear as normal messages.

By Odin Glynn-Martin

After the worker update deploys, agents can link a pull request from another authorized project repository. Review feedback and fixes use that repository's checkout, keeping the thread's primary repository separate. Additional-repository autofix requires a Modal or Daytona workspace.

By Odin Glynn-Martin

Agents can connect eligible pull requests to their tasks and activate permitted review auto-fix even when workspace tool verification is unavailable. Repository access and auto-fix permissions still apply. When linking is unavailable for another reason, agents continue checking CI and reviews manually without claiming automatic follow-up is active.

By Odin Glynn-Martin

Preview gives its browser checks a separate startup window, reducing timeouts when remote commands take longer to start. If a health probe fails, agents receive a clear verdict while the running app remains available. Available after the worker update is deployed.

By Odin Glynn-Martin

After the worker update deploys, an agent's next integration request opens a fresh session when the previous connection failed. Tool discovery also refreshes. Failed requests are reported without automatically repeating an action, and cancellation still stops the session.

By Odin Glynn-Martin

Add pull requests to the merge queue when the target branch requires it. Repositories that allow only squash merging show only squash and merge, so unavailable merge methods no longer appear as choices.

By Odin Glynn-Martin

After deployment, workspace preparation no longer stops at Git's ownership check when installing platform exclusions in a managed repository. Agents can continue with their existing files, while the ownership exception stays limited to that repository.

By Odin Glynn-Martin

When a model leaves the model picker, threads already using it keep running on it. Their message composer now names that model and sends your next message on it, instead of warning that the model is no longer available and asking you to choose another. You can still switch models at any time.

Older scheduled wakes on existing threads can resume coordination without a new human message. Hoplite verifies the saved schedule and execution before restoring access, and still enforces the creator’s current permissions, thread boundaries, and write limits.

By Odin Glynn-Martin

Retrying a failed thread continues from the existing conversation instead of sending your last message again. The agent receives a platform continuation notice with the failure reason, and the transcript marks the resumed point as Agent continuing from here.

By Odin Glynn-Martin

Hover over your message or a teammate’s message to see its timestamp without a background or card. Short messages keep the timestamp on one line, clear of the message text.

By Odin Glynn-Martin

For organizations with workspace warming and first-message parallel dispatch enabled, warm workspaces now prepare reusable project context before a thread has run on that commit. Captures run in the background and cannot hold up workspace readiness or adoption. A newer commit is captured again after the adopted workspace finishes setup.

By Bence Redmond

Thread activity shows workspace setup progress and completion as plain status rows with elapsed time. These rows no longer open a dropdown or display setup commands, logs, or other details.

By Odin Glynn-Martin

On paid plans, threads on a GPT model with a 1M option now use the long context window without choosing a separate 1M model, so long threads keep their history far longer before it is summarized. Each call is billed at the tier the provider charges: standard rates up to 272,000 input tokens, long-context rates for the whole call above that. Threads running on a ChatGPT subscription keep the standard window.

The Diff view replaces file tabs with a folder tree, a filter, and one continuous scroll of every changed file. Mark files as viewed, collapse them, and step between files with the [ and ] keys. Comment on a line or a range in place, then send all your comments to the agent together.

By Bence Redmond

Hoplite reads a new workspace's setup files while it checks out your repository, so the Workspace setup step settles as soon as the sandbox is ready when there is nothing to install. Repositories with a setup command also skip the repeated file checks before their command starts.

By Odin Glynn-Martin

Pause briefly while typing in the settings sidebar to open the top matching page automatically. Your search stays active so the page shows matching options, and your selected project stays in scope. Clearing the search cancels pending navigation.

Fresh workspaces and their nested submodules start with the selected revision and its files, without downloading other branches, tags, or earlier history. Agents can fetch additional history when a task needs it. Existing workspaces keep their history.

By Odin Glynn-Martin

Subagent rows show their task names and status without generated profile pictures, leaving more room to read what each subagent is doing.

For customers included in Hoplite's Attio integration, refresh checks who owns a changed email before updating it. Conflicts preserve the existing person link and allow later customer updates to continue. The email is checked again on the next refresh, so syncing can recover once ownership is corrected.

By Odin Glynn-Martin

New workspace images include the browser CLI’s runtime skill content alongside its installed binary, so agents can load browser automation instructions directly from the CLI.

By Odin Glynn-Martin

An active Claude connection unlocks Claude models for its member on Free workspaces, including project defaults. Runs use that member’s subscription and refuse platform funding when it cannot pay, so connecting Claude no longer requires a workspace upgrade.

By Odin Glynn-Martin

Agents can omit personal co-author credit for one commit or the rest of a workspace without disabling repository hooks. Existing repository commit hooks continue to run.

By Odin Glynn-Martin

Follow-up messages and connected integrations can react when a run finishes or their queued message starts, without waiting for the next periodic check. Recovery checks remain available if a worker restarts or the notification connection is interrupted.

By Odin Glynn-Martin

Stopping an active model call or tool updates the thread as soon as its work has settled. Explicit steering interrupts model work without waiting for a separate cleanup job. Completed tool results are preserved, and ordinary messages still wait for the current step.

By Odin Glynn-Martin

Agent file writes stage their content outside repository source directories. Android resource builds and broad Git staging no longer pick up temporary editor files while edits are being written.

By Odin Glynn-Martin

GitHub updates keep moving during large queues, and new pull request details and checks refresh while older automation catches up. Repository access checks and the order of updates stay enforced.

By Odin Glynn-Martin

Recovery keeps GitHub delivery IDs intact, allowing missed repository updates to be retried when GitHub uses larger identifiers. Previously, these identifiers stopped recovery before it could request a retry.

By Odin Glynn-Martin

GPT agents can now mark their goals complete or blocked, or pause them when you ask. Retried goal updates return the saved result, so completed work doesn't restart and newer goals stay untouched.

Your iMessage stays linked while a workspace is paused, so there is nothing to pair again. The reply names what is blocking the workspace and where to fix it, and messages work again as soon as billing is sorted.

By Bence Redmond

Punctuation values returned in identifier fields no longer rewrite slashes in comments, markup or non-English text. Existing thread bindings remain readable when an agent resumes work.

By Odin Glynn-Martin

When Meta restricts access to Muse Spark, Hoplite stops repeating the rejected model step and reports that the provider account is unavailable. Contact support before trying again. This handling does not lift the restriction or change model availability.

By Odin Glynn-Martin

Modal commands clear the provider’s inherited Python search path, preventing package setup from scanning inaccessible directories. Explicit project and command search-path overrides remain available.

By Odin Glynn-Martin

Subagent results now import successfully when a restored workspace's repository belongs to a different workspace user, so committed work can return to the parent thread.

By Odin Glynn-Martin

Projects pinned to an exact pnpm 12 or later release receive its native executable during setup, avoiding launch failures in tools such as Turbo. Project files and dependency build approvals stay intact. Repositories with an explicit mise tool declaration keep that selection.

By Odin Glynn-Martin

Agents refresh the attachment list when rebuilding their workspace context, so newly uploaded documents, videos and archives become available promptly during an active conversation.

By Odin Glynn-Martin

If the GitHub App is uninstalled while a PR review loop is active, Hoplite blocks the loop and turns off auto-merge. The PR view explains that the app needs to be reinstalled and reconnected before you can re-enable the loop.

Preview verification checks that old browser errors were cleared and fresh error results were read successfully. Failed or malformed browser responses report unavailable evidence instead of a misleading page verdict.

By Odin Glynn-Martin

Private Hoplite file links pasted by a run's initiating user or delivered through an authorized agent continuation become available in its workspace. Transfers check current read permission, retain their source, and accept up to five files of 50 MiB each. Continuations can share only files belonging to their recorded source conversation.

By Odin Glynn-Martin

Threads can recover from an unresponsive sandbox when a fresh copy of their work can be captured. Continuing in a new thread can also preserve work without relying on the stalled sandbox's commands. A continuation that failed to start no longer blocks deletion of its original thread once its runs have stopped.

By Odin Glynn-Martin

Readable repository labels and checksums keep their original spelling in command results, summaries and paged output, even when earlier calls used the same values as references. Resuming a thread preserves that behavior, so agents can compare source data and file digests consistently.

By Odin Glynn-Martin

Organizations with a Sazabi connection can request recent logs through the current query API. Queries retain their requested time window and result limit, with optional literal text and service filters.

By Odin Glynn-Martin

You can continue setup without choosing starter threads, and your workspace moves on without queuing any starter work.

Slack now acknowledges agent mentions right away, switches to a working reaction when a Hoplite thread starts, and shows completion when the thread is done or its pull request is ready to merge.

Slack-forwarded requests use Slack as the visible sender in web and mobile thread history, while keeping the original person named as attribution. Native Hoplite messages keep their existing sender names and profiles.

Delegated coding and review agents keep their command tool in both shared and forked workspaces. Nested tool calls can also use sleep, so agents can continue work and wait for commands without reporting missing tools.

By Odin Glynn-Martin

Members can turn on review auto-fix for an eligible thread even when workspace or project defaults are off. The choice stays with that thread's pull request, and defaults for other threads stay unchanged. Auto-merge still requires an owner or admin.

By Bence Redmond

Attachment downloads preserve international filenames without triggering storage errors. Filenames are sanitized and encoded for browsers, including Cyrillic names.

By Odin Glynn-Martin

Agents receive an explicit notice when workspace setup finishes. Missing-tool reports include the tools currently available to that agent, helping it continue with the correct execution and editing tools. Reports remain recorded for investigation, including when an agent retries the same complaint.

By Odin Glynn-Martin

Claude subscriptions are available to every workspace from Personal integrations. Connected members' Claude runs use their own plan without staff enablement. If a connection expires, reconnect directly with a new setup token.

By Odin Glynn-Martin

Scheduled runs use the automation creator’s current access, so coordination can resume without a new human message. Each run has a bounded write budget, and existing thread permissions and reply-chain limits still apply. Webhook automations and automations that start new threads are unchanged.

By Bence Redmond

Agents retry saving completed answers after temporary database connection failures, without generating them again. Stop keeps answers committed beforehand, even if acknowledgment was lost. Steering still discards superseded answers when Stop follows it. Retries are bounded and cannot recover earlier lost answers or survive a worker crash before saving.

By Odin Glynn-Martin

Resuming a conversation no longer stops when saved references compete for the same readable name. Conflicting references keep their original identifiers, while references in signed reasoning retain their original meaning.

For customers included in Hoplite's Attio integration, an email already owned by another person no longer blocks later customer updates. The conflicting customer's existing link stays unchanged and is retried on the next refresh, without automatically merging or reassigning CRM records.

When a thread's images exceed a model provider's request-size limit, the run stops with a clear explanation instead of a generic failure. Start a new thread with fewer images or remove images before retrying; retrying the same oversized request won't help.

When the CLI reconnects, readers from its previous connection can no longer consume the new connection's events. This protects streaming run updates while the CLI resumes an active session.

By Odin Glynn-Martin

Database connection setup and queued connection requests now fail promptly when the database is unavailable. Failed setup connections are discarded before any work is saved, so subsequent requests can establish fresh connections after service recovers. This bounds connection setup waits; it does not change live sync or retry interrupted writes.

By Odin Glynn-Martin

Desktop update checks now match the Pull requests inbox and the unavailable cloud controls when working offline. This removes an obsolete check that blocked publishing. New downloads remain subject to the release process; this change does not itself publish an update.

The local agent now finishes event writes already in progress before shutdown returns and leaves unsent updates available for the next launch. This prevents delayed uploads from writing after the host has stopped.

By Odin Glynn-Martin

Steering reaches a running agent sooner, so it can respond to your new direction without waiting for its current answer. Commands already running still finish safely before the agent replans.

By Odin Glynn-Martin

When GitHub takes too long to respond, Hoplite reports a temporary failure instead of an unexpected server error. Failed attempts leave the saved pull request state unchanged, so you can retry the action after GitHub recovers.

By Odin Glynn-Martin

Hoplite now masks the full length of GitHub’s new installation tokens in errors, preview logs, and tool output. Existing tokens remain protected, and GitHub authentication continues to treat tokens as opaque credentials.

By Odin Glynn-Martin

Runs funded by a connected X or SuperGrok subscription now use the current Grok client version. If Grok requires another upgrade, the run stops immediately with a clear error instead of repeatedly retrying the same rejected request.

GitCafe and iMessage now use recognizable brand icons instead of generic link and phone symbols, both in the integrations list and on their management pages.

By Odin Glynn-Martin

After the production rollout, the live-sync service has more room for growing data and backups, with an early warning before storage fills. This reduces the risk of updates freezing across threads when the sync service runs out of space.

Modal workspace archiving no longer mistakes a checkout ownership mismatch or an interrupted Git check for a missing workspace. Healthy checkouts can be saved before their sandboxes stop, and interrupted checks can retry safely. Workspaces whose files are genuinely missing still require recovery; this change does not discard their running sandboxes.

Deleting a project retries once when a temporary database conflict interrupts the operation. The retry keeps project removal and workspace cleanup together, so an interrupted attempt leaves no partial deletion. Persistent conflicts still return an error rather than claiming the project was removed.

Provider-key rows in workspace model settings now show the Anthropic and OpenAI logos instead of letter placeholders. Where provider keys are available, the familiar marks make each account easier to identify without changing how keys are connected or managed.

Switching a Codex thread to Claude no longer fails when the conversation contains earlier command calls. You can continue the same thread with its existing conversation and workspace instead of starting over.

Threads that previously used Codex's exec tool can now continue with another model without failing when the earlier tool call is replayed. Switching back to Codex still preserves the original tool-call history.

Thread issues now show a quiet divider with a clear message and a subtle refresh icon for direct retries. Click an issue for recovery actions with matching icons, including continuing in a new thread. Codex sign-in issues reconnect your ChatGPT account directly. Technical failure details stay in server diagnostics.

By Odin Glynn-Martin

When enabled, opening Hoplite prepares your recent projects before you start a thread. Workspaces are shared across open tabs and the CLI, replaced after use, and retired after the last client closes or becomes inactive. This rollout is off by default; eligible plans will be selected before release.

By Bence Redmond

For workspaces using Hoplite’s managed Attio integration, refreshes now add missing users and link their People records instead of skipping them. New records include their current activity stage. Existing records still receive only changed values, and retries match existing identities to avoid duplicate imports.

By Ryan Morrissey

One-shot CLI requests can now select a model and reasoning level, including when resuming a thread. Streaming JSON delivers the thread link, assistant text, tool activity, and usage as they arrive, followed by the final result. Existing JSON output stays unchanged.

For selected organizations, new threads can start replying before their workspace finishes provisioning when matching repository context is cached. Repository tools still wait for the live workspace, and changed instructions trigger a fresh plan. Cache misses and Claude Code engine runs keep the existing startup path. This rollout is off by default.

By Bence Redmond

The limited-time 2× usage offer has ended for OpenAI and Anthropic models on the Free plan. New usage consumes credits at standard rates, and model pickers no longer show the offer. Previously recorded usage is unchanged.

By Bence Redmond

The composer's model picker now lists providers on the left and their models on the right, with one search across every provider. Star models to pin them under Favorites, reorder or hide models from Edit models, and hover a model to see its speed, intelligence and price. Favorites and hidden models follow you across devices.

By Bence Redmond

The Models settings page now lists your own accounts and your organization's in the order Hoplite tries them. Owners and admins can reorder keys and gateways, pin a model to one account, remove models from the workspace, set when threads compact, and decide whether members use personal accounts. A new rule sets what happens when a subscription cannot run a model.

By Ryan Morrissey

A new Notifications page in Account settings routes each event (approvals, questions, failed runs, finished runs, failed pull request checks) to your desktop, your phone, or a Slack direct message. Pick a sound or upload your own MP3, skip the thread you are viewing, buzz your phone only when a desktop notification goes unseen, and hold everything during quiet hours.

By Bence Redmond

New workspaces now finish setup on the Free plan and go straight to their first thread, with no plan choice to make first. You can start a Pro trial or upgrade from billing settings at any time. Workspaces with more than one member or more than two projects, and signups where a card is required for Free, still choose a plan during setup.

Plus supports teammate invitations and includes 300 monthly credits per seat, unlimited projects, and boxes up to 8 CPUs and 16 GiB RAM. Current Team subscriptions include 500 monthly credits per seat, 50 concurrent sandboxes per seat, boxes up to 16 CPUs and 64 GiB RAM, and 250 new threads per hour. New credit amounts apply to new allowance periods; staff overrides and grandfathered credit allowances are preserved.

By Bence Redmond

Plus is a new single-seat plan at $20 a month or $200 a year, with up to 15 projects. Pro is now called Team and costs $60 per seat a month, or $600 a year, for new subscriptions. Existing Pro subscribers keep their current price and included credits unless they change plan themselves. Plus and Team are rolling out gradually, so they may not appear in billing settings yet.

When steering is enabled for your workspace, Hoplite receives guidance while a shell command continues. Command output survives worker restarts and remains available after completion or Stop. Your answer appears while cleanup settles. If a provider outage delays cleanup, cleanup stays retryable and stoppable. Interactive commands and screenshots keep their usual behavior.

By Bence Redmond

Open the diff, pull request, each preview port, terminal, subagents, Sentry issue or a file as tabs beside Chat. Split a pane right or down, drag tabs between panes, resize the dividers, and reopen closed tabs. Hoplite remembers each thread's layout in your browser. Phones show one pane with a scrolling tab strip.

By Bence Redmond

When a model request repeatedly fails to connect, agent runs and delegated subagent turns now report the failure after their initial connection attempts instead of replaying the same request for much longer. Temporary connection errors still get their normal retries.

Agent runs now keep a conflicting identifier in its original form instead of stopping the conversation. If an earlier readable name appears again in tool output, it keeps its original meaning.

Agents reuse their prepared project context after commands that leave it unchanged, including in larger projects and projects with linked skills. Reading or waiting for workspace status also avoids unnecessary preparation. Changes to instructions, settings, skills, or repository state still trigger fresh preparation.

By Bence Redmond

The CLI reuses API connections and remembers the project for your repository, reducing setup delays before your prompt is accepted. Editor clients start their session requests while connecting the event stream, and slow connection attempts retry sooner. Signing in or out refreshes the saved project selection.

By Bence Redmond

Updated CLI releases download compressed conversations, reducing the data transferred when you open a thread. Historical tool details also load concurrently, with a fixed limit, while keeping the conversation in order. This improves loading on slow connections; opening a thread still requires a connection to Hoplite.

Agents spend less time preparing conversation history before requesting their next response, reducing pauses that can also delay other conversations sharing a worker. Identifier handling remains unchanged.

By Bence Redmond

Agents reuse previously checked conversation messages when preparing another response, reducing repeated work as conversations grow. New and changed messages are still checked before reaching the model.

By Bence Redmond

After a reply finishes, its change summary refreshes in the background so your next turn can start without waiting for repository history to download. Background refreshes survive worker restarts and cannot replace a newer turn’s changes.

By Bence Redmond

Where shared caching is configured, agent turns reuse verified repository authentication setup instead of repeating it after a worker handoff. Credentials stay in the workspace, and repository access changes, replaced workspaces and expiring credentials still trigger verification.

By Bence Redmond

In the limited fast-interruption rollout, explicit guidance and Stop can interrupt a streaming response immediately instead of waiting for the next check. Queued messages still wait their turn, and missed notifications retain the existing fallback.

By Bence Redmond

Connected X and SuperGrok subscriptions use the current Grok client identity for model requests. If the upstream proxy requires another version, the run stops immediately instead of repeating the same rejected call.

Temporary agent session files no longer block idle workspace archives. When a workspace checkout is missing, Hoplite stops repeating the failed archive and flags the workspace for recovery instead of presenting it as ready. The sandbox remains available for investigation.

Recovery backups now wait until a thread is idle rather than slowing commands during an active run. Threads that finish immediately after setup still receive a backup, and repeated workspace checks reuse recent verification to reduce delays between steps.

By Bence Redmond

Agents can now read files and search your repository while a new thread installs dependencies in the background. This lets them start investigating sooner instead of waiting idle. Edits, command execution, tests, and Preview still wait for setup to finish.

By Bence Redmond

Workspace maintenance commands can now continue through short remaining time limits instead of failing immediately. This prevents a timing-related run failure while preserving the run's own deadline.

When you choose Plus or Team before signing up, finishing setup now keeps that choice and takes you to paid-plan checkout instead of completing signup on Free. Signup without a paid-plan choice can still finish directly on Free.

By Bence Redmond

When a sandbox disappears during an agent run, recovery no longer waits on session activity tied to the missing sandbox. The run can restore its saved workspace and continue instead of failing because the workspace appears busy.

Deleting a project now retries after a rare database conflict, so a temporary interruption is less likely to leave the project in your account.

Agents reuse unchanged built-in tool schemas instead of rebuilding them for each response. Available tools, permissions, and tool behavior remain unchanged.

By Bence Redmond

Agents can reuse repository authentication verified at the start of a run instead of repeating it on the following step. Repository access checks and credential-expiry safeguards remain in place. The first initialization after workspace setup still runs normally.

By Bence Redmond

New threads with default setup and no custom environment can skip a redundant remote branch check before their first response. Existing branches, custom setup, directly accessed workspaces, and uncertain or retried state keep the normal checks.

By Bence Redmond

Video frame extraction now bounds its processing threads, preventing resource-constrained environments from dropping every sampled frame. Existing frame-count, image-size, and processing-time limits remain unchanged.

By Bence Redmond

When a prepared workspace is unavailable, new workspaces transfer less repository history, inspect submodules without scanning unrelated files, and reuse verified runtime detection for the same revision. Toolchain caching and bounded file inspection reduce repeated preparation work. Startup time still depends on repository size and setup commands.

By Odin Glynn-Martin

Integrators who lose a thread ID can page through an app's threads, newest first, instead of searching the event feed. The events endpoint now filters by appId, with projectId as an alias. The Platform API is available to a limited set of organizations.

By Bence Redmond

Recovering missed thread subscriptions now checks bounded batches, reducing background database load while continuing to retry missing follow-ups.

By Bence Redmond

Agents limit how many large cached transcripts they decompress at once. Concurrent conversations wait for a decoding slot while keeping their cached history, reducing temporary memory spikes without adding database reads.

The CLI opens a thread's recent messages and settings together, reducing the wait when resuming or switching threads. Live updates connect in the background, and older messages remain available when scrolling. Requires an updated CLI and API. Repeat resumes also skip organization discovery after the thread's organization has been verified.

By Bence Redmond

After a preview start, Hoplite checks the dev server within a second instead of waiting ten. A workspace woken after its idle timeout stays up for its normal idle interval. The Platform API is available to a limited set of organizations.

By Bence Redmond

Agents can reuse more saved conversation context instead of repeatedly loading it from the database. Large context is cached when it fits, and the stored conversation remains the fallback when caching is unavailable.

When a desktop host has too many unfinished uploads, the cloud reports the transfer limit clearly and delays further thread uploads until capacity becomes available. Sharing, unsharing, other cloud deliveries, and thread deletions keep syncing during that wait.

Background GitHub refreshes avoid loading pull-request records that are still within their confirmation interval, reducing database work while preserving refresh order and installation limits.

By Bence Redmond

Preview starts and checks your configured local services before launching the app and supplies their connection settings without replacing explicit project environment values. Local database health checks now accept the full TCP port range. Unconfirmed service configurations must be reviewed before launch.

By Bence Redmond

When fetching queued webhooks slows, Hoplite spaces out its next batch instead of repeatedly polling a busy database. Slow webhook handlers alone do not reduce the polling cadence. This mitigates contention while the database recovers; it does not prevent external database outages.

Recovering unsettled usage now uses an index of pending platform usage, reducing background database work without changing how charges are calculated.

By Bence Redmond

When a desktop host has too many unfinished thread uploads, Hoplite now reports a temporary limit instead of an unexplained server failure. Local changes stay queued while the host retries after capacity becomes available.

Thread exports and history cleanup preserve complete subagent conversations when transcript compression is enabled. Cleanup keeps every piece needed to reconstruct retained conversations and safely removes superseded history. Compression remains behind its rollout flag.

Setup import now verifies a directory’s repository before attaching its project-specific tools or preview scripts. Unverified directories stay unbound, even when conversation history groups them with a similarly named repository or an old workspace.

By Bence Redmond

Hover over the views panel divider to see the horizontal resize cursor. Dragging and arrow-key resizing keep working as before.

By Bence Redmond

Recovering archived workspaces puts less load on Hoplite as your thread history grows. Workspaces with active runs remain protected, and failed archive attempts keep their existing retry delay.

Agents spend less time between finishing one action and starting the next. Hoplite now reuses the prepared project context across many more steps instead of rebuilding it, so long tasks with many commands, code cells, or helper agents pause less between steps.

By Odin Glynn-Martin

When helper agents or background commands may have changed a project’s instructions, agents now prepare their next response while checking those changes. Output stays hidden until the check passes. If the context changed, the agent rebuilds it before continuing.

By Odin Glynn-Martin

After an agent starts, waits on, or closes a helper agent, or starts or stops a preview, it keeps the project context it already prepared instead of setting it up again. These steps now add less waiting to a task.

By Odin Glynn-Martin

Billing now leads with your available credits, the reset date, and one Add credits button, with the included, prepaid, and spend-limit details as simple rows. Free workspaces see today's remaining usage in the sidebar. When a run stops for a limit, a one-line notice shows what ran out, when it comes back, and the single next step.

By Bence Redmond

View public PNG screenshots in agent replies and load older screenshots as you scroll through reopened threads in Ghostty or Kitty. Proportions stay correct when resizing, and a grey skeleton appears during background loading. Temporarily uncached images retry after scrolling. The image command displays local PNGs and public HTTPS screenshots, including in WezTerm. Available on macOS and Linux, including Ghostty over SSH, outside tmux; private-network, failed, or unsupported images remain clickable links.

By Bence Redmond

When a Codex agent sends a message to a helper agent, lists its helpers, or reports a platform issue, it now carries on with its next step straight away. These actions no longer add an extra setup pause in the middle of a task.

By Odin Glynn-Martin

The composer context panel now uses a compact model-and-token header, a segmented usage bar, and rows for used context, your draft, and free space. Costs stay in a small breakdown below it, with pending and unavailable pricing clearly marked. Explanatory paragraphs and nested cards are removed.

By Bence Redmond

CLI onboarding can import portable Cursor personal skills, local user rules, and project MCP connections. You can supply account rules from a text file. Cloud agents also read repository Cursor rules and skills with their original scope. Import summaries accurately count saved rules. Credentials still require separate consent; account policies, editor settings, and resource-bearing personal skills are not migrated.

By Bence Redmond

The changelog now groups updates by day, with Features first and Fixes below in compact bullet lists. Click the small triangle beside any update to open its details. Permalink buttons are removed, while existing links to individual updates still work.

By Bence Redmond, Ryan Morrissey

When a thread has been idle, the agent can now start working on your next message while its workspace is still waking up, instead of waiting for it first.

By Odin Glynn-Martin

In the limited rollout, Enter guides an active run and Command/Control+Enter queues a message for afterward, on web and terminal. Guide queued messages into the same run without stopping it. Guidance can continue while supported shell commands finish in the background, with their results retained and cleanup stoppable. Existing shortcuts remain unchanged outside the rollout; other running tools still finish before the next model turn.

By Bence Redmond

The subagents panel shows the task each subagent was given again, along with the model, reasoning effort and speed it runs on. A small composer lets you steer a running subagent after its current step or queue a message for the end of its turn, with images, PDFs or videos when its model can read them.

By Odin Glynn-Martin

The agent in a new thread now starts reading your code while the workspace installs its dependencies, instead of waiting for setup to finish first.

By Odin Glynn-Martin

Pull requests now shows 50 at a time, newest first, with keys to move between pages. A search box finds any open pull request by title, number, repository, branch, author or project, across every page.

By Odin Glynn-Martin

Changelog summaries now describe what changed and where it applies, instead of relying on short headlines. Existing updates have been rewritten from their published descriptions, and small square markers replace browser-default bullets. Open the trailing triangle for additional details.

By Bence Redmond, Ryan Morrissey

In the limited steering rollout, messages and guidance get immediate sending feedback, followed by confirmation when accepted. New threads show workspace preparation phases before the agent replies. Live activity labels show planning, reading, editing, running, testing, and tool waits, including the command or file. Guidance is acknowledged again when applied at a safe point.

By Bence Redmond

Agent history skips goal-event lookups for ordinary messages. Orchestrator conversations also avoid loading old replay details that are outside their context window.

By Bence Redmond

When background work changes project instructions during a response, the agent now finishes canceling that response before trying again. This prevents retries from getting stuck behind a discarded response and clears the progress indicator for interrupted summaries.

By Bence Redmond

The sidebar search icon stays centered when the sidebar is collapsed, with no stray mark beside it.

By Odin Glynn-Martin

The CLI documentation now displays its installation examples and sections correctly, without duplicated content or a squeezed text column. Code examples keep their original commands when copied.

By Bence Redmond

Opening the Diff view now loads your changes alongside the viewer, reducing the wait on the first visit.

By Odin Glynn-Martin

New workspaces for Hoplite's own repository no longer wait for optional native tools or Preview services before coding can begin. Starting a Preview still prepares its database and checks migrations, and worker Previews install their required service on demand. Other repositories continue to use their configured setup commands.

By Odin Glynn-Martin, Bence Redmond

Pull requests used to take more than 30 seconds to open on repositories with hundreds of open pull requests. It now opens straight away from a recent snapshot and updates check, merge and review verdicts within a few seconds.

By Odin Glynn-Martin

Credit balances can use verified transactional totals instead of repeatedly scanning ledger history. The rollout keeps existing reads until each organization has been rebuilt and verified.

By Bence Redmond

GitHub request scheduling no longer rewrites unchanged source-control connection records, reducing database and replication work while preserving catalog updates.

By Bence Redmond

Large bursts of GitHub activity take less work to process, helping Hoplite stay responsive while pull request and check updates arrive. Updates still process in order, and a delayed update does not block other connected GitHub accounts.

By Bence Redmond

The /goal command now appears in both new-thread slash menus when Cloud is selected. Choose it and describe your objective to start a thread with an active goal, so Hoplite can continue working toward completion. Goals also work with automated prompts and uploaded files, without treating attachment links as completion conditions. Existing-thread goal controls remain available as before.

By Odin Glynn-Martin

The reCAPTCHA badge no longer covers the corner of every page after you sign in. The sign-in form now notes that reCAPTCHA protects it instead.

Agents can discover your connected Linear tools when starting work from Slack or iMessage. Requests are checked against your current access before their contents are processed, so authorized runs retain their tools while unauthorized requests remain blocked.

By Odin Glynn-Martin

Modal sandbox pricing now shows as unavailable instead of treating an incomplete sample as the lifetime cost. Unverified amounts no longer count toward thread costs or spend limits. Verified charges from other sandbox providers remain visible, and subscription threads only show an unavailable-pricing notice when an unpriced sandbox exists. Accurate Modal lifetime pricing remains unavailable pending verification.

By Bence Redmond

Pull request webhooks and thread creation read and return only the fields they need, avoiding large review and diff payloads during bookkeeping.

By Bence Redmond

When a running command briefly loses its response, Hoplite retries reading the result instead of immediately reporting a tool failure. The command continues without being started twice.

By Odin Glynn-Martin

Production releases can complete the goal history update without repeatedly scanning unrelated events. If the update stalls, the release stops with a clear error instead of appearing stuck; customer fixes can ship once the recovery release succeeds.

By Odin Glynn-Martin

Opening a thread from a Slack card or a shared link now switches the sidebar, recent threads, and Threads list to that thread's project, so the thread no longer looks missing. Projects that share a name are told apart in the project switcher, and local desktop projects are marked.

By Bence Redmond

Slack task cards now refresh even when a separate message-delivery task fails, so completed, waiting, and failed work no longer stays marked as working.

By Odin Glynn-Martin

When you steer a running agent with Cmd+Enter or the mobile steer action, Hoplite interrupts the model's current response and starts again with your message. Steers no longer wait for the agent to finish its current step. A command that is already running still finishes first.

By Odin Glynn-Martin

The goal banner no longer shifts to the right when the thread navigation rail is visible.

By Odin Glynn-Martin

Workspace lifecycle checks read only the state they need, reducing database transfer while preserving full context for operations that use it.

By Bence Redmond

Open the changelog directly from your account menu. An unread badge highlights new updates, up to 99+, and clears when you visit the page. Existing updates start as read; your reading progress is saved per account in this browser.

By Odin Glynn-Martin

Use /goal in an existing cloud thread to set an objective, check progress, pause, resume, or clear it. Hoplite continues until the goal is complete, blocked, or reaches its budget. New-thread composers also offer slash menus for skills from your selected repository or pull request.

By Odin Glynn-Martin

Hoplite's changelog now puts meaningful features and fixes in one short, dated list. Open any update for a plain-language explanation, and share a direct link with your team. Updates include contributor credit when verified.

By Odin Glynn-Martin

Pull request review conversations appear inline with code changes. Review feedback without switching away from the diff you are inspecting.

By Odin Glynn-Martin

Organizations with early access to the Platform console can see what each app costs in model usage and sandbox compute, and export it as CSV. Owners and admins on Pro or Scale can set monthly budgets per app. Free plans see shares and counts instead of dollar amounts. The console is rolling out to a limited set of organizations.

By Bence Redmond

The Issues page is replaced by Pull requests, which lists every open pull request across a project's repositories, sorted by what to do next. Failing checks, merge conflicts and unresolved review comments get a one-click fix that starts an agent on the branch, and one key fixes every broken pull request at once.

By Odin Glynn-Martin

Deleting a thread, project, workspace, or account now preserves the information needed to shut down its sandboxes and record their final usage. Cleanup continues after deletion, including for subagents that are still starting.

By Bence Redmond

The preview panel in the desktop app showed a blank page instead of your running app. Previews now load inside the panel, as they do on the web, so you no longer need to open them in a separate browser window.

By Bence Redmond

Clicking the Hoplite logo on the website now returns you to the homepage even when you are signed in, instead of opening the app.

By Bence Redmond

Hoplite saves refreshed sign-in credentials for connected tools. Later requests can use the updated credentials instead of reusing expired ones and interrupting your task.

By Bence Redmond

Queued messages are picked up after an agent run finishes, fails, or stops. Recovery also finds messages left waiting without an active run, so follow-up requests are not stranded.

By Bence Redmond

Agents sharing a workspace no longer race while setting up or rotating repository access. Parallel work keeps a single credential owner, avoiding intermittent setup failures and conflicting credential updates.

By Bence Redmond

Messages from another thread no longer remove an agent's coordination tools during ongoing work. Message-started runs can read and reply to their source thread, with bounded reply chains and repeated-message protection to prevent runaway conversations.

By Bence Redmond

Images and files attached in the desktop app now appear in the thread on web, desktop, and mobile instead of showing as blocked. Messages sent before this fix display their attachments again.

By Bence Redmond

The terminal client keeps tool activity visible and shows previews alongside the conversation, making it easier to follow what your agent is doing.

By Bence Redmond

Create an additional workspace directly from the workspace switcher. You can set up a separate workspace without leaving the app to find the creation flow.

By Bence Redmond

Projects with multiple repositories no longer fail to prepare a workspace just because an additional repository has no commits yet. Hoplite prepares the empty repository so work can continue.

By Odin Glynn-Martin

Attach files or paste a screenshot when sending a terminal message. The files travel to your cloud agent, so it can work with material that is only on your computer.

By Bence Redmond

Remove a pull request from a task while preserving the agent’s conversation context. You can correct a link without starting the task over.

By Odin Glynn-Martin

Trial limit messages distinguish the daily limit from the available balance and explain what a credit top-up must cover. You can see what is needed before trying to continue.

By Bence Redmond

A disconnected browser tab no longer keeps counting agent work as though it were still live. Timers pause until the connection returns, and outdated tabs refresh when it is safe.

By Bence Redmond

Usage accounting now includes pending charges when checking available credit and reconciles missed charges. Balance checks better reflect the work your organization has used.

By Bence Redmond

Use hoplite push or /sync to send local changes to a task’s cloud workspace without committing them first. Conflicting changes are identified, and common credential files are excluded.

By Bence Redmond

Hoplite suggests connected tools based on the technologies found in your project’s repositories. Each suggestion includes a reason, helping you find relevant integrations without searching the entire directory.

By Bence Redmond

The interactive terminal client brings Hoplite tasks, tool activity, approvals, and pull request status into your terminal. You can also send requests from scripts, open a remote shell, and connect supported editors.

By Bence Redmond

Local-agent tasks can be shared with your organization, keeping work on your Mac visible to teammates. Pull request status also shows when a change is waiting in GitHub’s merge queue.

By Bence Redmond, Odin Glynn-Martin

Projects with supported dependency files now prepare dependencies and previews ahead of time by default. This reduces repeated setup when opening a workspace. You can turn this preparation off for individual projects.

By Bence Redmond

Search the model picker and see more information before choosing. Clearer names and hover details help distinguish similar models.

By Bence Redmond

A compact message composer leaves more room for your task list on a phone. Agent activity appears in its activity view instead of being mixed into ordinary chat messages.

By Bence Redmond

The desktop beta shows an in-app update notification instead of a separate system dialog. Install an update immediately or let it wait until you are idle.

By Bence Redmond

Switching models during a task now sends requests that custom model providers can accept. This fixes failures caused by an incompatible message format.

By Bence Redmond

A failed session lookup now shows an offline recovery screen instead of leaving the app unreachable. You can understand the connection problem and try again.

By Bence Redmond

After completing checkout, Hoplite returns you to where you started. Upgrading or adding credit no longer sends you to an unrelated page.

By Bence Redmond

Optional analytics and attribution cookies wait for your consent. Declining analytics keeps those cookies from being enabled.

By Bence Redmond

Redirecting an active agent keeps earlier reply drafts and separates the activity from each attempt. You can follow how the work changed without losing the previous response.

By Bence Redmond

The agent no longer condenses conversation history earlier than necessary. More of your task’s original details stay available while the work continues.

By Bence Redmond

Tasks waiting for checks and reviews now resume to report a passing result instead of remaining parked. They also wake when the pull request’s target branch changes.

By Bence Redmond, Ryan Morrissey, Odin Glynn-Martin

Signup shows a clear message when a network verification check is rejected instead of leaving you without an explanation. Where available, an additional verification step helps complete the check.

By Bence Redmond

Added Muse Spark 1.3 and Claude Fable 5.1 to the supported model lineup, giving teams more choices for their coding tasks.

By Bence Redmond

In a limited organization rollout, parallel agents can build, test, and edit in their own cloud workspaces. This separates their changes while they work on different parts of a task.

By Bence Redmond

Previews recognize more development servers, handle slow startup without repeatedly switching to an error, and retain crash output to help explain what went wrong.

By Bence Redmond

Opening a task uses information already synchronized to your browser instead of waiting for several separate requests. Your conversation and task details become available sooner.

By Bence Redmond

Connect a custom model endpoint with your own credentials and billing. Choose its models for a task alongside Hoplite’s other model options.

By Bence Redmond

Large repository transfers use larger batches, reducing delays when a cloud workspace is prepared. This helps large projects get back to useful work sooner.

By Bence Redmond

Task rows use two lines on small screens, keeping important details readable without horizontal scrolling.

By Bence Redmond

Daytona-backed workspaces can expand storage during restart when the disk is nearly full. This gives large installs and builds more room to finish.

By Bence Redmond

Mention or delegate an issue to Hoplite in a connected Linear project. The agent works on it and sends progress and pull request links back to the issue.

By Bence Redmond

Schedule routine coding work instead of starting it by hand each time. Each automation run creates a task where you can review its progress and results.

By Bence Redmond