diff --git a/AGENTS.md b/AGENTS.md
index 0697edd..21957f8 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -16,12 +16,10 @@ The navigation keeps Home first and sorts the top-level sections alphabetically.
- **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.
- **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. Keep Cloud and daemon credentials and administration separate. 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 Local** - `/workspaces/*`. Setup and everyday use on your own machine, followed by settings and maintenance. Keep macOS and Linux as choices inside one setup guide. Request daemon download links from support; do not publish unlisted release URLs. API access is documented under Fluso API.
+- **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.
- **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.
- **Release notes** - `/release-notes`. Customer-facing changes, newest first.
-- **Remote access** - `/remote/*`. Ways to use Fluso away from the desktop app.
- **Workflows** - `/workflows/*`. Six concrete stories: bug-to-PR, content launch, knowledge recall, meetings, morning brief, and research-to-deck.
The home page (`/`) is a router into the journey, with three sections: just landed, already set up, daily user.
diff --git a/content/docs/api/cloud/apps.mdx b/content/docs/api/cloud/apps.mdx
index 67799bc..b0363c6 100644
--- a/content/docs/api/cloud/apps.mdx
+++ b/content/docs/api/cloud/apps.mdx
@@ -6,7 +6,7 @@ description: Connect a supported Cloud app when your integration needs its data
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.
-For a daemon or a custom server, use [custom MCP connections](/api/workflows/connections).
+For a custom server, use [custom MCP connections](/api/workflows/connections).
## Connect the requested app
diff --git a/content/docs/api/cloud/client-sign-in.mdx b/content/docs/api/cloud/client-sign-in.mdx
index 30950c2..ba025a8 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, including Telegram. 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. Current browser callbacks support configured Fluso handoffs. 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/daemon/meta.json b/content/docs/api/daemon/meta.json
deleted file mode 100644
index 839afd6..0000000
--- a/content/docs/api/daemon/meta.json
+++ /dev/null
@@ -1,9 +0,0 @@
-{
- "title": "Daemon API",
- "icon": "server",
- "defaultOpen": false,
- "pages": [
- "pairing",
- "settings"
- ]
-}
diff --git a/content/docs/api/daemon/pairing.mdx b/content/docs/api/daemon/pairing.mdx
deleted file mode 100644
index 1d06321..0000000
--- a/content/docs/api/daemon/pairing.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Pair an API client
-icon: link
-description: Give a client access to your Fluso Local workspace.
----
-
-A daemon belongs to one owner. Each paired device gets its own token for that owner's workspace. Pairing does not create a separate account or private set of files.
-
-[Set up Fluso Local](/workspaces/setup) and its provider before submitting work. For remote access, use HTTPS or an SSH tunnel.
-
-## Get a device token
-
-On the daemon's host, run this from the installed package folder. Use the same state root as your running daemon:
-
-```bash
-./fluso-daemon pair --root /path/to/state
-```
-
-Exchange its one-use code from your client:
-
-```bash
-curl --fail-with-body --silent --show-error \
- 'http://127.0.0.1:4111/daemon/v1/pair' \
- -H 'Content-Type: application/json' \
- --data-raw '{"code":"PAIRING_CODE","name":"Weekly report integration"}'
-```
-
-Replace the address for a remote daemon. Replace `PAIRING_CODE` with the code from the host.
-
-Save `token` privately. Keep the returned client `id` and `daemonId` with your connection settings. If that daemon identity changes later, pair again.
-
-Codes expire after ten minutes and work once. If the exchange response is lost, generate a new code. Device tokens expire after 30 idle days. Authenticated use renews them.
-
-
- A normal device token grants read/write workspace access, including tool approvals. Add `--manage-host` only for clients that also need machine administration.
-
-
-Use the token as `Authorization: Bearer YOUR_TOKEN`. Browser requests must come from the daemon's exact origin. Use a native or server client for an integration hosted elsewhere. For the [first request](/api/first-request), set `FLUSO_API_URL` to `http://127.0.0.1:4111/v1` or your remote equivalent.
-
-## Check support and readiness
-
-`GET /v1/capabilities` reports supported features. Use it to show only the controls available on that daemon.
-
-`GET /daemon/v1/discovery` reports identity and configuration state. Its `ready` status means configuration is ready. Check `/v1/agent/runtime/status` for runtime readiness.
-
-`GET /healthz` only proves the daemon is listening. A successful health check does not prove that the model provider works.
-
-## Remove a device
-
-Send `DELETE /daemon/v1/clients/{clientId}` to revoke a token. A device can revoke itself. Host-management access also permits listing and revoking other devices.
-
-Revocation closes that device's streams and prevents further access. The workspace, accepted work, and schedules remain. [Stop work](/api/workflows/runs#stop-work) or [pause schedules](/api/workflows/schedules) separately.
-
-
- | Method and path | Access and use |
- | --- | --- |
- | `GET /healthz` | No token. Check liveness. |
- | `POST /daemon/v1/pair` | One-use pairing code. Issue a device token. |
- | `GET /daemon/v1/discovery` | Paired device. Read identity and configuration state. Host fields require host management. |
- | `GET /v1/capabilities` | Paired device. Read feature support. |
- | `GET /v1/confidential/attestation` | Paired device. Read the configured confidential-mode verification response. |
- | `POST /daemon/v1/pairing-codes` | Host management. Create a code with `manageHost: true` or `false`. |
- | `GET /daemon/v1/clients` | Host management. List current devices without token values. |
- | `DELETE /daemon/v1/clients/{clientId}` | Self, or host management for another device. Revoke access. |
-
- Pairing returns `expiresAt` in Unix milliseconds. Device listings use `expires_at` and `manage_host`. Use the exact field names in each response.
-
-
-After enabling and applying confidential mode, `/v1/confidential/attestation` reports `success`, `unavailable`, or `error`. `unavailable` can mean the mode is off or no key is active.
-
-Cloud sign-in, developer-token management, managed app catalogs, and public sharing are unavailable on a daemon. Use [custom MCP connections](/api/workflows/connections) and its own [host settings](/api/daemon/settings).
diff --git a/content/docs/api/daemon/settings.mdx b/content/docs/api/daemon/settings.mdx
deleted file mode 100644
index 387c7e3..0000000
--- a/content/docs/api/daemon/settings.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Host settings
-icon: settings-2
-description: Change a daemon's model provider, sandbox resources, and shared folders safely.
----
-
-These operations require a device paired with `--manage-host`. Ordinary pairing already permits workspace work. Host management adds authority over this machine's configuration and connected devices.
-
-Prefer [Workspace settings in Fluso](/workspaces/manage) for interactive setup. Use this API when your client needs to manage the same settings.
-
-## Read, save, then apply
-
-Saving settings does not apply them to the running sandbox.
-
-1. Read `GET /daemon/v1/settings` and `GET /daemon/v1/sandbox`.
-2. Keep each response's `revision`.
-3. Save the change with that resource's `expectedRevision`.
-4. Keep the new revisions returned by the saves.
-5. Apply both revisions with `POST /daemon/v1/apply`.
-6. Read discovery and runtime status to check the outcome.
-
-For example, change the model while keeping the existing provider and key:
-
-```json
-{
- "expectedRevision": "SETTINGS_REVISION_FROM_READ",
- "settings": {
- "FLUSO_MODEL": "MODEL_ID_SUPPORTED_BY_YOUR_PROVIDER"
- }
-}
-```
-
-Send that body to `PATCH /daemon/v1/settings`. Omitted fields remain unchanged. `null` clears a field. Returned `secrets` are presence flags, not key values.
-
-Apply the saved revisions with:
-
-```json
-{
- "settingsRevision": "SETTINGS_REVISION_FROM_SAVE",
- "sandboxRevision": "SANDBOX_REVISION_FROM_READ",
- "interrupt": false
-}
-```
-
-A 409 `INTERRUPTION_REQUIRED` means active work would be interrupted. Ask the owner before repeating with `interrupt: true`.
-
-## Change the provider or sandbox
-
-For an OpenAI-compatible endpoint, set `FLUSO_PROVIDER: "custom"`, `OPENAI_BASE_URL`, `FLUSO_MODEL`, and `OPENAI_API_KEY`. Include `/v1` in the base URL when the provider requires it. Other provider choices are `openrouter`, `openai`, and `pcci`.
-
-A saved key stays tied to its endpoint. Enter a key again when changing that destination. Audio has separate provider and key settings. The [daemon's schema](/api#find-the-exact-fields) lists every supported setting.
-
-Sandbox changes use `PUT /daemon/v1/sandbox` with `expectedRevision` and the complete `config`. Preserve all intended `hostFiles` grants. An empty list removes shared-folder access.
-
-Host paths refer to the daemon's machine, even when you connect remotely. Grant only the required folders. Writable grants permit changing or deleting the original host files. Workspace `/v1/files` paths do not grant access to arbitrary host paths.
-
-
- | Method and path | Use |
- | --- | --- |
- | `GET /daemon/v1/settings` | Read saved provider settings and their revision. |
- | `PATCH /daemon/v1/settings` | Save changed fields. `preview: true` validates without saving. |
- | `GET /daemon/v1/sandbox` | Read configuration, revision, host RAM, and disk budgets. |
- | `PUT /daemon/v1/sandbox` | Replace the sandbox configuration with revision protection. |
- | `POST /daemon/v1/apply` | Apply the saved settings and sandbox revisions. |
-
- Sandbox `config` contains `runtimeProfile`, `hostFiles`, `memoryGiB`, and `diskGiB`. RAM is the VM allocation. Disk is the combined saved-work and temporary-work budget. It excludes images, backups, and shared host folders. Existing workspace data must fit a smaller budget before you apply it.
-
- On 409 `CONFIGURATION_CONFLICT`, reload both resources and review the newer changes. Do not substitute a fresh revision without reviewing them.
-
- During an update or apply, workspace routes can return 503 with `Retry-After`. Discovery shows `applying` or `configuration_error` where applicable. Resolve a configuration error before resubmitting work. A 423 locked credential store requires recovery on the host.
-
- Discovery exposes saved and applied revisions and `restartRequired` to host-authorized clients. After a lost apply response, read those values before another apply.
-
-
-Binary updates, backups, and credential-store recovery use the [daemon CLI](/workspaces/manage). The settings API does not replace those operations.
diff --git a/content/docs/api/first-request.mdx b/content/docs/api/first-request.mdx
index 442489d..ffea445 100644
--- a/content/docs/api/first-request.mdx
+++ b/content/docs/api/first-request.mdx
@@ -8,7 +8,7 @@ This example asks Fluso to explain three ways to check a source. You get a compl
## 1. Get access
-For Cloud, create a [developer token](/api/cloud/tokens) with **Read and write** access. For Fluso Local, [pair a client](/api/daemon/pairing) after configuring its model provider.
+Create a [developer token](/api/cloud/tokens) with **Read and write** access.
Open your workspace's [API reference](/api#find-the-exact-fields) to check availability in that release.
@@ -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`. For a local daemon, use `http://127.0.0.1:4111/v1`. The token must belong to that workspace.
+For Fluso Dev, use `https://api.dev.khichdi.cc/v1`. The token must belong to that workspace.
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 8d3a848..f3232f6 100644
--- a/content/docs/api/index.mdx
+++ b/content/docs/api/index.mdx
@@ -12,28 +12,15 @@ Start with one conversation. Add schedules, connections, or live updates when yo
Get access, submit a short task, and read the saved answer.
-## Choose your workspace
+## Base URL and access
-Cloud and Fluso Local share the conversation, Agent, file, and schedule APIs. Their credentials and administration differ. Data stays in the workspace you address.
-
-| | Cloud API | Daemon API |
-| --- | --- | --- |
-| Where work runs | Your Fluso Cloud workspace | Your own machine's Fluso Local workspace |
-| Access for scripts | [Developer token](/api/cloud/tokens) | [Paired device token](/api/daemon/pairing) |
-| Example base URL | `https://api.fluso.ai/v1` | `http://127.0.0.1:4111/v1` |
-| Connected apps | Managed apps and custom MCP servers | Custom MCP servers |
-| Public sharing | Agents, conversations, and files | Unavailable |
-| Machine settings | Managed by the service | [Provider, sandbox, and devices](/api/daemon/settings) |
-
-Fluso Dev uses `https://api.dev.khichdi.cc/v1`. Use credentials from the same environment as the URL.
-
-For a remote daemon, use its HTTPS address or an [SSH tunnel](/workspaces/setup#connect-from-another-mac). A Cloud token cannot access a daemon.
+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.
## Find the exact fields
-Open **Settings → Developer tokens → API reference** in Cloud. On a daemon's host, open `http://127.0.0.1:4111/docs`.
+Open **Settings → Developer tokens → API reference** in Fluso.
-Releases with this API serve the endpoint reference at `/docs` and the OpenAPI schema at `/v1/openapi.json`. These describe the fields and operations available in that deployment. The reference also supplies runnable examples under `/v1/examples/`. The daemon serves its schema and examples locally. Its interactive reference needs internet access to load the viewer.
+Releases with this API serve the endpoint reference at `/docs` and the OpenAPI schema at `/v1/openapi.json`. These describe the fields and operations available in that deployment. The reference also supplies runnable examples under `/v1/examples/`.
The guides below explain how to combine those operations. Endpoint tables sit inside each guide, after the main workflow.
@@ -41,9 +28,6 @@ The guides below explain how to combine those operations. Endpoint tables sit in
Create a developer token and choose its access.
-
- Pair a client with your own workspace.
-
Continue work and read the complete answer.
diff --git a/content/docs/api/meta.json b/content/docs/api/meta.json
index 894994d..5bb1687 100644
--- a/content/docs/api/meta.json
+++ b/content/docs/api/meta.json
@@ -4,7 +4,6 @@
"[code-xml][Overview](/api)",
"first-request",
"cloud",
- "daemon",
"workflows"
]
}
diff --git a/content/docs/api/workflows/connections.mdx b/content/docs/api/workflows/connections.mdx
index f344585..e711dc1 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. Cloud offers managed apps such as Google Workspace. Fluso Local uses custom MCP servers.
+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.
The examples below use `api`, `thread_id`, and `run_id` from [your first request](/api/first-request).
@@ -65,11 +65,11 @@ The response identifies its transport and authentication method. Choose the matc
Open the returned `authorization_url` for OAuth. `already_connected` needs no sign-in. Wait for the session status to become `connected` before treating setup as complete.
- On Cloud, the callback submits `completion_proof` under the initiating account. On a daemon, `/daemon/v1/oauth/callback` completes it directly. Use the returned authorization URL unchanged.
+ The callback submits `completion_proof` under the initiating account. Use the returned authorization URL unchanged.
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 Cloud app session or a paired daemon device.
+ A developer write token can decide one-time tool approvals. Permanent rules require a signed-in app session.
@@ -79,11 +79,10 @@ Open the returned `authorization_url` for OAuth. `already_connected` needs no si
| `POST /v1/mcp-oauth/connections/static` | Save a key-based or unauthenticated connection. |
| `POST /v1/mcp-oauth/sessions` | Start custom OAuth authorization. |
| `POST /v1/mcp-oauth/sessions/byo-oauth` | Start OAuth with your client registration. |
- | `POST /v1/mcp-oauth/sessions/complete` | Cloud only. Save the connection from its completion proof. |
+ | `POST /v1/mcp-oauth/sessions/complete` | Save the connection from its completion proof. |
| `GET /v1/mcp-oauth/sessions/{session_id}/status` | Read authorization progress. |
- | `GET /daemon/v1/oauth/callback` | Daemon only. Receive the provider's OAuth callback. |
| `GET /v1/mcp-oauth/connections` | List connections without exposing secrets. |
- | `POST /v1/mcp-oauth/connections/refresh` | Refresh Cloud registrations or daemon tool discovery. |
+ | `POST /v1/mcp-oauth/connections/refresh` | Refresh registrations and tool discovery. |
| `DELETE /v1/mcp-oauth/connections/{server_id}` | Disconnect and invalidate its pending authority. |
| `GET /v1/mcp-oauth/connections/{server_id}/tools` | Read tool descriptions, input schemas, and read-only classifications. |
| `POST /v1/mcp-oauth/connections/{server_id}/tools` | Refresh or repair the connection before tool discovery. |
@@ -108,7 +107,7 @@ Open the returned `authorization_url` for OAuth. `already_connected` needs no si
| `GET /v1/mcp-oauth/connections/{server_id}/permissions` | Read saved and effective tool policies. |
| `PUT /v1/mcp-oauth/connections/{server_id}/permissions` | Change persistent connection or tool policies. |
- Cloud developer tokens cannot use these PUT routes or decision `scope: "always"`. Use a signed-in app session for permanent changes. Paired daemon devices can make these changes.
+ Cloud developer tokens cannot use these PUT routes or decision `scope: "always"`. Use a signed-in app session for permanent changes.
A stale permission version returns 409. Enabling thread auto-approval can resolve an eligible pending request. An explicitly denied tool remains denied. Changing the account default does not decide an existing pending approval.
diff --git a/content/docs/api/workflows/schedules.mdx b/content/docs/api/workflows/schedules.mdx
index c72dfdc..16a98bb 100644
--- a/content/docs/api/workflows/schedules.mdx
+++ b/content/docs/api/workflows/schedules.mdx
@@ -57,8 +57,6 @@ Pausing or deleting a schedule does not cancel work already accepted. [Cancel th
- The daemon host must be awake for work to run. After downtime, missed recurring runs combine into one catch-up run.
-
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 1b340fb..fe1958e 100644
--- a/content/docs/api/workflows/streaming.mdx
+++ b/content/docs/api/workflows/streaming.mdx
@@ -49,8 +49,6 @@ 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.
-
- For a daemon behind a proxy, disable response buffering for this stream.
diff --git a/content/docs/api/workflows/usage.mdx b/content/docs/api/workflows/usage.mdx
index 794829f..08d2567 100644
--- a/content/docs/api/workflows/usage.mdx
+++ b/content/docs/api/workflows/usage.mdx
@@ -32,7 +32,7 @@ Use the records to compare model calls within the task. Further filters include
api /token-usage | jq '{totals, last_updated}'
```
-Reports can arrive after execution. They are recorded estimates, not a final bill. For a daemon using your provider key, check that provider's billing too.
+Reports can arrive after execution. They are recorded estimates, not a final bill.
| Method and path | Use |
diff --git a/content/docs/deployment-models.mdx b/content/docs/deployment-models.mdx
index 91da9ca..1197f9a 100644
--- a/content/docs/deployment-models.mdx
+++ b/content/docs/deployment-models.mdx
@@ -2,7 +2,7 @@
title: Deployment models
sidebarTitle: Overview
icon: server-cog
-description: Compare Fluso Cloud, a workspace on your machine, and Enterprise deployments.
+description: Compare Fluso Cloud and Enterprise deployments.
---
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.
@@ -10,7 +10,6 @@ Your deployment model decides who operates Fluso and where its runtime, durable
| Model | Availability | Operations |
| --- | --- | --- |
| Fluso Cloud | Available | Managed by Fluso |
-| Fluso Local | Contact Fluso for a matching Mac or Linux package | You operate one owner's workspace |
| 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 |
@@ -21,12 +20,6 @@ Fluso Cloud is the standard managed service. It runs on AWS with European hostin
Choose it when you want to start without operating infrastructure. See [Legal](/resources/legal) for Fluso's privacy policy.
-## Fluso Local
-
-Install the daemon to run one owner's workspace on an Apple Silicon Mac or a supported Linux host. Conversations and files stay on that host. You manage its provider credentials, service, updates, and backups.
-
-The desktop app connects to this workspace. It does not install or update the daemon. This is separate from an Enterprise deployment of the whole platform. Start with [Set up Fluso Local](/workspaces/setup).
-
## 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.
@@ -64,7 +57,6 @@ Traces can include prompt and response text. For a dedicated or on-premises depl
## Choose a model
- Start with Fluso Cloud when managed operations and European hosting meet the requirement.
-- Use [Fluso Local](/workspaces) when you want to operate a workspace on your own machine.
- 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.
diff --git a/content/docs/features/approvals.mdx b/content/docs/features/approvals.mdx
index 55f5344..483f948 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, web, and Telegram.
+Open **Settings → Approvals & permissions**. **Auto-approval** sets your default across desktop and web.
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 0e933c8..c0e5f84 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. Telegram has its own conversation mode: using `/fast` in Telegram does not change an app chat, and changing the app control does not change Telegram.
+This only affects the chat you are using in the app.
## Approval mode
diff --git a/content/docs/features/open-architecture.mdx b/content/docs/features/open-architecture.mdx
index 991cce7..4c7910e 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 on Cloud and [daemon workspaces](/workspaces). Authenticate with a Cloud developer token or a paired daemon 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. Authenticate with a developer token. Store only the data your integration needs.
diff --git a/content/docs/index.mdx b/content/docs/index.mdx
index abc44c4..7a32da8 100644
--- a/content/docs/index.mdx
+++ b/content/docs/index.mdx
@@ -48,9 +48,6 @@ Pick a workflow that matches a problem you have right now. Each one is a story,
## When you need it
-
- Set up Fluso on your own machine and use it with your files, Agents, and routines.
-
The five primitives: chat, apps, skills, tasks, memory.
@@ -61,7 +58,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 Cloud or Fluso Local, submit work, and read the result.
+ Connect a script to Fluso, submit work, and read the result.
Plans, limits, billing.
diff --git a/content/docs/meta.json b/content/docs/meta.json
index 530d2a0..039aa2b 100644
--- a/content/docs/meta.json
+++ b/content/docs/meta.json
@@ -12,8 +12,6 @@
"...features",
"---Fluso API---",
"...api",
- "---Fluso Local---",
- "...workspaces",
"---Get started---",
"going-deeper",
"introduction",
@@ -24,8 +22,6 @@
"...resources",
"---Release notes---",
"release-notes",
- "---Remote access---",
- "...remote",
"---Workflows---",
"...workflows"
]
diff --git a/content/docs/release-notes.mdx b/content/docs/release-notes.mdx
index c018f4f..f8f10d3 100644
--- a/content/docs/release-notes.mdx
+++ b/content/docs/release-notes.mdx
@@ -307,7 +307,7 @@ description: "What's new in Fluso - product updates, improvements, and fixes."
**Smarter assistant**
- The inline editor opens Markdown, documents, and code, with a per-thread list of the files in that chat. Your edits are handed back to the assistant instead of being overwritten the next time it works on the file.
-- Fast mode lives in the composer and stays set for that thread. On Telegram, send `/fast` to toggle Fast for the current Telegram conversation.
+- Fast mode lives in the composer and stays set for that thread.
- The assistant is clearer about what it can and can't do, and points you to the docs for how it works rather than claiming features that aren't set up.
**Plans & limits**
@@ -365,7 +365,6 @@ description: "What's new in Fluso - product updates, improvements, and fixes."
**Find things faster**
- Search past conversations from the sidebar, with matches highlighted.
-- Telegram chats are now labelled in the sidebar so you can tell sources apart at a glance.
**Smarter assistant**
- Deep Research asks a clarifying question when your request is ambiguous instead of guessing, and uses refreshed web-search connectors.
diff --git a/content/docs/remote/telegram.mdx b/content/docs/remote/telegram.mdx
deleted file mode 100644
index 59cee88..0000000
--- a/content/docs/remote/telegram.mdx
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: Telegram
-sidebarTitle: Telegram
-icon: send
-description: Fluso's Telegram bot. Sign in once, then chat with Fluso from a private Telegram conversation.
----
-
-Fluso has a Telegram bot for the times you are away from your Mac. Sign in once with your Fluso account, and the bot is the same Fluso you use on the Mac app, just over Telegram.
-
-The bot only works in private chats. One Telegram account, one Fluso. It will not work in group chats.
-
-## Find the bot in the Mac app
-
-The easiest way to get to the bot is from inside Fluso:
-
-1. In the Fluso Mac app, click your name at the bottom left.
-2. Pick **Settings** from the menu.
-3. Scroll to the bottom of Settings. You will see a **Telegram** panel with a QR code and an **Open Telegram** button.
-4. Scan the QR code with your phone, or click **Open Telegram** if Telegram is already on your computer.
-
-Either way, you land in a private chat with `@fluso_bot`. That is the bot.
-
-## Sign in
-
-Once you are in the chat with `@fluso_bot`:
-
-1. Send `/login`.
-2. Tap the **Sign in** button the bot sends back.
-3. Finish signing in to Fluso in your browser.
-4. Telegram opens again and the bot confirms you are signed in.
-
-You will get signed out after a while. If the bot ever asks you to sign in again, send `/login` once more.
-
-## Connect your apps
-
-Before Fluso can read your Gmail, post in your Slack, or open issues for you, it needs to be connected to those apps. You only have to do this once per app. Connections you make here on Telegram are shared with the Mac app, so you do not have to set them up twice.
-
-- `/connect` shows the list of apps you can connect.
-- `/connect ` connects an app by name. Try `/connect google`, `/connect github`, `/connect slack`, or `/connect linear`.
-
-When you connect **Google**, you get all of Google in one go: Gmail, Drive, Docs, Sheets, Slides, Calendar, Meet, and Tasks. You do not need to connect Gmail or Calendar separately.
-
-`/status` tells you what is connected right now. `/disconnect` removes a connection. `/apps` shows the full list of apps you can connect.
-
-## What to ask
-
-Once you are signed in and have at least one app connected, ask in plain English.
-
-> *"Summarise my unread Gmail from today."*
-
-> *"Find the latest issue assigned to me in Linear."*
-
-> *"Search Slack for the deployment thread from yesterday."*
-
-> *"Read this document and pull out the key numbers."*
-
-> *"Use this voice note as my instruction."*
-
-If you ask for something that needs an app you have not connected yet, the bot will say so. Send `/connect ` and ask again.
-
-Connector writes in Telegram follow the same effective **Allow**, **Ask**, or **Deny** policy as the app. With **Ask**, the bot shows an approval card and waits for your decision. **Allow** or **Allow everything** can continue without a per-action prompt; **Deny** blocks the action.
-
-## Fast mode
-
-Send `/fast` to switch the current Telegram conversation to Fast mode. Fast mode turns reasoning off for quick, lighter work and can use fewer tokens.
-
-Send `/fast` again in the same Telegram conversation to switch back to High mode. The bot sends a short confirmation each time, so you can see whether Fast mode is on or off.
-
-This is conversation-specific, not an account setting. `/newchat` starts a fresh Telegram conversation back in High mode.
-
-Telegram mode and app mode are separate. Using `/fast` in Telegram does not change any chat in the app, and changing the app's response mode does not change Telegram.
-
-## Files, images, voice
-
-You can send more than just text:
-
-- **Files and documents** — Fluso saves them and reads them for you.
-- **Images** — same thing. Fluso can look at the picture and answer questions about it.
-- **Voice or audio** — Fluso treats it as your instruction. The reply may come back as voice or as text.
-- **Video and video notes** — these work too.
-- **Animated and video stickers** — these are not supported.
-
-Very large files may not go through. If a file is rejected, send a smaller version or split it into parts.
-
-## Conversation controls
-
-| Command | What it does |
-|---|---|
-| `/newchat` | Start a fresh conversation. Your files are kept. |
-| `/fast` | Toggle the current conversation between Fast and High. `/newchat` resets it to High. |
-| `/reset` | Wipes everything: files, chat history, and what Fluso has learned. Cannot be undone. |
-| `/abort` | Stop what Fluso is doing right now. |
-| `/schedules` | Show anything Fluso has scheduled, if any. |
-| `/logout` | Sign out of the Telegram bot. |
-| `/help` | Show the bot's commands. |
-
-
- `/reset` cannot be undone. It clears your files, chat history, and everything Fluso has remembered on Telegram. If you only want a fresh conversation, use `/newchat` instead.
-
-
-## While Fluso is working
-
-A long answer may arrive as a few Telegram messages in a row instead of one big message. Any files Fluso creates for you will arrive as attachments.
-
-If Fluso is still starting up, the bot will say so and ask you to try again in about a minute.
-
-## Troubleshooting
-
-
-
- You have been signed out. Send `/login` and finish the browser sign-in to start again.
-
-
- Send `/connect `, then ask your original question again.
-
-
- The file is too big. Send a smaller version, or split it into parts.
-
-
- Send `/abort` to stop it. If the bot says it is still loading, wait a moment and try again.
-
-
- Send `/newchat` to start fresh. Your files are kept. Only use `/reset` if you want to wipe everything.
-
-
-
-## See also
-
-
-
- What app connections are and how to manage them.
-
-
- How chat works in Fluso. Telegram works the same way.
-
-
diff --git a/content/docs/workspaces/index.mdx b/content/docs/workspaces/index.mdx
deleted file mode 100644
index 26fe754..0000000
--- a/content/docs/workspaces/index.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Fluso Local
-sidebarTitle: Overview
-icon: monitor
-description: Set up Fluso on your own machine and use it for your daily work.
----
-
-Fluso Local runs your workspace on a computer you control. Use your Mac for work with local files, or a Linux machine for work that continues after you close your laptop.
-
-You still talk to Fluso in the desktop app. Your conversations, Agents, and workspace files stay on the machine you choose.
-
-## Choose where to run it
-
-| Where | Useful for | How you connect |
-| --- | --- | --- |
-| Your Apple Silicon Mac | Working with documents on your laptop | Choose **This Mac** in Fluso |
-| A supported Linux machine | Keeping work running while your laptop is closed | Connect from Fluso on your Mac |
-
-A Linux machine can be at home or on a server you manage. A Raspberry Pi works only with a supported 64-bit system and working hardware virtualization.
-
-
-
- Get the download, choose macOS or Linux, and connect the app.
-
-
- Work with your files, keep an Agent, and schedule useful work.
-
-
-
-## What you need
-
-You install a background program called the **daemon** on the machine that will do the work. It runs separately from the desktop app. You also supply a model provider key and keep that machine awake for work to continue.
-
-[Contact us](mailto:support@premai.io?subject=Fluso%20Local%20download) for the daemon download links. Include your operating system, processor type, and whether you use Fluso or Fluso Dev.
-
-The [setup guide](/workspaces/setup) checks your machine before installation. You do not need Docker or a source checkout. For use without the desktop app, follow [API access](/api/first-request) after setup.
-
-## Where your work stays
-
-Each machine has its own conversations, Agents, files, and connections. They are separate from Fluso Cloud. Switching workspaces does not move or synchronize your work.
-
-Fluso can use files you upload or folders you explicitly share. It has no access to your other personal folders by default.
-
-Your chosen model provider receives the content needed to answer. Connected services receive their tool requests. Local storage does not make all processing local. The desktop interface still needs internet access and Fluso sign-in.
-
-
- Conversations, Agents, files, routines, and custom MCP connections use the selected workspace. Cloud billing, managed app connections, ingestion services, legacy Tasks, and public sharing are not available through the daemon.
-
- Each paired client has access to the same owner's workspace. Pairing does not create separate user accounts or private areas for different people.
-
-
-Start with [Set up Fluso Local](/workspaces/setup). Return to [settings and maintenance](/workspaces/manage) for provider changes, updates, and backups.
diff --git a/content/docs/workspaces/manage.mdx b/content/docs/workspaces/manage.mdx
deleted file mode 100644
index bafd6d5..0000000
--- a/content/docs/workspaces/manage.mdx
+++ /dev/null
@@ -1,140 +0,0 @@
----
-title: Manage your workspace
-sidebarTitle: Settings and maintenance
-icon: settings-2
-description: Choose a provider, share folders, adjust resources, and keep your workspace recoverable.
----
-
-Open **Workspaces** in Fluso and select the machine you want to change. These settings belong to that host, even when you use the app on another Mac.
-
-To use the terminal instead, run the commands below from the installed package folder on the host. Add `--root /path/to/state` only when selecting a different installation.
-
-## Choose a model provider
-
-Open **Model provider**, enter your provider details, then **Save and apply**. You supply the credentials. The daemon does not include a Fluso Cloud inference allowance.
-
-| Provider | What you supply |
-| --- | --- |
-| OpenRouter or OpenAI | API key and model ID |
-| Custom | An OpenAI-compatible base URL, API key, and exact model ID |
-| Prem · Confidential | Prem API key, then **Enable confidential inference** |
-
-For terminal setup, use `./fluso-daemon configure --apply`. Prompts hide your keys. Pressing Enter keeps a saved value.
-
-Saved changes need Apply or a restart before they take effect. Applying settings can restart the workspace's compute. Finish active work first. An explicit interruption can stop a running task.
-
-
- A custom endpoint must support streaming and tool calls, a 128K context window, and up to 16K output tokens. Use HTTPS for a remote provider. Local or trusted-network inference endpoints can use HTTP.
-
- `localhost` refers to the daemon's host. For a Pi workspace, it does not refer to the Mac running Fluso. Changing an endpoint requires entering its key again.
-
- Prem confidential inference verifies the provider and encrypts inference requests. It does not encrypt every workspace file or make external tools confidential. Image generation and speech synthesis are unavailable in this mode. Turning it off restores your saved standard provider.
-
- Provider failures do not silently switch to another provider. Media features can need separate provider credentials. Configure these with the same CLI command.
-
-
-## Connect an app
-
-Open **Plugins → MCP → Add MCP** and choose **Custom server**. Enter the service's public MCP endpoint and supply its credentials or complete its OAuth sign-in.
-
-The daemon does not copy Cloud connections or provide the managed app catalog. Custom MCP destinations must be public: private network addresses and redirects are blocked. Review the service's permissions before you connect it.
-
-## Share a folder
-
-No personal host files are shared by default. Uploaded workspace files are separate from these grants.
-
-1. In **File access**, add the file or folder the Agent needs.
-2. Keep **Read only** for reference material. Choose **Read and write** for files the Agent should edit.
-3. Review the native confirmation and select **Save and apply**.
-
-For a report-writing task, share a reference folder read-only and a separate drafts folder with write access. Tell the Agent which folder holds each kind of file.
-
-On a remote workspace, enter paths on that remote host. A Mac path such as `/Users/alex/Drafts` appears to tools under `/mnt/host/Users/alex/Drafts`.
-
-Read-only access prevents edits, but content can still reach the chosen model provider. Share a specific folder instead of your entire home directory.
-
-
- Use `./fluso-daemon host-files --apply` for the same settings in a terminal.
-
- A folder grant includes its descendants. A single-file grant permits in-place edits. Share the parent folder when a tool must rename or replace files. Overlapping grants are rejected.
-
- Remove a path and apply the change to revoke access. This does not delete content already copied into the workspace or conversation. Operating-system permissions still apply to writable grants.
-
-
-## Adjust memory and storage
-
-The default sandbox has **3 GiB of RAM** and a **64 GiB disk budget**. The disk grows as needed: 56 GiB holds saved work and 8 GiB is for temporary work.
-
-Change these values in the workspace settings, or run `./fluso-daemon resources --apply`. Leave memory and disk space for the operating system and other applications.
-
-Runtime images, backups, and shared host folders are outside this disk budget. Reducing a limit must still leave room for saved data. Applying the change preserves saved files and replaces temporary storage.
-
-**Resources and storage** shows the data directory. On This Mac, **Open data folder** opens it in Finder. In a terminal, `./fluso-daemon info` shows the same paths.
-
-## Update the daemon
-
-Run this on the host:
-
-```bash
-./fluso-daemon update
-./fluso-daemon version
-./fluso-daemon status
-```
-
-The command finds the latest release for the installed development or production channel. You do not need another download URL or a GitHub login.
-
-It checks the download and signature before stopping the service. Updates keep files, conversations, settings, and pairings. If the replacement cannot start correctly, the updater restores the previous package.
-
-Updates run only when requested. The desktop app updates separately. A stopped service stays stopped. Active work must finish unless you explicitly allow interruption.
-
-Keep the current and previous package folders for recovery. Internet access is required for release verification.
-
-## Back up your work
-
-Run these commands one at a time on the host. Use a new backup folder:
-
-```bash
-mkdir -p "$HOME/fluso/backups"
-./fluso-daemon shutdown
-./fluso-daemon backup --backup-dir "$HOME/fluso/backups/first-backup"
-./fluso-daemon start
-```
-
-Continue to backup only after shutdown succeeds. Shutdown refuses to interrupt active work. If backup fails, inspect the error and restart the service when ready.
-
-The backup includes workspace files and its database. It excludes shared host folders. Back up those folders separately.
-
-Keep the **encryption key and file-access settings separately**. The backup does not contain the key needed to read saved credentials.
-
-- On macOS, the key is in the owner's Keychain.
-- On Linux, the key is in the installation's `keys` folder.
-- With `--root`, file-access settings are in `/sandbox/config.json`. The default Mac path is `~/.fluso/sandbox/config.json`.
-
-Backup files can contain readable documents. Store them privately and include them in your protected host backups.
-
-
- Restore accepts a backup from the same installation. Keep its original encryption key available. Stop the service, then run `./fluso-daemon restore --backup-dir /path/to/backup`. Start the service after restore succeeds.
-
- Restore keeps the pre-restore data separately. You must pair clients again, restore host-file access, and explicitly resume schedules. Pending work and approvals are not resumed automatically.
-
- If the key is lost, ask support about a credential reset. This can preserve files and conversations, but requires new credentials and connections.
-
- Ask support before moving a workspace to another machine. Copying only the project-files folder or SQLite database is not a complete migration.
-
-
-## When something needs attention
-
-Start with `./fluso-daemon status` and `./fluso-daemon doctor`. `./fluso-daemon doctor --fix` can repair startup or an interrupted update without resetting credentials or deleting workspace data.
-
-| Symptom | What to check |
-| --- | --- |
-| Settings cannot be changed | Reconnect with a code made by `pair --manage-host`. |
-| Pairing code rejected | Generate a new code. Codes expire after ten minutes and work once. |
-| Remote workspace unreachable | Check the host service and SSH tunnel or HTTPS address. |
-| Configuration saved but not active | Apply it. If another client changed settings, reload and review before saving again. |
-| Work pauses when the laptop closes | Keep the host awake, or use an always-on Linux host. |
-| Model or tool call fails | Check that provider's credentials and the saved result before retrying work. |
-
-For logs, check `daemon.log` in the Mac data directory. On Linux, use `journalctl --user -u fluso-daemon` for the user service. Share the relevant error with [support](mailto:support@premai.io), without API keys or pairing codes.
-
-Disconnecting a reachable workspace revokes that client's access. Forgetting an offline connection cannot confirm revocation. Signing out or uninstalling the desktop app does not stop the daemon.
diff --git a/content/docs/workspaces/meta.json b/content/docs/workspaces/meta.json
deleted file mode 100644
index fc64b41..0000000
--- a/content/docs/workspaces/meta.json
+++ /dev/null
@@ -1,12 +0,0 @@
-{
- "pages": [
- "!index",
- "[monitor][Overview](/workspaces)",
- "!setup",
- "[download][Setup](/workspaces/setup)",
- "!use",
- "[messages-square][Everyday use](/workspaces/use)",
- "!manage",
- "[settings-2][Settings and maintenance](/workspaces/manage)"
- ]
-}
diff --git a/content/docs/workspaces/setup.mdx b/content/docs/workspaces/setup.mdx
deleted file mode 100644
index ddb9280..0000000
--- a/content/docs/workspaces/setup.mdx
+++ /dev/null
@@ -1,206 +0,0 @@
----
-title: Set up Fluso Local
-sidebarTitle: Setup
-icon: download
-description: Install on macOS or Linux, choose a model provider, and connect Fluso.
----
-
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
-
-Install the daemon on the machine that will run your work. You can use the same Mac as the desktop app, or connect to a separate Linux machine.
-
-You need internet access and your own model provider key. Allow at least 8 GiB of memory and 8 GiB of free disk space, plus room for files and backups.
-
-## 1. Get the download
-
-[Email support@premai.io](mailto:support@premai.io?subject=Fluso%20Local%20download) for the daemon package. Include your operating system, processor type, and whether you use Fluso or Fluso Dev.
-
-On a Mac, find these details in **Apple menu → About This Mac**. On Linux, run `uname -m` and `cat /etc/os-release`.
-
-Ask for the release version, archive URL, and matching checksum URL:
-
-| Machine | Archive | Checksum |
-| --- | --- | --- |
-| Apple Silicon Mac | `daemon-darwin-arm64.tar.gz` | `daemon-darwin-arm64.sha256` |
-| Linux ARM64 (`aarch64`) | `daemon-linux-arm64.tar.gz` | `daemon-linux-arm64.sha256` |
-| Linux x64 (`x86_64`) | `daemon-linux-x64.tar.gz` | `daemon-linux-x64.sha256` |
-
-Use links supplied by Fluso. You do not need a GitHub account, Docker, Bun, or a source checkout.
-
-## 2. Install on your machine
-
-Choose the operating system of the machine that will run Fluso:
-
-
-
-
-You need an **Apple Silicon Mac**. This package does not support Intel Macs.
-
-**Download and check.** Open Terminal. Replace `ARCHIVE_URL` and `CHECKSUM_URL` with your links, keeping the quotes:
-
-```bash
-mkdir -p "$HOME/Downloads/fluso-daemon" &&
-cd "$HOME/Downloads/fluso-daemon" &&
-curl --fail --location 'ARCHIVE_URL' -o daemon-darwin-arm64.tar.gz &&
-curl --fail --location 'CHECKSUM_URL' -o daemon-darwin-arm64.sha256 &&
-shasum -a 256 -c daemon-darwin-arm64.sha256
-```
-
-Continue only if the check prints `daemon-darwin-arm64.tar.gz: OK`. If it fails, download both files again from the matching release links.
-
-**Extract the package.** Replace `RELEASE_VERSION` with the version supplied by support. Use a new folder:
-
-```bash
-mkdir -p "$HOME/fluso/releases" &&
-mkdir "$HOME/fluso/releases/RELEASE_VERSION" &&
-tar -xzf daemon-darwin-arm64.tar.gz -C "$HOME/fluso/releases/RELEASE_VERSION" &&
-cd "$HOME/fluso/releases/RELEASE_VERSION"
-```
-
-Keep the whole folder in place. The executable needs the other files beside it. For later releases, use [update](/workspaces/manage#update-the-daemon).
-
-**Start and configure.** Run these commands one at a time as your normal Mac user, without `sudo`. If a command fails, stop and check its error:
-
-```bash
-./fluso-daemon setup --manage-host
-./fluso-daemon configure --apply
-./fluso-daemon status
-```
-
-Setup checks the signed package and installs a background service. Follow the prompts to choose your model provider, model, and API key. Key entry stays hidden. Prem confidential inference needs only your Prem API key.
-
-Respond to macOS Keychain or folder-access prompts. Wait for `status` to report that the workspace is ready.
-
-The service starts when you log in. Closing Fluso leaves it running. Putting the Mac to sleep pauses its work.
-
-
-
-
-Use **64-bit glibc Linux with systemd**: Ubuntu 24.04, Debian 13, or newer. The packages support ARM64 and x64.
-
-The host needs **KVM**, Linux's hardware virtualization facility. A virtual machine also needs nested virtualization from its host provider.
-
-**Check access to KVM.** Run this on the Linux machine:
-
-```bash
-test -r /dev/kvm && test -w /dev/kvm && echo 'KVM access is ready'
-```
-
-If it does not print `KVM access is ready`, stop here. Ask your administrator to enable KVM and grant your user read/write access. After a group-permission change, sign out and sign in again.
-
-
- A Raspberry Pi needs a supported 64-bit operating system and kernel with usable KVM. An ARM64 processor alone is not enough. Send your system details and KVM check to support if you are unsure.
-
-
-On Ubuntu or Debian, install the native library and download tools:
-
-```bash
-sudo apt-get update
-sudo apt-get install libcap-ng0 curl ca-certificates
-```
-
-**Download and check.** These commands use ARM64. On x64, replace every `arm64` with `x64`. Replace the two URL placeholders with your links:
-
-```bash
-mkdir -p "$HOME/Downloads/fluso-daemon" &&
-cd "$HOME/Downloads/fluso-daemon" &&
-curl --fail --location 'ARCHIVE_URL' -o daemon-linux-arm64.tar.gz &&
-curl --fail --location 'CHECKSUM_URL' -o daemon-linux-arm64.sha256 &&
-sha256sum -c daemon-linux-arm64.sha256
-```
-
-Continue only if the check prints `OK`. If it fails, download both files again from the matching release links.
-
-**Extract the package.** Replace `RELEASE_VERSION` with the supplied version. Use a new folder:
-
-```bash
-mkdir -p "$HOME/fluso/releases" &&
-mkdir "$HOME/fluso/releases/RELEASE_VERSION" &&
-tar -xzf daemon-linux-arm64.tar.gz -C "$HOME/fluso/releases/RELEASE_VERSION" &&
-cd "$HOME/fluso/releases/RELEASE_VERSION"
-```
-
-Keep all extracted files together. Do not overwrite an installed package. Use [update](/workspaces/manage#update-the-daemon) for later releases.
-
-**Start and configure.** Run these commands one at a time as the workspace owner, without `sudo`. If a command fails, stop and check its error:
-
-```bash
-./fluso-daemon setup --root "$HOME/fluso/state" --manage-host
-./fluso-daemon configure --root "$HOME/fluso/state" --apply
-./fluso-daemon status
-```
-
-Follow the prompts for your own model provider and key. Setup keeps data and keys under `~/fluso/state`, outside the package. It remembers this installation for later commands.
-
-Wait for the workspace to become ready. Setup also arranges for the user service to run after logout and at boot. If administrator approval is needed, it prints a `sudo loginctl enable-linger` command. Have your administrator run that exact command.
-
-
-
-
-`--manage-host` lets the connected app change the provider, resource limits, and shared folders. You can review these in [workspace settings](/workspaces/manage).
-
-## 3. Connect Fluso
-
-Open the matching, current [Fluso desktop app](https://fluso.ai/) on your Mac and sign in.
-
-### On the same Mac
-
-1. Open **Workspaces** from the account menu. **View → Workspace settings** opens the same page.
-2. Open the workspace selector and choose **This Mac**. Complete any native confirmation.
-
-### Connect from another Mac
-
-The machine running Fluso must be reachable through SSH or HTTPS. For a Linux host, the SSH connection below is a way to start. You do not need a daemon on the Mac that connects to it.
-
-On the host, create a pairing code from the package folder:
-
-```bash
-./fluso-daemon pair --manage-host
-```
-
-Keep the code private. Each code works once and expires after ten minutes. It gives the client workspace access and permission to change host settings.
-
-On your Mac, open Terminal. Replace `USER` and `HOST` with your host login and address:
-
-```bash
-ssh -N -o ExitOnForwardFailure=yes -L 127.0.0.1:4111:127.0.0.1:4111 USER@HOST
-```
-
-Leave this terminal open. Use the same local and remote port shown by setup. The daemon checks the port in incoming requests.
-
-1. Open **Workspaces** in the current Fluso desktop app.
-2. Under **Connect a remote workspace**, enter a name, such as `Home server`.
-3. Enter `http://127.0.0.1:4111` as the **Workspace URL**, then paste the pairing code.
-4. Select **Connect**.
-
-Closing the tunnel disconnects the client. It does not stop work on the host. Reopen the tunnel to reconnect. Pairing remains valid unless revoked or unused for 30 days.
-
-
- A Mac daemon or another tunnel may already use that port. For a new host installation, choose two free ports during setup, for example `--port 4211 --control-port 4212`.
-
- Forward `127.0.0.1:4211` to `127.0.0.1:4211` and use port `4211` in the workspace URL. For an existing host, stop its service before repeating setup with changed ports. Keep its original `--root`.
-
-
-
- For a host with DNS and a trusted TLS certificate, add `--public-origin https://workspace.example.com` during setup. Put an HTTPS reverse proxy in front of port `4111`.
-
- The proxy must preserve the requested Host, support streamed responses, and block `/control/*`. Keep both daemon ports on loopback. Port `4112` is private runtime control. Configure OAuth callbacks for the final HTTPS origin.
-
- Use the HTTPS URL and a fresh pairing code in Fluso. Ordinary remote HTTP is not accepted. Ask support for help if you do not manage this infrastructure.
-
-
-## 4. Try your first task
-
-Open a chat in the selected workspace. Attach a short document and ask Fluso to summarize its main points.
-
-Your Cloud conversations stay in Cloud. This workspace has its own data. Continue with [Use Fluso Local](/workspaces/use) for files, Agents, and routines.
-
-
- From the package folder, run `./fluso-daemon status` and `./fluso-daemon doctor`. Use `./fluso-daemon info` to see its paths and API address.
-
- Start a stopped service with `./fluso-daemon start`. If configuration is missing, rerun `./fluso-daemon configure --apply`.
-
- In **Workspaces**, refresh the workspace list. A release mismatch requires a compatible desktop app and daemon. Changing the data directory does not fix it. Keep the original data and keys when diagnosing an existing installation.
-
- If macOS cannot verify the developer, use **System Settings → Privacy & Security → Open Anyway** only for the package supplied by Fluso. Follow [Apple's instructions](https://support.apple.com/en-us/102445) after checking the download. For a damaged-file or malware warning, contact support with the exact message.
-
diff --git a/content/docs/workspaces/use.mdx b/content/docs/workspaces/use.mdx
deleted file mode 100644
index 730148e..0000000
--- a/content/docs/workspaces/use.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Use Fluso Local
-sidebarTitle: Everyday use
-icon: messages-square
-description: Work with your files, return to an Agent, and keep useful work running.
----
-
-After [setup](/workspaces/setup), you use Fluso through the same desktop app. Start with a small task and check the result before giving it more work.
-
-## Open your workspace
-
-Open **Workspaces** from the account menu. Choose **This Mac** or the remote connection you saved.
-
-Each workspace has its own conversations, Agents, files, and connections. If your Cloud chats are missing, switch to **Fluso Cloud** to see them.
-
-When you reopen the app, it starts on Cloud. Select your saved local or remote workspace again.
-
-## Start with a document
-
-Open a chat and attach a document with the **+** button, or drag it into the conversation. Try a set of meeting notes:
-
-> *"Turn these notes into a short plan for next week. Separate agreed actions from open questions. Include an owner or date only where the notes give one."*
-
-Read the answer against your notes. Continue in the same chat to correct a detail or add another document.
-
-An attachment copies the file into the selected workspace. It does not give Fluso access to the rest of your computer.
-
-## Work with a folder
-
-For files you use repeatedly, [share a folder](/workspaces/manage#share-a-folder) in workspace settings. Keep reference files read-only. Grant write access only where you want Fluso to edit files.
-
-Tell Fluso the folder path shown by the settings and what you want:
-
-> *"Review the meeting notes in this folder. Give me a short list of decisions that are still open, with the source file for each. Leave the files unchanged."*
-
-For a remote workspace, shared folders belong to the remote machine. Attach a file from your Mac when you want to copy it there.
-
-## Keep an Agent for repeat work
-
-Create an [Agent](/developers/agent-builder) in this workspace to keep instructions for a job you return to. For example, keep an assistant for reviewing your project notes.
-
-Once its results are useful, ask in the Agent's working conversation:
-
-> *"Every Friday at 4 PM in Europe/Zurich, review this project's notes. Summarize progress, open decisions, and next week's priorities here."*
-
-Use your own time and timezone. Check the saved [routine](/developers/schedules) in **Routines**. Read its results in the conversation or **Inbox**.
-
-The machine running Fluso must stay awake and connected. Closing the desktop app leaves accepted work running. After downtime, missed recurring runs are combined into one catch-up run.
-
-## Return from another location
-
-For a remote machine, reopen your [SSH tunnel](/workspaces/setup#connect-from-another-mac) or use its configured HTTPS address. Your Mac must be able to reach that machine. Pairing alone does not make a home computer reachable over the internet.
-
-Select the saved connection to return to its work. Closing the tunnel disconnects your app, but leaves work running on the remote machine.
-
-To use an external service, [connect its custom MCP server](/workspaces/manage#connect-an-app) in this workspace. Cloud app connections do not carry over.
-
-For provider changes, storage, updates, and backups, open [settings and maintenance](/workspaces/manage).
diff --git a/public/_redirects b/public/_redirects
index e8391c6..8298817 100644
--- a/public/_redirects
+++ b/public/_redirects
@@ -40,12 +40,12 @@
/developers/architecture /api 301
/developers/architecture/ /api 301
/llms.mdx/docs/developers/architecture/content.md /llms.mdx/docs/api/content.md 301
-/workspaces/macos /workspaces/setup 301
-/workspaces/macos/ /workspaces/setup 301
-/workspaces/linux /workspaces/setup 301
-/workspaces/linux/ /workspaces/setup 301
-/llms.mdx/docs/workspaces/macos/content.md /llms.mdx/docs/workspaces/setup/content.md 301
-/llms.mdx/docs/workspaces/linux/content.md /llms.mdx/docs/workspaces/setup/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,3 +76,26 @@
/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