What's new in Hoplite

When an agent wrapped a preview link in bold or ended it with punctuation, the formatting characters became part of the link. The message showed stray asterisks and the preview opened the wrong address. Formatting now stays outside the link in the web and mobile apps, so previews open the page the agent meant.

By Bence Redmond

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

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

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

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 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

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

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

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

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

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

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

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

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

The compaction threshold under Settings, Models, and each model's override, now sets how full a thread's context gets before Hoplite summarizes its earlier history. Before, compaction started near the model's limit regardless. The default is 60% of the model's context window, so threads on default settings now compact earlier. Compaction always starts before the model's limit and leaves room to work afterward, and switching models compacts first when needed.

By Bence Redmond

For organizations with Paper enabled and connected, select a Paper file link in chat to open that design in the thread’s Paper tab. The selected file stays available when switching tabs or reloading the thread.

By Odin Glynn-Martin

For organizations with Paper inline canvas enabled and Paper connected, agents can show live Paper designs directly in their responses. Interact with the embedded Paper canvas without leaving the conversation.

By Odin Glynn-Martin

For organizations with Paper enabled and connected, a Paper tab appears when an agent uses Paper. Open it to watch the design update, and return to the file after the run finishes without searching through the conversation.

By Odin Glynn-Martin

Repository skills appear in composer menus as they are added. Complete a skill with Tab to keep it visibly selected while editing the rest of your prompt, or choose repository skills when creating a swarm.

By Odin Glynn-Martin

Selected organizations can connect a Revyl workspace so agents can build and test iOS and Android apps, capture screenshots, and share reports. A dedicated Revyl page lets teammates open live app previews. An organization admin must approve the connection, and testing uses the connected Revyl workspace’s billing and limits.

By Odin Glynn-Martin

Use /loop 5m followed by a prompt to check deployments, review progress, or repeat other work in the same conversation. Loops continue while your browser is closed, wait while the conversation is busy, and expire after seven days. Use /loop status to inspect the schedule or /loop stop to cancel it.

By Odin Glynn-Martin

Stopping or steering a Claude Code chat now interrupts a stalled model connection and shuts down its execution sandbox, allowing your follow-up to proceed without waiting for the stalled response.

By Odin Glynn-Martin

Threads following pull requests now retry temporary billing interruptions instead of creating a failed run before work starts. Check results and merge updates can resume the same thread once the interruption clears, without duplicating the run.

By Bence Redmond

Hidden reasoning data was counted as if it filled the context window, so long GPT runs could drop earlier messages and summarize at under half of the window. GPT threads no longer compact far below their real context usage.

By Bence Redmond

For organizations with Paper enabled, agents can continue editing a design after the connected account session renews without losing their discovered tools. Reconnecting or disconnecting the account still invalidates the previous connection.

By Odin Glynn-Martin

Subagents now check context before each saved step and shrink rejected requests using the gateway's reported token count. Long delegated tasks can continue without restarting completed tools when a gateway reports more tokens than estimated.

By Odin Glynn-Martin

Set your personal default for new threads to shared or private. Existing accounts keep shared as their default until you change it. You can still change sharing for an individual thread without changing your personal default.

By Odin Glynn-Martin

A filter beside the search on the Pull requests page switches between your team's open pull requests and only the ones you opened from the GitHub account linked to Hoplite. The choice stays in the page address with your search, so a reload or a shared link keeps it.

By Bence Redmond

On long threads the outline beside a conversation now includes your most recent 500 prompts, not only the messages already loaded. Selecting an older prompt loads the conversation back to it.

By Bence Redmond

Available in enabled organizations. Set your preferred visibility in Settings, then change individual threads whenever needed. Organization admins can override the default for new threads while leaving per-thread choices available. Existing threads keep their current visibility.

By Odin Glynn-Martin

Starting a local thread no longer fails because an attachment used the same request identifier. Multiple attachments stay distinct, and retrying a previously blocked draft recovers without restarting the app.

By Odin Glynn-Martin

Projects with a long history could fail to delete with a database timeout, and retrying never helped. Deleting a project now removes it and its threads from view first, then clears their history in the background. If a delete is interrupted, trying again picks up where it stopped. Hoplite confirms what was deleted by name.

