The ultimate unified dashboard to view, trigger, and manage every scheduled job you own —
Windows Task Scheduler, AI assistants, and cron, all in one place.

Explore the docs »

▶️ Try the live demo · 🌐 Website & Template Gallery · 🗺️ Roadmap

Report Bug · Request Feature

Your scheduled jobs are scattered across Windows Task Scheduler, AI assistant routines, GitHub Actions, and cron lines you half remember writing. Cronsole pulls them all into one dashboard — see every job, run it, pause it, edit its schedule — without moving a single one off the platform it already runs on.

📸 Dashboard, Templates, Settings, Views, and Themes

Template library — parameterized script starters	Apply Template — fill in the blanks, get a real task
Task detail — metadata, run history, Run Now	New Task — Cronsole-native or Windows, with cron presets
List view — sortable columns and quick actions	Kanban view — tasks grouped by status
Schedule view — chronological by next run	Light theme — the same dashboard, light variant

1. Clone the repo:

   git clone https://github.com/ai-automation-tools/cronsole.git
   cd cronsole

2. Bring up the dev stack (Postgres + Redis + backend + frontend):

   docker compose --profile docker up --build
   #   → frontend  http://localhost:7373
   #   → backend   http://localhost:3000   (GET /api/health to verify)

   Database migrations apply themselves on boot, so there is no schema step. (Verified 2026-09-11 from a clean clone on a machine that had never run Cronsole — which is the only way this can be checked, and how #90 was found.)

   [!IMPORTANT] The --profile docker is not optional. Backend and frontend are opt-in profiles, so a plain docker compose up starts Postgres and Redis only and nothing answers on :7373. Omit the profile when you want to run the backend and frontend as host processes instead (the manual path below).

3. Start the Windows agent so your real Task Scheduler tasks appear (PowerShell as Administrator; must run on the Windows host, not in Docker):

   cd agent
   Set-ExecutionPolicy Bypass -Scope Process -Force; .\setup-agent-startup.ps1

4. Open localhost:7373. The first load asks you to create the owner account — that is the only account-creation path there is, and it works once. After that, the Windows Agent status in the sidebar should read Online with your tasks imported.

# Backend — needs a PostgreSQL 16 instance
cd backend
cp .env.example .env        # then set DATABASE_URL + secrets (JWT_SECRET,
                            # ENCRYPTION_KEY, AGENT_PAIRING_SECRET) — the backend
                            # fail-fasts without them; see docs/setup/README.md
npm install
npm start                   # http://localhost:3000 — `prestart` migrates first

# Frontend — in a second terminal
cd frontend
cp .env.example .env.local  # set VITE_DEV_TOKEN so the dashboard can reach the backend
npm install
npm run dev                 # http://localhost:7373

# Windows agent — in a third terminal (Windows only)
cd agent/Cronsole.Agent
dotnet run                  # connects out to the backend, pushes Task Scheduler tasks

(back to top)

Full documentation lives in docs/. The main sections:

And the key guides, one click away:

Building Cronsole with an AI agent? The repo ships an Agent Skill — a briefing that gives Claude Code the project's mental model before it touches anything: the architecture, the invariants that must never break (schedules are cron-UTC, exec is never implicitly shelled, the registry is content-addressed), and the traps that quietly eat an afternoon (a Dockerized backend that won't hot-reload; an agent that must be republished).

# Windows — junctions, so no admin rights or Developer Mode needed
pwsh scripts/setup-skill-links.ps1

# macOS / Linux
./scripts/setup-skill-links.sh

Run once per clone, then restart your CLI — it activates automatically on Cronsole work. The script links skills/cronsole/ into .claude/skills/, so the agent reads the tracked source directly and no second copy exists to drift. The skill routes to docs/ rather than restating it, for the same reason.

Two more Cronsole skills live in the org's skill library — agent-skills › Skills/Projects/cronsole/. They cover the other half: not how to work on Cronsole, but how to design the jobs it schedules — the archetypes a Windows Task Scheduler job turns out to be, and the prompt contract a scheduled agent routine needs. Install them over this clone with that repo's installer.

Cronsole is an MVP-stage project. If you're working on it, start with CONTRIBUTING.md and CLAUDE.md, and track work on the Roadmap. Recent changes are logged in docs/CHANGELOG.md.

Before opening a PR, run the suites and — for anything touching the agent, real Task Scheduler, or security — the relevant manual runbook:

cd backend  && npm test && npm run test:integration
cd ../frontend && npm run lint && npm test
cd ../agent  && dotnet test

See 🧪 Testing for what each layer covers and where the gaps are.

(back to top)

Part of the mikesailab.com ecosystem · Documentation · Roadmap

_{© 2026 Michael Schecht · Licensed under Apache-2.0 · Local-first, pre-1.0}