Run persistent local computer-use agents with invisible_dots
Give each agent its own local QEMU desktop, browser identity, files, memory, task queue, and approval rules for supervised long-running web and computer workflows.
npx skills add agentskillexchange/skills --skill run-persistent-local-computer-use-agents-with-invisible-dots
Use invisible_dots when an operator needs a persistent local computer-use agent with its own VM, desktop, browser profile, files, memory, scheduled tasks, and explicit allow/ask/deny permissions. Invoke it instead of driving the product manually when a repeatable agent should handle permitted research, account workflows, downloads, monitoring, or long-running browser tasks while keeping state between runs and waiting for human approval on sensitive actions. The scope boundary is the supervised local Dot runtime and its persistent computer; this is not a generic browser automation library, hosted sandbox, scraping card, or broad agent framework listing.
What this skill actually does
Inputs and prerequisites: Node.js 24+, Go 1.25+, Git, QEMU or Windows Hypervisor Platform/KVM, hardware virtualization, and an OpenRouter API key.
Setup notes: Clone https://github.com/feder-cr/invisible_dots, run npm ci, build the CLI with npm run build –workspace @invisible-dots/cli, run node apps/cli/dist/invisible-dots.mjs setup –all, then start the server with node apps/cli/dist/invisible-dots.mjs server and create a Dot from the local web UI.
Source and verification boundary: use https://github.com/feder-cr/invisible_dots/blob/main/docs/guide.md as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.