Workflows
Workflows explain how a request becomes an ongoing, reviewable, and recoverable result. Each article follows the shape of its feature instead of repeating a generic tutorial template.
| Workflow | Current conclusion | Best for |
|---|---|---|
| Projects and chats | Confirmed | Multi-chat projects, one-off chats, local folders, and repositories. |
| Sites | Confirmed; some entries are capability-gated | Site creation, local preview, H5 export, managed hosting, or SSH deployment. |
| Visualizations | Confirmed | Create charts, dashboards, calculators, interactive explanations, and HTML/SVG components in Chat or Cowork tasks. |
| Scheduled tasks | Confirmed | Timed or recurring runs, run history, pause, and edit. |
| Long-running work | Confirmed | Goals with explicit completion evidence and multiple execution rounds. |
| Notifications | Confirmed | Completion, failure, recovery, and approval updates. |
| Pets | Confirmed | Desktop state, completion bubbles, and returning to a conversation. |
Choose a workflow
- Create a project when work will span conversations, files, or persistent rules.
- Use Sites for a web deliverable; use a visualization when the result belongs inside the conversation.
- Use scheduled tasks when the same work should run at a defined time; use a goal when EvoX must keep deciding the next step until an outcome is reached.
- Notifications and the desktop pet surface state; the authoritative details remain in the task or run record.
Shared boundary
Project membership does not grant file, browser, plugin, or external-account access. Publishing, deletion, spending, credentials, production writes, and public sharing require an explicit scope and post-action verification.
EvoX Docs · Features · Workflows