Run durable Node agent jobs without Redis using Sidequest
Use Sidequest to run durable Node.js agent jobs, retries, cron schedules, and queue dashboards on PostgreSQL, MySQL, SQLite, or MongoDB without adding Redis.
npx skills add agentskillexchange/skills --skill run-durable-node-agent-jobs-without-redis-using-sidequest
Use Sidequest when an agent or operator needs to move Node.js work out of an interactive request and into a durable queue: enqueue research jobs, webhook follow-ups, report generation, notification sends, retries, scheduled refreshes, and stale-job recovery while keeping persistence in an existing database.
What this skill actually does
This is skill-shaped because the repeatable job is specific: configure Sidequest, choose a database backend, define job classes, enqueue work, monitor execution in the dashboard, and tune retries or cron schedules. Invoke it when a Node agent workflow needs reliable background processing instead of asking a user to babysit a terminal, run ad hoc cron scripts, or operate Redis just for queues. It is not a generic Node.js library listing, framework card, or dashboard product page; the boundary is durable job execution for agent workloads.
Inputs and prerequisites: Node.js 22.6 or newer, the sidequest npm package, a supported database backend package, and optionally the built-in dashboard..
Setup notes: Install the core package with npm install sidequest , then install the backend driver for the database you will use, such as npm install @sidequest/postgres-backend . Start Sidequest in your Node.js process with the backend configuration, define job classes, and enqueue work with Sidequest.build(JobClass).enqueue(…) .
Source and verification boundary: use https://docs.sidequestjs.com 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.