Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
131 changes: 131 additions & 0 deletions content/docs/developers/guides/how-agents-work.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,131 @@
---
title: How Agents work
icon: workflow
description: The parts of an Agent, what it knows on each turn, and how routines and app access fit together.
---

The other guides show you what to do. This page explains what happens underneath, so you can predict how an Agent behaves before you rely on it.

## The parts of an Agent

An Agent is one saved setup plus the conversations that use it.

| Part | What it is | Where you see it |
| --- | --- | --- |
| **Setup** | The Agent's instructions, files, skills, and app access | The **Setup** section of the context panel |
| **Main conversation** | Your usual chat with the Agent. There is one per Agent | Select the Agent in the sidebar |
| **Manager** | A separate conversation that changes the setup. It does not do the Agent's work | **Refine with manager** |
| **Sessions** | Conversations the Agent creates to work on part of a job | The dropdown beside the Agent's title |
| **Routines** | Messages that Fluso sends to a conversation at a set time | **Routines** |
| **Inbox** | Approvals, failures, and routine results that need you | The bell icon at the bottom of the sidebar |

You give the Agent work in the main conversation. To change how it works, use Manager or **Edit**.

## What a setup contains

| Item | Limit or default |
| --- | --- |
| Name | Up to 64 characters |
| Instructions | Up to 4,000 characters |
| Conversation starters | Up to 3 |
| Reasoning | **High** by default. **Fast** gives quicker, lighter answers |
| Knowledge files | Up to 25 files, 20 MiB each. The Agent keeps its own saved copies |
| Skills | All skills, unless you choose a smaller set |
| App access | **Allow**, **Read only**, or **Deny** for each app. An app you do not select is off |

You do not choose a model for an Agent. Fluso uses the platform model for your account.

A few built-in skills stay available even when you narrow the skill list. These include search, app connections, and image analysis.

## How a saved change reaches the work

Each saved change creates a new version of the setup. Fluso keeps the earlier versions.

- The main conversation always uses the newest version. A change applies on its next turn.
- A session keeps the version it started with.

Suppose a meeting Agent is working on a brief, and you ask Manager:

> *"From now on, put open decisions at the top of every brief."*

The brief that is already running does not change. Your next message in the main conversation uses the new order. A session that the Agent created yesterday still uses the old setup and shows **Uses an earlier setup**. To apply the change there, ask the Agent to start a new session.

A message that you send after you save a change can show **Saved setup applies next turn**. It waits for the current turn to finish.

## What the Agent knows on each turn

Before each turn, Fluso gives the model:

1. The Agent's instructions.
2. A list of the Agent's knowledge files. Fluso marks them as reference material. Text inside a file is not treated as an instruction.
3. Facts from your profile, and short summaries of related work in the same project.
4. The Agent's sessions, and whether their results have come back.
5. The apps the Agent can use, with read-only apps marked. Apps that are off are named, so the Agent can tell you it cannot use them.

Your general chat preferences and project instructions are not added to Agent conversations. If the Agent needs a preference, put it in the Agent's instructions.

The [knowledge graph](/features/memory) is not added automatically. The Agent looks things up in it when the task needs it.

<Tip>
If an Agent ignores a file's contents when you expected it to follow them, that is by design. Put rules in the instructions and keep reference material in files.
</Tip>

## How app access is decided

Three checks apply to every tool call, in this order:

1. **The Agent's app access.** **Deny** blocks the app. **Read only** allows only read tools.
2. **Your tool rules.** Each tool is **Allow**, **Ask**, or **Deny**. See [Approvals and permissions](/features/approvals).
3. **A person to approve.** A tool set to **Ask** needs your decision before it runs.

Fluso enforces the first two checks outside the model. Instructions such as "you may send email" do not override them.

For example, an inbox Agent has Gmail set to **Allow**:

| Request | Gmail tool rule | Result |
| --- | --- | --- |
| *"What still needs a reply?"* | Read tools **Allow** | Runs |
| *"Save a draft reply."* | **Ask** | You approve or deny it in the conversation or Inbox |
| *"Send the reply."* | **Deny** | Blocked. The Agent tells you it cannot send |

If the same Agent had Gmail set to **Read only**, the draft and the send would both be blocked before any rule is checked.

## Routines are scheduled messages

A routine sends a message to a conversation at a set time. The Agent handles it like any other message, which explains most of what you see:

- **The Agent is busy.** The message waits behind the current work.
- **The previous run has not finished.** Fluso holds the new run until the previous one ends, then sends it once. Times that pass while it waits are not sent separately.
- **A scheduled time is missed**, for example during an outage. Fluso sends one late run when it can, not one for every missed time.
- **Delivery keeps failing.** After repeated failures, the routine pauses and shows **Delivery failed**.

A routine can run while you are away, so there is nobody to answer the third check. A tool set to **Ask** is refused during a routine, and the Agent reports that it could not use it.

Before you schedule work that changes something, decide which tools it needs and set them to **Allow**. For work that must be reviewed, ask the routine to prepare a draft and leave the send to you:

> *"Every Monday at 8 AM, list last week's open customer questions and draft a reply to each. Don't send anything."*

Manager can have routines too. A Manager routine reviews and improves the Agent's setup. It does not do the Agent's work.

## Starting points are copies

