Apps roadmap
Discoflare apps are top-level workspace surfaces that share one membership and authorization model. Integrations connect an external capability. These are different product boundaries.
Available
| App | Released role |
|---|---|
| Chat | Channels, Direct Messages, Threads, files, presence, notifications, and optional Huddles. |
| Tasks | Boards and durable Agent work with assignment, dependencies, progress, results, and Run history. |
| Shared domain Mailboxes, external conversations, Internal Notes, and per-Mailbox access. |
In development: Data
The Data app is being developed as a human-managed structured workspace surface. The current scope is deliberately smaller than a general database platform:
- workspace Databases;
- typed custom Fields;
- inline Record editing;
- filtering and sorting; and
- permission-gated schema and Record changes.
Data remains in D1 as workspace state. It does not provision a separate Cloudflare D1 database for every user-created Database, and Tasks or Mail will not be reduced to special cases of this generic record model.
Until Data is included in a tagged release, operators should not expect it in a fresh installation or build workflows around its draft schema.
Exploring: Project
A Project surface may connect Task execution to an existing GitHub repository, pull requests, checks, previews, and deployment evidence. The design goal is coordination and visibility; GitHub remains the source-control and review system.
See the Agents roadmap for the proposed first repository workflow.
Planned cross-app work
- clearer links between source conversations, Tasks, Mail conversations, structured Records, and Agent Runs;
- consistent search and activity signals across app boundaries; and
- evidence views that distinguish saved workspace state, external-provider state, and deployed runtime state.
Not available today
Discoflare does not currently expose an installable app marketplace, arbitrary third-party app runtime, or compatibility promise for draft internal APIs. New extension points need a permission, data, audit, and upgrade model before they can become a public platform surface.