From a human request to an agent update
Work where you already work. Keep agents in the loop.
The goal is a complete round trip—not simply an imported task or a successful login.
1. Choose cloud or portable
Cloud provides managed hosting and account-based access. Portable software runs on your hardware. They are separate offers with different operational responsibilities.
2. Connect your supported tools with consent
Select the resources you intend to synchronize. Connecting a task provider is separate from using Google or GitHub to sign in. Publisher setup is our deployment responsibility, not a request for each cloud customer to visit developer consoles or paste app secrets.
3. Bind the agent’s work surface
Use the supported CLI, API, MCP or task-authority integration on the agent’s server. Grant only the required workspace access. Your agent runtime decides how work is executed; Flow Mesh synchronizes the associated task state.
4. Complete a real round trip
Create or update a task in your board. Have the authorized agent pick it up through its connected work surface, update progress and return a result. Confirm that the human sees the change back in their board—and that later human corrections reach the agent’s work surface.
5. Keep the connection understandable
Review real activity, reconcile conflicts and reconnect when a provider revokes consent. Export and backup paths matter because synchronization should not lock you into one interface or obscure the state of your work.