fimo 2.10.1-staging.1 → 2.10.1-staging.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (43) hide show
  1. package/assets/skills/fimo-cli/SKILL.md +57 -139
  2. package/assets/skills/fimo-cli/SKILL.studio.md +42 -0
  3. package/assets/skills/fimo-cli/references/branches.md +43 -106
  4. package/assets/skills/fimo-cli/references/content/bulk.md +48 -0
  5. package/assets/skills/fimo-cli/references/content/entries.md +54 -0
  6. package/assets/skills/fimo-cli/references/content/localized.md +56 -0
  7. package/assets/skills/fimo-cli/references/content/schemas.md +29 -0
  8. package/assets/skills/fimo-cli/references/content/sql.md +57 -0
  9. package/assets/skills/fimo-cli/references/content.md +33 -272
  10. package/assets/skills/fimo-cli/references/deploy.md +35 -126
  11. package/assets/skills/fimo-cli/references/domains.md +38 -131
  12. package/assets/skills/fimo-cli/references/forms.md +1 -1
  13. package/assets/skills/fimo-cli/references/init.md +36 -170
  14. package/assets/skills/fimo-cli/references/locales.md +2 -2
  15. package/assets/skills/fimo-cli/references/projects.md +1 -1
  16. package/assets/skills/fimo-code/references/design.md +42 -126
  17. package/assets/skills/fimo-migration/SKILL.md +114 -408
  18. package/assets/skills/fimo-migration/references/content-delivery.md +67 -0
  19. package/assets/skills/fimo-migration/references/frameworks/nextjs.md +1 -1
  20. package/assets/skills/fimo-migration/references/qa/browser.md +41 -0
  21. package/assets/skills/fimo-migration/references/qa/guardrails.md +95 -0
  22. package/assets/skills/fimo-migration/references/qa/results.md +78 -0
  23. package/assets/skills/fimo-migration/references/qa.md +102 -383
  24. package/assets/skills/fimo-migration/references/questions-and-improvements.md +77 -168
  25. package/assets/skills/fimo-migration/references/setup.md +90 -0
  26. package/assets/skills/fimo-migration/references/workers/validator.md +2 -2
  27. package/assets/skills/fimo-migration/references/workers.md +1 -1
  28. package/assets/skills/fimo-migration/references/workflow.md +117 -171
  29. package/assets/skills/fimo-studio/SKILL.md +12 -11
  30. package/assets/skills/fimo-studio/references/ai-chat/agents.md +46 -0
  31. package/assets/skills/fimo-studio/references/ai-chat/default-agents.md +57 -0
  32. package/assets/skills/fimo-studio/references/ai-chat/routines.md +53 -0
  33. package/assets/skills/fimo-studio/references/ai-chat.md +39 -76
  34. package/assets/skills/fimo-studio/references/custom-domains.md +2 -2
  35. package/assets/skills/fimo-studio/references/publish-and-deploy.md +1 -1
  36. package/dist/cli/bundle.json +1 -1
  37. package/dist/cli/index.js +38 -17
  38. package/package.json +8 -8
  39. package/templates/astro/package.json +3 -3
  40. package/templates/nextjs/package.json +4 -4
  41. package/templates/react-router/package.json +5 -5
  42. package/templates/sveltekit/package.json +3 -3
  43. package/templates/vite/package.json +5 -5
@@ -1,98 +1,61 @@
1
- ## Where to Find It
1
+ # AI chat
2
2
 
3
- Open the **Chats** tab in the site header. On a phone, the Chat tab at the bottom opens the chat list first; select a chat to open it.
3
+ How people work with chat in Studio. For agents (plans, **New agent**, the default agents), read `ai-chat/agents`; for what each default routine does, `ai-chat/default-agents`; for routines (triggers, runs, reports, agent-hours), `ai-chat/routines`.
4
4
 
5
- ## Working in Several Chats
5
+ Chat can write and edit code, create pages, manage CMS content, generate images, install packages, search the web and fix bugs.
6
6
 
7
- 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; one orange dot marks unread activity, a pending question, or both. Hover over the dot for the reason. Opening the chat clears unread activity for you; the dot stays while a question still needs your answer. 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. To rename a chat for everyone, double-click its name above the open chat, or right-click its row and select **Rename**; Enter saves and Escape keeps the old name. 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.
7
+ ## Where to find it
8
8
 
9
- ## Agents
9
+ Open **Chats** in the site header. On a phone, the **Chat** tab opens the chat list first; select a chat to open it.
10
10
 
11
- The plan decides the agents (FIMO-2856): Free has the SEO and GEO default agents, each running only its weekly checkup (**Weekly SEO checkup**, **Weekly AI check**), and its agent settings list the routines Starter adds with **See plans**; Starter has every default agent with its detailed routines, and a change wakes each routine at most once a day (the changes made meanwhile wait and the next run, a day after the last one started, checks them together; the routine's next run shows when, and **Run now** and schedules never wait); Pro runs them right after each change and adds live agents of one's own (**New agent**: any plan can set one up, only Pro makes it live). In the **+** menu, what the plan does not include shows **Upgrade** and opens the plans. Default agents are Fimo's: their routines follow Fimo's instructions, only switch off and on or get deleted (a deleted one stays deleted), and nothing is added to them (`routine_is_default`); routines of one's own live in a custom agent, on Pro (`routine_needs_pro` below Pro). A default agent's name, summary, instructions and portrait cannot be changed on any plan, and a live custom agent's change only on Pro: below Pro its settings are read-only, say its routines are paused and offer **See plans**, and it can still be deleted. A plan change changes which agents open and which routines run; agents, routines and past runs stay. Fimo support can give an organization Pro's agents on any plan. A routine Fimo retires from a default agent stops running and leaves the list.
11
+ ## Several chats
12
12
 
13
- An agent is a chat with a job: a name, a one-line summary for people, and instructions that Fimo reads at the start of every reply in that chat and every run of its routines (FIMO-3079). Live agents are shared like any chat, with an **Agent** tag after the name. The **+** above the chat list is a menu: **New chat** (blank), **New agent** (opens the new agent's chat at once: the agent asks what it should do with three one-click answers, then drafts its name, summary, instructions and routines on one card; **Create agent** sends the person's agreement and the agent goes live, the team sees it and its routines start; until then only its creator sees it, as **New agent** with **Setting up…**, its routines do not run, and its chat changes nothing on the site (it reads the site, its data and the web; no CLI, files, work sessions or publish), and it goes live only after the person saw its latest draft; a routine time the person did not name keeps its hour and Fimo picks the minute; below Pro, **Create agent** opens the plans), and under **Agents** Fimo's default agents (**SEO**, **GEO**, **Content**, **Quality**, **Compliance**); a new site starts with SEO and GEO listed, their routines active from the start; Content, Quality and Compliance, and every default on an older site, are created the first time someone selects them, routines active, the same chat every time after. In an agent, the header shows the name alone and the message box reads **Message <name>**. A default agent's empty state greets in its own words and offers its own starter requests; its description stays in its settings. A starter is sent as shown, by anyone who can send messages. Asked to, an agent changes its own instructions with its `agent` tool; the chat shows **Updated instructions** with **View change** (before and after). The agent's settings page has **Summary** and **Instructions** fields, shared with everyone (empty means none), and an **Instruction history** where **Restore previous** puts back the text a change replaced. In text, an agent links another as `[Name](agent://id)`, shown as a chip that opens it. The filter icon's **Kind** option shows only chats or only agents; search finds an agent by its name.
13
+ - A site has many chats, shared by everyone on the site. The list shows **Agents** above and **Chats** below, the most recently active first. A row shows what the chat does while it works, then the start of its last message. The **Chats** tab shows how many chats have new activity.
14
+ - One orange dot marks unread activity, a question that waits for you, or both. Hover over it for the reason. Opening the chat clears unread activity for you only; the dot stays while a question still waits for an answer.
15
+ - **+** then **New chat** starts a blank chat. It joins the list, for everyone, when its first message is sent, and takes its name from that message. An empty chat offers starter requests.
16
+ - The search icon finds a chat by name or last message. The filter icon shows only **Working** or **Done** chats, or with **Kind** only chats or only agents. The list settings change the order and show read, unread or archived chats.
17
+ - For you only (the buttons above the open chat, or right-click a row): **Mark as unread**, **Pin**, **Archive** (turn on **Show archived** to see it again), **Mute**.
18
+ - To rename a chat for everyone, double-click its name above the open chat, or right-click its row and select **Rename**. Enter saves; Escape keeps the old name.
19
+ - The settings icon above the open chat changes its portrait (shape, eyes, mouth, color), renames it, holds the same pin, mute and archive switches, and deletes it. **Deleting stops a running reply and removes the chat for everyone.**
20
+ - Each chat has its own messages and context. When you refer to an earlier discussion, chat searches this site's chats and answers from the messages it found.
21
+ - The open chat is in the page address (`/chats?chat=<id>`), so a link or a reload opens the same chat.
14
22
 
15
- The **SEO** default runs six routines backed by Studio's built-in `fimo-seo` skill, which checks the site as a browser renders it and fixes at the source: **Technical SEO** (status, redirects, canonicals, sitemap, robots.txt, language, main heading, changes since its last run: pages moved without a redirect, and, with Search Console, old addresses Google still shows that the site no longer serves), **Broken links**, **Meta tags** (titles, descriptions, Open Graph, the site's title ending, length in characters and pixels), **Image SEO** (alt text, file names, images over 200 KB: one in the media library or the site's own files is rendered through Fimo's resizing on its own, a file of the site uploaded first), **Hreflang** (only on a site in more than one language) and **Internal linking** (orphan and deep pages, articles with no link up to a hub or product page or more than eight links). Each default routine wakes on the changes on main that can matter to it, before a publish (CMS edits, code changes, images, languages, forms; the first publish and a new domain for Technical SEO and Cookie consent): a small model reads each change first, so a quiet site runs nothing, and the run checks what changed (the whole site on its first run). A schedule covers what no single change shows: every Monday, Technical SEO, Meta tags and Internal linking read every page of main's hosted preview (pages out of the sitemap, shared titles and title shape, orphan and deep pages); what changes without anyone touching the site also keeps one: Broken links checks outbound links on the 1st of every month, Content refresh runs on the 2nd, Content lifecycle every three months, Privacy and legal pages once a year. A page it changed is left alone for 8 weeks, the time Google takes to show the effect. A fix with one right answer from the page's own words is made without a message (a link only once the new target is checked to be the same content in the same language; a link on words the text already uses to name another page; a 301 from a page's old address once the same page is live at a new one); a change to what visitors read, which page wins a search, whether a page exists, a redirect with more than one possible target, a price or a legal page is asked as a decision; page removals and the robots policy are never changed on its own. A change a person asks for in a chat is made. What a check could not tell (a timeout, a 5xx, a page past the crawl limit) is never acted on: the run retries once, then says the check was incomplete.
23
+ ## Send a message
16
24
 
17
- The **GEO** default runs three routines backed by Studio's built-in `fimo-geo` skill, which shares `fimo-seo`'s crawl and its rule for what a run may change alone: **AI readiness** (llms.txt, the text each page serves before JavaScript, landmarks and heading levels) and **Structured data** (valid JSON-LD; Organization and WebSite, Article, BreadcrumbList; Product and FAQ where they fit) and **AI citation optimization** (a direct answer under each content page's H1, question headings on long pages). On its own it writes a missing llms.txt and keeps its links in step, adds Organization, WebSite, Article and BreadcrumbList from fields the site already has (never an invented logo, address, author or rating), and fixes landmarks and heading levels without changing words; an opening answer, new headings, FAQ or Product data, and how pages are rendered are asked as decisions; who robots.txt lets crawl, AI crawlers included, prices and claims are never changed, nor reported: asked whether an assistant can read the site, it checks and names the crawlers robots.txt keeps out. Where AI assistants cite the site needs a visibility source; until one is connected there is no routine for it.
25
+ 1. Type in the message box at the bottom; its placeholder follows the workspace you are in. Be specific: "Add a hero with a dark green background and the heading Fresh beans weekly" works better than "make it look nice".
26
+ 2. Press **Enter** or select the send button.
27
+ 3. The reply streams. Progress lines name each task chat works on, and the preview updates.
18
28
 
19
- The **Content** default runs three routines backed by Studio's built-in `fimo-content` skill, on the same crawl and rule: **Content refresh** (past years written as the present, events and offers whose date passed, "coming soon" text, product names the team retired, pages losing visitors in Fimo analytics), **Content lifecycle** (thin pages, pages that repeat another, pages nothing links to that are also thin or out of date) and **Translation** (CMS entries missing in a locale, or whose source changed after the translation; on a site with one locale it stops at once). On its own it translates missing and outdated entries in the site's tone, keeping slugs, dates, media and names, and renders a copyright year typed in the code from the date; any other sentence a visitor reads is asked as a decision quoting the exact words; merging, redirecting or retiring a page is only proposed; a price or a legal page is changed or translated only once a person agreed. Writing from briefs and watching competitors need data sources; until they are connected there is no routine for them.
29
+ While a reply runs, the send button becomes **Stop** (a square). Select it when the reply goes the wrong way. Messages sent during a reply wait at the end of the chat as **Queued** and run in order, one reply each.
20
30
 
21
- The **Quality** default runs two routines backed by Studio's built-in `fimo-quality` skill, whose crawl also measures accessibility in each page and opens one or two pages of each template again 390 px wide: **Accessibility** (WCAG AA contrast, heading levels, links, buttons and fields without a name, images used as links with no name, positive tabindex, invisible focus, the page language) and **Mobile optimization** (a missing viewport or one that blocks zoom, sideways scrolling, images, tables and forms wider than the screen, tap targets under 24 × 24 px, text mostly under 12 px). On its own it names a control or labels a field from words the page shows, fixes heading levels, tabindex and a removed focus outline, lets visitors zoom again and keeps media inside the screen; a colour, a size or a layout change is asked as a decision. Image alt text stays with the SEO agent; brand compliance needs brand guidelines, so there is no routine for it yet.
31
+ ## Answer a question
22
32
 
23
- The **Compliance** default runs three routines backed by Studio's built-in `fimo-compliance` skill, on the same crawl, which can also open a sample of pages with no consent given and record the cookies, third-party requests, consent banner and form fields a first visit gets: **Brand compliance** (words, terms, claims and voice of what changed, against the brand rules in the site knowledge, `AGENTS.md` and the agent's memory; it runs on Claude Haiku 5.5), **Cookie consent** (trackers and third-party cookies before a choice, a missing banner, a banner with no way to refuse) and **Privacy and legal pages** (a privacy page that exists, names the services loaded and the kinds of field the forms collect, and was updated in the last two years). On its own it changes only a term the brand rules replace; every other sentence, the consent setup and every legal page are proposed as decisions, with placeholders for legal details, and it never states that a site is compliant.
33
+ A reply can hold choices, cards, tables, images and actions. Optional suggestions do not stop the conversation.
24
34
 
25
- ### Routines
35
+ When chat needs an answer to continue, it opens a form under the message that asks, and waits. Move with **Previous**, **Next** and **Submit**; a step with choices has an optional note field.
26
36
 
27
- A routine is saved instructions an agent runs in a thread of its own, by hand, on a schedule, or when something happens in the project, so each run sees its earlier runs and the agent's chat never fills with its work. The agent creates, changes, runs and deletes its routines from its chat with its `routines` tool: a person asks in the chat ("check the prices every Monday", "run after each publish"), and Studio only shows routines. A trigger is set in words; Fimo checks them and either says when the routine runs or why it cannot follow them and what it can do instead; for what Fimo cannot see as an event (traffic, rankings, errors) the agent offers a schedule whose run checks it and stops when there is nothing to do. Fimo follows publishes of the site (or only its first publish) and content changes on the main branch by content type, action, locale, changed fields, the entry's current values ("price over 100", "status changes to archived") or a yes/no question about what the content says ("mentions Contentful or Sanity"; for "a competitor" it uses the names given or those in the site knowledge, and asks for them otherwise; a run started on an uncertain answer says so), media files uploaded or changed (by name or file type), the site's code changing through a deploy or a merge (by file path glob, or a yes/no question about the changed files such as "a page was added"), another routine of the same agent finishing (optionally with a yes/no question about its report; never its own end), a visitor submitting a form (optionally with a yes/no question about the answers), a form or content type changing, a branch merged into main, a locale added, removed or made the default, a publish of the site failing, a domain added or removed, and the prices on a page of another web site changing ("tell me when https://example.com/pricing changes its prices": checked daily, a change must hold on three reads before the routine runs, the run lists each plan with its old and new price, the routine page shows the watch as **OK**, **Needs repair**, **Blocked** or **Unstable** with its last check, at most 10 watched pages a project); comparing a field's old and new values is not supported; what a routine changes, publishes or reports can start the agent's other routines, in chains of any length, each routine at most once per change that started the chain (across every routine that change leads to, so routines never loop or multiply; a person's new change, a run by hand or on a schedule starts a new chain); events that come in while a run is busy wait, then run together in one next run, which the Runs list shows as one run with its event count (a very large burst, such as a bulk import, runs in several runs, in order); the agent can also make a routine's event runs wait until the changes stop for a set number of minutes (at most 2 hours from the first), then read them all in one run (a yes/no question is then answered once for all the waiting changes, each entry once in its latest version; a waiting change it says no to leaves the queue, and when it says no to all of them no run starts); the default routines that read what changed (Technical SEO, Meta tags, Image SEO, Internal linking, AI readiness, Structured data, AI citation optimization, Content lifecycle, Translation, Accessibility, Mobile optimization, Brand compliance) wait 10 minutes after the last change, and those that guard the live site (Broken links, Hreflang, Cookie consent, Privacy and legal pages) run at once. The agent's settings list its **Routines** as cards (name, when it runs such as its event trigger's title, **Every Monday at 08:00** or **By hand**, next run, an **Active** switch); the default agents come with theirs (a new project's defaults wake on changes from five minutes after it is created, so its first push and seed start no run). A routine's page is read-only: **What it does** (one or two plain sentences the agent writes with the routine, Fimo's for a default routine), with **Instructions** folded under it (the task, run on every trigger; a routine created before descriptions shows only its **Instructions**), **Model** (the model its runs use: Opus 5.5 by default, while most default routines run on Claude Haiku 5.5 or Claude Sonnet 5.5; the agent sets another when asked), **Triggers** (**By hand** with **Run now**, which starts a run right away; **Schedule** and the event trigger, given a short title by Fimo from the words it was set with and showing those words, shown when set), 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**, **On event**, 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), and the **Active** switch in the header (pauses the schedule and the trigger, not **Run now**). 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 `routines` tool and the routine runs again with it. Only the agent answers a routine: its page has no answer box. 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. Routine runs use the plan's agent-hours, from each run's start to its end (Studio chats do not); Billing shows the hours used this period, and each run shows its duration and credits. Once the included hours are used, nothing runs (no schedule, event or Run now, which the routines tool reports to the agent); Studio shows **Routines paused** under the chat list and in the agent's settings with the reset date and the button that resumes them sooner (**Upgrade**), and the routine's page says until when. No run lasts longer than 2 hours.
37
+ - **Submit** sends only the form. Text in the message box stays unsent.
38
+ - Sending from the message box sends your message with the choices already made. With no choices, it is an ordinary message and the question stays open.
39
+ - If you send a message that does not answer it, the question folds to one line with an orange **?** where it was asked. Select it to open it and answer, at any time. The answer is sent as a new message at the end of the chat, and an answered question shows a gray check.
40
+ - **Minimize** folds the form to one line and keeps your answers; select the line to open it again.
41
+ - When a routine asks again before anyone answered, its earlier question stays unanswered, folded where it was asked.
28
42
 
