For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

November 2026

5 November

• Cuttlefish, an iOS app for DigitalOcean Harness Runtime, is available in public preview on the App Store. Follow and steer sessions, approve or deny tool calls, and work with workspace files and checkpoints from your iPhone. To get started, see How to Steer and Approve Harness Runtime Sessions from the Cuttlefish iOS App.

2 November

• Persistent workspaces for DigitalOcean Harness Runtime are in public preview and are enabled per team. A persistent workspace keeps the files in /workspace after you remove the session or take a checkpoint, so a later session can start from those files. To create one and attach it to a session, see How to Use Persistent Workspaces with Harness Runtime.

October 2026

26 October

• DigitalOcean Harness Runtime can start a sandbox with no harness in it. Set harness: none in the environment spec, and the session boots the base image with a general-purpose toolchain and nothing running. You run commands with doctl harness-runtime exec, move files with upload and download, and reach services with port-forward. This option is available through doctl and the API. To create one, see How to Run a Sandbox on DigitalOcean Harness Runtime.

  The environment spec field that selects the adapter is now named harness. The previous name, agent, is still accepted, so existing spec files and Environment Configs work without changes. A spec can set one of the two, but not both. See the Environment Spec Reference.

25 October

• DigitalOcean Harness Runtime platform templates have been rebuilt to address CVE-2026-111497, a remote code execution vulnerability in the Brotli decoder affecting Node.js and other components. The updated templates are codex, claude-code, opencode, hermes, and openhands, along with the LangGraph and CrewAI base images. Sessions created after this update use the patched templates automatically. If you use a custom template (BYOT), rebuild it on the patched base template before creating new sessions.

  Existing running or paused sessions continue to use the image they were created from, and resuming, checkpointing, or forking a session does not apply the fix. To remediate, remove affected sessions and create new ones from your existing environment spec or Agent Config. For more information, see How to Manage Harness Runtime Sessions and How to Use a Custom Sandbox Template (BYOT).

  • codex, claude-code, opencode: Node.js 20 to Node.js 24.22.1
  • hermes: Hermes Agent v0.22.5, Node.js 26.12.1, Python 3.14
  • openhands: OpenHands agent server 1.58.2, Node.js 24.22.1

12 October

• DigitalOcean Harness Runtime now supports OpenHands agents. Run the OpenHands Agent Server in an isolated sandbox, create agents from OpenHands Agent Canvas or the DigitalOcean API, and connect a model such as one from DigitalOcean Serverless Inference. To set up an agent, see How to Run an OpenHands Agent on DigitalOcean Harness Runtime.

8 October

• DigitalOcean Signals is now available in public preview for Harness Runtime agents and Serverless Inference. Signals detects behavioral signals in conversations, such as a user asking for a human, a failed tool call, or an execution loop, so you can find the conversations that went wrong without reading every transcript. Signals collects data only after you opt in. See Use Signals with Harness Runtime and Use Signals with Serverless Inference.

6 October

• Harness Runtime Bring-Your-Own-Template (BYOT) registration now requires a recommended base template (codex-base, opencode-base, claude-code-base, hermes-base, or langgraph-base). Recommended bases provide stronger isolation for custom templates than previously supported bases (coding-codex, coding-opencode, coding-claude-code, coding-hermes, and langgraph). The legacy bases remain available for existing custom templates and for rebuilds of those templates. Support for them in BYOT will be removed in a future release. Sessions that use the legacy base templates as adapter default templates continue to work as usual. For more information, see How to Use a Custom Sandbox Template (BYOT).

• DigitalOcean Harness Runtime now supports CrewAI agents. Package a CrewAI repository, declare kickoff inputs, connect a model and Action Gateway tools, and deploy your crew in an isolated sandbox. For more information, see How to Run a CrewAI Agent on DigitalOcean Harness Runtime.

September 2026

21 September

• Managed Agents is now available in public preview for all users. Managed Agents is a set of services that gives every agent its own microVM execution environment and governed tool access so that developers can scale agentic work without having to build and maintain infrastructure themselves. Developers can pick from agent harnesses that they already use (like Claude Code or agents built with frameworks like LangGraph and Hermes), securely connect it to more than 16,000 tools and have their agents do meaningful work in seconds, from the Control Panel or the DigitalOcean CLI. Teams can also register custom OCI images as sandbox templates with Bring-Your-Own-Template (BYOT).

  DigitalOcean Harness Runtime combines the functionality of a lightweight microVM, built-in tools like chromium and a coding sandbox needed by agents to do work. The product also offers rich lifecycle APIs that persist conversational history and working state across sessions, along with pause/resume/fork semantics so that developers can control costs and adapt workflows to the nonlinear quirks of agentic work.

  Action Gateway gives agents governed access to 16,000+ tools through a single managed MCP endpoint. This includes DigitalOcean-maintained tools such as Web Search, Web Fetch, Browser Automation, and DigitalOcean infrastructure management APIs, along with connectors for platforms like GitHub, HubSpot, Stripe, Snowflake, and more. Teams can also extend the catalog with their own MCP servers and internal tools.