
Why it mattersA team sandboxing a coding agent now gives it live web access without widening the firewall. One host replaces a long allowlist.
A team that runs a coding agent in a Docker Sandbox takes a trade. The agent is safe from the open internet, and the agent cannot read the open internet. A new release from Docker swaps that trade for a narrower one. The agent still cannot reach the whole internet. It can reach the web through one Firecrawl endpoint.
Docker published the Firecrawl kit for Docker Sandboxes on 16 November. The announcement is on the Docker blog. The kit is Apache 2.0. It is on Docker Hub as firecrawl/sbx-kit-firecrawl. A team installs it like any other sandbox kit.
What the kit does
The kit gives a sandboxed agent three jobs through one added host, api.firecrawl.dev. The agent can run a web search. It can scrape a single page. It can crawl a site. Every page comes back as clean markdown, not raw HTML. Docker's post names the three jobs behind one host, api.firecrawl.dev: web search, page scraping and site crawling. Every page comes back as clean markdown.
Why one host matters
A sandboxed agent that needs the web usually ends up with a long allowlist of documentation sites. The list grows every week. It is also a list of trust decisions a team has to review. The kit turns the list into one line. The team trusts Firecrawl. The agent reads the sites through Firecrawl. The firewall has one hole instead of many.
What the agent can now do
The use case Docker names is documentation that came out after the model's training cutoff. An agent trained in the spring of 2026 does not know about an API that launched in November. The agent can now search for the current docs. It can scrape the page it needs. It can fold the text into its answer. The agent can also check a changelog before it writes code that depends on an API behaviour.
What it does not do
The kit does not bypass a sandbox. The agent still cannot open an arbitrary port. It still cannot reach a database it has no credentials for. The one added route is a single, logged, read-only route to Firecrawl. A team that does not want to trust Firecrawl can skip the kit. The sandbox still works.
For a team already using Docker Sandboxes
Install the kit. Give the agent the one tool call. Check the audit log. A team that has been keeping an allowlist of doc sites can now delete the list. A team that has been running the agent with no web access can now give it current documentation. Both changes are small and testable in one afternoon.
Source
Docker: Give sandboxed agents live web access with the Firecrawl kit for Docker Sandboxes.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.


