fimo 2.8.0-staging.8 → 2.8.0-staging.9

package/assets/skills/fimo-studio/SKILL.md

@@ -32,6 +32,15 @@ Use plain, friendly language. Describe what users see, where they click, and wha
 
 **Always read the relevant reference file before describing any UI feature, button, or panel.** Do not rely on your own knowledge of the interface — it changes frequently. If you are about to mention where something is located or how to access a feature, read the reference first.
 
+## Studio layout
+
+- **Header (desktop):** the site menu (site name; History is here) and the Branch switcher, then the workspaces: Chats, Getting started, Preview, Content, Assets, Agents, Analytics, Settings. Only workspaces the user can access appear. Workspaces that do not fit move into **More**. On the right: Earn free credits, Invite, Clone, Publish, and Merge on a Branch.
+- **Phone:** bottom tabs for Chat, Preview, Agents and Settings. Invite, Earn free credits and Clone ("Work on this site locally") move into the site menu.
+- **Settings:** General, Domains, Knowledge, SEO and Languages are listed directly. Models, Environments, Secrets, Schedules, Webhooks and Connections are under **Advanced settings**.
+- **Shortcuts:** Alt+1 Preview, Alt+2 Content, Alt+3 Assets, Alt+5 Settings, Alt+E edit mode, Cmd/Ctrl+K command palette.
+
+When a reference says "open X", X can be inside **More** on a narrow window.
+
 ## Topic index
 
 Read the relevant reference file when the user's question matches a topic.

package/assets/skills/fimo-studio/references/ai-chat.md

@@ -4,7 +4,15 @@ Open the **Chats** tab in the site header. On a phone, the Chat tab at the botto
 
 ## Working in Several Chats
 
-Chat has its own **Chats** tab in the site header; the tab shows how many chats have unread activity. A site can have several chats, shared by everyone on the site. The left list shows them most recently active first with a status (**Working** with a spinner while replying, **Done** once the reply finished) and their last words; a dot marks unread activity. Select **+** for a new chat (it joins the list when its first message is sent, and its name comes from that message; an empty chat offers starter requests), the search icon to find a chat, the filter icon to show only Working or Done chats, and the list settings for ordering and showing read, unread, or archived chats. The buttons above an open chat (or a right-click on a row) mark it unread, pin, archive, or mute it, for you only; the settings icon opens the chat's settings, which change its portrait (shape, face, color) and rename it for everyone, hold the same pin, mute and archive switches, and delete it, stopping a running reply first. Each chat has its own messages and context; when you refer to an earlier discussion, Chat searches the site's chats and answers with the messages it found. The open chat is in the page address (`/chats?chat=<id>`), so a link or reload opens the same chat.
+Chat has its own **Chats** tab in the site header; the tab shows how many chats have unread activity. A site can have several chats, shared by everyone on the site. The left list shows them most recently active first with a status (**Working** with a spinner while replying, **Done** once the reply finished) and their last words; a dot marks unread activity. Select **+** for a new chat (it joins the list when its first message is sent, and its name comes from that message; an empty chat offers starter requests), the search icon to find a chat, the filter icon to show only Working or Done chats, and the list settings for ordering and showing read, unread, or archived chats. The buttons above an open chat (or a right-click on a row) mark it unread, pin, archive, or mute it, for you only; the settings icon opens the chat's settings, which change its portrait (shape, eyes, mouth, color) and rename it for everyone, hold the same pin, mute and archive switches, and delete it, stopping a running reply first. Each chat has its own messages and context; when you refer to an earlier discussion, Chat searches the site's chats and answers with the messages it found. The open chat is in the page address (`/chats?chat=<id>`), so a link or reload opens the same chat.
+
+## Agents
+
+An agent is a chat with a job: a name and a description that Fimo reads at the start of every reply in that chat. Agents are shared like any chat and are listed as soon as they are created, with an **Agent** tag after the name. The **+** above the chat list is a menu: **New chat** (blank), **New agent** (a name and a description, then the empty agent opens), and under **Agents** Fimo's default agents (**SEO**, **Site health**, **Writer**, **Translator**); a new site starts with all four listed, their routines off until someone turns them on, and on an older site selecting a default creates the site's chat for it the first time, the same chat every time after. In an agent, the description shows next to its name in the header, the empty state introduces the agent by name and job, and the message box reads **Message <name>**. The agent's settings page has a **Description** field, shared with everyone; empty means none. The filter icon's **Kind** option shows only chats or only agents; search finds an agent by its name.
+
+### Routines
+
+A routine is saved instructions an agent runs in a thread of its own, by hand or on a schedule, so each run sees its earlier runs and the agent's chat never fills with its work. The agent's settings list its **Routines** as cards (name, cadence such as **Every Monday at 08:00** or **By hand**, next run, an **Active** switch) with a **New routine** button; the default agents come with theirs. A routine's page holds **Name**, **Instructions** (the task, run on every trigger), **Triggers** (**By hand** with **Run now**, which starts a run right away, or sends the routine a message as its next run; **Schedule**: none, every day, every week on a weekday, or every month on a day, at a time, in the timezone shown (a default agent's routines take the opener's browser timezone), at most every 15 minutes), the **Runs** list (newest first, two lines each: how it ended (**Quiet**, **Sent to agent**, **Asked for a decision**, or **Failed** and **Stopped** in red), when and what started it (**On schedule**, or **By hand** with the person's name or **agent** when their message started it), then the first sentence of what it told the agent; select one to open the routine's thread, read-only, at that run), the **Active** switch in the header (pauses the schedule only) and **Delete routine** (removes its thread too). Routines report to the agent, never to a person: a run that has something the agent should know writes it to the agent's chat as a message only the agent reads, and the agent takes a turn on it (reports waiting together are read in one turn); a run with nothing to say reports nothing. The agent decides what the team sees: nothing (the chat stays as it was, the row stays read), one short message (several reports folded into one), or a form when a person must decide, and the chat's row reads **Needs you** while that form is open. A person answers the form in the chat; the agent sends the decision to the routine with its `send_message` tool and the routine runs again with it; the routine page's **Answer the routine** (shown once the routine has run) does the same from there and answers the agent's open question for that routine in the chat with the same words (**Your answer starts a run. Anything that needs your attention appears in the agent chat.**). Quiet runs leave no message: they fold into one line placed where the last run happened among the messages (**N runs since <date>**), counted from the last report the agent answered visibly, and the chat's row reads **Ran <date>** with that count while the newest thing in the chat is a run, the ordinary status and the last words when a message is newer, and **First check <day> <time>** or **No checks scheduled** before the first run. A routine whose runs keep failing or are refused for credits is reported to the agent once per streak, as a message from Fimo.
 
 ## Sending a Message
 

