FLUJOChoose your AI.
Use different models for different kinds of work.
Connect cloud providers, supported subscription logins, or a local model through Ollama. Save a connection once and reuse it across agents.
Connect your first AIStart with a task.
Grow from there.
Choose an AI, connect its tools, and save an assistant you can use again. Try Website Builder: keep its general instructions in the agent and give each website brief in chat.
Bring useful tools.
Let an assistant work with more than what you type.
Connect apps and tools through MCP, a common way for AI apps to connect to outside services. Install a server from GitHub, use a remote service, or choose a listed option. Review and test what you connect.
Connect tools for Website BuilderAnother example: try the coffee web-reading helper.
Make the steps yours.
A simple recipe, or a visual flow when you need one.
Choose an AI and the tools it may use. Add steps, branches, or reusable flows for a more involved task. You can review a run and inspect what happened along the way. Reuse a helper inside another agent, or bring agents into a shared meeting.
Explore the agent guidesPick up a goal.
Work with a persona that has a role and ongoing context.
Experimental Personas bring conversations, memory, and goals together. Review their work and keep the server running for scheduled activity. Short demonstrations don’t establish unattended reliability.
Meet MayaRun it again.
Give a repeatable task a schedule or a trigger.
Start agents on a schedule, a webhook, a file change, or a watched tool or page. FLUJO must be running, and failures or approval requests may need your attention.
Browse the feature guidesKeep work organized.
Separate projects, reuse connections, inspect results.
Workspaces organize your agents and conversations. Interactive connected apps can bring their own controls into the conversation. Backups and portable workers help move a setup; treat exports containing credentials as private.
Read about workspace transferFor the curiousConnect it to
Connect it to
your other software.
Developers can call FLUJO agents through an OpenAI-compatible endpoint and reuse configured tools through its MCP proxy. The in-app documentation explains the supported routes and limits.
Read the API guideA personal workspace, with clear boundaries. Local storage doesn’t make every request private to your computer. Cloud providers and remote tools receive request data. Connected local tools run with the server’s permissions. Workspaces organize projects; they don’t provide separate user accounts. Read the setup notes.