Keep Drive turns inside the window, retry 429s, and add a SCHEDULES modal

[ishu86]

Summary

• Drive now trims history by turn and asks OpenAI to compact before a long thread 400s; 429s retry instead of being treated as an unsupported-param fallback.
• Daily schedules keep an IANA timezone (box-local if omitted) and skip when the box is short on RAM. Compose points the scheduler at Drive's existing POST /api/brain, which reuses runTurn and CASE_DRIVE_API_KEY — no second runtime on the cased image.
• The Drive sidebar has a SCHEDULES modal (list, create, run, delete). Scheduled runs show up as Drive threads titled by the schedule name.

Made with Cursor

Greptile Summary

The PR keeps Drive history within provider limits, retries provider throttling, and adds timezone-aware scheduled Drive runs.

• Trims history at whole-turn and tool-call boundaries and adds OpenAI compaction support.
• Distinguishes rate limits from unsupported-parameter failures and applies cancellable backoff.
• Adds persisted schedule timezones, DST-gap handling, an HTTP scheduler-to-Drive path, and schedule management UI.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
web/web-ui/serve.mjs	Adds whole-turn history trimming, compaction, scheduled brain execution, and corrected rate-limit fallback behavior; the prior orphan-output issue is fixed by filtering all unmatched retained calls and outputs.
control-plane/scheduler.py	Adds timezone-aware scheduling, DST-gap validation before and after jitter, HTTP brain execution, and low-memory skip handling; both previously reported DST cases are addressed.
control-plane/store.py	Adds and migrates the nullable schedule timezone column and persists it on schedule creation.
web/web-ui/index.html	Adds responsive schedule listing, creation, immediate-run, and deletion controls.
web/web-ui/case-tools.mjs	Centralizes rate-limit detection and retry-delay calculation while preserving cancellation during backoff.
tests/test_scheduler.py	Covers named and box-local timezone behavior, DST gaps, jitter crossing a gap, HTTP brain outcomes, and resource-based skips.
web/web-ui/test_serve.mjs	Exercises history trimming across oversized turns and batched, non-adjacent tool call/output pairs.

Sequence Diagram

sequenceDiagram
    participant User
    participant UI as Drive UI
    participant Cased as Control Plane
    participant Scheduler
    participant Brain as POST /api/brain
    participant Provider
    User->>UI: Create schedule
    UI->>Cased: POST schedule with prompt, time, timezone
    Cased->>Scheduler: Persist next valid UTC run
    Scheduler->>Scheduler: Detect due schedule and check resources
    Scheduler->>Brain: POST computer_id, prompt, name
    Brain->>Provider: Run Drive turn with box credentials
    Provider-->>Brain: Responses and tool calls
    Brain-->>Scheduler: Completion summary
    Scheduler->>Cased: Persist run status and next run

Loading

_{Reviews (3): Last reviewed commit: "Keep daily jitter from landing in a DST ..." | Re-trigger Greptile}

[ishu86]

Jitter-after-DST: compute_next now re-checks the wall clock after adding jitter. If that lands in a spring-forward gap, the run moves to the next day that has that time.