By Bence Redmond

Compatible WebMCP browser agents can list your projects, find threads, read their messages, and start coding tasks using your signed-in organization. Task creation uses the same access and billing checks as the app. Availability requires a browser that supports WebMCP.

By Odin Glynn-Martin

Organizations with GitCafe enabled can connect repositories and manage pull requests through the current API. Existing hosted connections update automatically. Older self-hosted servers must be upgraded before connecting or reconnecting: their API must support GET /repos?affiliation=member with an items/next cursor response. Ask your GitCafe operator to upgrade the server to that API, then reconnect in Hoplite.

By Odin Glynn-Martin

Where Swarms is enabled, coordinators can now compare a worker's reported commit with the pull request's actual head and base. Check summaries from a different revision are reported as unverified, so a coordinator cannot mistake those checks for evidence about the requested revision.

By Odin Glynn-Martin

Open Settings, then Skills, to see every skill your runs can load, where each one comes from, and which one wins when two share a name. Typing / in a thread's composer now also offers the repository skills its agent found, including those under .claude/skills.

By Bence Redmond

Where Swarms is enabled, swarm settings include a Threads at once limit, eight by default. Once that many of its threads are running, the swarm cannot start or restart another until one finishes, so a large plan cannot fan out unchecked. Threads you restart yourself still run. Retrying an earlier request still reuses its original thread.

By Bence Redmond

Where Swarms is enabled, the swarm thread list shows tokens used by each thread and by the whole swarm, and the About panel shows the swarm's own share. Counts include input and output tokens across every run and refresh every 30 seconds.

By Bence Redmond

hoplite skills import-global stopped with a limit error once your personal library held 20 skills. Your library now holds up to 100 skills, re-importing an unchanged skill succeeds, and a full library explains its limit, how many skills you have, and where to remove some.

By Bence Redmond

Workspaces now move to the next connected account automatically when one hits its limit, including workspaces whose saved settings defaulted to Ask every time. Workspaces that chose Ask every time keep it. Subagents in a session paid by a Claude subscription used to crash with an unexpected error. They now stop at once, explain that they are not supported yet, and point the agent to a separate thread.

By Bence Redmond

Projects with threads now accept new repositories, in the app and through the API, so a late repository no longer needs its own project. Existing threads keep the repositories they started with, and the project's default repository stays the same. Removing or replacing a repository still needs a separate project.

By Bence Redmond

Press ⌘K on a thread to see it named above the search field. Rename turns the field into the new title, Change model lists the same models as the composer picker, and Delete asks for confirmation in place. Backspace on an empty field steps back.

By Bence Redmond

In a pull request's Comments, touch and hold a review comment to open its whole thread, replies included, with formatting shown as on GitHub. Write a reply there and it posts to GitHub from your connected GitHub account.

By Bence Redmond

Grant a service account Skills, Linear or PR review settings access to manage them through the API. Linear covers project bindings, repository routes and team and project pickers; installing Linear still happens in the browser. Accounts limited to specific projects can only use those projects' Linear routes.

By Bence Redmond

In the iOS app, question cards from the agent appeared faded with the note "Waiting for someone with access", so even the thread's owner could not pick an option, type an Other answer, or submit. Members can now answer from the card. Replying in the message box instead now closes the open question on every app, and the agent continues from your reply.

By Bence Redmond

On iPhone, the reasoning effort and Fast setting you choose for a new thread now carry into its follow-up messages instead of resetting to the default after the first one. The effort control also shows the level that will run, such as Medium, instead of Default, and marks the default level in its menu.

By Bence Redmond

Back and Forward now use the familiar shortcuts: ⌘[ and ⌘] (Ctrl+[ and Ctrl+] on Windows and Linux), plus ⌘← and ⌘→ in the Mac app. They never fire while you type a message. Moving to the previous or next thread is now ⌥⌘↑ and ⌥⌘↓, listed in the shortcut sheet and the Mac app's View menu.

By Bence Redmond

