Show upcoming scheduled wakes with live countdowns
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by locating the agent UI timeline or entity header that reads manifest schedule rows. Trace pending future_send rows, self-target matching, and cron rows, then check whether the existing runtime cron helper is browser-safe or exported. Done means pending wakes are visibly summarized with countdown or cron details, without overlapping the separate fired self-send rendering fix.
Written by the indexing model from the issue text.
Description
Summary
It would be useful for the agent UI to surface upcoming scheduled wakes, especially self-scheduled sends and cron schedules.
Examples:
- "The agent will wake again in 3:25" with a live countdown for pending self-targeted future sends.
- "Scheduled cron wake: every 5 minutes" and, if feasible, "next wake in 2:17" for cron schedules.
Motivation
When an agent sends a message to itself with afterMs, or has a cron schedule configured, the timeline currently doesn't make the upcoming wake obvious. A small notice would make scheduled autonomous behavior much easier to understand and debug.
Possible approach
Future sends
Use manifest schedule rows:
manifest.kind === 'schedule'
manifest.scheduleType === 'future_send'
manifest.status !== 'sent'
manifest.status !== 'failed'
For self-wake language, additionally require:
manifest.targetUrl === entityUrl
Then render a compact notice with a live countdown to fireAt:
Agent will wake again in 3:25Agent is waking now…- optionally
Scheduled wake overdueif still pending afterfireAt
For future sends targeting another entity, use different copy, e.g.:
Will send a message to /agent/foo in 3:25
Cron schedules
Use manifest schedule rows:
manifest.kind === 'schedule'
manifest.scheduleType === 'cron'
Initial UI could display the cron expression and timezone. A follow-up could compute the next fire time client-side if the existing runtime cron helper is browser-safe/exported, or if we add a small browser-safe helper.
Placement ideas
- Inline in the timeline as a compact schedule row.
- Entity header/status area as a persistent upcoming wake notice.
- Possibly both: header summary + timeline details.
Notes
This should be a separate PR from the self-send wake rendering bug fix. That PR makes fired self-send wakes readable; this issue is about making upcoming scheduled wakes visible before they happen.
- Dominant language
- TypeScript
- Stars
- 10.4k
- Forks
- 399
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from electric-sql/electric
-
camelToSnake and snakeCamelMapper() drop the underscore when a digit precedes a camelCase boundaryOpen
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
electric-sql/electric#4855 ·
-
ShapeStream does not notify subscribers when it gives up on a non-Error valuePossibly taken @Tyagiquamar claimed this 19 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
electric-sql/electric#4830 ·
-
@electric-sql/client throws SecurityError on import when the browser blocks site storage (typeof localStorage outside try)Possibly taken @mohanedmoh claimed this 37 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
electric-sql/electric#4826 · 1 comment ·
-
agents-chat-starter: spawn PUT goes to the durable-streams proxy, so no entity is created and agents never wakePossibly taken @adityavkk claimed this 133 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
electric-sql/electric#4687 ·
-
Listen IP addressOpenfeature request triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
electric-sql/electric#4150 · 1 comment ·
All issues in electric-sql/electric
Similar issues
-
area:cli area:security bug priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
"code source" and "numerique.gouv" links: "new window" mention duplicated in the accessible nameOpenaccessibility
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
numerique-gouv/lasuite-landingpage#315 ·
Maintainers usually reply within 1 day
-
needs:triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
HyeokjaeChoi/vaultme#585 ·
Maintainers usually reply within 1 day
-
enhancement priority/P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
beettlle/pi-smart-router#200 ·