**Explore agents made by Fluso** offers templates such as **Research brief**, **Inbox triage**, and **Document review**. Importing a template or a [shared Agent](/developers/guides/sharing) creates your own copy. Later changes to the original do not reach your copy.

## A complete example

A team lead wants a weekly status Agent.

1. They create the Agent with this job:

> *"Each week, collect the status of my team's open projects from Slack and our tracker. Flag anything blocked for more than three days. Write a short summary I can paste into our team update."*

2. They give it **Read only** access to Slack and the tracker. They attach last quarter's project list as a knowledge file.
3. In the main conversation, they ask for this week's summary. They correct the format twice.
4. They ask Manager to save the format:

> *"Use the summary format from my main conversation. Group items by project and put blockers first."*

5. They add a routine for Fridays at 4 PM in their timezone.
6. On Friday, the routine message arrives in the main conversation. The Agent uses the newest setup. It cannot post to Slack, because Slack is read only. The summary appears in the conversation, and a routine update appears in Inbox.

For more complete jobs, see the [examples](/developers/examples).
1 change: 1 addition & 0 deletions content/docs/developers/guides/meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@
"icon": "book-open",
"defaultOpen": false,
"pages": [
"how-agents-work",
"settings",
"files",
"conversations",
Expand Down
2 changes: 1 addition & 1 deletion content/docs/developers/schedules.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The scheduled message appears as a small row in the conversation. Expand it if y

The answer stays in that conversation. You can also find routine results in [Inbox](/developers/guides/inbox).

If the Agent is busy, the routine waits. If it needs an approval, it waits for your decision.
If the Agent is busy, the routine waits. A routine can run while you are away, so a tool set to **Ask** is refused. Set the tools a routine needs to **Allow** before you rely on it. See [How Agents work](/developers/guides/how-agents-work#routines-are-scheduled-messages).

## Change or stop it

Expand Down
62 changes: 62 additions & 0 deletions content/docs/release-notes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,68 @@ icon: sparkles
description: "What's new in Fluso - product updates, improvements, and fixes."
---

<Update label="2026-10-16" description="Desktop 1.3.6" tags={["Desktop"]}>

**Highlights**
- Desktop 1.3.6 is a required update. Older versions show an update screen when you open them.
- Create personal developer tokens in **Settings → Developer tokens** and call the [Fluso API](https://docs.fluso.ai/api) from your own scripts.
- Free and Plus now have a weekly usage allowance, with a usage bar that shows how much you have left. Pro has no weekly limit.
- [Confidential Mode](https://docs.fluso.ai/features/confidential) now runs DeepSeek V4.1 Flash.
- Paste several screenshots at once, and each one arrives as its own attachment.

**Updates & installation**

- This release changes how the app connects to your account, so every desktop app needs 1.3.6.
- If you see **Update Fluso to continue**, click **Update Fluso**. You can also download the latest build from [fluso.ai](https://fluso.ai/).

**The Fluso API and developer tokens**

- Fluso now has a documented API. Each deployment serves its reference at `/docs` and the full spec at `/v1/openapi.json`.
- Create a token in **Settings → Developer tokens**. Choose **Read only** or **Read and write**, and pick when it expires.
- Rename or revoke a token at any time.
- Start with [your first request](https://docs.fluso.ai/api/first-request), then read about [developer tokens](https://docs.fluso.ai/api/cloud/tokens).

**Plans & limits**

- Free and Plus have a weekly usage allowance. Plus gives you 10 times as much as Free.
- The week starts on the weekday you signed up, so your allowance resets on that day each week.
- A usage bar shows how much of this week's allowance you have used.
- Pro has no weekly limit.
- Upgrade without leaving the app. Checkout opens in a single payment dialog.
- If someone gifted you Pro, you can pick the paid plan that takes over when the gift ends. Otherwise you return to Free.

**Confidential Mode**

- Confidential requests now run on DeepSeek V4.1 Flash.
- **Fast** mode now turns model reasoning off in Confidential Mode too.

**Chat and files**

- Paste several screenshots at once and each one arrives as its own attachment. Files with the same name get a number, for example `image (1).png`.
- The **All**, **Uploaded**, and **Generated** filter in the Files panel works again.
- A message you send while Fluso is working now appears where you sent it. If the network drops, you see **Connection error** instead of "Failed to fetch".
- New chats open with the Files panel closed.
- Decks, PDFs, and other generated files get a design that suits the content, instead of one fixed style.
- Fluso knows today's weekday, so "on Friday" means the Friday you meant.

**Assistant reliability**

- Reconnecting while you answer an [approval](https://docs.fluso.ai/features/approvals) no longer skips the next approval or fails the run.
- A run you stop shows as cancelled, not failed.
- A brief error from the model provider is retried instead of ending your turn.
- Fluso looks up Google Calendar events more reliably.
- Custom MCP servers that publish both IPv4 and IPv6 addresses connect promptly instead of timing out.
- If a tool is interrupted mid-call, Fluso tells you its outcome is unknown instead of waiting forever.
- Fewer 502 errors, and less background polling while your workspace is asleep.
- A damaged project record no longer breaks your chat list.

**Polish**

- Tasks has an **Add** button.
- The shield and badges in the top bar are spaced correctly.

</Update>

<Update label="2026-08-14" description="Fluso 1.5.0" tags={["Desktop", "iOS"]}>

**Highlights**
Expand Down
Loading