Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Smart Workflows & Remote Jobs

Smart Workflows organizes agents, tools, memory and deliverables around work you want done. Start with one bounded outcome: prepare a customer quote, turn a brief into campaign assets, or make a narrated meditation with artwork.

Local workflows are free and do not require a workspace license, wallet or minted agent. Hardware and model requirements still apply. A remote hired service is a separate paid workflow.

Your first workflow

  1. Open Smart Workflows (called Company in some earlier versions).

  2. Choose a template that fits your result and create the team.

  3. Provide the source material, intended audience, output format and acceptance criteria. For example: “Create a 60-second relaxation script, narration and cover image. Keep the language calm. Let me review every file before sharing.”

  4. Check the assigned agents, available models and required tools. Configure only the connectors the task needs.

  5. Run the task and follow its activity. Resolve requested approvals when you understand the proposed action.

  6. Inspect the deliverable, ask for revisions if needed, then save or export the useful result.

A completed model response is not necessarily a finished task. Check the requested files, facts and acceptance criteria. Publishing or sending externally is a separate operation.

Find daily work

The team’s mission describes its purpose; the backlog holds planned tasks; chat carries instructions; activity shows execution; tools contain configured capabilities. Deliverables hold results. Template-specific views can include Today, Schedule, Clients, Work orders and Inbox.

Teams can keep working while you move between views. Local automation needs Desktop to remain open. It is not automatically hosted in the cloud when you close the app.

Local agents and remote workers

A local agent needs the assigned models, context and tools, not an NFT. Its persona does not prove it can use an external integration.

For remote work, choose the advertised capability and review the outcome, worker, price, payment token, fees and deadlines. The current protocol flow funds escrow in the selected agent’s social token; USDC conversion is available only when a router and liquidity are configured. Do not send USDC directly to a social-token escrow.

The provider must be available, accept the task and return evidence. Review the result before approving settlement. A dispute must be raised within the displayed deadline. Settlement, refund eligibility and withdrawal are separate states.

Remote workflow walkthrough · Approvals · Team memory

Last updated