Imported from vouchington/vouchington (backend/entrypoints/worker-io/AGENTS.md). Install upstream with npx skills add vouchington/vouchington --skill worker-io. Copyright stays with the author.

worker-io

IO-bound workers for deployments that split worker capacity.

Queue placement source: ../../modules/worker-queue-inventory/worker-queue-policy.json. CPU-only queues must never be added here. Local development uses worker-cpu instead.

Rules

Keep this entrypoint free of CPU-worker-only modules: sharp and @jongleberry/vurst-ai. Route image processing, native AI detection, and browser crawl work through worker-cpu. The no-mistakes rules lightweight entrypoints must not reach worker-cpu-only modules and worker-io workspace closure excludes worker-cpu-only packages enforce this (pnpm run no-mistakes).
Definition identity tests that import a live Worker singleton must close it. backend-data-stores uses isolate: false; a leftover consumer deterministically drains later enqueue calls before they return, so getJobs('waiting') assertions in later files see nothing waiting. See parallel-safety.

See ../../worker-runtime/ for the shared worker framework.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install worker-io and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

worker-io

About

worker-io

Rules

Use it

Install worker-io and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews