fimo 2.9.0 → 2.10.0-staging.2

package/assets/skills/fimo-studio/references/integrations.md

@@ -0,0 +1,103 @@
+# Integrations
+
+Integrations let a site use external services without exposing credentials to editors, chat, or agents. Studio, the CLI, and
+agent chats all resolve the same integration state.
+
+## Connect an integration for the organization
+
+Open **Integrations** in the organization sidebar. It lists the integrations the organization already connected, then the ones still
+available, with the number of sites each integration is on. Choose an integration to open its panel.
+
+An organization admin connects an integration once for the whole organization, with no site needed:
+
+- **Google Search Console** and **Google Analytics**: **Sign in with Google**, using a Google account that can see the
+  site's property, and approve the permissions Fimo lists.
+- Integrations you sign in to: Ahrefs, DataForSEO, PostHog, Resend, Calendly and Cal.com. **Connect <integration>**
+  opens the provider's sign-in page and returns to Fimo. Finish in the same browser, signed in to Fimo as yourself.
+  Ahrefs, PostHog and Resend also offer **Use an API key instead**.
+- Semrush connects with a Semrush API key: **Connect Semrush** opens the form with the `Authorization` header and
+  `Apikey ` prefix filled in.
+- Slack: **Add to Slack** (in the organization's Integrations or a site's Integrations; each sign-in adds a workspace), then choose each
+  site's channels.
+
+People who are not organization admins see **Copy link** instead, to send its link to an admin. The panel also shows
+the connected account, with **Disconnect** (removes the integration from every site, with its settings and always-allowed tools), or **Reconnect** when the
+provider stopped accepting it. A custom MCP server's **…** menu has **Rename** and **Delete server**. An MCP integration's
+panel also shows its server and tools: see [Manage an MCP server](#manage-an-mcp-server).
+
+### Site access
+
+Under **Site access** in the integration's panel, choose **All sites** to give every site access, including sites created later,
+or **Only select sites** and **Select sites**. Choose **Save**. A site left out loses the integration, and its managers cannot
+turn it back on until an admin gives the site access again.
+
+## Use an integration on a site
+
+Open the site, then **Settings** → **Integrations**. The page lists the integrations **On for this site** first, then the **Available**
+ones. Select an integration to open its panel. It says whether the integration is on for the site; the account, credentials and tools
+live in the organization's **Integrations**:
+
+- The switch turns the integration on or off for this site. People who manage the site can do this for any integration the site has
+  access to; others see it without changing it. An integration the organization has not connected says so and links to **Integrations**.
+- Settings appear once the integration is on. Google integrations ask for the **Search Console property** or **Google Analytics
+  property** the site uses; Fimo suggests the one that matches the site's domain. An integration still missing a setting shows
+  **Finish setup** on its card, and its panel asks for the setting first; connecting from the site opens it there.
+- **Manage the account and site access in Integrations** opens the organization page, for admins.
+
+## Approve a change
+
+Reads from an integration run straight away, and so do changes a person runs. When an agent wants to change data in an integration,
+the chat shows a card with the integration, the tool and why it asks:
+
+- **Allow** runs that exact change once.
+- **Always allow** (for changes that are not paid actions) runs it and lets agents run that tool on this site
+  without asking again, in any chat.
+- **Decline** stops it.
+
+Paid actions ask every time. Changes asked from Slack, a routine, the CLI or the hosted MCP give a link to
+**Settings** → **Integrations**, where the same card appears. For Slack, Fimo continues in the thread once it is allowed. A
+routine cannot wait, so its link offers only **Always allow** and **Decline**, and its later runs make the change. For
+the CLI or an AI client, **Allow** shows a one-time code to paste back; after **Always allow** the same call runs without
+one. A request is answered once and an approval runs one exact change, both within an hour.
+
+## Slack channels
+
+Open **Slack**, then **Workspaces and channels**. Each Slack workspace the site answers in has a row. Open one to turn
+it on for the site and choose the channels where Fimo answers mentions. Which sites use a workspace is Site access, and
+disconnecting it is the account's **…** menu, both on Slack's page in the organization's Integrations, where **Add another
+account** adds another workspace.
+
+## Add an MCP server
+
+Choose **Add MCP server** in a site's **Settings** → **Integrations** (anyone who manages the site), or on the organization's
+**Integrations** page (organization owners and admins). A server added from a site shows in the organization's Integrations too:
+
+1. Enter a **Name** and the server's **MCP URL**, a Streamable HTTP `https://` endpoint. A listed MCP integration, such as Semrush
+   or PostHog, fills both when you connect it from its panel.
+2. **Connect with** shows the recommended sign-in path. Fimo checks the endpoint; public servers connect immediately,
+   while OAuth servers open their provider sign-in page and return after approval.
+3. Open **Other ways to connect** when the server instead documents an access token, custom headers, or no
+   authentication.
+4. In a site, **Use from another site** reuses a server another site already connected.
+
+For **Paste an access token**, enter only the token; Fimo adds the `Bearer` scheme. For **Send custom headers**, enter
+each complete value exactly as the server expects, including any prefix (`Authorization` with `Bearer abc123`). Fimo
+encrypts every saved grant and never shows its private value again.
+
+## Manage an MCP server
+
+An MCP integration's panel in the organization's **Integrations** shows the server's address and its tools, grouped into reads,
+changes and deletes; open a group, then a tool, for its full description. When the tools stop loading, the panel offers
+the one repair for how the organization signs in:
+
+- **Reconnect** signs in again for OAuth.
+- **Update credentials** replaces a bearer token or the complete custom-header bundle after it stops working.
+- **Retry connection** asks a public server for its tools again without touching any credential.
+
+The account's **…** menu also has **Rotate credentials**, to replace a healthy token or header bundle. A custom
+server's **…** menu has **Delete server**, which removes the server from the organization, for every site that uses it.
+Only organization owners and admins can replace a shared credential or delete a server.
+
+Only integrations turned on for the site are available to Studio chat and the Fimo CLI for this site. Agents should discover
+them with `fimo integrations list`, inspect one with `fimo integrations info <integration>`, and run an allowed tool with
+`fimo integrations run <integration> <tool>`.

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-10-21T15:49:00.346Z",
+  "bundledAt": "2026-10-23T10:48:42.104Z",
   "cliVersion": "2.9.0",
   "external": [
     "oxc-parser",