First — thanks for Pad. We piloted it as the queryable work-state layer for a small multi-repo/agent setup, and the agentic-first design (playbooks, trigger-scoped conventions, project standup/reconcile, the typed dependency graph) has held up genuinely well over a couple of weeks of real use. The reconcile + stale surface in particular is a great fit for autonomous agents.
Gap we hit: there is no native due-date or reminder/scheduled-notify primitive. stale/reconcile/standup are excellent reactive signals (time-since-update), but nothing fires proactively at a target time — so anything shaped like "revisit TASK-X on 2026-08-01" or "this deferred item wakes up next Tuesday" has to live in an external scheduler (cron, etc.), outside the work-state layer that otherwise owns "what/when."
What would close it (rough shape, non-prescriptive):
- An optional
due (and maybe remind_at) field on items — surfaced in dashboard/ready/stale and sortable/filterable.
- A time-based trigger that can fire a webhook (you already have the webhook surface) or mark an item "reminder due" so an agent polling
ready/stale picks it up — no push-notification infra needed on your side.
Modeling a due field via a custom collection schema is possible today, but there is no engine to act on it, which is the actual missing half.
Happy to help test if useful. Thanks again for building this in the open.
First — thanks for Pad. We piloted it as the queryable work-state layer for a small multi-repo/agent setup, and the agentic-first design (playbooks, trigger-scoped conventions,
project standup/reconcile, the typed dependency graph) has held up genuinely well over a couple of weeks of real use. Thereconcile+stalesurface in particular is a great fit for autonomous agents.Gap we hit: there is no native due-date or reminder/scheduled-notify primitive.
stale/reconcile/standupare excellent reactive signals (time-since-update), but nothing fires proactively at a target time — so anything shaped like "revisit TASK-X on 2026-08-01" or "this deferred item wakes up next Tuesday" has to live in an external scheduler (cron, etc.), outside the work-state layer that otherwise owns "what/when."What would close it (rough shape, non-prescriptive):
due(and mayberemind_at) field on items — surfaced indashboard/ready/staleand sortable/filterable.ready/stalepicks it up — no push-notification infra needed on your side.Modeling a
duefield via a custom collection schema is possible today, but there is no engine to act on it, which is the actual missing half.Happy to help test if useful. Thanks again for building this in the open.