Prompt-time is a Windows desktop reminder toolset for Claude Desktop. It survives MSIX boundaries, persists across restarts, and has zero dependencies. It uses only PowerShell and Windows Task Scheduler to schedule and manage reminders.

🛠️ Key Features

Three included tools: schedule_reminder, list_reminders, cancel_reminder
One-time or recurring desktop reminders
Zero external dependencies
Persists across reboots and app boundary changes

🚀 Use Cases

Schedule timely prompts from Claude Desktop on Windows
View all active reminders at a glance
Cancel reminders by ID as project needs evolve

⚡ Developer Benefits

Self-contained with minimal setup (PowerShell + Task Scheduler)
Clear command surface and ID-based management
Lightweight, easy to audit and extend

⚠️ Limitations

Desktop reminders limited to Windows environments
Relies on Windows Task Scheduler; requires appropriate permissions

prompt-time

Schedule Windows desktop reminders directly from Claude Desktop. Zero dependencies — just PowerShell + Windows Task Scheduler.

What it does

Adds three tools to Claude Desktop:

Tool	What it does
`schedule_reminder`	Set a one-time or recurring desktop reminder
`list_reminders`	Show every reminder currently scheduled
`cancel_reminder`	Cancel a reminder by ID

Reminders persist across reboots and Claude restarts. There is no cloud surface — everything runs locally.

Install in 60 seconds

Download prompt-time-v2.2.6.zip from the latest release.
Right-click the zip → Extract All. Windows must extract — running install.bat from inside the zip preview window will not work.
Open the extracted folder, double-click install.bat.
If Claude Desktop is running, the installer will prompt to restart it. Accept — the MCP tools only show up after Claude Desktop is restarted.
Done. The tools are live.

No Node, no npm, no admin rights, no internet required.

The extracted folder is disposable after install. v2.2.6+ copies both the MCP server and the watcher into the prompt-time data directory at install time, and points Claude Desktop's config + the scheduled task at the data-dir copies. You can move or delete the extracted folder afterwards without breaking anything. (Re-run install.bat from a fresh extract if you ever want to upgrade.)

Usage examples

Just talk to Claude:

"Remind me to send the weekly update at 4pm today" "Set a reminder every weekday at 9am to check my inbox" "Remind me about the board call next Monday at 2pm" "What reminders do I have set?" "Cancel reminder PROMPTTIME-A1B2C3D4"

Recurrence: once, daily, weekly, weekdays. Granularity is ~10 seconds (the watcher's poll interval).

How it works

Two pieces:

MCP server (prompt_time.ps1) — runs inside Claude Desktop's process tree. Validates and enqueues reminders to a JSONL file on disk.
Watcher daemon (prompt-time-watcher.ps1) — registered once at install as a Task Scheduler At LogOn task. Polls the queue, renders the toast popup in-process, and advances recurring entries.

The MCP server never talks to Task Scheduler at runtime, never spawns a process, and never displays UI. It only writes one JSONL line per reminder. Everything else is the watcher's job.

Why two processes — the MSIX boundary

Claude Desktop ships as an MSIX-packaged app. MSIX containers transparently virtualize file writes: a server running inside the package that calls Add-Content $env:APPDATA\prompt-time\queue.jsonl does not write to %APPDATA%\Roaming\prompt-time\queue.jsonl — it writes to a per-package shadow tree under %LOCALAPPDATA%\Packages\<package-family>\LocalCache\….

Anything Task Scheduler spawns runs outside the package, so a per-reminder schtasks task would look for files at the real path and find nothing.

prompt-time resolves this once: at startup, every component (prompt_time.ps1, prompt-time-watcher.ps1, install.ps1, uninstall.ps1) discovers the Claude AppX package and computes the same canonical data directory inside its LocalCache. Server writes and watcher reads land at the same physical file. The watcher renders the popup itself rather than asking Task Scheduler to do it, which keeps every state-bearing operation on the same side of the boundary.

The installer also pre-creates the queue file at the canonical path before the MCP server's first write — without that, MSIX file-virtualization redirects new file creation into the package shadow even though existing files at the real path are written through.

The same trap bites the Claude Desktop config itself. If MSIX-packaged Claude has ever written to its own claude_desktop_config.json (e.g. saving preferences), MSIX materializes a per-package shadow copy at %LOCALAPPDATA%\Packages\<family>\LocalCache\Roaming\Claude\claude_desktop_config.json and then reads from the shadow on every subsequent boot. An installer that writes only to %APPDATA% becomes invisible to Claude on those machines. v2.2.3+ reads shadow-first as the source of truth and writes the merged config to both paths atomically; uninstall removes from both. v2.2.4 adds post-write self-verify so install fails loudly with an actionable error if the entry doesn't survive (AV rollback, managed-policy override, etc.) instead of reporting a false success. Run diagnose.bat for a full breakdown.

Troubleshooting

Notifications muted by Focus Assist. Windows Focus Assist (Settings → System → Focus) silences toasts. Either turn it off or add powershell.exe to the Priority list.

Tools don't appear in Claude Desktop.

Fully quit Claude Desktop (right-click tray icon → Quit) and reopen it. The "X" close button only minimizes; tools won't reload.
Run diagnose.bat from the extracted folder. It reads your config, spawns prompt_time.ps1 the way Claude Desktop will, reads Claude Desktop's MCP logs, and prints an actionable hint for each failure. Most "install ran but nothing appeared" cases are diagnosed here without needing IT.
If diagnose.bat says all checks pass but tools still don't show: run diagnose.bat -Json and attach the output when filing a bug.

install.bat closes immediately. Run it from a cmd prompt instead so you can read the error: install.bat from inside the unzipped folder. The installer also writes a debug log at %APPDATA%\prompt-time\prompt-time.debug.log (or the MSIX LocalCache equivalent) — check there.

Reminders not firing. Check the watcher task is running:

powershell

Get-ScheduledTask -TaskName PROMPTTIME-Watcher | Get-ScheduledTaskInfo

LastTaskResult should be 267009 (running) or 0 (success).

Uninstall

Double-click uninstall.bat. It removes the prompt-time entry from Claude Desktop's config, deletes the PROMPTTIME-Watcher scheduled task, and clears the data directory. Other MCP servers in your config are untouched.

Tests

powershell

.\tests\run.ps1

Installs Pester 5 if missing, runs the Pester suite, and emits NUnit XML at tests/pester-results.xml. CI runs the same harness plus Invoke-ScriptAnalyzer on every push.

Security

See SECURITY.md for the trust model, supply-chain story, and how to report a vulnerability. Short version: the trust boundary is your local Windows user; reminder titles and messages are stored on disk in cleartext (don't put secrets in them); prompt-time registers a logon-time scheduled task as a standard persistence primitive.

License

MIT — see LICENSE.

Built by Ryan Stewart

io.github.RyanJamesStewart/prompt-time