Compare
WidgetFlow vs Macro
Compare a shared company workspace for teams with a desktop workspace for the tools you build. Both offer a canvas, tasks, docs, and connected agents.
See which tool fits your workflow| Topic | WidgetFlow | Macro |
|---|---|---|
| Workspace | Put tasks, docs, agent chat, and running local web apps in movable windows. | Bring company email, chat, calls, docs, tasks, and other team tools together. |
| Canvas | Open a running local web app in a window beside the project it supports. | Use a shared whiteboard to draw and plan with live references to docs, tasks, and other work.Macro Canvas guide |
| Files | Tasks and documents are Markdown files on your computer. SQLite indexes power search. | Collaborate on Markdown documents, edit an open doc offline, and sync on reconnect. Markdown export is available.Macro Docs guide |
| Agents | Connected agents can use project references and act through WidgetFlow’s local MCP server. | Connect a local coding agent, including Codex or Claude Code, to the team workspace.Macro agent setup |
| Availability | Public beta installer in preparation. | Sign up for the hosted workspace or self-host Macro under the AGPLv3 license.Macro self-hosting information |
Which tool fits your workflow?
Choose Macro if
- Your team wants shared work across email, chat, calls, tasks, and documents.
- You want people and agents to co-edit documents in real time.
Consider WidgetFlow if
- You already run local tools and want them beside your tasks and reference documents.
- You want the working copies of your tasks and docs on your computer as Markdown files.
- You want to give a connected agent reusable project context and have it act through a local MCP server.
The WidgetFlow team checked Macro’s published material on . Product details may change. Check WidgetFlow beta availability.
Keep exploring
Compare WidgetFlow and AFFiNE
Explore another approach to project work.
Try the browser demo
Arrange notes, tasks, and documents on the canvas.