package/assets/skills/fimo-studio/references/billing-and-credits.md

@@ -39,7 +39,7 @@ Buying credits is available while a paid plan is effective, including after sche
 
 ## Refilling Credits Automatically
 
-Organization billing admins on a paid plan can configure auto-refill from **Settings > Billing**:
+Organization billing admins on a paid plan can configure auto-refill from the organization's **Billing & usage** page:
 
 1. Choose the balance threshold that should trigger a refill.
 2. Choose the dollar amount to purchase when the balance crosses that threshold.
@@ -52,7 +52,7 @@ Turn auto-refill off from the same control. Leaving a paid plan locks automatic-
 You can upgrade from two places:
 
 - Click **Upgrade** in the credit dropdown.
-- Or go to your organization settings, then the **Billing** tab.
+- Or open **Billing & usage** in your organization.
 
 From there:
 

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

@@ -13,7 +13,7 @@ Pages is still a pre-release Studio surface. It is visible in development and st
 
 ## Browsing Your Content
 
-1. Click the **Content tab** (the database icon) in the top navigation bar.
+1. Open **Content** (the database icon).
 2. Choose **Pages**, **Collections**, or **Singles** in the left sidebar. **Forms** and **Labels & Text** follow them in the same list.
 3. Hover over or focus the info icon beside any item for a short explanation.
 4. Pages shows the site's route tree. Collections and Singles show cards for the schemas in that group.

package/assets/skills/fimo-studio/references/command-palette.md

@@ -13,6 +13,7 @@ The palette includes the destinations you are allowed to use:
 - Agent runs, definitions, and individual agents
 - Site settings sections, individual schedules and webhooks, connections, and MCP servers
 - Asset folders
+- Chats, including archived ones, and **New chat** (use the **Chats** tab to search only chats)
 
 You can also open documentation, feedback, account actions, site history, invitations, and the Publish review flow. Use **Escape** to return from a searchable subpage to the main command list, then press it again to close the palette.
 

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

@@ -6,8 +6,7 @@ CLI, and site agents all resolve the same project-scoped connection state.
 ## See what is available
 
 1. Open the site.
-2. Open **More**, then **Settings**.
-3. Choose **Connections**.
+2. Open **Settings** → **Advanced settings** → **Connections**.
 
 The page has two groups:
 

package/assets/skills/fimo-studio/references/custom-domains.md

@@ -11,8 +11,8 @@ If you're driving Fimo from the terminal, the equivalent commands are `fimo doma
 
 ## Adding a Custom Domain
 
-1. Open **Settings** from the top navigation bar (gear icon), alongside Preview, Content, Assets, Agents, and Analytics.
-2. In the Settings menu on the left, select **Domains** (globe icon) — listed with General and SEO.
+1. Open **Settings**.
+2. Select **Domains** (globe icon).
 3. Click the **Add domain** button (+ icon) in the top-right of the panel. (When domain purchase is enabled, a **Buy domain** button with a shopping-cart icon sits next to it.)
 4. A drawer opens. Type or select a domain — you can enter a subdomain or an apex domain. Domains your organization already owns appear in an autocomplete dropdown, and Fimo checks availability live as you type. For an apex domain, a checkbox lets you also redirect it to the `www` subdomain (on by default). Confirm to add it.
 5. A DNS table appears showing the record(s) you need to add. For a **subdomain** it's a single CNAME record:

package/assets/skills/fimo-studio/references/media-library.md

@@ -1,6 +1,6 @@
 ## Uploading Files
 
-1. Click the **Assets tab** (image icon) in the top navigation.
+1. Open **Assets** (image icon).
 2. You see a grid view of your files with a folder sidebar on the left.
 3. Click the **Plus (+) dropdown** at the top. It offers three options:
    - **Upload File** -- select files from your computer.
@@ -58,7 +58,6 @@ There are several ways to share files with the AI or reference them in conversat
 - Click the **+** button in the chat and choose **Attach Assets** to browse your media library.
 - Choose **Upload from Computer** to add a new file directly from the chat.
 - Type **@** to reference a specific file inline.
-- **Drag a file** from the media library into the chat.
 - Ask the AI to use a specific image by name (for example, "Use the hero-banner image on the home page").
 
 ## Bulk Actions

package/assets/skills/fimo-studio/references/preview-and-responsive.md

@@ -1,8 +1,8 @@
 ## Using the Preview
 
-Click the **Preview** tab (the cursor/pointer icon) to see a live version of your site right inside the editor. You can also press **Alt+1** to jump to the preview tab.
+Open **Preview** (the cursor icon) or press **Alt+1** to see a live version of your site.
 
-- For Fimo-integrated sites, use the **route selector** dropdown at the top to navigate between different pages.
+- For Fimo-integrated sites, use the **route selector** dropdown at the top to navigate between different pages. The selected page is in the Studio address, so a reload or a shared link opens the same page and Branch.
 - Click the **refresh** button to reload the preview.
 - Click the **external link** icon to open your site in a new browser tab for a full-screen view.
 
@@ -10,7 +10,7 @@ The preview updates in real-time as you make changes, so you always see the late
 
 ## Responsive Testing
 
-Click the device-toolbar toggle (the monitor/smartphone icon) in the preview toolbar to open the device toolbar. This lets you see how your site looks on different screen sizes.
+On desktop, click the device-toolbar toggle (the monitor/smartphone icon) in the preview toolbar to open the device toolbar. This lets you see how your site looks on different screen sizes.
 
 ### Preset Devices
 
@@ -43,11 +43,6 @@ You may see different overlays depending on what is happening:
 
 ## Switching Workspaces
 
-The preview is one of several workspaces, and only one is shown at a time. Switch between them from the header navigation or with keyboard shortcuts:
-
-- **Alt+1** -- Preview
-- **Alt+2** -- Content (CMS)
-- **Alt+3** -- Assets
-- **Alt+5** -- Settings
+The preview is one of several workspaces, and only one is shown at a time. Switch from the header (or **More**), the bottom tabs on a phone, or the shortcuts in the Studio layout section of SKILL.md.
 
 When the Preview workspace is open, the visual editor can appear alongside it as a preview side panel.

package/assets/skills/fimo-studio/references/project-creation.md

@@ -1,16 +1,32 @@
 ## Create a Site
 
 1. Open **Sites** in Fimo Studio.
