> fix the flaky retry test
edit src/retry.py
run pytest tests/test_retry.py
2 passed, 1 failing
history is on the hub
The data is synthetic. The endpoints and tool names are real.
Continue a session on another host and harness. Answer its approval from your phone.
> fix the flaky retry test
edit src/retry.py
run pytest tests/test_retry.py
2 passed, 1 failing
handoff brief from laptop/codex
drover_recall_bundle("retry test")
summary + 1 open loop + 3 files
resuming at tests/test_retry.py
3 passed
waiting for approval:
git push origin fix/retry-jitter
approved. pushing...
git push origin fix/retry-jitterSynthetic data.
POST /harness/sessions/{id}/continue starts the new session and briefs it.Your orchestrator plans and reviews. Drover runs the sessions and records them.
Add rate limiting to /export
studio · codex
PR #212
Migrate the config loader
laptop · claude-code
PR #213
Document the export API
buildbox · codex
PR #214
Synthetic data.
An agent that connects to the hub can query past sessions. Type a query or select one.
Removed the Redis cache in front of quote lookups. It hid stale prices after a currency update and saved under 4 ms. Replaced it with an in-process LRU keyed by rate version.
The retry test failed about one run in twelve because jitter was not seeded. Seeded the RNG in the fixture and tightened the backoff assertion.
Added constant-time signature checks for inbound webhooks and a replay window of five minutes. Rejected requests are counted but not logged with their body.
Switched /export from offset to cursor pagination after a timeout on large accounts. Kept the old parameter working behind a deprecation warning.
Synthetic data.
drover_search, drover_recall_bundle and drover_open_loops are real MCP tools.