In Settings → Models, Add account now offers Add another for ChatGPT (Codex) and Claude, so you can connect several personal subscriptions from the same provider. Each one gets its own row with its plan usage, in the order you choose. Connecting an account you already added refreshes it instead of creating a duplicate or replacing another.

By Bence Redmond

Agents using a connected Claude subscription now receive previously viewed screenshots as images when continuing a task, so they can inspect visual changes instead of receiving unreadable image data.

By Odin Glynn-Martin

In Settings → Models, each connected ChatGPT (Codex) and Claude subscription has its own row with its plan usage. Members can move a personal subscription to the workspace without reconnecting; owners and admins can reorder, remove or return workspace subscriptions. When one reaches its usage limit, the run continues on the next subscription from the same provider before keys or credits, and the thread notes the switch.

By Bence Redmond

Cloud agents can ask questions without pausing their work. Open the question dialog to choose one or several options, write an answer, or enter a number, date, email address, URL, or yes/no response. You can close the dialog and answer later, including after the agent finishes.

By Odin Glynn-Martin

Where Swarms is enabled, coding agents can publish compact findings and failed approaches after a separate verification call checks their supporting evidence. Other agents can search and expand those findings during work. The coordinator retains control over scope, budgets and completion.

By Odin Glynn-Martin

Where Swarms is enabled, an orchestrator can keep creating threads as work expands, without a per-run thread count cap. Retrying a creation still reuses its original thread. Organization concurrency and spending controls continue to apply.

By Odin Glynn-Martin

New feature cards show a short explanation and an image or video preview. Open more details or dismiss a card to see the next update. Dismissed cards stay hidden for your account in the same browser.

By Odin Glynn-Martin

Run hoplite mcp connect with a server URL and thread ID to use Paper, Figma, or other MCP tools from your cloud thread. The native macOS and Linux CLI handles browser sign-in when supported and keeps credentials on your computer. Keep it running while connected; use --read-only to disable tools that change things.

By Odin Glynn-Martin

Your message appears in the conversation the moment you send it. The sending notes, the setup steps shown before the first reply, the dimmed new-thread row and the workspace preparation chip are gone; you see the agent working instead. Failed sends and queued messages are still called out.

By Bence Redmond

After a reload, the web app no longer pauses between loading its own parts before showing your sidebar and thread. Once everything it needs is on your device, the workspace appears straight away instead of after a short built-in delay.

By Bence Redmond

When you are signed in, reloading the web app or opening a link now paints the sidebar and page panel in your light or dark theme straight away, then fills in your workspace. The dark blank screen and the full-screen logo loader no longer appear in between.

By Bence Redmond

A reload or a saved link in the web app now opens your workspace from this browser's saved session straight away, instead of waiting about a second for Hoplite's servers first. Your session is still confirmed in the background, and you are signed out as before if it has ended.

By Bence Redmond

The line above the message box that explained where messages go while subagents are running has been removed, so the space above the composer stays clear.

By Bence Redmond

For threads with PR-event wakeups enabled, check updates now reflect the latest results and repeated notifications no longer restart the same work. Blank replies to informational check updates stay hidden when no tools were used. Replies with meaningful text remain visible.

By Bence Redmond

Long threads preserve earlier work without replaying the same tool exchanges repeatedly. Resuming cancelled work and compacting older conversations also preserve context without multiplying permanent instructions or discarding separate answers to repeated requests.

By Odin Glynn-Martin

Owners and admins could not act on this warning, since only each subscription's owner can reconnect it. Your own expired subscriptions still show a notice with a Reconnect button.

By Bence Redmond

Sidebar lists scroll independently, with controls reachable in short windows. An invisible Get Started card no longer reserves empty space. Thread workspaces align with other page edges while keeping gaps between split panes. The sidebar Search control is removed, and New thread opens Home with your selected project. Starting a thread from Home opens the new thread after creation succeeds.

Identify each open thread directly from its browser tab, even when multiple threads belong to the same project.

By Bence Redmond

Opening a thread keeps the page edges and title position steady as its content loads. Thread titles align with other page headings. Chat headers no longer show the branch name or a separate pull request indicator.