29
- ## Sending a Message
43
+ ## Attach context
30
44
 
31
- 1. Click the text area at the bottom of the chat panel. The placeholder text changes based on your current workspace context.
32
- 2. Type your request. Be as specific as you can (for example, "Add a hero section with a gradient background and a centered heading that says Welcome" works better than "Make it look nice").
33
- 3. Press **Enter** or click the **send button**.
34
- 4. The AI responds in a stream. You see tool status badges appear as it works, and the preview updates automatically.
45
+ - **+** in the message box: **Attach assets** (media library), **Attach entries** (CMS content), **Upload from computer**. For GLB, self-contained glTF, FBX, OBJ, STL and PLY models, Fimo renders four views and saves a description, so every chat model can understand the model. ZIP archives up to 20 MiB are supported; chat can open them under `/tmp` in its sandbox, and the original stays attached to the conversation.
46
+ - Type **@** to refer to files, pages or content.
35
47
 
36
- ## Responding to Choices and Forms
48
+ ## Edit, regenerate, stop
37
49
 
38
- The AI can place choices, cards, tables, images, and contextual actions directly in its reply. Optional suggestions do not interrupt the conversation.
50
+ Hover over a message. Your messages have **Copy** and **Edit** (change and resend; chat replies again); a form answer has no **Edit**. AI messages have **Copy** and **More**; the last AI message also has **Regenerate** (try again with the same request) when no reply is running.
39
51
 
