diff --git a/AGENTS.md b/AGENTS.md
index 21957f8..0aafd1d 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -13,12 +13,12 @@
The navigation keeps Home first and sorts the top-level sections alphabetically. Agents follows the user journey. Other sections keep their existing order:
- **Agents (Beta)** - `/developers/*`. Start with a familiar task, then improvement and scheduling. Keep Examples and More about Agents (`/developers/guides/*`) collapsed by default. Introduce features when they help the reader's current task. Keep prompts natural and explain terms before using them.
-- **App setup** - `/integrations/{github, gmail, google-calendar, slack, zoom}`. Per-app permissions and prompts, not feature pages. All of them connect through the Apps tab of the Add MCP dialog.
-- **Deployment models** - `/deployment-models`. Current availability and operating boundaries for Fluso Cloud, dedicated AWS VPC, planned Azure VNet, and scoped on-premises deployments.
+- **App setup** - `/integrations/{github, gmail, google-calendar, slack, zoom}`. Per-app permissions and prompts, not feature pages. Use the current Apps catalog under Plugins → MCP → Add MCP. Google services connect separately; native Fluso connectors have the Fluso mark.
+- **Deployment models** - `/deployment-models`. Released Fluso Cloud and custom Enterprise deployments requiring confirmed scope.
- **Features** - `/features/*`. Approvals and permissions, Apps and MCP servers, Chat, Confidential mode, Imports, Memory, Projects, Skills, and Tasks.
-- **Fluso API** - `/api/*`. Start with access and a first request. Document shared workflows once under Use the API. Lead with a useful task, runnable requests, and the expected result. Reuse the deployment's example helpers. Put protocol details and recovery rules beside the step that needs them. Each deployment's `/docs` and `/v1/openapi.json` own exact request and response schemas. Keep endpoint tables collapsed after the workflow. Preserve old API URLs with redirects.
+- **Fluso API** - `/api/*`. Start with access and a first request. Document the released Cloud API; do not publish daemon setup or pairing instructions. Document shared workflows once under Use the API. Lead with a useful task, runnable requests, and the expected result. Reuse the deployment's example helpers. Put protocol details and recovery rules beside the step that needs them. Each deployment's `/docs` and `/v1/openapi.json` own exact request and response schemas. Keep endpoint tables collapsed after the workflow. Preserve old API URLs with redirects.
- **Get started** - `/going-deeper`, `/introduction`, `/quickstart`. These pages explain the path from first setup to daily use.
-- **Reference** - `/resources/{faq, legal, pricing}`. Legal links to the terms of service at `https://fluso.ai/terms` and privacy policy at `https://fluso.ai/privacy`; do not duplicate the policies in the docs.
+- **Reference** - `/resources/{availability, faq, legal, pricing}`. Legal links to the terms of service at `https://fluso.ai/terms` and privacy policy at `https://fluso.ai/privacy`; do not duplicate the policies in the docs.
- **Release notes** - `/release-notes`. Customer-facing changes, newest first.
- **Workflows** - `/workflows/*`. Six concrete stories: bug-to-PR, content launch, knowledge recall, meetings, morning brief, and research-to-deck.
@@ -34,16 +34,16 @@ This is the mental model the docs use. Every page should reinforce it, not contr
- **Apps & MCP** are the plugs into external apps. Every connection is an MCP connection: managed apps from the catalog, or custom servers by URL.
- **Skills** are the capabilities Fluso reaches for when a request matches one (built-in or custom via `SKILL.md`).
- **Tasks** is the unified to-do system, populated mostly automatically.
-- **Memory** is the knowledge graph that builds in the background.
+- **Memory** includes saved preferences, project context, and working-memory summaries. Do not promise complete automatic indexing of every connected app.
Email, calendar, code, content, research are skills, not separate features. The skills page (`/features/skills`) is the catalog. Per-app integration pages (`/integrations/*`) cover setup and permissions.
## Terminology
- **Fluso** — the product.
-- **Apps** / **MCP connections** — the connections to third-party apps. There is no separate connector system; connections live under **Plugins → MCP**. Use **Connectors** when referring to the Agent editor's capability picker.
+- **Apps** / **MCP connections** — the connections to third-party apps. Native Fluso and provider-managed connections live under **Plugins → MCP**. Use **Connectors** when referring to the Agent editor's capability picker.
- **Agent** — saved setup and a continuing main conversation. **Manager** refines that one Agent; **sessions** are delegated conversations; **routines** are scheduled messages. Main conversations take saved setup changes on their next turn; existing delegated sessions retain their setup.
-- **Knowledge graph** — Fluso's persistent memory. Lowercase.
+- **Memory** — saved context with the boundaries described on the Memory page.
- **Skills** — specialised capabilities that activate automatically. Built-in or custom (`SKILL.md`).
- **Projects** — workspaces that scope context, files, and tasks.
@@ -84,11 +84,17 @@ Use the [ASD-STE100 writing skill](https://github.com/danyuchn/asd-ste100-skill/
## Content boundaries
+- Compare current production release evidence and feature configuration with source before describing a feature as available. A dev merge is not a public release.
+- Fluso Local is not enabled in production; the Telegram bot is retired. Keep their setup guides out of navigation, search, and generated Markdown. Redirect old routes to Availability. Preserve historical release notes.
+- All standard plans have weekly allowances: Plus is 10 times Free, Pro is 10 times Plus. Do not publish pending accounting changes or internal budget values.
+- Native connectors do not imply every catalog entry is native. Encrypted inference does not imply enclave-hosted workspace storage, tools, or connected apps.
+- Do not publish an unconfirmed release date, bug-fix version, or measured performance claim.
+
- Fluso Admin is internal. Do not publish its operator guide, navigation, links, or panel instructions in this public documentation site.
- Never invent feature behaviour. If a capability isn't documented in source materials, leave it out.
- When describing external sends, explain how to request and review a draft and choose **Ask me first**. Do not claim every write requires approval: saved tool rules, connection settings, and the chat's mode determine that behavior.
- Verify Agent behavior against both current frontend and backend code. Do not restore removed Studio graphs, evaluations, version rollback, YAML transfer, webhook triggers, or thread-management toggles from historical release notes.
-- For product actions, point users to the macOS download at `https://fluso.ai/` and to support at `support@premai.io`. Don't link to `app.fluso.ai`. Fluso is a desktop app.
+- For product actions, point users to the desktop downloads at `https://fluso.ai/` and to support at `support@premai.io`. Don't link to `app.fluso.ai`. Fluso has macOS, Windows, and iOS apps. Desktop guides do not establish mobile feature parity.
## Publishing release notes
diff --git a/content/docs/api/cloud/apps.mdx b/content/docs/api/cloud/apps.mdx
index b0363c6..746b4cf 100644
--- a/content/docs/api/cloud/apps.mdx
+++ b/content/docs/api/cloud/apps.mdx
@@ -4,10 +4,16 @@ icon: plug
description: Connect a supported Cloud app when your integration needs its data or tools.
---
-Cloud can guide users through connecting supported apps, such as Google Workspace. A connection belongs to the authenticated account. Completing sign-in does not remove its tool-approval rules.
+Cloud can guide users through connecting supported apps, such as Gmail. A connection belongs to the authenticated account. Completing sign-in does not remove its tool-approval rules.
For a custom server, use [custom MCP connections](/api/workflows/connections).
+## Native and provider-managed apps
+
+Read the current catalog rather than hard-coding app IDs. Its `connect_kind` distinguishes native Fluso, Google, Microsoft, and provider-managed flows. Only configured services are available. Google services have separate entries.
+
+An app may require an API key or account-specific setup instead of OAuth. If the catalog flow returns `API_KEY_REQUIRED` or `SUBDOMAIN_REQUIRED`, complete that setup in Fluso, then recheck the connection. Do not treat a provider redirect or an old saved connection as proof that migration is complete.
+
## Connect the requested app
For example, a morning-brief Agent may need a calendar connection. Its run can enter `waiting_action` with an `mcp_connect` action in thread state.
diff --git a/content/docs/api/cloud/client-sign-in.mdx b/content/docs/api/cloud/client-sign-in.mdx
index ba025a8..c3385b6 100644
--- a/content/docs/api/cloud/client-sign-in.mdx
+++ b/content/docs/api/cloud/client-sign-in.mdx
@@ -73,7 +73,7 @@ Use `auth.access_token` as `Authorization: Bearer TOKEN` for API requests. Save
Store `auth` in the client's credential store. It includes `access_token`, `refresh_token`, `expires_in`, `session_id`, and `user`.
- The browser step calls `POST /v1/auth/client/complete` with the returned state under the user's Clerk app session. Current browser callbacks support configured Fluso handoffs. A developer token cannot perform that browser step.
+ The browser step calls `POST /v1/auth/client/complete` with the returned state under the user's Clerk app session. Only configured Fluso callback clients are supported. A developer token cannot perform that browser step.
Sign-in state expires after ten minutes. The returned code expires after five minutes and works once. If the exchange response is lost, start sign-in again.
diff --git a/content/docs/api/first-request.mdx b/content/docs/api/first-request.mdx
index ffea445..49670cf 100644
--- a/content/docs/api/first-request.mdx
+++ b/content/docs/api/first-request.mdx
@@ -20,7 +20,7 @@ Set the URL for your workspace:
export FLUSO_API_URL='https://api.fluso.ai/v1'
```
-For Fluso Dev, use `https://api.dev.khichdi.cc/v1`. The token must belong to that workspace.
+The token must belong to your production Cloud account.
Read your token without showing it or saving it in shell history:
diff --git a/content/docs/api/index.mdx b/content/docs/api/index.mdx
index f3232f6..8c5e736 100644
--- a/content/docs/api/index.mdx
+++ b/content/docs/api/index.mdx
@@ -12,9 +12,11 @@ Start with one conversation. Add schedules, connections, or live updates when yo
Get access, submit a short task, and read the saved answer.
-## Base URL and access
+## Use your Cloud workspace
-Send requests to `https://api.fluso.ai/v1` with a [developer token](/api/cloud/tokens). Fluso Dev uses `https://api.dev.khichdi.cc/v1`. Use credentials from the same environment as the URL.
+The production base URL is `https://api.fluso.ai/v1`. Authenticate with a [developer token](/api/cloud/tokens) from the same account you use in Fluso. Requests use that account's workspace and allowance.
+
+These guides cover the released Cloud API. See [product availability](/resources/availability) for unsupported deployment options.
## Find the exact fields
diff --git a/content/docs/api/workflows/connections.mdx b/content/docs/api/workflows/connections.mdx
index e711dc1..5fcaaed 100644
--- a/content/docs/api/workflows/connections.mdx
+++ b/content/docs/api/workflows/connections.mdx
@@ -6,7 +6,7 @@ description: Connect a service once, then help users decide when Fluso needs per
Your integration can use the services already connected to the same Fluso workspace. A connection gives access to tools. The user's permission settings decide which actions can proceed.
-For an initial setup, connect the service in **Plugins → MCP** in Fluso. Fluso offers managed apps such as Google Workspace, and you can add custom MCP servers.
+For an initial setup, connect the service in **Plugins → MCP** in Fluso. The catalog offers native Fluso and provider-managed apps. Google services such as Gmail and Calendar connect separately.
The examples below use `api`, `thread_id`, and `run_id` from [your first request](/api/first-request).
@@ -69,7 +69,7 @@ Open the returned `authorization_url` for OAuth. `already_connected` needs no si
Read `GET /v1/mcp-oauth/connections` to inspect saved connections. `needs_reauth` means the user must reconnect. Saved inventory alone does not prove the service is reachable.
- A developer write token can decide one-time tool approvals. Permanent rules require a signed-in app session.
+ A developer write token can decide one-time tool approvals. Permanent rules require a signed-in Cloud app session.
diff --git a/content/docs/api/workflows/schedules.mdx b/content/docs/api/workflows/schedules.mdx
index 16a98bb..63e4d65 100644
--- a/content/docs/api/workflows/schedules.mdx
+++ b/content/docs/api/workflows/schedules.mdx
@@ -57,6 +57,8 @@ Pausing or deleting a schedule does not cancel work already accepted. [Cancel th
+ Delayed recurring work does not replay every missed occurrence. Check the saved next-run time and conversation state.
+
Delivery failures can pause a schedule. A failed accepted run does not automatically pause recurring work.
A one-time schedule stops submitting after acceptance, even if its run later fails. Inspect the saved run before deciding whether to request that work again.
diff --git a/content/docs/api/workflows/streaming.mdx b/content/docs/api/workflows/streaming.mdx
index fe1958e..ecc8676 100644
--- a/content/docs/api/workflows/streaming.mdx
+++ b/content/docs/api/workflows/streaming.mdx
@@ -49,6 +49,8 @@ After a disconnection, repeat that sequence. Continue checking saved state perio
Buffer incomplete frames across network chunks. Ignore unknown event types and keepalive comments. Use a client that supports an Authorization header. Keep tokens out of URLs.
If you use `stream: true` during input submission, save the first `input.accepted` receipt. It contains the IDs for recovery if the stream fails.
+
+ If your client connects through a proxy you operate, disable response buffering for this stream.
diff --git a/content/docs/deployment-models.mdx b/content/docs/deployment-models.mdx
index 1197f9a..edba9d0 100644
--- a/content/docs/deployment-models.mdx
+++ b/content/docs/deployment-models.mdx
@@ -2,63 +2,31 @@
title: Deployment models
sidebarTitle: Overview
icon: server-cog
-description: Compare Fluso Cloud and Enterprise deployments.
+description: Start with Fluso Cloud, or discuss a custom Enterprise deployment with the team.
---
-Your deployment model decides who operates Fluso and where its runtime, durable data, and diagnostics can live. It does not by itself control where connected Apps or external model providers process data.
-
-| Model | Availability | Operations |
-| --- | --- | --- |
-| Fluso Cloud | Available | Managed by Fluso |
-| Dedicated AWS VPC | Supported for scoped Enterprise deployments | Responsibilities agreed during deployment design |
-| Azure VNet | Coming soon | Not available today |
-| On-premises | Scoped Enterprise engagement | Responsibilities agreed before implementation |
-
## Fluso Cloud
-Fluso Cloud is the standard managed service. It runs on AWS with European hosting by default. Fluso operates the application services, Agent runtimes, storage, and platform updates; you manage your workspace, users, connected Apps, and approval policies.
-
-Choose it when you want to start without operating infrastructure. See [Legal](/resources/legal) for Fluso's privacy policy.
-
-## Dedicated AWS VPC
-
-A dedicated AWS VPC deployment is available for Enterprise customers whose network or residency requirements do not fit the managed service. It is a scoped deployment, not a self-service switch.
-
-Before launch, your team and Fluso agree on AWS account ownership, region, network connectivity, ingress and egress, DNS, secrets, data stores, backups, upgrades, and support access.
+Fluso Cloud is the standard managed service. Fluso operates the application, Agent runtimes, storage, and platform updates. You manage your files, connected apps, and approval settings.
-## Azure VNet (coming soon)
+The desktop and mobile apps connect to this service. Installing them does not run the workspace or inference locally. See [current availability](/resources/availability).
-Azure VNet support is planned but is not available today. There is no published availability date. Do not make an Azure deployment dependency until Fluso confirms the required region and services are supported.
+Workspace data is hosted in Europe by default. Model inference and connected apps have separate processing boundaries. Pro includes optional [encrypted inference](/features/confidential); this protects model requests without moving the whole workspace into an enclave.
-## On-premises
+## Custom Enterprise deployments
-On-premises deployments are scoped with Enterprise customers against the target infrastructure. Fluso does not currently offer a one-click installer or a generic support promise for every Kubernetes, virtual-machine, or bare-metal environment.
+Contact the team to assess a dedicated VPC or on-premises requirement. These are scoped engagements, not self-service options included automatically with a Cloud subscription.
-Agree on these boundaries before treating the design as approved:
+Before relying on a proposed deployment, agree on:
-| Boundary | What to decide |
+| Area | What to confirm |
| --- | --- |
-| Data residency | Where the database, project files, knowledge data, and backups are stored |
-| Runtime and inference residency | Where Agent runtimes execute and which model endpoints may receive requests |
-| Diagnostic-data residency | What diagnostic data is captured, where it is stored, how long it is retained, and who can access it |
-| Network access | Which inbound paths and outbound destinations are permitted |
-| Connected Apps | Which external systems may be read or changed, and what returned data Fluso may persist |
-
-
- Running Fluso on-premises does not automatically keep model inference or connected-App data on-premises. External providers keep their own processing boundaries. Confirm every provider and route as part of the deployment design. See [Legal](/resources/legal) for Fluso's privacy policy.
-
-
-## Operational telemetry
-
-AWS deployments send service logs to CloudWatch and define CloudWatch alarms. Fluso's knowledge service emits structured logs and can export traces and metrics through OpenTelemetry (OTLP). The current AWS collector routes traces to X-Ray and metrics to CloudWatch; Prometheus scraping is optional.
-
-Traces can include prompt and response text. For a dedicated or on-premises deployment, agree which signals are captured, where they are stored, how long they are retained, and which customer-owned collectors are supported.
-
-## Choose a model
+| Infrastructure | Supported environment, region, and who operates it |
+| Data | Storage, backups, retention, deletion, and support access |
+| Models and tools | Inference endpoints, connected systems, and outbound network access |
+| Identity and audit | Required identity integration and audit records, including implementation scope |
+| Operations | Updates, monitoring, recovery, and support responsibilities |
-- Start with Fluso Cloud when managed operations and European hosting meet the requirement.
-- Scope an AWS VPC deployment when you need a dedicated AWS network boundary.
-- Treat Azure VNet as future availability, not a current option.
-- Scope on-premises only after Fluso validates the infrastructure, residency, provider, telemetry, and support requirements.
+A private deployment does not automatically make external inference or app connections local. An offline or air-gapped requirement needs a specific design and confirmed feature scope.
-For a custom deployment, [contact Fluso](mailto:sales@premai.io).
+For a custom deployment, [contact Fluso](mailto:sales@premai.io). For the standard service's policies, see [Legal](/resources/legal).
diff --git a/content/docs/developers/examples/document-filing.mdx b/content/docs/developers/examples/document-filing.mdx
index 377b0bc..1cb3bf3 100644
--- a/content/docs/developers/examples/document-filing.mdx
+++ b/content/docs/developers/examples/document-filing.mdx
@@ -6,7 +6,7 @@ description: Make proposals and attachments easier to find after you send them.
Customer documents often stay buried in sent email. An Agent can copy them into the right Google Drive folders and keep track of what it already filed.
-This job needs a [Google Workspace connection](/integrations/gmail) with **Allowed** access, because it writes files to Drive.
+Connect [Gmail](/integrations/gmail) and **Google Drive** separately. Select both in the Agent setup. Drive needs **Allowed** access because the task writes files there; Gmail can stay **Read only**.
## Start with one week
diff --git a/content/docs/developers/examples/email.mdx b/content/docs/developers/examples/email.mdx
index 92ac073..a9372ba 100644
--- a/content/docs/developers/examples/email.mdx
+++ b/content/docs/developers/examples/email.mdx
@@ -8,7 +8,7 @@ After a busy day, the hard part is often deciding which messages still need you.
An inbox Agent can read the recent conversation, identify an unanswered request, and help you write a reply.
-Connect [Google Workspace](/integrations/gmail) and select it in the Agent's [app access](/developers/guides/settings#grant-app-access).
+Connect [Gmail](/integrations/gmail) and select it in the Agent's [app access](/developers/guides/settings#grant-app-access).
## Give it a clear job
diff --git a/content/docs/developers/examples/people-graph.mdx b/content/docs/developers/examples/people-graph.mdx
index bbacdfc..f0428d3 100644
--- a/content/docs/developers/examples/people-graph.mdx
+++ b/content/docs/developers/examples/people-graph.mdx
@@ -10,7 +10,7 @@ An Agent can build one from your email and give you a page to search. This is a
## Build a useful first version
-Connect [Google Workspace](/integrations/gmail). Give the Agent **Read only** access if you only want it to read mail.
+Connect [Gmail](/integrations/gmail). Give the Agent **Read only** access if you only want it to read mail.
Describe the job:
diff --git a/content/docs/developers/guides/settings.mdx b/content/docs/developers/guides/settings.mdx
index d473182..19b9fb9 100644
--- a/content/docs/developers/guides/settings.mdx
+++ b/content/docs/developers/guides/settings.mdx
@@ -12,7 +12,7 @@ For changes to its usual way of working, start with [Improve your Agent](/develo
**Skills** help an Agent do particular kinds of work, such as reading a PDF or making a spreadsheet.
-**Connectors** let it use apps you connect, such as Google Workspace. A meeting assistant working from pasted notes may need no connected apps.
+**Connectors** let it use apps you connect, such as Gmail or Google Drive. A meeting assistant working from pasted notes may need no connected apps.
Choose what the job needs. You can add more later.
diff --git a/content/docs/developers/schedules.mdx b/content/docs/developers/schedules.mdx
index ebe977c..b4285b8 100644
--- a/content/docs/developers/schedules.mdx
+++ b/content/docs/developers/schedules.mdx
@@ -18,7 +18,7 @@ For repeat work, be clear about what should change each time:
> *"Every weekday at 9 AM, review mail since your last check. Show me what needs a reply and draft responses here. Don't send anything."*
-For that email example, the Agent needs your [Google Workspace connection](/integrations/gmail).
+For that email example, the Agent needs your [Gmail connection](/integrations/gmail).
Check the saved time and timezone under **Routines** in the side panel. If the timing could be ambiguous, include your timezone in the request.
diff --git a/content/docs/features/approvals.mdx b/content/docs/features/approvals.mdx
index 483f948..ae5eddc 100644
--- a/content/docs/features/approvals.mdx
+++ b/content/docs/features/approvals.mdx
@@ -22,7 +22,7 @@ For an external send, ask Fluso to prepare a draft, review its recipients and co
## Set the default
-Open **Settings → Approvals & permissions**. **Auto-approval** sets your default across desktop and web.
+Open **Settings → Approvals & permissions**. **Auto-approval** sets your default across supported Fluso apps.
Chats where you explicitly picked a mode keep it. Other chats follow the current default, including existing chats without an override. A Settings change does not itself decide an approval already waiting.
diff --git a/content/docs/features/chat.mdx b/content/docs/features/chat.mdx
index c0e5f84..6706330 100644
--- a/content/docs/features/chat.mdx
+++ b/content/docs/features/chat.mdx
@@ -23,7 +23,7 @@ Fast suits straightforward questions and small edits. Medium balances speed and
The mode is chat-specific. Ordinary new chats start in Medium unless you switch them. Saved Agents take **High** or **Fast** from their [setup](/developers/guides/settings).
-This only affects the chat you are using in the app.
+The reasoning mode belongs to the selected chat. Changing it does not change the mode of other conversations.
## Approval mode
diff --git a/content/docs/features/confidential.mdx b/content/docs/features/confidential.mdx
index d505793..bc6d5b8 100644
--- a/content/docs/features/confidential.mdx
+++ b/content/docs/features/confidential.mdx
@@ -2,18 +2,16 @@
title: Confidential mode
sidebarTitle: Confidential
icon: lock-keyhole
-description: Run your work through models hosted in a hardware-sealed enclave.
+description: Protect model requests with encrypted inference, and understand the separate workspace and app boundaries.
---
Confidential mode routes your inference through Prem API's confidential compute, an isolated enclave that infrastructure operators and the cloud provider cannot access. It is available on the Pro plan. You can turn it off later to return future requests to standard provider routing.
## What it protects
-At the gateway, your request is encrypted for processing and sent to an enclave: hardware-isolated regions of the server that the host OS, the hypervisor, and anyone operating the infrastructure cannot read. The cloud provider can't see your data there. Someone with physical access to the hardware can't either.
+Fluso encrypts model requests for Prem's confidential inference service. Hardware isolation protects the model's processing memory, and attestation verifies the confidential environment.
-Before the gateway, your requests pass through Fluso's infrastructure on AWS. Both the sandbox and gateway run in a secure cloud environment we control.
-
-The enclave itself isn't protected by a policy or a promise. Isolation is enforced in the hardware, and attestation reports signed by the chip vendor let you verify it.
+The Fluso runtime prepares requests and uses the returned answers outside the inference enclave. Files, conversation history, tool execution, and connected services have their own processing and storage boundaries. Enabling this mode does not turn Fluso Cloud into an offline or fully enclave-hosted workspace.
For the full technical picture, see Prem's [confidential compute documentation](https://docs.prem.io/basics/learn-more/overview).
@@ -57,6 +55,6 @@ Open **Settings** and find **Encrypted Inference**. Without Pro access, use **Up
Pro, including an active Pro trial or gifted Pro access. Free and Plus do not include confidential mode.
- Inside the enclave, no. At the gateway, your request is encrypted for a hardware-sealed environment that infrastructure operators and the cloud provider cannot access. Before that, traffic passes through Fluso's AWS infrastructure.
+ Hardware isolation protects model processing inside the enclave from the host infrastructure. The Fluso runtime prepares requests and reads responses outside it. Connected tools and saved workspace data remain separate from this protection.
diff --git a/content/docs/features/connectors.mdx b/content/docs/features/connectors.mdx
index 142d4fd..a75a881 100644
--- a/content/docs/features/connectors.mdx
+++ b/content/docs/features/connectors.mdx
@@ -2,15 +2,9 @@
title: Connectors
sidebarTitle: Connectors
icon: plug
-description: Connectors have been replaced by MCP connections. Everything now connects through the Plugins page.
+description: Find native Fluso connectors and custom MCP connections under Plugins.
---
-Connectors no longer exist as a separate system. Every app connection in Fluso is now an MCP connection: the same one-click sign-in, managed through **Plugins** in the sidebar, with per-tool permissions on top.
+Open **Plugins → MCP** to connect an app and manage its tool permissions. Native Fluso connectors have the Fluso mark beside their names. You can also add a custom MCP server.
-What you used to do here:
-
-- **Connect Gmail, Slack, GitHub, and other apps** — now the **Apps** tab of the Add MCP dialog. Same one-click sign-in on the app's own page. See [Apps and MCP servers](/features/mcp).
-- **Per-app setup guides** — unchanged: [Gmail](/integrations/gmail), [Google Calendar](/integrations/google-calendar), [Slack](/integrations/slack), [GitHub](/integrations/github).
-- **Disconnect an app** — the connection row's menu on the Plugins page.
-
-Head to [Apps and MCP servers](/features/mcp) for the full picture.
+See [Apps and MCP servers](/features/mcp) for setup, Google service connections, and troubleshooting. For a saved Agent, select the connection in its [app access](/developers/guides/settings#grant-app-access) as well.
diff --git a/content/docs/features/mcp.mdx b/content/docs/features/mcp.mdx
index 293c66f..941acbd 100644
--- a/content/docs/features/mcp.mdx
+++ b/content/docs/features/mcp.mdx
@@ -2,162 +2,102 @@
title: Apps and MCP servers
sidebarTitle: Apps & MCP
icon: plug-zap
-description: Every connection in Fluso is an MCP connection. One-click managed apps, custom servers by URL, and per-tool permissions.
+description: Connect supported apps or a custom MCP server, then choose which tools Fluso may use.
---
-Fluso reaches other software through MCP. There is no separate connector system anymore: a Gmail connection, a Slack connection, and a private MCP server your team runs are all the same thing — an MCP connection with its own sign-in and its own tool permissions.
+Connections give Fluso access to external tools through MCP. You can connect an app from the catalog or add your own MCP server.
-Two ways in, one list:
+## Connect an app
-- **Apps.** A catalog of about a hundred managed apps — Google Workspace, GitHub, Slack, Linear, Notion, Jira, HubSpot, Stripe, and so on. One click, sign in on the app's own page, done. Fluso runs the MCP server for you.
-- **Custom server.** A publicly reachable HTTPS endpoint that implements MCP over Streamable HTTP. This can be a server your team operates or a SaaS endpoint outside the managed catalog.
+1. Open **Plugins → MCP**.
+2. Select **Add MCP**, then **Apps**.
+3. Search for the app you need and select **Connect**.
+4. Complete the sign-in or credential form shown for that app.
+5. Check that the connection appears as connected.
-## Where to find them
+Ordinary chats can use the connection on their next message. For a saved Agent, also select it under [Connectors](/developers/guides/settings#grant-app-access).
-
-
-
+You can also request a connection in chat. Use the **Authorize** card when it appears, then check the result before continuing.
-Open **Plugins** in the left sidebar. The **MCP** tab lists every connection in this workspace — managed apps and custom servers together — with its status. **Web Search** is connected out of the box. The **Skills** tab on the same page holds [skills](/features/skills), which shape how Fluso works rather than what it can reach.
+## Native Fluso connectors
-## Connecting an app
+The Fluso mark beside an app identifies a **Native** connector built and run by Fluso. These connectors use Fluso's own connection flow instead of Composio.
-Click **Add MCP**. The dialog opens on the **Apps** tab.
+The catalog can also contain provider-managed connections and vendor-hosted MCP services. Check the app and sign-in screen you are using. A native connector still calls the connected service, such as Google or Slack. It does not move that service's processing into Fluso or into an enclave.
-
-
-
+Use the current catalog as the list of available connections. A connector's presence in source code or an earlier screenshot does not mean it is enabled for your account.
-Search for the app, click **Connect**, and sign in on the app's own login screen. You approve the permissions there, the window closes itself, and the row appears in your list. Ordinary chats can use it from the next message. For a saved Agent, also select it under [Connectors](/developers/guides/settings#grant-app-access).
+### Google services connect separately
-A few rows worth knowing about:
+**Gmail**, **Google Calendar**, **Google Drive**, **Google Docs**, **Google Sheets**, and **Google Slides** have separate entries. Connect the services you need and check each one's status. Connecting Gmail alone does not connect Calendar or Drive.
-- **Google Workspace** is one connection that covers Gmail, Drive, Docs, Sheets, Slides, Calendar, Meet, and Tasks. One sign-in, the whole suite.
-- **Slack** connects as you; **Slackbot** connects with a bot token instead. Most people want Slack.
-- **Web Search** (Exa) comes pre-connected on new workspaces.
+Google may reuse an existing consent for related services. Review the permissions it requests rather than assuming that one sign-in grants the whole suite.
-The catalog runs from the everyday — Outlook, Teams, Notion, Dropbox, Zoom — to the specialised: Salesforce, Stripe, Supabase, Sentry, Figma, YouTube, Zendesk, and the rest. If an app you need is missing, email [support@premai.io](mailto:support@premai.io), or add it yourself as a custom server if it has an MCP endpoint.
+### OAuth and API keys
-## Connecting a custom server
+Many apps open their own sign-in page. Some require an API key, personal token, or account name. Follow the selected app's form. Your provider account and its permissions still determine what Fluso can access.
-Switch to the **Custom server** tab and paste the endpoint URL.
+If an older connection asks you to reconnect after the native connector rollout, open the current catalog entry and finish that flow. Check the connection and any saved Agent selections before running unattended work.
-
- Use the exact Streamable HTTP endpoint. It must be reachable from Fluso over
- public HTTPS; `localhost`, private network addresses, and `stdio` commands
- are not connection URLs. The workspace or organization
- network-egress policy, plus any provider
- policy applied to that origin, must allow it.
-
+## Connect a custom server
-
-
-
+In **Add MCP**, choose **Custom server** and enter the server's Streamable HTTP endpoint.
-Click **Continue**. Fluso probes the URL — no credentials are sent — and reads the server's public sign-in metadata. The result appears as a suggestion, with four tabs for the auth method the server actually uses:
+The endpoint must be reachable from Fluso over public HTTPS. A `localhost` address, private-network address, or `stdio` command is not a supported Cloud connection URL. Network and provider policies also apply.
-
-
-
+Select **Continue** to discover the server's authentication options:
-### OAuth
+| Method | What to provide |
+| --- | --- |
+| **OAuth** | Sign in through the server's authorization flow |
+| **OAuth (BYO)** | Your registered client ID and any required client secret or OAuth endpoints |
+| **API key** | The key and header name expected by the server; the default is `X-Api-Key` |
+| **Bearer** | The token expected in the `Authorization` header |
-The one-click case. The server supports OAuth with Dynamic Client Registration, so Fluso registers itself on the fly. Click **Authorize**, sign in on the server's own page, and the row appears. This is what Linear, Notion, and most modern MCP servers look like.
+For a custom OAuth client, the callback is `https://api.fluso.ai/v1/mcp-oauth/callback`.
-### OAuth (BYO)
-
-OAuth, but the server doesn't let Fluso register itself. Register an app in the server's developer console and bring the credentials back.
-
-
-
-
-
-Client ID and secret go where they say. Authorization and token endpoints are auto-detected if left blank. **Authorize** works the same as the OAuth tab from there.
-
-
- When the provider's console asks for a redirect URL, use: `https://api.fluso.ai/v1/mcp-oauth/callback`
-
-
-### API key
-
-The server expects a key in an HTTP header. Paste the key; the header name defaults to `X-Api-Key`. Click **Save**.
-
-### Bearer
-
-A static token sent as `Authorization: Bearer ` — the GitHub-PAT style.
-
-
-
-
-
-
- Whatever you paste goes to the backend over HTTPS and is stored encrypted at rest, the same way OAuth tokens are. The UI does not persist or redisplay it after save, and it does not appear in logs.
-
-
-## Connecting from chat
-
-You don't have to start from the Plugins page. Ask in chat:
-
-> *"Connect the Notion MCP server for me."*
-
-
-
-
-
-Fluso surfaces the same sign-in inline as an access card. Click **Authorize**, approve on the app's page, and the conversation carries on. Connections made in chat show up on the Plugins page; connections made on the Plugins page are usable from chat. One list, two ways in.
+Only connect servers you trust. Review requested access before authorizing them. A successful sign-in does not establish that every tool works or is permitted.
## Tool permissions
-Expand any connection row to see its tools and set rules per tool.
-
-
-
-
-
-- **Auto-approve read-only tools** allows operations classified as GET, list, search, and fetch to run without asking. Explicit Ask or Deny rules still win.
-- Each tool has its own **Allow**, **Ask**, or **Deny**. Allow runs without asking, Ask pauses for approval when the chat uses **Ask me first**, and Deny blocks the tool. **Allow everything** can bypass Ask, but not Deny.
-- Tools are grouped read-only versus everything else, so you can see at a glance what can only look and what can act.
-
-These rules work together with your chat-level approval mode. See [Approvals and permissions](/features/approvals) for how the modes and rules interact.
-
-## Managing connections
+Expand a connection to inspect its tools and set **Allow**, **Ask**, or **Deny**:
-Each row shows the connection's status. The three-dot menu holds the two actions you'll need:
+- **Allow** lets that tool run without a per-call approval.
+- **Ask** requests approval when the chat uses **Ask me first**.
+- **Deny** blocks the tool, including in **Allow everything** mode.
-
-
-
+**Auto-approve read-only tools** permits tools classified as reads unless an explicit Ask or Deny rule applies. **Allow everything** can bypass Ask, but cannot bypass Deny or organization restrictions.
-**Reconnect** drops the stored sign-in and runs the connect flow again. Use it when a connection stops working, or to sign in as a different account.
+For email or other external messages, request a draft, use **Ask me first**, and keep send tools on **Ask**. See [Approvals and permissions](/features/approvals).
-**Disconnect** removes the connection. Fluso loses access from the next message on. This removes the sign-in on Fluso's side only — to revoke it at the source, use the app's own settings page (for Google, [Google Account → Security → Third-party apps](https://myaccount.google.com/permissions); for GitHub, [Settings → Applications](https://github.com/settings/applications)).
+## Reconnect or disconnect
-## Things to know
+Use the connection row's menu to reconnect when access expires, or disconnect when you no longer want Fluso to use it. Actions depend on the connector; a shared built-in service may not offer a personal reconnect control.
-- **Connections are per account, not per chat.** Sign in once and reuse the connection across chats. Saved Agents can use only their selected connections. Sign-ins survive runtime restarts.
-- **The runtime never stores tokens.** Tools fetch a short-lived token from the backend per request, use it, and drop it. Sign-in happens on the app's own page — Fluso never sees your password.
-- **Custom servers have prerequisites.** Fluso supports public HTTPS Streamable HTTP endpoints with OAuth, API-key, or bearer-token access. A successful sign-in does not override network-egress or provider policy.
-- **Rules set by your organization take precedence** over anything you allow yourself.
+Disconnecting removes Fluso's saved connection. You can also revoke access in the provider's settings. Disconnecting does not delete content already saved in conversations or files, or undo actions already completed.
-
- MCP servers run tools on your behalf. Only connect ones you trust. A malicious server can advertise harmless-looking tools that do harmful things.
-
+For Google services, check each related service after disconnecting or revoking access. Some services share an underlying grant.
## Troubleshooting
-
- The URL is probably the docs page, not the MCP endpoint. Try `mcp..com` or `.com/mcp`.
-
-
- The app probably revoked or rotated the token. Open the row's three-dot menu and click **Reconnect**.
-
-
- The server advertises Dynamic Client Registration but rejected the registration. Switch to **OAuth (BYO)** and register an app in the server's developer console yourself.
-
-
- Its rule is set to **Ask**, or your chat's approval mode is **Ask me first**. Set the tool to **Allow** in the row's tool permissions, or change the mode — see [Approvals](/features/approvals).
-
+
+
+ Search by the service name. If it is still missing, contact [support](mailto:support@premai.io). A public HTTPS MCP endpoint can be an alternative, but a listed app elsewhere is not a guarantee of a supported Fluso connection.
+
+
+ Read the error and check the provider account's permissions. Reconnect if authorization expired. A connection can be saved even when a provider tool is unavailable or rate-limited.
+
+
+ Connect **Google Calendar** separately. Gmail, Calendar, and Drive have their own catalog entries.
+
+
+ Check that the connection is selected in the Agent's setup. Then check its read-only setting and saved tool rules. Account connection and Agent access are separate choices.
+
+
+ Check that the URL is the MCP endpoint. If the server does not support dynamic registration, use **OAuth (BYO)** with a client registered with that provider.
+
+
## Next
-Per-app setup and prompts: [Gmail](/integrations/gmail), [Google Calendar](/integrations/google-calendar), [Slack](/integrations/slack), [GitHub](/integrations/github), [Zoom](/integrations/zoom). For capabilities that shape *how* Fluso works rather than what it can reach, see [Skills](/features/skills).
+See [Gmail](/integrations/gmail), [Google Calendar](/integrations/google-calendar), [GitHub](/integrations/github), [Slack](/integrations/slack), and [Zoom](/integrations/zoom) for app-specific guidance.
diff --git a/content/docs/features/open-architecture.mdx b/content/docs/features/open-architecture.mdx
index 4c7910e..96cbef3 100644
--- a/content/docs/features/open-architecture.mdx
+++ b/content/docs/features/open-architecture.mdx
@@ -49,4 +49,4 @@ These exports are independent snapshots. Later Fluso changes do not silently rew
## APIs for continuous access
-Use [API access](/api/first-request) when a one-time download is not enough. The account API covers Agents, conversations, files, schedules, runs, and usage. Authenticate with a developer token. Store only the data your integration needs.
+Use [API access](/api/first-request) when a one-time download is not enough. The account API covers Agents, conversations, files, schedules, runs, and usage on Fluso Cloud. Authenticate with a developer token. Store only the data your integration needs.
diff --git a/content/docs/features/tasks.mdx b/content/docs/features/tasks.mdx
index 3d44b79..d3c5e5f 100644
--- a/content/docs/features/tasks.mdx
+++ b/content/docs/features/tasks.mdx
@@ -5,13 +5,13 @@ icon: list-checks
description: Fluso's task list, mostly populated automatically from email, meetings, and Slack. Where tasks come from, how to open one, and how to keep the list tidy.
---
-A task in Fluso is a small piece of follow-up that came out of your day. A reply someone is waiting for. A meeting to confirm. A decision someone asked you for. Fluso watches the apps you have connected and turns the action items into tasks for you.
+A task in Fluso is a small piece of follow-up that came out of your day. A reply someone is waiting for. A meeting to confirm. A decision someone asked you for. Fluso can extract action items from supported connected apps and from work you ask it to process.
You spend your time on the work. The list mostly keeps itself.
## Where tasks come from
-Most tasks arrive without you asking. Fluso pulls them out of your connected apps in the background.
+Background extraction depends on the connected service and its sync state. It is disabled in [confidential mode](/features/confidential). You can still ask Fluso to review supplied material and create tasks explicitly.
**Email.** A message that asks you to do something becomes a task on you. The thread is linked, so the original is one click away.
diff --git a/content/docs/going-deeper.mdx b/content/docs/going-deeper.mdx
index c0f9d5e..4deec9f 100644
--- a/content/docs/going-deeper.mdx
+++ b/content/docs/going-deeper.mdx
@@ -21,7 +21,7 @@ A few patterns worth practising.
**Queue while Fluso works.** Press Enter during a run and the message waits in the editable follow-up queue. For a correction that cannot wait, use **Send now** on its queue row to steer the live run. The full set of controls is in [While Fluso is working](/features/chat#while-fluso-is-working).
-**Reference earlier work.** Threads remember everything. *"Reply to the one from Legal"* makes sense after Fluso has summarised your inbox. *"Use the same tone as my last email to the team"* works because Fluso has the previous draft in context.
+**Reference earlier work.** Threads retain conversation history, but long context can be summarized. *"Reply to the one from Legal"* makes sense after Fluso has summarised your inbox. *"Use the same tone as my last email to the team"* works because Fluso has the previous draft in context.
**Set the audience and the tone.** "For technical buyers" produces different writing from "for board members" produces different writing from "for a customer success follow-up". The default audience is generic. If you tell it the audience, it writes for them.
@@ -74,7 +74,7 @@ The full mechanics are in [Skills](/features/skills). The bar for building one i
Memory builds itself in the background. You do not have to maintain it. A few habits keep it useful and on-scope. The mechanics are in [Memory](/features/memory) — this is what to do with them.
-
+See [Memory](/features/memory) for preferences, project context, and working-memory boundaries.
**Be explicit when something is durable.** *"Remember that I prefer drafts in plain text"*, *"add to project context: the Q3 launch ships on August 14"*. Background learning is conservative on purpose; explicit asks are the fast path.
@@ -128,9 +128,7 @@ Share a finished file or an [Agent's setup](/developers/guides/sharing) when a c
A short list of features that are easy to overlook.
-The slash commands inside chat: `/status` shows what Fluso is doing right now (useful when something's slow), `/schedules` lists pending scheduled actions, `/abort` stops the current run.
-
-Saying *"new thread"* starts a fresh context. Useful when the conversation has drifted but you don't want to reach for the mouse.
+Use the **Stop** button to stop a run. For scheduled work, open **Routines** in the Agent conversation's side panel. Start a separate conversation with the new-chat control when the topic changes.
You can attach files to messages. PDFs, images, CSVs, audio. *"Summarise this"*, *"what does this chart show?"*, *"make a deck from this data"*. The file becomes part of the prompt.
diff --git a/content/docs/index.mdx b/content/docs/index.mdx
index 7a32da8..342060a 100644
--- a/content/docs/index.mdx
+++ b/content/docs/index.mdx
@@ -5,7 +5,7 @@ icon: house
description: Get set up, see Fluso work on a real task, and build the habits that turn it into your daily assistant.
---
-Fluso is an AI assistant that lives inside the apps you already use. It reads your email, runs your calendar, processes your meetings, drafts what you'd otherwise write, and remembers all of it.
+Fluso brings chats, files, and connected apps into one workspace. Use it to research, draft documents, manage tasks, and return to saved project context.
Three reading paths, depending on where you are.
@@ -26,28 +26,31 @@ Pick a workflow that matches a problem you have right now. Each one is a story,
- Inbox, schedule, tasks, follow-ups in two minutes.
+ Review your inbox, schedule, tasks, and follow-ups.
Prep, transcript, summary, tasks, follow-ups.
- A CEO ask on Monday, deck ready by 10am.
+ Research a topic, check the sources, and prepare a deck.
- Bug report to merged PR in fifteen minutes.
+ Investigate a bug and prepare a PR for review.
## Daily user, want more
- Projects, custom skills, prompt patterns, knowledge graph maintenance, team workflows. The stuff that turns daily users into pros.
+ Projects, custom skills, prompt patterns, memory maintenance, team workflows. The stuff that turns daily users into pros.
## When you need it
+
+ Supported apps, current limitations, and help with reported problems.
+
The five primitives: chat, apps, skills, tasks, memory.
@@ -58,7 +61,7 @@ Pick a workflow that matches a problem you have right now. Each one is a story,
Create an Agent, refine its setup, and return to its conversations, routines, and Inbox.
- Connect a script to Fluso, submit work, and read the result.
+ Connect a script to Fluso Cloud, submit work, and read the result.
Plans, limits, billing.
diff --git a/content/docs/integrations/github.mdx b/content/docs/integrations/github.mdx
index e906c37..8c47124 100644
--- a/content/docs/integrations/github.mdx
+++ b/content/docs/integrations/github.mdx
@@ -13,7 +13,7 @@ If you don't write code, the rest of this page is safely ignorable. If you do, t
Open **Plugins** in the sidebar, click **Add MCP**, and click **Connect** on **GitHub**. GitHub's OAuth flow opens.
-Choose repository scope on GitHub's screen: specific repositories or all repositories you have access to. Either is fine, and you can change the set later from your GitHub settings without reconnecting.
+Review the permissions requested by the connection. Repository access depends on your GitHub account, the authorization method, and any organization approval. Do not assume an OAuth screen offers a per-repository selection.
Read access is what lets Fluso browse code, answer architecture questions, and review PRs. Write access to issues and PRs is what lets it file issues, open PRs, and leave comments, subject to the effective tool and chat policy.
@@ -86,7 +86,7 @@ You can also revoke from [GitHub → Settings → Applications](https://github.c
## Troubleshooting
- Rerun authorisation and add the repo to the allowlist, or grant access to all repositories.
+ Check that your GitHub account and the authorized app or token can access the repository. Organization policy may require administrator approval.
Your organisation may require an admin to approve the OAuth app. Check **Org → Settings → Third-party access**.
@@ -102,6 +102,6 @@ You can also revoke from [GitHub → Settings → Applications](https://github.c
The code skills (Q&A, PR review, scaffolding, bug fixes) and others.
- Bug report to merged PR in fifteen minutes.
+ Investigate a bug and prepare a PR for review.
diff --git a/content/docs/integrations/gmail.mdx b/content/docs/integrations/gmail.mdx
index c51e33a..54334f9 100644
--- a/content/docs/integrations/gmail.mdx
+++ b/content/docs/integrations/gmail.mdx
@@ -14,15 +14,15 @@ You ask Fluso to summarise your inbox, search for something specific, draft a re
- Inbox triage in plain English (*"summarise my unread emails from today"*)
- Search across the full mailbox (*"find the email where Thomas sent the pricing spreadsheet"*)
- Draft replies in your voice (*"reply to Sarah, I'll have estimates by Thursday"*)
-- Auto-task extraction running in the background
+- Background task extraction when enabled; it is unavailable in confidential mode
- Thread summaries (*"summarise the email thread about the vendor negotiation"*)
- Follow-up tracking (*"has the client responded about the contract?"*)
## Setup
-Gmail comes in through the **Google Workspace** app, which also covers Calendar, Drive, Docs, Sheets, Slides, Meet, and Tasks in one sign-in.
+Gmail has its own native Fluso connector. Calendar, Drive, Docs, Sheets, and Slides connect separately. See [native connectors](/features/mcp#native-fluso-connectors).
-Open **Plugins** in the sidebar, click **Add MCP**, and click **Connect** on **Google Workspace**. Sign in to Google with the account you want Fluso to assist with and approve the permissions on Google's own screen. Reading powers summaries, search, and task extraction. Sending follows the Gmail tool's effective **Allow**, **Ask**, or **Deny** policy.
+Open **Plugins** in the sidebar, click **Add MCP**, and click **Connect** on **Gmail**. Sign in to Google with the account you want Fluso to assist with and approve the permissions on Google's own screen. Reading powers summaries, search, and task extraction. Sending follows the Gmail tool's effective **Allow**, **Ask**, or **Deny** policy.
A click and a confirmation screen. You can also just ask in chat — *"connect my Gmail"* — and approve the access card that appears.
@@ -68,20 +68,20 @@ Header metadata is used for categorisation and handled under the same subprocess
## Disconnecting
-In **Plugins**, open the Google Workspace row's three-dot menu and click **Disconnect**. The token is deleted immediately and Fluso loses access.
+In **Plugins**, open the Gmail row's three-dot menu and click **Disconnect**. The token is deleted immediately and Fluso loses access.
You can also revoke directly from [Google Account → Security → Third-party apps](https://myaccount.google.com/permissions).
## Troubleshooting
- Verify Google Workspace still shows as **Connected** in Plugins. If it does, reconnect from the row's menu. If the issue persists, you may have hit a Gmail API rate limit. Wait a few minutes and try again.
+ Verify Gmail still shows as **Connected** in Plugins. If it does, reconnect from the row's menu. If the issue persists, you may have hit a Gmail API rate limit. Wait a few minutes and try again.
OAuth tokens occasionally expire. In **Plugins**, open the row's three-dot menu and click **Reconnect**.
- Auto-task extraction runs periodically and learns the shape of your inbox over a couple of days. You can also force a sweep with *"Scan my inbox for tasks."*
+ Background extraction is unavailable in confidential mode. Check the connection and sync status, or ask *"Scan my inbox for tasks."* for an explicit review.
## See also
diff --git a/content/docs/integrations/google-calendar.mdx b/content/docs/integrations/google-calendar.mdx
index 4594794..964acf0 100644
--- a/content/docs/integrations/google-calendar.mdx
+++ b/content/docs/integrations/google-calendar.mdx
@@ -13,9 +13,9 @@ Calendar enables several skills that activate automatically — see [Skills](/fe
## Setup
-Calendar comes in through the **Google Workspace** app — the same connection that covers Gmail, Drive, Docs, and the rest of the suite. If you already connected it for Gmail, Calendar is on and there is nothing to do here.
+**Google Calendar** has a separate native connection. A connected Gmail account does not enable Calendar automatically.
-Otherwise: open **Plugins** in the sidebar, click **Add MCP**, and click **Connect** on **Google Workspace**. Sign in with the Google account whose calendar you want Fluso to run, and approve the permissions on Google's screen. Reading is what shows your schedule and availability; write access is what lets Fluso create and modify events when you ask.
+Open **Plugins** in the sidebar, click **Add MCP**, and click **Connect** on **Google Calendar**. Sign in with the Google account whose calendar you want Fluso to run, and approve the permissions on Google's screen. Reading is what shows your schedule and availability; write access is what lets Fluso create and modify events when you ask.
## Prompts that work well
@@ -51,7 +51,7 @@ Prep:
## Disconnecting
-In **Plugins**, open the Google Workspace row's three-dot menu and click **Disconnect**. Tokens are deleted immediately. Note this disconnects the whole Google Workspace connection, Gmail included.
+In **Plugins**, open the Google Calendar row's three-dot menu and click **Disconnect**. This removes the Calendar connection. Check related Google services if you also revoke the underlying consent in Google.
You can also revoke from [Google Account → Security → Third-party apps](https://myaccount.google.com/permissions).
diff --git a/content/docs/integrations/slack.mdx b/content/docs/integrations/slack.mdx
index ae3f784..1b69095 100644
--- a/content/docs/integrations/slack.mdx
+++ b/content/docs/integrations/slack.mdx
@@ -11,11 +11,11 @@ If your team mostly coordinates outside Slack, this connection isn't urgent. If
## Setup
-Open **Plugins** in the sidebar, click **Add MCP**, and click **Connect** on **Slack**. The Slack authorisation screen asks which workspace to connect; pick the one you want. You can connect more than one if you split work across them.
+Open **Plugins** in the sidebar, click **Add MCP**, and click **Connect** on **Slack**. The Slack authorisation screen asks which workspace to connect; pick the one you want. Use the workspace authorized by that connection.
Reading messages in authorised channels is what powers catching up, search, and surfacing action items. Posting follows the Slack tool's effective **Allow**, **Ask**, or **Deny** policy.
-The catalog also has **Slackbot**, which connects with a bot token instead of your own account. Most people want plain Slack.
+Use the **Slack** entry in the current catalog. The available tools depend on the account and scopes you authorize.
## Prompts that work well
@@ -75,7 +75,7 @@ You can also revoke from your Slack workspace at **Settings → Integrations →
Add the Fluso bot to the private channel, or rerun the authorisation and select the channel.
- Connect each separately. Fluso treats them as independent. Disambiguate in the prompt: *"What did I miss in [workspace] #channel?"*
+ Check which workspace the current connection authorizes. Do not assume one connection grants access to all your Slack workspaces. Contact support if your workflow needs more than the available connection supports.
OAuth tokens occasionally expire. In **Plugins**, open the Slack row's three-dot menu and click **Reconnect**.
diff --git a/content/docs/integrations/zoom.mdx b/content/docs/integrations/zoom.mdx
index 5660a23..9557319 100644
--- a/content/docs/integrations/zoom.mdx
+++ b/content/docs/integrations/zoom.mdx
@@ -62,7 +62,7 @@ Zoom asks you to approve these scope groups when you connect:
| Cloud recordings | List recordings; delete only when you ask |
| Contacts | Read |
-Fluso fetches Zoom data on demand to answer your request. It does not keep a copy of your Zoom content. OAuth tokens are stored encrypted and are deleted when you disconnect.
+Fluso fetches Zoom data on demand to answer your request. Requested work can save returned content in conversation records or workspace files. Disconnecting does not delete those saved results. OAuth tokens are stored encrypted and are deleted when you disconnect.
The full policies are the [privacy policy](https://fluso.ai/privacy) and the [terms of service](https://fluso.ai/terms).
diff --git a/content/docs/introduction.mdx b/content/docs/introduction.mdx
index f31620d..b5b41f7 100644
--- a/content/docs/introduction.mdx
+++ b/content/docs/introduction.mdx
@@ -34,7 +34,7 @@ Anything that starts in one place and finishes somewhere else.
Every project is built from five things working together.
- **[Chat](/features/chat)**, where you ask for work in plain English.
-- **[Apps & MCP](/features/mcp)**, the tools where your work already lives. Gmail, Calendar, Drive, Slack, GitHub, and a hundred more — every connection speaks MCP.
+- **[Apps & MCP](/features/mcp)**, the tools where your work already lives. Gmail, Calendar, Drive, Slack, GitHub, and other supported services. Check the app catalog for current availability.
- **[Skills](/features/skills)**, repeatable workflows Fluso can run on demand.
- **[Tasks](/features/tasks)**, the commitments Fluso finds or creates. Each one has an owner, a deadline, and a source.
- **[Memory](/features/memory)**, a curated record of preferences, decisions, and project context that travels with you across chats.
@@ -62,7 +62,7 @@ You will see how Fluso reads context, where it finds evidence, and how much revi
Your workspace runs inside a dedicated environment. Data is not used to train shared models, is hosted in Europe, and is grounded in Switzerland through Prem AI's infrastructure.
-Enterprise deployments can be scoped for a dedicated AWS VPC or an on-premises environment. Azure VNet support is coming soon. Compare the current [deployment models](/deployment-models), then see [Legal](/resources/legal) for Fluso's privacy policy.
+Enterprise deployments can be scoped for a dedicated AWS VPC or an on-premises environment. Compare the current [deployment models](/deployment-models), then see [Legal](/resources/legal) for Fluso's privacy policy.
## Next
diff --git a/content/docs/quickstart.mdx b/content/docs/quickstart.mdx
index 1693b97..35de3bd 100644
--- a/content/docs/quickstart.mdx
+++ b/content/docs/quickstart.mdx
@@ -21,9 +21,9 @@ In this quickstart, you will:
## Before you start
-Fluso runs on macOS. Download it from [fluso.ai](https://fluso.ai/) and install the app.
+Download Fluso for macOS or Windows from [fluso.ai/download](https://fluso.ai/download). Fluso is also on the [App Store](https://apps.apple.com/us/app/fluso/id6780937477) for iPhone and iPad.
-Windows and iOS are coming. For now, you need a Mac.
+This walkthrough shows the desktop interface. See [availability and troubleshooting](/resources/availability) for platform differences and attachment issues. All these apps connect to Fluso Cloud.
Pick one project before you open the app. Good first projects include:
@@ -192,7 +192,7 @@ Add the missing source, ask for citations, or narrow the prompt. Fluso is most u
**Can Fluso send messages or updates for me?**
-Fluso can draft replies, updates, and follow-ups. Review drafts before anything goes out.
+Fluso can draft and send through connected apps. Request a draft, select **Ask me first**, and keep send tools on **Ask** when you want to review each send. See [Approvals and permissions](/features/approvals).
**What should I try after this?**
diff --git a/content/docs/resources/availability.mdx b/content/docs/resources/availability.mdx
new file mode 100644
index 0000000..84087b7
--- /dev/null
+++ b/content/docs/resources/availability.mdx
@@ -0,0 +1,43 @@
+---
+title: Availability and troubleshooting
+sidebarTitle: Availability
+icon: circle-help
+description: Supported apps, current availability, and what to send when you report a problem.
+---
+
+## Apps you can use today
+
+Fluso Cloud is the released service. Sign in with the same account to use your workspace across supported apps.
+
+| App | Where to get it |
+| --- | --- |
+| macOS | [Download for Apple Silicon or Intel](https://fluso.ai/download) |
+| Windows | [Download for Windows](https://fluso.ai/download) |
+| iPhone and iPad | [Fluso on the App Store](https://apps.apple.com/us/app/fluso/id6780937477) |
+
+Most guides show the desktop interface. Mobile controls and feature availability can differ. Installing an app does not move the Cloud runtime or model inference onto your device.
+
+## Fluso Local and Telegram
+
+**Fluso Local is not available in the production app.** There is no public production daemon package or announced release date. Development previews are not production support. A Linux server does not currently provide a supported way to run your production workspace locally.
+
+**The Fluso Telegram bot is retired.** Use the desktop or iOS app to access your workspace. Older release notes describe historical features.
+
+## Attachment problems on iOS
+
+Image attachments have been reported to crash the iOS app. A confirmed fix version is not available in this guide. Audio attachment failures have also been reported; include the type of failure in your report.
+
+Check the App Store for the latest version. If the problem continues, try the desktop app with the same account. This is an alternative upload path, not a confirmed fix for the iOS issue. You can paste text if your task does not need the original file.
+
+Use **Report a bug** if accessible, or email [support@premai.io](mailto:support@premai.io). Include:
+
+- Your app version, device model, and operating-system version.
+- The file type and approximate size.
+- Whether you used Photos, Files, recording, or the share sheet.
+- The steps, approximate time, and any error shown.
+
+Send a non-sensitive example if one reproduces the problem. Do not include passwords or access tokens.
+
+## Connections and usage
+
+For a missing or expired app connection, see [Apps and MCP servers](/features/mcp#troubleshooting). For a usage limit, check **Settings → Plans** for your remaining allowance and reset date. [All three plans have weekly allowances](/resources/pricing#weekly-usage).
diff --git a/content/docs/resources/faq.mdx b/content/docs/resources/faq.mdx
index eed9726..9a49897 100644
--- a/content/docs/resources/faq.mdx
+++ b/content/docs/resources/faq.mdx
@@ -9,13 +9,13 @@ description: The questions that come up most often. What Fluso is, how it works,
- An AI assistant that connects to your apps — Gmail, Calendar, Slack, GitHub, and a hundred more — and helps you manage work through conversation. It reads your inbox, drafts replies, runs your calendar, creates documents, researches topics, writes code, and remembers everything along the way.
+ An AI assistant that connects to your apps — Gmail, Calendar, Slack, GitHub, and other supported services — and helps you manage work through conversation. It reads your inbox, drafts replies, runs your calendar, creates documents, researches topics, writes code, and keeps useful project context and preferences.
No. A chatbot answers questions. Fluso performs actions: sending mail, scheduling, opening PRs, generating files. It works across the apps where your work already happens, not just inside a chat window.
- Those are general-purpose assistants in a chat window. Fluso connects directly to your tools, builds a private knowledge graph from your work, takes action across apps, and remembers what's happened. It's an executive assistant, not a conversational AI.
+ Fluso combines conversations, project files, connected apps, and saved Agents in one workspace. Compare the connections, permissions, and workflows you need before choosing a product.
Anyone who loses too much time to email, meetings, research, content creation, or context-switching. Founders, executives, developers, PMs, researchers, and teams all use it.
@@ -55,7 +55,7 @@ description: The questions that come up most often. What Fluso is, how it works,
It asks clarifying questions: *"Which project?"* or *"What format?"* Answer for a better result.
- Fluso runs on macOS today. Download it from [fluso.ai](https://fluso.ai/). Windows and iOS are coming later.
+ Fluso is available on macOS, Windows, iPhone, and iPad. See [downloads and current limitations](/resources/availability). The apps connect to Fluso Cloud; they do not run the Cloud workspace locally.
Primarily English, but it understands and responds in many. Quality varies by language and task.
@@ -70,7 +70,7 @@ description: The questions that come up most often. What Fluso is, how it works,
The Fluso runtime is separate from encrypted inference. Its data is protected by strict internal access policies and procedures under our SOC 2 Type II compliance program; the runtime itself does not run inside an enclave.
- For greater control, Fluso can run in your own VPC or cloud while using Prem's encrypted inference. Your workspace stays in your infrastructure, and inference content is protected inside the enclave. See [deployment options](/deployment-models).
+ For greater control, discuss a custom VPC or on-premises deployment with the team. The workspace, inference, and connected-system boundaries must be agreed for that deployment. See [deployment options](/deployment-models).
Deleting your account deletes your dedicated sandbox and all associated data, including your files, conversations, connected-account credentials, and other records held by Fluso. We do not retain your data after account deletion.
@@ -82,7 +82,7 @@ description: The questions that come up most often. What Fluso is, how it works,
Gmail send tools follow your effective **Allow**, **Ask**, or **Deny** policy. Use **Ask** to review each draft before it sends; **Allow** or **Allow everything** can continue without a per-action prompt.
- In your isolated workspace on encrypted infrastructure. Files, conversations, tasks, and the knowledge graph are private to you.
+ In your isolated workspace on encrypted infrastructure. Files, conversations, tasks, and memory belong to your workspace. Review content before creating a public share link.
Yes. Individual entries, connected apps' data (tokens destroyed), or the entire account. Deletion is permanent.
@@ -104,16 +104,16 @@ See [Legal](/resources/legal) for Fluso's privacy policy.
Yes. Free costs $0 and includes the core workspace features, apps, and skills with a weekly usage allowance. No payment card is required.
- Plus costs $10/user/month and includes 10 times the weekly usage allowance of Free. Pro costs $30/user/month, has no weekly token limit, and includes confidential mode. Prices are in USD. Enterprise pricing is custom.
+ Plus costs $10/user/month and includes 10 times the weekly usage allowance of Free. Pro costs $30/user/month, includes 10 times the weekly usage allowance of Plus, and includes confidential mode. Prices are in USD. Enterprise pricing is custom.
Eligible new subscribers can start a 30-day Pro trial with a payment card. Pro renews at $30/month unless you cancel before the trial ends. Open **Settings → Plans** to check the offer available to your account. You can use Free without starting a trial or adding a card.
- Free and Plus allowances reset every seven days from when you signed up. **Settings → Plans** shows your usage bar and next reset date. Usage is measured in tokens, rather than a fixed number of messages. Agent runs use the same allowance. Pro has no weekly token limit.
+ Free, Plus, and Pro allowances reset every seven days from when you signed up. **Settings → Plans** shows the percentage remaining and next reset date. Usage is not a fixed message count. One prompt can trigger several model calls, and Agent runs use the same allowance.
- Wait for the next weekly reset or upgrade your plan to continue. Your existing files and conversations remain available.
+ Wait for the next weekly reset or choose a higher plan if one is available. Your existing files and conversations remain available.
Yes. Manage your subscription in **Settings → Plans**. If you cancel a paid subscription, access continues until the end of the current billing period, then returns to Free unless you have another active entitlement. To avoid the first Pro charge after a trial, cancel before the trial ends.
@@ -129,7 +129,7 @@ Plan details on [Pricing](/resources/pricing).
Specialised capabilities: creating PDFs, generating images, processing meetings, deep research. They activate when you ask for something they can do.
- No. Fluso picks the right skill based on the request.
+ Built-in skills are already available. Add marketplace skills or create your own under **Plugins → Skills**. Fluso chooses from the available skills based on your request.
Yes. Open **Plugins → Skills**, click **Add skill** at the top right, and pick **Build with Fluso**. The skill-creator skill takes it from there in chat: it asks what workflow the skill should handle, what inputs it takes, what shape the output should have, and which tools or apps are involved, then writes the skill and adds it to **My Skills**. See [Skills](/features/skills#building-your-own) for the full flow.
@@ -143,14 +143,17 @@ Plan details on [Pricing](/resources/pricing).
- Check Google Workspace is connected (**Plugins**). Try reconnecting from the row's menu. If the issue persists, you may have hit a Gmail API rate limit. Wait a few minutes.
+ Check Gmail is connected (**Plugins**). Try reconnecting from the row's menu. If the issue persists, you may have hit a Gmail API rate limit. Wait a few minutes.
- Start a new thread (the **+** button) if the conversation has drifted. *"Forget the context so far and start fresh on this topic"* also works. Being more specific in the request usually helps.
+ Start a new thread (the **+** button) if the conversation has drifted. Being more specific in the request usually helps.
Refresh the page or reconnect. OAuth tokens occasionally expire. **Plugins** → row menu → **Reconnect**.
+
+ See [attachment troubleshooting](/resources/availability#attachment-problems-on-ios) for current guidance and the details to include in a bug report.
+
Email [support@premai.io](mailto:support@premai.io). Enterprise support arrangements are agreed as part of the engagement.
diff --git a/content/docs/resources/meta.json b/content/docs/resources/meta.json
index 9cc6b5c..980bfda 100644
--- a/content/docs/resources/meta.json
+++ b/content/docs/resources/meta.json
@@ -1,3 +1,8 @@
{
- "pages": ["faq", "legal", "pricing"]
+ "pages": [
+ "availability",
+ "faq",
+ "legal",
+ "pricing"
+ ]
}
diff --git a/content/docs/resources/pricing.mdx b/content/docs/resources/pricing.mdx
index 61b013d..f7a4a69 100644
--- a/content/docs/resources/pricing.mdx
+++ b/content/docs/resources/pricing.mdx
@@ -5,9 +5,9 @@ icon: credit-card
description: Compare Free, Plus, Pro, weekly usage allowances, and the Pro trial.
---
-Choose Free, Plus, or Pro for Fluso desktop. Plus gives you 10 times the weekly usage allowance of Free. Pro has no weekly token limit and includes confidential mode. Enterprise is available for custom deployments, data residency, and identity or audit integrations.
+Choose Free, Plus, or Pro for Fluso desktop. Plus gives you 10 times the weekly usage allowance of Free. Pro gives you 10 times the weekly usage allowance of Plus and includes confidential mode. Enterprise is available for custom deployments, data residency, and identity or audit integrations.
-Fluso uses only open-source models across all features. Your data never trains shared models.
+Fluso uses open-source and open-weight models. Connected apps and other tools use their own services. Your data never trains shared models.
## Plans
@@ -33,20 +33,20 @@ Fluso uses only open-source models across all features. Your data never trains s
For higher usage and confidential inference.
- Everything in Plus
- - No weekly token limit
+ - 10 times the weekly usage allowance of Plus
- Confidential mode
**Custom pricing**
For organisations with custom needs.
- - Everything in Pro
- - Server-integrated identity (implementation scoped)
+ - Scope with your team
+ - Identity integration, scoped with your team
- Dedicated account executive
- Dedicated support
- - Custom obligation detection
- - Custom data retention
- - Server-backed audit logging (implementation scoped)
+ - Custom workflows and connectors
+ - Data retention requirements, scoped with your team
+ - Audit requirements, scoped with your team
- Custom skills
@@ -69,7 +69,7 @@ Free, Plus, and Pro share the core workspace features. Your plan determines your
- **Chat and workspace tools.** Projects, memory, tasks, connected apps, skills, and document creation.
- **Agents (Beta).** Use saved setups for repeatable work. Agent runs use your plan's allowance. See [Agents](/developers).
-- **Open-source models only.** All Fluso features use open-source models.
+- **Open-source and open-weight models.** Availability can change. Connected apps and other tools use their own services.
- **European hosting.** GDPR-aligned by default.
- **Your data is yours.** Nothing trains shared models.
@@ -78,7 +78,7 @@ Free, Plus, and Pro share the core workspace features. Your plan determines your
| | Free | Plus | Pro | Enterprise |
|---|---|---|---|---|
| Price (USD) | $0 | $10/user/month | $30/user/month | Custom |
-| Weekly token usage | Standard allowance | 10 times Free | No weekly limit | Custom |
+| Weekly usage | Standard allowance | 10 times Free | 10 times Plus | Custom |
| Core workspace features, apps, and skills | Included | Included | Included | Included |
| Confidential mode | Not included | Not included | Included | Included |
| Identity and audit integrations | Not included | Not included | Not included | Scoped integration |
@@ -86,21 +86,25 @@ Free, Plus, and Pro share the core workspace features. Your plan determines your
## Weekly usage
-Free and Plus usage resets every seven days from when you signed up. Open **Settings → Plans** to see your usage bar and next reset date. The allowance measures tokens used by model requests, so a long conversation or an Agent run can use more than a short message.
+Free, Plus, and Pro allowances reset every seven days from when you signed up. Open **Settings → Plans** to see the percentage remaining and next reset date. Chat and Agent activity use the same allowance.
-If you reach your allowance, wait for the next reset or upgrade your plan to continue. Your existing files and conversations remain available. Pro has no weekly token quota; storage, service availability, and operational limits still apply.
+Usage is not a fixed number of messages. A prompt can trigger several model calls, tool steps, or a long conversation history. Short visible replies can still use a substantial allowance.
+
+If you reach your allowance, wait for the next reset or choose a higher plan if one is available. Your existing files and conversations remain available. Storage, service availability, and other operational limits still apply.
+
+Check a stopped task before continuing it. Restored allowance does not mean interrupted work or delayed routines have already resumed. There is no self-service purchase of an extra weekly reset.
## Common questions
- Fluso uses only open-source models across all features.
+ Fluso uses open-source and open-weight models. Check the available modes in the app. Connected apps and other tools use their own services.
Fluso Cloud stores workspace data in the EU by default. Model inference and connected-App processing have their own provider boundaries. Enterprise customers can scope alternative data residency. Your data is never used to train shared models. See [Legal](/resources/legal) for Fluso's privacy policy.
- Plus costs $10/month and gives you 10 times the weekly usage allowance of Free. Pro costs $30/month, removes the weekly token limit, and includes confidential mode. Choose Pro if you need more usage than Plus or want confidential inference.
+ Plus costs $10/month and gives you 10 times the weekly usage allowance of Free. Pro costs $30/month, gives you 10 times the weekly usage allowance of Plus, and includes confidential mode. Choose Pro if you need more usage than Plus or want confidential inference.
Yes. Open **Settings → Plans** to upgrade, downgrade, or cancel. Upgrades take effect immediately. Paid-plan downgrades and cancellations take effect at the end of the current billing period. Review the amount and effective date shown before confirming a change.
@@ -109,7 +113,7 @@ If you reach your allowance, wait for the next reset or upgrade your plan to con
Pro includes model inference inside a hardware-isolated enclave. The Fluso runtime and connected apps have separate processing boundaries. See [Confidential mode](/features/confidential) for how it works and what it protects.
- Custom data retention is part of the Enterprise scope. Governance records persist the configured identity and access history, but Microsoft Entra metadata does not verify a directory or provide SSO by itself. Prem has attained SOC 2 Type II. [Review the current security posture.](https://www.premai.io/security-at-prem)
+ Identity, retention, audit records, and custom deployment requirements must be agreed with the team. They are not self-service features of a standard Cloud plan. Prem has attained SOC 2 Type II. [Review the current security posture.](https://www.premai.io/security-at-prem)
You can create workspace skills on Free, Plus, and Pro. See [Skills](/features/skills). Custom skills built with the Fluso team can be scoped as part of an Enterprise engagement.
@@ -121,6 +125,6 @@ If you reach your allowance, wait for the next reset or upgrade your plan to con
## Get started
-Start with Free without a payment card, or review the eligible Pro trial in **Settings → Plans**. [Download Fluso for Mac.](https://fluso.ai/)
+Start with Free without a payment card, or review the eligible Pro trial in **Settings → Plans**. [Download Fluso.](https://fluso.ai/)
For a custom setup, [get in touch.](mailto:sales@premai.io)
diff --git a/content/docs/workflows/content-launch.mdx b/content/docs/workflows/content-launch.mdx
index 8b6d377..dc9c78a 100644
--- a/content/docs/workflows/content-launch.mdx
+++ b/content/docs/workflows/content-launch.mdx
@@ -2,9 +2,13 @@
title: A launch in an afternoon
sidebarTitle: Content launch
icon: megaphone
-description: Landing page, blog post, social graphics for a product launch. Forty-five minutes instead of two or three days.
+description: An example of preparing a landing page, blog post, and social graphics for review.
---
+
+ This is an illustrative workflow. Results and timing depend on your inputs, connected tools, and available allowance. Review the output before using or sharing it.
+
+
Marketing asks: *"We need a landing page for the new product launch, a blog post announcing it, and social media graphics. Can you have it by Friday?"*
It's Wednesday. Two days. The old plan is to panic. There's a better one.
@@ -23,6 +27,8 @@ Post comes back. You read it, drop in the actual customer quote you have on hand
## Social graphics
+Image generation is unavailable in [confidential mode](/features/confidential).
+
> *"Generate five social media graphics for the DataLens launch. 1080×1080, brand colours, featuring key stats: 'Real-time analytics', '10x faster insights', 'No SQL required'."*
Five variants generated. You pick three. Done.
diff --git a/content/docs/workflows/dev-bug-fix.mdx b/content/docs/workflows/dev-bug-fix.mdx
index 453968c..970bb62 100644
--- a/content/docs/workflows/dev-bug-fix.mdx
+++ b/content/docs/workflows/dev-bug-fix.mdx
@@ -2,9 +2,13 @@
title: A bug to a PR
sidebarTitle: Bug → PR
icon: bug
-description: Bug report to merged PR in fifteen minutes. Fluso traces the code, finds the cause, writes the fix, opens the pull request for your review.
+description: Investigate a bug, test a proposed fix, and prepare a pull request for review.
---
+
+ This is an illustrative workflow. Results and timing depend on your inputs, connected tools, and available allowance. Review the output before using or sharing it.
+
+
Users report password reset emails aren't arriving. It's affecting customers. You need to find the bug and fix it.
## The old version
@@ -31,7 +35,7 @@ Fluso updates the template, writes a test that validates the link format, and op
*"Done. PR #156 — fixed the reset link domain, added a test that validates the link format. Ready for review."*
-You read the diff. Run the test locally. Approve the PR. Fifteen minutes from "we have a bug" to "the bug is fixed."
+You read the diff. Run the test locally. Request review before merging. A proposed fix still needs your repository's checks and release process.
## Variations
diff --git a/content/docs/workflows/knowledge-recall.mdx b/content/docs/workflows/knowledge-recall.mdx
index 2653cf5..49a3062 100644
--- a/content/docs/workflows/knowledge-recall.mdx
+++ b/content/docs/workflows/knowledge-recall.mdx
@@ -5,6 +5,10 @@ icon: search
description: That company you researched in January, the decision from the April planning meeting, the Slack thread from last summer. Retrieved in time to sound informed.
---
+
+ This is an illustrative workflow. Results and timing depend on your inputs, connected tools, and available allowance. Review the output before using or sharing it.
+
+
You're in a meeting with a potential partner. They mention a company you researched three months ago. Your colleague glances at you. Do you remember the details?
## Without Fluso
@@ -42,17 +46,11 @@ You sound informed and prepared, because you are. The thing you would have forgo
| Last contact | *"When did I last talk to the Stripe team?"* |
| Relationship health | *"How's the Acme relationship going? Any red flags?"* |
-## How recall scales over time
-
-The graph builds. The longer you've been using Fluso, the deeper the recall.
-
-In week one, it can recall your frequent contacts and current projects.
-
-By the end of month one, key relationships have history, project status is real-time, your communication patterns are visible.
+## What recall depends on
-At three months, Fluso starts surfacing patterns you wouldn't think to ask about: relationships you've gone quiet on, projects that are stalled, topics that keep coming up without resolution.
+Fluso uses saved preferences, project context, working-memory summaries, and the sources its tools can access. A new chat does not automatically receive every past message or every document in your connected accounts.
-After six months, it's institutional memory. *"What was the outcome of that vendor negotiation in January?"* gets a real answer, with citations.
+Ask for source links when a detail matters. If a fact is missing or outdated, supply the source and correct the project context. See [Memory](/features/memory) for the scope and limits.
## When recall is most valuable
@@ -70,13 +68,13 @@ Gmail connected (see [Gmail](/integrations/gmail)). Calendar connected so meetin
## Privacy
-The graph is yours alone. Lives in your isolated workspace. Never shared with other users. Never used to train models. Delete individual entries or wipe the whole thing whenever you want. See [Legal](/resources/legal) for Fluso's privacy policy.
+Memory belongs to your workspace. You can ask Fluso to read or correct it. Content included in a shared file or conversation is visible to anyone with that public link. See [Legal](/resources/legal) for Fluso's privacy policy.
## Related
- The full deep dive on the knowledge graph.
+ Preferences, project context, and working memory.
Meeting prep is recall in action — see it in context.
diff --git a/content/docs/workflows/meetings.mdx b/content/docs/workflows/meetings.mdx
index 6fca7bf..206d22e 100644
--- a/content/docs/workflows/meetings.mdx
+++ b/content/docs/workflows/meetings.mdx
@@ -2,12 +2,16 @@
title: A meeting, end to end
sidebarTitle: Meetings
icon: calendar-clock
-description: The full lifecycle on a real Tuesday. Prep at 9:55, meeting at 10, processed and follow-ups drafted by 10:47.
+description: An example of meeting preparation, notes, action items, and follow-up drafts.
---
+
+ This is an illustrative workflow. Results and timing depend on your inputs, connected tools, and available allowance. Review the output before using or sharing it.
+
+
The savings on meetings come from two places: the half hour before that you usually spend scrambling, and the forty-five minutes after that you usually spend on notes, tasks, and follow-up emails. Fluso compresses both. The meeting itself is exactly the same length.
-## A real Tuesday
+## An example Tuesday
It's 9:00 AM. You have a project review with the Acme team at 10. You haven't prepped.
@@ -75,7 +79,7 @@ For async-style recordings:
> *"Process this Loom and create tasks from the action items."*
-Works for any video or audio source, not just live calls.
+Provide an accessible recording or transcript. Format, size, permissions, and available tools can affect whether Fluso can process it.
## When you have multiple meetings in a row
diff --git a/content/docs/workflows/morning-brief.mdx b/content/docs/workflows/morning-brief.mdx
index da51d2e..aa4a2e0 100644
--- a/content/docs/workflows/morning-brief.mdx
+++ b/content/docs/workflows/morning-brief.mdx
@@ -2,9 +2,13 @@
title: Morning brief
sidebarTitle: Morning brief
icon: sunrise
-description: The two-minute version of the morning routine. Inbox triage, schedule, tasks, follow-ups, all in one prompt.
+description: Review inbox messages, calendar events, tasks, and follow-ups in one request.
---
+
+ This is an illustrative workflow. Results and timing depend on your inputs, connected tools, and available allowance. Review the output before using or sharing it.
+
+
The most common workflow on day one. If you connect Gmail and Calendar and only ever do this one thing, Fluso has earned its keep.
## The morning, before
@@ -45,7 +49,7 @@ The prompt language is loose. Anything that gestures at the same intent works.
## Setup checklist
-Gmail connected (see [Gmail](/integrations/gmail)). Calendar connected (see [Google Calendar](/integrations/google-calendar)). Auto-task extraction is on by default. Slack is optional but adds team context to the brief if you've connected it.
+Gmail connected (see [Gmail](/integrations/gmail)). Calendar connected (see [Google Calendar](/integrations/google-calendar)). Background task extraction is unavailable in confidential mode. Ask explicitly for the review you need. Slack is optional but adds team context to the brief if you've connected it.
## What changes through the week
diff --git a/content/docs/workflows/research-to-deck.mdx b/content/docs/workflows/research-to-deck.mdx
index 7f4fe94..3c5b241 100644
--- a/content/docs/workflows/research-to-deck.mdx
+++ b/content/docs/workflows/research-to-deck.mdx
@@ -2,9 +2,13 @@
title: From a CEO request to a board deck
sidebarTitle: Research to deck
icon: presentation
-description: "The classic Monday-morning ask. Old version: twelve hours over three days. New version: an hour total, deck ready three days early."
+description: Research a topic, review the sources, and prepare a presentation for your audience.
---
+
+ This is an illustrative workflow. Results and timing depend on your inputs, connected tools, and available allowance. Review the output before using or sharing it.
+
+
A common ask: *"Can you put together a competitive analysis of the top five AI agent platforms? I need it for the board on Thursday."*
It's Monday. You have three days. The old plan involves a lot of tabs.
diff --git a/public/_redirects b/public/_redirects
index 8298817..728eb1b 100644
--- a/public/_redirects
+++ b/public/_redirects
@@ -40,12 +40,6 @@
/developers/architecture /api 301
/developers/architecture/ /api 301
/llms.mdx/docs/developers/architecture/content.md /llms.mdx/docs/api/content.md 301
-/workspaces/macos /deployment-models 301
-/workspaces/macos/ /deployment-models 301
-/workspaces/linux /deployment-models 301
-/workspaces/linux/ /deployment-models 301
-/llms.mdx/docs/workspaces/macos/content.md /llms.mdx/docs/deployment-models/content.md 301
-/llms.mdx/docs/workspaces/linux/content.md /llms.mdx/docs/deployment-models/content.md 301
/developers/api-ref/authentication /api/first-request 301
/developers/api-ref/authentication/ /api/first-request 301
/llms.mdx/docs/developers/api-ref/authentication/content.md /llms.mdx/docs/api/first-request/content.md 301
@@ -76,26 +70,35 @@
/api/architecture /api 301
/api/architecture/ /api 301
/llms.mdx/docs/api/architecture/content.md /llms.mdx/docs/api/content.md 301
-/workspaces /deployment-models 301
-/workspaces/ /deployment-models 301
-/llms.mdx/docs/workspaces/content.md /llms.mdx/docs/deployment-models/content.md 301
-/workspaces/setup /deployment-models 301
-/workspaces/setup/ /deployment-models 301
-/llms.mdx/docs/workspaces/setup/content.md /llms.mdx/docs/deployment-models/content.md 301
-/workspaces/use /deployment-models 301
-/workspaces/use/ /deployment-models 301
-/llms.mdx/docs/workspaces/use/content.md /llms.mdx/docs/deployment-models/content.md 301
-/workspaces/manage /deployment-models 301
-/workspaces/manage/ /deployment-models 301
-/llms.mdx/docs/workspaces/manage/content.md /llms.mdx/docs/deployment-models/content.md 301
-/api/daemon/pairing /api 301
-/api/daemon/pairing/ /api 301
-/llms.mdx/docs/api/daemon/pairing/content.md /llms.mdx/docs/api/content.md 301
-/api/daemon/settings /api 301
-/api/daemon/settings/ /api 301
-/llms.mdx/docs/api/daemon/settings/content.md /llms.mdx/docs/api/content.md 301
-/remote/telegram /quickstart 301
-/remote/telegram/ /quickstart 301
-/llms.mdx/docs/remote/telegram/content.md /llms.mdx/docs/quickstart/content.md 301
-/remote /quickstart 301
-/remote/ /quickstart 301
+/workspaces /resources/availability 301
+/workspaces/ /resources/availability 301
+/llms.mdx/docs/workspaces/content.md /llms.mdx/docs/resources/availability/content.md 301
+/workspaces/setup /resources/availability 301
+/workspaces/setup/ /resources/availability 301
+/llms.mdx/docs/workspaces/setup/content.md /llms.mdx/docs/resources/availability/content.md 301
+/workspaces/use /resources/availability 301
+/workspaces/use/ /resources/availability 301
+/llms.mdx/docs/workspaces/use/content.md /llms.mdx/docs/resources/availability/content.md 301
+/workspaces/manage /resources/availability 301
+/workspaces/manage/ /resources/availability 301
+/llms.mdx/docs/workspaces/manage/content.md /llms.mdx/docs/resources/availability/content.md 301
+/workspaces/macos /resources/availability 301
+/workspaces/macos/ /resources/availability 301
+/llms.mdx/docs/workspaces/macos/content.md /llms.mdx/docs/resources/availability/content.md 301
+/workspaces/linux /resources/availability 301
+/workspaces/linux/ /resources/availability 301
+/llms.mdx/docs/workspaces/linux/content.md /llms.mdx/docs/resources/availability/content.md 301
+/api/daemon /resources/availability 301
+/api/daemon/ /resources/availability 301
+/llms.mdx/docs/api/daemon/content.md /llms.mdx/docs/resources/availability/content.md 301
+/api/daemon/pairing /resources/availability 301
+/api/daemon/pairing/ /resources/availability 301
+/llms.mdx/docs/api/daemon/pairing/content.md /llms.mdx/docs/resources/availability/content.md 301
+/api/daemon/settings /resources/availability 301
+/api/daemon/settings/ /resources/availability 301
+/llms.mdx/docs/api/daemon/settings/content.md /llms.mdx/docs/resources/availability/content.md 301
+/remote/telegram /resources/availability 301
+/remote/telegram/ /resources/availability 301
+/llms.mdx/docs/remote/telegram/content.md /llms.mdx/docs/resources/availability/content.md 301
+/remote /resources/availability 301
+/remote/ /resources/availability 301