For organizations in the limited rollout, the last few threads you opened stay ready in the background. Switching back to one shows it right away, with your scroll position and draft where you left them. Previews and terminals in background threads pause until you return. The rollout is off by default and starts with selected organizations.

By Bence Redmond

You can add GitHub repositories you contribute to even when their owner's installation is connected to another Hoplite workspace. Checking GitHub access discovers repositories you can write to, while other repositories stay hidden. The Hoplite GitHub App must have access to the repository.

By Odin Glynn-Martin

Kimi K3.1 Pro is Moonshot's newest open-weights model, with a 1M-token window. It appears under Moonshot in the model picker, and hovering it now shows its description and its speed and intelligence ratings.

By Tommy Byrne

Continuing a long thread preserves earlier instructions and tool results until context compaction summarizes them. Workspace recovery notices also preserve the existing conversation prefix, helping avoid unnecessary prompt cache misses.

By Odin Glynn-Martin

Periodic workspace backups could pause an active agent for up to 30 seconds before it replied or ran a tool. Agents whose saved work is fully backed up elsewhere now keep running.

By Bence Redmond

Link your owner-managed personal GitHub installation in each workspace to use its repositories in projects. Repository changes stay in sync across linked workspaces, including pull request updates and merge automations. Restricted collaborator connections cannot be shared this way.

By Odin Glynn-Martin

Projects with large archives now load non-archived threads separately, so older ready threads aren't crowded out by newer archived threads. Loading older threads prioritizes remaining non-archived work, while archived threads remain accessible through the archive filter.

By Odin Glynn-Martin

When a workspace backup falls due while an agent is working, Hoplite now starts it as soon as the agent's next command needs it, instead of waiting for a periodic background pass. Commands held behind an overdue backup now wait for the backup itself rather than for its turn in the queue.

By Bence Redmond

hoplite.sh/download lists the stable and Nightly Mac apps with version, date, size, and publisher, and every CLI archive with its size and SHA-256, plus install and verification steps. The old hoplite.sh/downloads address now opens this page, and the Windows docs recommend npm or a checksum-verified manual install.

By Bence Redmond

Link your GitHub account and choose Check GitHub access again. Hoplite adds repositories where you have write, maintain, or admin access from accounts with the Hoplite app installed, unless that installation already belongs to another workspace. Other repositories in the installation stay out of your workspace.

By Odin Glynn-Martin

Owners and admins can add other GitHub review apps in workspace settings, so their reviews start autofix passes like Greptile or CodeRabbit already do. A trusted app's review text guides the agent, so only add apps you would let direct changes. Hoplite's own app can never be added.

The VM usage tooltip overlays memory and disk history alongside CPU, with distinct colours, line styles and current readings. Labelled percentage and GiB scales keep the units clear, while missing measurements remain visible as gaps.

By Odin Glynn-Martin

Results from connected tools, such as search, issue trackers and code hosts, could show the agent a package name, page slug, app identifier or commit hash as an unrelated three-word placeholder. Agents then sometimes wrote those placeholders into files, docs and commits. Names and hashes now reach the agent exactly as they appear, and existing threads keep working.

When an agent added a second repository to a thread, commits in that repository could fail because no author was set. Attached repositories now commit with the same Hoplite author as the main repository. Repositories attached before this update are fixed the next time the agent attaches them again.

Automations that start when a pull request is opened could silently skip a PR that was edited or received new commits moments after it was opened, which is common for PRs created by agents. These PRs now start the automation exactly once, using the title and description the PR was opened with. A PR that is already closed or merged by then is still skipped.

Automations triggered by pull request updates no longer start duplicate threads and post duplicate reviews when GitHub sends several updates for the same commit, such as a push followed by a description edit or a ready-for-review change. Each automation now runs once per pull request head commit, and the next push starts a new run.

Stop is no longer refused during workspace setup. The agent stops working right away, including while a workspace is being restored, so a thread started by mistake no longer keeps running until setup finishes. If the workspace is still being created, the run shows Stopping until it is ready, then ends as stopped.

When a thread's spend limit was lower than its next model request, the run could stay queued indefinitely with no error. It now stops as failed with a spend limit message, in the app and through the API. Raise or remove the limit, then retry or send a new message to continue.