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

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion content/docs/api/cloud/apps.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion content/docs/api/cloud/client-sign-in.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
9 changes: 0 additions & 9 deletions content/docs/api/daemon/meta.json

This file was deleted.

71 changes: 0 additions & 71 deletions content/docs/api/daemon/pairing.mdx

This file was deleted.

75 changes: 0 additions & 75 deletions content/docs/api/daemon/settings.mdx

This file was deleted.

4 changes: 2 additions & 2 deletions content/docs/api/first-request.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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:

Expand Down
24 changes: 4 additions & 20 deletions content/docs/api/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,38 +12,22 @@ Start with one conversation. Add schedules, connections, or live updates when yo
Get access, submit a short task, and read the saved answer.
</Card>

## 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.

<CardGroup cols={2}>
<Card title="Cloud access" icon="cloud" href="/api/cloud/tokens">
Create a developer token and choose its access.
</Card>
<Card title="Daemon access" icon="server" href="/api/daemon/pairing">
Pair a client with your own workspace.
</Card>
<Card title="Send messages" icon="messages-square" href="/api/workflows/conversations">
Continue work and read the complete answer.
</Card>
Expand Down
1 change: 0 additions & 1 deletion content/docs/api/meta.json
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,6 @@
"[code-xml][Overview](/api)",
"first-request",
"cloud",
"daemon",
"workflows"
]
}
Loading
Loading