Independent testing will determine whether Caged Code provides a practical browser-hosted isolation and packaging pattern for running the standard Claude Code binary outside a conventional local terminal.
state: expiredheat: lowuncertainty: highconvergesscott: mediumcoding-agents agent-harnesses sandboxingTom LarkworthyAnthropic
What is this?
Caged Code is presented in the supplied case as a project by Tom Larkworthy that runs Anthropic’s standard Claude Code binary inside a webpage, proposing browser-hosted packaging and containment instead of a conventional local terminal. The snippets establish that coding-agent isolation commonly combines permission controls, filesystem restrictions, network proxies, and container-style boundaries, but they provide no direct evidence about Caged Code’s implementation or independent testing. Accordingly, the claim that it offers practical or secure isolation remains unverified by the supplied search results.
Why it matters to Scott
Caged Code independently packages the standard Claude Code binary behind a browser-hosted containment boundary, converging with Scott’s architectural-containment position and his browser-mediated coding-agent implementations. If testing confirms useful isolation without degrading the native harness, it could extend his active packaging patterns; for now it remains an unverified implementation rather than a validated security result.
ip:source.give-the-agent-a-workshop-ebookip:concept.architectural-containmentdev:project.superleverdev:technology.claude-coderadar:openchamber-agentic-development-environmentradar:concept.agent-sandboxingradar:concept.agent-harnessesradar:concept.coding-agents
queries asked of Scott's wikis
- browser-hosted coding-agent runtimes
- coding-agent sandbox and containment architecture
- agent harness packaging beyond the terminal
- filesystem and network isolation for autonomous coding agents
- standard agent binary versus custom harness
- secure execution of coding agents near sensitive credentials
Measured heat
no measured readings yet — the hourly heat pass fills this in
How the heat travelled
no chain yet — the hourly chain pass fills this in
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-08-15T22:24:45Z
No independent testing, implementation detail, adoption, or discussion emerged within the observation horizon. The browser-packaging demo remains unvalidated and has faded without earning continued active tracking.
2026-08-13T21:34:32Z
The forced re-evaluation adds no independent testing or implementation detail; Caged Code remains an unvalidated browser-packaging demo rather than evidence of practical isolation.
2026-08-13T21:27:46Z
grounded: converges/medium — Caged Code independently packages the standard Claude Code binary behind a browser-hosted containment boundary, converging with Scott’s architectural-containmen
2026-08-13T21:25:06Z
case created — A usable first-party artifact demonstrates a novel browser-contained deployment pattern, but it has not yet received independent testing.
Decision trace
- 08-16 08:24expireNo independent testing, implementation detail, adoption, or discussion emerged within the observation horizon. The browser-packaging demo remains unvalidated and has faded without earning continued ac
- 08-16 08:24alert_silentThe only delta is elapsed staleness with unchanged engagement and no technical validation; there is nothing consequential or time-sensitive to surface.
- 08-16 08:24alert_routeThe only delta is elapsed staleness with unchanged engagement and no technical validation; there is nothing consequential or time-sensitive to surface.
- 08-14 07:34repriceThe forced re-evaluation adds no independent testing or implementation detail; Caged Code remains an unvalidated browser-packaging demo rather than evidence of practical isolation.
- 08-14 07:34alert_silentNothing consequential changed: engagement is flat and no technical artifact, independent test, or security evidence has appeared. It can wait for a substantive validation result.
- 08-14 07:34alert_routeNothing consequential changed: engagement is flat and no technical artifact, independent test, or security evidence has appeared. It can wait for a substantive validation result.
- 08-14 07:31alert_silentA browser-hosted packaging demo appears to exist, but the supplied evidence does not establish its isolation properties, implementation details, or practical advantages over existing agent sandboxes.
- 08-14 07:31surface_candidateA browser-hosted packaging demo appears to exist, but the supplied evidence does not establish its isolation properties, implementation details, or practical advantages over existing agent sandboxes.
- 08-14 07:31alert_routeA browser-hosted packaging demo appears to exist, but the supplied evidence does not establish its isolation properties, implementation details, or practical advantages over existing agent sandboxes.
- 08-14 07:27groundCaged Code independently packages the standard Claude Code binary behind a browser-hosted containment boundary, converging with Scott’s architectural-containment position and his browser-mediated codi
- 08-14 07:25createA usable first-party artifact demonstrates a novel browser-contained deployment pattern, but it has not yet received independent testing.