Claude Prompt Scheduler Abhinav Biju מאת

1. Click the extension's toolbar icon.
2. Type your prompt, pick a date/time, click Schedule.
3. Keep Firefox running (minimized is fine) until that time.
4. At the scheduled time, the extension will find an open claude.ai tab
   (or open one if none exists), type your prompt, and click Send.

• Firefox must be running (not fully closed) at the scheduled time.
• Your laptop must not be asleep (see your power settings — you mentioned
  you're changing these separately).
• You should be logged into claude.ai already, since the extension doesn't
  handle login.

• Fixed-time or auto-detect scheduling. Fixed sends once at a chosen time.
  Auto-detect polls every minute and sends as soon as the page no longer
  looks rate-limited — see the heuristic caveat below.
• New chat toggle. Force a fresh conversation instead of reusing an
  already-open claude.ai tab.
• Auto-retry. Fixed-time jobs that fail (input box or send button not
  found) automatically retry up to 3 times, 2 minutes apart, before giving up.
• Dashboard (dashboard.html) — view/search/filter the live queue, edit
  a job's time/prompt/mode/new-chat setting inline, or delete it.
• History (history.html) — log of every send attempt: sent, failed,
  retrying, or missed (job's time passed while Firefox was closed).

There's no official signal for "your usage limit has reset." The content
script guesses using two checks together: the send button appears disabled,
and the page text matches patterns like "reached your limit", "try again
later", "usage limit". Both need to match to reduce false positives.

This is inherently fragile — if claude.ai changes its rate-limit UI wording,
auto-detect may never fire (safe failure: it just keeps waiting) or may
misfire. If you notice it's not triggering when you'd expect:

1. Open claude.ai while actually rate-limited, open devtools (F12).
2. Look at the exact text shown and inspect the send button's disabled/
   aria-disabled state.
3. Update LIMIT_TEXT_PATTERN near the top of content.js to match.

The UI follows a "scheduling console / departures board" concept — timestamps,
countdowns, and queued prompt text are set in JetBrains Mono (bundled locally
in fonts/, no network dependency), with Space Grotesk for headers and
interface labels. The queue page shows a "next departure" hero card for the
soonest fixed-time job with a live countdown, and the rest of the queue as a
board-style table. Status is shown via small colored LED dots (amber =
retrying, blue pulse = auto-detect watching, green = sent, red = failed)
rather than pill badges. All styling lives in styles.css, shared across
popup.html, dashboard.html, and history.html.

• manifest.json — extension config and permissions
• styles.css — shared design tokens and components (colors, type, buttons, board table, hero card, switches)
• fonts/ — bundled Space Grotesk + JetBrains Mono woff2 files
• popup.html / popup.js — quick-add UI: prompt, mode (fixed/auto-detect), new-chat toggle
• dashboard.html / dashboard.js — queue view: hero "next up" card, search/filter, inline editing
• history.html / history.js — log of past send attempts, filterable by status
• background.js — owns alarms, retry logic, auto-detect polling, and history logging
• content.js — injects prompt text, clicks send, and (for auto-detect) checks whether the limit looks cleared