40
- When the AI needs an answer before it can continue, it opens a form in the conversation, under the message that asks, and waits for your response. The form goes one step at a time with **Previous**, **Next**, and **Submit**, and a step with choices has an optional note field under them. If you send a message that does not answer it, the question folds to one line with an orange **?** where it was asked. Select it to open it there and answer it at any time; the answer is sent as a new message at the end of the chat. An answered question shows a gray check next to its title. When a routine asks again before anyone answered, its earlier question stays unanswered, folded where it was asked. Select **Minimize** to fold the form to one line without losing your answers, then select that line to reopen it. **Submit** sends only the completed form and leaves anything typed in the message box unsent. Sending from the message box includes any selections already made in the form with your message; with no selections, it is an ordinary reply and the question stays open.
52
+ ## Proposals, reviews and merges
41
53
 
42
- ## Attaching Context
43
-
44
- Give the AI more to work with:
45
-
46
- - **+ button**: Opens a dropdown with options:
47
- - **Attach Assets** -- browse your media library and attach files.
48
- - **Attach Entries** -- attach CMS content for the AI to reference.
49
- - **Upload from Computer** -- upload a file directly. For GLB, self-contained glTF, FBX, OBJ, STL, and PLY models, Fimo renders four views and saves a description so every chat model can understand the attachment. ZIP archives are supported up to 20 MiB; the AI can download and inspect them under `/tmp` in its sandbox while the original stays attached to the conversation.
50
- - **@ mentions**: Type **@** in the chat to reference specific files, pages, or content inline.
51
-
52
- ## Editing and Regenerating
53
-
54
- Hover over a message to see its action icons. The icons differ by who sent the message:
55
-
56
- - On **your own messages**: a **Copy icon** and an **Edit icon**. Editing lets you change your message and resend it; the AI generates a new response based on your updated request.
57
- - On **AI messages**: a **Copy icon**, a **Regenerate icon** (ask the AI to try a different approach without changing your original message), and a **More menu** for additional actions.
58
-
59
- To halt the AI mid-generation, use the **Stop button** in the input bar — while the AI is generating, the send button turns into a Stop (square) button. Click it to stop if the response is going in the wrong direction.
60
-
61
- ## Understanding Tool Badges
62
-
63
- While the AI works, you see small badges in the chat showing what it is doing. Each badge displays a tool name and its current status. Examples include reading files, writing code, searching your site, or generating images. These badges help you follow along without needing to understand the technical details.
64
-
65
- ## Reviewing Proposals
66
-
67
- Ask the AI to keep alternatives as named proposals. Open the Branch picker and choose one from **Proposals** to preview its work. Each proposal has its own changes. The picker follows visibility: internal work stays hidden even when saved, durable, or given more time. Extending retention does not show the work.
68
-
69
- A review request saves the selected session's current work and makes that same session visible and durable. Follow its review card to the proposal, or its Preview and Changes links from chat, Slack, or an agent report. These links open the current Branch in Studio and require site access. A review request refers to saved work: if that work changes, request a new review before merging. Exploring or merging proposal B keeps A, C, and D available unless you ask to discard them. Merging does not publish the site.
70
-
71
- Delete a proposal from the Branch picker when you no longer need it. Pull is unavailable for proposals; ask the AI to update the proposal instead. New Branch defaults to the proposal's upstream. Merge the proposal first if you want to create a Branch from its changes.
72
-
73
- ## Reviewing Changes That Could Not Merge
74
-
75
- Chat changes are prepared separately and then applied to the environment you are viewing. Most changes merge automatically.
76
-
77
- If the site changed in the same place while the AI was working, the response shows a **Review changes** card and an attention banner above the chat input.
78
-
79
- Choose **Auto fix** or keep chatting to let Fimo continue in the retained proposal, resolve the conflict, and retry the merge. Choose **Review manually** to inspect and resolve the proposal yourself. Discarding leaves the current environment unchanged and permanently removes the proposal.
80
-
81
- ## Tips for Better Results
82
-
83
- - **Be specific**: Mention colors, layout, text content, and spacing when you can.
84
- - **Reference existing elements**: Say "Change the navbar background" instead of "Change the top thing."
85
- - **Use visual details**: Describe what you want to see, not just what you want it to do.
86
- - **The AI can do a lot**: Write and edit code, create new pages, manage CMS content, generate images, install packages, search the web, and fix bugs.
54
+ - Ask chat to keep alternatives as named proposals. Open the Branch picker and choose one under **Proposals** to preview it; each has its own changes. Internal work stays hidden there, even when saved or kept longer. Exploring or merging one keeps the others unless you ask to discard them. Delete a proposal from the Branch picker. Pull is not available for a proposal: ask chat to update it. **New Branch** starts from the proposal's upstream; merge the proposal first to branch from its changes.
55
+ - A review request saves the session's current work and makes that same session visible and durable. Work waiting for review shows in a strip above the message box (**View changes**, **Open preview**), and the conversation keeps a line with **View changes** where it was saved. Opening a review approves nothing. The Preview and Changes links, also in Slack or an agent report, open the Branch in Studio and need site access. If the work changes, request a new review before merging.
56
+ - Chat prepares changes separately and merges them into the environment you view; most merge automatically. If the site changed in the same place, a banner above the message box (**Your last changes need attention**) offers **Auto fix** (chat continues in the retained proposal, resolves the conflict and retries the merge; keep chatting has the same effect) and **Review manually**. Discarding leaves the environment unchanged and removes the proposal for good.
57
+ - **Merging does not publish the site.**
87
58
 
