Cloudflare Computer is a virtual filesystem whose state is stored in SQLite inside a Durable Object and exposed through selectable execution backends. It lets coding agents work with files, shell commands, JavaScript modules, containers, and networked Linux environments.
Borrowing it
Nothing to install: this file belongs to cloudflare/computer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cloudflare/computer/main/.agents/skills/debugging-computerd-fuse/SKILL.mdgit clone --depth 1 https://github.com/cloudflare/computerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cloudflare/computer/debugging-computerd-fuse)<a href="https://agentmods.dev/skills/cloudflare/computer/debugging-computerd-fuse"><img src="https://agentmods.dev/badge/skills/cloudflare/computer/debugging-computerd-fuse/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cloudflare/computer/debugging-computerd-fuse"><img src="https://agentmods.dev/badge/skills/cloudflare/computer/debugging-computerd-fuse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 40 Potential security issue detected. Manual review is recommended.Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
- high Privilege Escalation · line 52 Potential security issue detected. Manual review is recommended.Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
- high Privilege Escalation · line 53 Potential security issue detected. Manual review is recommended.Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
- medium MCP Rug Pull · line 367 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00120 | $0.04428 |
| Opus 5.5 | $0.00048 | $0.01771 |
| Sonnet 5.5 | $0.00024 | $0.00886 |
| Haiku 4.5 | $0.00012 | $0.00443 |
Grade C, and why
debugging-computerd-fuse scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
To remove a root before `rm -rf`, call the daemon's detach endpoint: Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf http://127.0.0.1:18080/health How it starts
The opening of the file, as written. The whole thing — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging computerd against real FUSE
This skill captures the recipe for isolating bugs in computerd that only
fire when the kernel-FUSE backend is the one wired up. Most unit
tests run against SQLiteTestStorage and an in-process VFS or the
userspace FUSE_MOUNT=shim polling driver — neither exercises the
kernel-FUSE callback path. Several production-only bugs (write
buffer never spilled to the VFS, spawn(cwd=/mount) deadlocks)
have shipped to next and not been caught by the regular suites
because the harness is hard to drive end-to-end from a dev box.
The workflow here bypasses workerd, wrangler, and the
vitest-pool-workers harness. It boots the computerd SEA binary in a real
docker container with /dev/fuse and SYS_ADMIN, and drives its
capnweb endpoints from a plain Node script.
When to reach for this
- A user report of "wrote a file via FUSE, RPC reads see 0 bytes."
- A report of "exec hangs forever" or "computerd
/healthstops responding after the first shell call." - Adding a new computerd op (FUSE callback, sync RPC, runner feature) and you want a smoke test that doesn't depend on Docker-in-DO or Cloudflare Containers.
- The harness vitest suite (
packages/computer/src/test-harness/) hangs atws.shell.execagainst the docker container and you need to attribute the wedge to computerd vs workerd vs the network shim. - Confirming a fix actually settles in the deployed binary: the SEA build is what wrangler ships, and reproducing locally with the same binary is the only way to be sure.
What you need
- Docker, with
/dev/fuseand--privilegedavailable. In Pi's sandbox this works through DinD; on a Linux dev box it works natively; on macOS you needcolima start --vm-type=vz(the default qemu vm doesn't surface/dev/fuse). - A fresh computerd binary at
artifacts/computerd/computerd-linux-x64. Build it withnpm run build:bin --workspace @cloudflare/computerd, or justnpm run build:allfrom the repo root if you need the docker image too.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago Changed · +47 lines scan A → C 86c8db2c1f7c
- 2mo ago First seen · 376 lines · 120 tokens per session scan A 2e64f7972528
debugging-computerd-fuse is a skill published in the GitHub repository cloudflare/computer (9,753 stars, last pushed today), licensed MIT. It adds 120 tokens to every session and 4,428 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.