System status
What Taskmorrow can do, what needs a connection, and what is not included.
This page is the plain-language boundary model. The product should feel useful now without pretending external providers are already connected.
Built now
These capabilities work as local or copy/export flows today.
- Local reminders
- Check-ins
- Prepared drafts
- Approval queue
- Preference memory
- Tomorrow planning
- Action ledger
- Copy/export fallback
Connection required
These are meaningful external actions. They require a real provider connection and explicit confirmation.
- Gmail draft creation
- Calendar writes
- SMS sending
- Cloud sync
Being hardened
These areas are being tightened before they are pushed harder in the product experience.
- Mobile polish for non-technical users
- Clearer onboarding around one-task capture
- Boundary copy consistency across app surfaces
- Provider connection handling before any external write is exposed
Not included
These are intentionally outside the consumer assistant wedge.
- Hidden sending
- Autonomous purchases
- Social posting
- Enterprise admin
- Developer marketplace
- Crypto or trading actions
The boundary is simple: Taskmorrow prepares. You approve.
If a provider is not connected, Taskmorrow should still be useful: copy the draft, export the object, keep the reminder, or log the next step. It should never hide limitations behind vague automation language.