88
59
  ## Credits
89
60
 
90
- The AI runs on credits. You can see your balance by clicking the **coin icon** near the send button.
91
-
92
- Clicking it opens a breakdown showing:
93
-
94
- - **Monthly credits** included with your plan.
95
- - **Purchased credits** you bought separately.
96
- - **Earned credits** from referrals or promotions.
97
-
98
- You get a warning when credits are running low. To keep going, upgrade your plan or buy more credits from the billing page.
61
+ Chat uses AI credits. For people who can view billing, the coin icon near the send button shows the balance; select it for **Monthly credits**, **Purchased credits**, **Earned credits** (referrals and promotions) and, when present, **Daily free credits**. A warning shows when credits run low. To continue, upgrade the plan or buy credits on the billing page (`billing-and-credits`).
@@ -1,10 +1,10 @@
1
1
  ## Also available via CLI
2
2
 
3
- If you're driving Fimo from the terminal, the equivalent commands are `fimo domains add`, `fimo domains refresh`, and `fimo domains remove`. The default URL (the `<slug>.fimo.site` subdomain) is managed with `fimo domains rename-default` and `fimo domains suggest-default` — both free, no Premium needed. See the `fimo-cli` skill's `references/domains.md`. Full docs: https://fimo.ai/docs/deploy/custom-domains.
3
+ If you're driving Fimo from the terminal, the equivalent commands are `fimo domains add`, `fimo domains refresh`, and `fimo domains remove`. The default URL (the `<slug>.fimo.site` subdomain) is managed with `fimo domains rename-default` and `fimo domains suggest-default` — both free on every plan. See the `fimo-cli` skill's `references/domains.md`. Full docs: https://fimo.ai/docs/deploy/custom-domains.
4
4
 
