Open architecture
Keep a usable copy of your work and move it through documented files, links, and APIs.
Fluso keeps core work in ordinary formats instead of locking every object behind one interface. You can download project files, move Agent definitions, and read conversation history through the API.
Different exports serve different purposes. A project ZIP is a file backup; a shared Agent is a reusable setup; a shared chat is a reviewable snapshot.
What you can take out
| Data | Export path | What you receive |
|---|---|---|
| Projects and files | Open Projects, use the project's ••• → Export as zip, or open a project and select Export | A ZIP of the project's regular files, their folder paths, context.md, and project metadata; empty folders are omitted |
| Individual files | Open a project file and select Download | The original file in its stored format |
| Shared project files | Open a project file, select Share, then create a link | A revocable public link to the selected file |
| Generated documents and presentations | Use the artifact's export menu | Documents as PDF, Word, HTML, or Markdown; presentations as PDF, PowerPoint, or a Google Slides copy |
| Agent copies | Open the Agent's actions menu, then Share | A revocable snapshot of the setup and selected resources that another person can import |
| Conversation history | Open a chat and select Share chat, or read messages with the Threads API | A revocable public snapshot, or structured persisted messages through the API |
Project ZIPs skip dotted runtime entries and symbolic links. They do not serve as a complete conversation archive. Use the Threads and messages API when you need persisted chat records in a system you control.
Skills stay readable
Open Plugins → Skills and select a skill to read its SKILL.md. This is the instruction document Fluso follows.
The skill document is view-only. For a custom skill you own, keep its SKILL.md and source files before removing it from Fluso. An Agent share can include selected custom skill folders; built-in skills remain references to the recipient's installed versions.
What an Agent share includes
Instructions and settings are included. You choose whether to include knowledge files, complete custom skill folders, and custom connection URLs. Built-in skills and missing reference files are listed by name.
Stored account credentials, conversations, routines, and project files stay private. The recipient connects their own apps. Publish later changes explicitly with Update shared version, or revoke the link with Stop sharing. Imported copies remain independent.
See Sharing and copies for the full flow and resource limits.
A practical handoff
To hand a customer-support workflow to another team:
- Export the support project as ZIP so they receive the runbooks and working files.
- Share the Agent's saved setup and any reference files the recipient needs.
- Share any example conversation as a snapshot, removing sensitive messages first.
- In the destination workspace, import the Agent, upload the project files, connect Apps, and try a real task before scheduling work.
These exports are independent snapshots. Later Fluso changes do not silently rewrite the copies you already saved.
APIs for continuous access
Use API access when a one-time download is not enough. The account API covers Agents, conversations, files, schedules, runs, and usage on Cloud and daemon workspaces. Authenticate with a Cloud developer token or a paired daemon token. Store only the data your integration needs.