Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
Use when moving a Node.js project from Bee-Queue to glide-mq: converting the chained job builder to options, splitting Queue and Worker, and mapping settings, methods and events.
Use when moving a Node.js project from BullMQ (or BullMQ Pro groups) to glide-mq, or comparing the two APIs: connection format, changed signatures, removed options, and what replaces them.
Use when building or changing code that uses glide-mq, the Node.js job queue on Valkey/Redis Streams: queues, workers, retries, schedulers, workflows, broadcast, serverless producers, HTTP proxy, or its AI primitives (usage, streaming, suspend/resume, budgets, fallbacks, vector search).