5
5
  ## Before You Start
6
6
 
7
- - You need a **premium plan**. Without it, the Domains option shows an "Upgrade" label.
7
+ - You need the **Starter plan or higher**. Without it, the Domains option shows an "Upgrade" label.
8
8
  - Your site must be **published at least once**. An alert appears if it has not been published yet.
9
9
  - You need access to your **domain registrar** (GoDaddy, Namecheap, Cloudflare, etc.).
10
10
  - Both **subdomains** (e.g., `blog.example.com`) and **apex/root domains** (e.g., `example.com`) are supported. A subdomain uses a single CNAME record; an apex domain uses two A records, with an optional automatic redirect to its `www` subdomain. The redirect direction can be reversed later without changing DNS.
@@ -37,7 +37,7 @@ The header **Publish** button itself only shows the label "Publish" (or a spinne
37
37
 
38
38
  - **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.
39
39
  - **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.
40
- - **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.
40
+ - **Custom domains**: On the Starter plan or higher, set up a custom domain in Settings > Domains. Your domain works once your site is published.
41
41
  - **Unpublishing**: To take your site offline, go to Settings > General and click Unpublish. A confirmation dialog appears before proceeding.
42
42
 
43
43
  ## Troubleshooting
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "bundled": true,
3
3
  "bundler": "esbuild",
4
- "bundledAt": "2026-10-28T12:48:54.828Z",
4
+ "bundledAt": "2026-10-28T19:00:54.826Z",
5
5
  "cliVersion": "2.10.0",
6
6
  "external": [
7
7
  "oxc-parser",