-2. Select **Create site**. If the button is unavailable, ask an organization admin for site creation permission.
-3. Enter a site name and select **Create**.
-4. Studio opens the new site's **Getting started** view.
+2. Select **Create site**. If the button is unavailable, ask an organization admin for site creation permission. When the organization is at its plan's site limit, Studio offers an upgrade instead.
+3. Enter the address of the website you already have. See [Start From a Website](#start-from-a-website).
 
-## Set Up the Site
+Someone who signs up without a website address lands on the same address page.
 
-The **For agents** tab is the default. Copy its prompt into your coding agent, or use one of the available agent shortcuts. The prompt identifies this as a newly created Fimo site, gives the agent the exact `fimo init` command, pins the selected CLI channel for every `fimo` command in the setup, and links to the coding-agent guide. Following that guide, the agent initializes the site and creates its first hosted preview with one plain preview deploy — unless you tell it not to deploy.
+To build with your own AI instead, select **Build with ChatGPT, Claude or a coding agent** below the address field. See [Build With Your Own AI](#build-with-your-own-ai).
+
+## Start From a Website
+
+1. Enter the website address. Fimo checks that it can read the site; if it cannot, it says why and nothing is created.
+2. Fimo creates the site, reads its homepage, then asks three questions in a short chat: what the business does, who its competitors are, and what sets it apart. The answers are saved as the site's knowledge.
+3. The report shows how ready the site is for search engines (SEO) and AI answers (GEO), with every check and how to fix it. Leaving and coming back resumes where you left off.
+4. Select **Clone & fix your homepage**. The site opens on its **Getting started** chat, where Fimo rebuilds the homepage with the report's problems fixed. Fimo covers the cost of the analysis, the questions and the rebuild; credits are not used.
+
+The report and the homepage copy Fimo read are deleted after 7 days.
+
+Once the homepage is rebuilt, a banner offers to bring over the other pages: copy a prompt into an AI, or book a call or write to the Fimo team. Website migration is in alpha, so review every result. Dismissing the banner hides it for good.
+
+## Build With Your Own AI
+
+The **Build with your own AI** dialog covers every starting point: existing code, a website to rebuild or redesign, or a new idea. Its prompt asks which one to start from.
+
+The **For agents** tab is the default. Copy its prompt into your coding agent, or open it in ChatGPT or Claude. The coding-agent prompt gives the agent the exact `fimo init` command, pins the selected CLI channel for every `fimo` command in the setup, and links to the coding-agent guide. Following that guide, the agent creates the site, builds it, and creates its first hosted preview with one plain preview deploy — unless you tell it not to deploy. In ChatGPT or Claude, the prompt uses the Fimo connector and its `fimo-site` skill instead of the CLI.
 
 Use **Manual setup** when you want to run the steps yourself. It provides the exact `fimo init` command, coding-agent shortcuts, and the final `fimo deploy` command.
 
-The first deploy completes onboarding and removes **Getting started** from the site. You can also select **Dismiss getting started** to hide it without deploying.
+Nothing is created until the AI creates the site; it then appears in Studio.
 
 Deploying creates a preview. It does not publish the site. Publishing is a separate action in Fimo Studio; see **Publish & Deploy** when the site is ready to go live.

package/assets/skills/fimo-studio/references/publish-and-deploy.md

@@ -6,7 +6,7 @@
 4. Once done, the panel shows a **Published** status, your live URL under a **Published site** heading, and a **Last published** date and time.
 5. Click the URL to open your live site in a new tab.
 
-> **Next step:** After publishing, consider inviting teammates to collaborate using the **Invite** button in the site header. You can grant them Full, Edit, Comment, or View access.
+> **Next step:** After publishing, consider inviting teammates to collaborate with **Invite**. You can grant Full access, Can edit, or Can view.
 
 ## Re-publishing After Changes
 
@@ -36,7 +36,7 @@ The header **Publish** button itself only shows the label "Publish" (or a spinne
 ## Key Concepts
 
 - **Saving vs. publishing**: Edits save automatically as you work (like a draft). Publishing sends those changes to your live site. Visitors only see published changes.
-- **SEO before publishing**: Go to Settings > SEO to set your page title, description, and share image before going live. After changing SEO settings, a yellow banner reminds you to publish to apply the changes.
+- **SEO before publishing**: Go to Settings > SEO to set your page title, description, and share image before going live. After changing SEO settings, a reminder asks you to publish to apply the changes.
 - **Custom domains**: If you are on a premium plan, set up a custom domain in Settings > Domains. Your domain works once your site is published.
 - **Unpublishing**: To take your site offline, go to Settings > General and click Unpublish. A confirmation dialog appears before proceeding.
 

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

@@ -4,9 +4,8 @@ Schedules run recurring site commands in one environment. Use the Studio surface
 
 ## Open schedules
 
-1. Open the site and choose **Settings**.
-2. Select **Schedules**.
-3. Choose the environment whose schedules you want to manage.
+1. Open **Settings** → **Advanced settings** → **Schedules**.
+2. Choose the environment whose schedules you want to manage.
 
 The list shows each schedule's name, cron, command, enabled state, and latest status. Usage and retention policy are shown for the selected environment.
 

package/assets/skills/fimo-studio/references/seo-settings.md

@@ -1,6 +1,6 @@
 ## Where to Find SEO Settings
 
-Open **Settings** (gear icon in the top toolbar) and select **SEO** from the settings menu on the left.
+Open **Settings** and select **SEO** in the settings menu.
 
 ## Setting Things Up
 
@@ -22,7 +22,7 @@ This is the image that shows up when someone shares your link on social media (F
 
 ## Saving and Publishing
 
-All SEO changes auto-save as you make them. However, a small amber reminder appears in the top-right corner: "Publish your website to apply your changes." Click Publish to push the changes to your live site.
+All SEO changes auto-save as you make them. A reminder above the fields asks you to publish. Click Publish to push the changes to your live site.
 
 Current templates include SEO wiring. For older Next.js, Astro or SvelteKit sites, ask the coding agent to update Fimo and connect these values to the app's existing SEO flow. Route-specific content must reach that flow too. Load the matching recipe: `fimo skills get fimo-code --ref frameworks/next`, `fimo skills get fimo-code --ref frameworks/astro`, or `fimo skills get fimo-code --ref frameworks/sveltekit`.
 

package/assets/skills/fimo-studio/references/sharing-and-collaboration.md

@@ -1,13 +1,12 @@
 ## Inviting People to Your Site
 
-1. Click the **Invite** button in the site header.
+1. Click **Invite** in the site header (on a phone, it is in the site menu).
 2. A sharing panel opens showing your current team. On desktop this appears as a popover; on mobile it opens as a drawer.
 3. Type the email address of the person you want to invite.
 4. Choose an access level for them:
    - **Full access** -- complete control over the site, including settings and member management.
    - **Can edit** -- can edit content and assets, and use the AI chat to change code. Cannot change site settings.
-   - **Can comment** -- can view the site and leave comments but cannot make edits.
-   - **Can view** -- can see the site but cannot make any changes or comments.
+   - **Can view** -- can see the site but cannot make changes.
 5. Click **Invite**.
 6. The invite appears in the member list marked **Pending invitation** until the person accepts it.
 

package/assets/skills/fimo-studio/references/visual-editing.md

@@ -16,7 +16,7 @@ Incomplete JSON drafts stay local. Leaving an empty JSON field saves `null` and
 
 ### References and Components
 
-Selecting a field rendered from a referenced entry edits that entry. For example, selecting an author's name opens the Author entry, not the Post relation that links to it. The header shows the relation path. Select the owning entry in that path to return to its complete form with the relation field focused; use that relation field to open, replace, or clear the linked entry.
+Selecting a field rendered from a referenced entry edits that entry. For example, selecting an author's name opens the Author entry, not the Post relation that links to it. Use the back arrow beside the entry title to return to its complete form with the relation field focused; use that relation field to open, replace, or clear the linked entry.
 
 Selecting a field inside a component focuses that nested field. Choose **All fields** to see it in the complete entry form without moving it out of schema order. The shared CMS form provides the existing add, duplicate, remove, and reorder controls for repeatable components and blocks.
 

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

@@ -8,12 +8,11 @@ Only site members with Full Access can see Webhooks in Settings or manage its de
 
 ## Create one
 
-1. Open the site and choose **Settings**.
-2. Select **Webhooks**.
-3. Choose **New webhook**.
-4. Name it, select one event, and enter the destination URL.
-5. Optionally narrow form, agent, media, or entry events with the filter shown for that event.
-6. Review the request and select **Save**.
+1. Open **Settings** → **Advanced settings** → **Webhooks**.
+2. Choose **New webhook**.
+3. Name it, select one event, and enter the destination URL.
+4. Optionally narrow form, agent, media, or entry events with the filter shown for that event.
+5. Review the request and select **Save**.
 
 The event groups are Entries, Forms, Publish, Agents, Analytics, Media, Domains, Labels, Locales, and Environments. Webhooks belong to the site, with up to 20 configurations. Choose the Main Branch, All Branches, Production, Preview, or one custom Environment. Main Branch is the default.
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-10-08T08:47:47.864Z",
+  "bundledAt": "2026-10-09T17:40:11.586Z",
   "cliVersion": "2.7.1",
   "external": [
     "oxc-parser",