Send a request
1
Describe the outcome
State what should change and any constraints the result must follow. Refer to the page, content, or file by name
when you can.
2
Add context
Attach available site assets or content when the request depends on them. You can also use
@ to reference
supported site context.3
Review and continue
Read the response and inspect the site changes. Send another message to refine the result.
Worked for 18s when the turn reported how long it
took, and Work details when it did not. Select it to review the thoughts and
tool activity for that turn, in the order they happened. The reported duration
stays the same when you reload the conversation.
You can stop a running turn from the chat input. In a long conversation, Fimo may compact earlier context so the conversation can continue. The same model that works on your request writes a summary of the earlier part, and your latest request and recent work stay as they are. If it cannot write a usable summary, Fimo removes the oldest context instead. Your visible chat history remains available.
Project memory
Chat keeps notes that every chat of the project can use. When you give a rule or preference that should last, such as “page titles never use emoji”, chat saves it, and later chats follow it without being told again. To change or remove a note, tell chat what is no longer true. A note saved in one chat applies to your other chats from their next message. Memory belongs to the project, not to a branch, so a note does not wait for a merge or publish. Chat does not save passwords, keys, or other secrets. Agents and their routines keep notes of their own as well. An agent’s chat and all of its routines share the agent’s notes, so a routine knows what another one changed, for example a page title it should leave alone for a few weeks. Each routine also keeps notes between its runs, such as the last ranking it saw, so it can compare against them even after a long run history was summarized. A routine that compares the site with its last run, such as Technical SEO, also keeps the file its script wrote, for example the list of pages it saw, as a data file of up to 1 MB in its own notes. Chat never reads that file; only the routine’s script does, and search skips it. Anything another chat would need still goes to the project’s memory. To make a routine remember something between runs, tell the agent, and it writes what to keep into the routine’s instructions. When a routine is deleted, the agent sees its notes first and keeps what still matters; deleting an agent deletes its notes. Memory is separate from site knowledge, which your team writes. Chat changes site knowledge only when you ask. When you tell chat something that contradicts it, chat saves the change to memory and tells you the site knowledge still says otherwise. If your connection drops while a reply is streaming, Studio shows “Reconnecting 1/5” and reattaches to the same reply for about a minute. Nothing is sent twice: the reply keeps running on Fimo while you are reconnecting. If Fimo updates while a reply is running, the reply pauses at a safe point and continues automatically once the update is live. The conversation keeps one request and one reply, and any changes made before the update carry over. If Fimo cannot continue the reply, or your connection does not come back, Studio shows a Retry action so you can run the request again. If a workspace problem stops a reply, Studio shows “Something went wrong.” Select Retry to try the request again. If the AI model sends nothing for 5 minutes, chat stops waiting for it and shows that the model returned an error. Messages that wait for their turn continue. Select Retry to run the request again.Work in several chats
Chat has its own Chats tab in the site header. A site can have several chats, one per topic, and everyone on the site shares them. The tab shows how many chats have new activity for you. A Fimo loader appears while chat history loads. The conversation opens at its newest messages. Scroll up to read older messages; a small Loading older messages… note appears at the top while they load, keeping your place in the conversation. The list on the left shows every chat, the most recently active first, with its status and the start of its last message:- Working and a spinner show that a chat is still working on a reply.
- Done shows that the last reply has finished.
- One orange dot shows that a chat has unread activity, needs your input, or both. Hover over it to see why. Opening the chat clears unread activity for you only. A chat needs your input while the agent’s question is its last message: answer the question, or write anything else, and the dot goes.
- Mark as unread keeps the dot until you open the chat again.
- Pin keeps a chat at the top of the list.
- Archive hides a chat from the list. Turn on Show archived in the list settings to see it again.
- Mute stops a chat from showing as unread.
Give an agent a job
What agents you get depends on your plan:
On Free, each checkup is one pass over the most important problems, so the
plan’s agent-hours last the month, and an agent’s settings name the routines
Starter adds, with See plans. On Starter, a routine that ran on a change
runs again on the next change a day after that run started at the earliest:
the changes made meanwhile wait, and the next run checks them together. The
routine’s next run shows when that is, and the agent’s settings say so, with
See plans. Run now and schedules never wait. In the + menu, an
agent your plan does not include shows Upgrade, and opens the plans.
On Starter and Pro, a routine that reads the pages that changed (such as
Meta tags, Internal linking or Translation) starts 10 minutes after
the last change, so a page saved many times while you edit it is checked once.
Fimo also decides only then whether the changes matter to the routine: a
waiting change that does not leaves the queue, and if none does, no run starts.
Routines that guard the live site (Technical SEO, Broken links,
Cookie consent) start right away.
Moving between plans changes which agents open and which routines run;
agents, routines and past runs stay.
An agent is a chat with a job. It has a name and a description that Fimo reads
at the start of every reply in that chat, so the whole conversation stays on
that job. Everyone on the site shares an agent, like any chat, and it joins the
list as soon as it is created, with an Agent tag after its name.
Select + above the chat list to open its menu:
- New chat starts a blank conversation.
- New agent (Pro) asks for a name and a description, then opens the empty agent at once.
- Under Agents, Fimo offers its default agents: SEO, GEO, Content, Quality and Compliance. A new site starts with SEO and GEO in its list, their routines already running; selecting one opens it. Content, Quality and Compliance join a site only when you select them, since their routines use credits, and so does any default on an older site: the first selection creates the agent with its description ready and its routines running. It opens at once, and its row in the list reads Setting up… until its first check is scheduled. A site has one chat per default agent, so selecting it again opens the same chat.
The SEO agent
The SEO agent keeps every page of your site findable on Google. It checks your site the way a browser shows it, on a working copy, and fixes each problem where it comes from: a page’s title or description, a CMS field, the layout, the sitemap or robots.txt. It comes with six routines. Each one wakes when a change on your site’s main branch can matter to it, before you publish: Fimo first reads the change with a small model and wakes only the routines it concerns, so a site where nothing changes costs nothing. Its run then checks what changed, and the whole site on its first run. Once a week, Technical SEO, Meta tags and Internal linking also check every page of your site’s main branch, for what no single change shows, such as two pages with the same title or a page nothing links to.
A fix with one right answer, written from the page’s own words, the agent makes
on its own and does not announce: a missing description or alt text, a link
whose new address it has opened and checked, a canonical that leaks a preview
address, a link on words your text already uses to name another page, and a
redirect from a page’s old address once the same page is live at a new one. It
asks you before changing what visitors read, which page wins a search, whether a
page exists, or a redirect with more than one possible target, such as what to
do about a page that disappeared. Prices and legal pages are yours: it proposes
a change and waits for you, and it never removes a page or changes your robots
policy on its own. When you ask it in a chat, it makes those changes too. When a page does not answer or a check
cannot finish, it tries once more and otherwise says the check was incomplete,
instead of guessing.
Images over 200 KB that live in your media library or in your site’s own files, the agent fixes on its own: it uploads a file of the site to the media library, then renders the image with the width it is shown at, so Fimo serves a smaller, modern copy. An image on another site’s host it cannot resize, so it proposes a smaller export.
The GEO agent
The GEO agent keeps your pages easy for AI assistants such as ChatGPT, Claude and Perplexity to read, trust and quote. It checks your site the same way the SEO agent does, on a working copy as a browser shows it, and also reads the text each page sends before JavaScript runs, which is all most AI crawlers see. It comes with three routines:
On its own, and without announcing it, the agent writes a missing llms.txt and
keeps it in step with your pages, adds Organization, WebSite and Article
structured data from what your pages and CMS entries already say,
and fixes page landmarks and heading levels without changing a word. It never
invents a fact: no logo, address, author or rating your site does not show. It
asks you before changing what visitors read: an opening answer or new
headings, FAQ or product structured data, or how your pages are rendered. It
never changes who may crawl your site in robots.txt, AI crawlers included, nor
a price or a claim; ask it and it tells you which crawlers are kept out.
Where AI assistants cite your site needs a visibility source; once one is
connected, the agent tracks that too.
The Content agent
The Content agent keeps what your site says true, and your CMS entries complete in every language your site serves. It reads your pages the same way the SEO agent does, on a working copy as a browser shows them, and works in the CMS for translations. It comes with three routines:
On its own, and without announcing it, the agent translates missing and
outdated CMS entries in your site’s tone, keeping names, addresses, dates and
images as they are, and keeps a copyright year in your code current. Its
translations wait on your working copy like any other change, until you
publish. It asks you before changing any other sentence a visitor reads, and
quotes the exact words it would use. It never removes a page, merges two or
adds a redirect without you: it proposes which page to merge, redirect or
retire, and where; once you choose, it makes the change and the redirect. It
asks before changing or translating a price or a legal page. On a site in one language, Translation does nothing.
Writing new pages from briefs and watching competitors need data sources;
once they are connected, the agent does those too.
The Quality agent
The Quality agent keeps every page usable by every visitor: with a keyboard, with a screen reader, and on a phone. It checks your site the way a browser shows it, measures each page, and opens a sample of pages again at a phone’s width. It comes with two routines:
On its own, the agent names a link, button or field from the words your page
already shows for it, fixes heading levels and tab order, lets visitors zoom
again, and keeps images and tables inside a phone’s screen. It asks you before
changing a colour, a size or a layout, since how your site looks is yours, and
proposes the colour or size it would use. Image alt text stays with the SEO
agent.
The Compliance agent
The Compliance agent keeps what your site says in line with your own rules, and what it loads and collects in line with what it tells visitors. It comes with three routines:
Brand compliance reads your rules from your site knowledge,
your project’s
AGENTS.md and what you told the agent before: write them there
(“say members, not users”, “we never promise results”). On its own, it changes
only a term your rules replace, word for word; it proposes every other sentence
with the words it would use. It runs on a smaller, cheaper model, since it
compares text with rules rather than writing.
The cookie and privacy checks open your site the way a first visitor sees it,
before any choice, and record what loads. The agent proposes every change to
your consent setup and to legal pages, with placeholders for details only you
know, and never changes them on its own. It is not a lawyer: it tells you what
it found and what your pages say, not whether a law is met.
Routines
A routine is a task an agent runs on its own, by hand, on a schedule, when something happens in the project, or when you answer it. Each routine works in a thread of its own, so a run sees what its earlier runs found, and the agent’s chat stays a conversation between people and the agent. Routines are the agent’s team: a run reports to the agent, never to you, and only when the agent should know something. The agent decides what reaches the chat: nothing, one short message, or a question when you must decide. A run that finds nothing, or does its work with nothing to add, reports nothing. A default agent’s routines are Fimo’s: they follow Fimo’s default instructions, so when Fimo improves them, every site’s routines run the new ones. You can switch each one off and on, or delete it, and a default routine you delete stays deleted; nothing else changes them, and nothing is added to a default agent. A routine Fimo retires from a default agent stops running and leaves its list. Routines of your own live in an agent of your own (Pro). To add or change one, ask the agent in its chat: “check the titles every Monday at 9:00”, “run this after each publish”, “pause the link sweep”. The agent creates, changes, runs and deletes its routines, and tells you in one sentence when a routine runs. Fimo can start a routine after each publish of the site, or when content changes on the main branch (by content type, created, updated or deleted, locale, or the fields that changed). Fimo can also check the entry’s current values (“when a product’s price goes over 100”, “when a category’s status changes to archived”) and ask a yes/no question about what the content says (“when a blog post mentions Contentful or Sanity”). For “a competitor”, Fimo uses the names you give or the ones in the site knowledge; when neither names them, the agent asks you to. A run started by an uncertain answer says so, so the agent checks before it acts. A routine can also start when a media file is uploaded (“when an image is uploaded”), when the site’s code changes through a deploy or a merge (“when the styles change”, by file path), or when another routine of the same agent finishes (“when the link sweep finds broken links”, optionally with a question about what it reported). What a routine changes, publishes or reports can start the agent’s other routines, in a chain of any length. A routine runs at most once for each change that starts a chain, however many routines that change leads to, so two routines never start each other in a loop and routines that react to each other’s work never multiply. A new change by you, a run by hand or on a schedule starts a new chain. A routine can also start when a visitor submits a form (“when someone submits the contact form”, optionally with a question about the answers, such as “when a big company asks for a demo”), when a form or a content type changes, when a branch is merged into main, when a locale is added, removed or made the default, when a publish of the site fails, or when a domain is added or removed. A routine can also watch the prices on a page of another web site (“tell me when https://example.com/pricing changes its prices”). Fimo reads the page when the trigger is set and checks it once a day; a price change must show on three reads in a row before the routine runs, so a page that tests two prices at random does not start it. The run’s message lists each plan with its old and new price. The routine’s page says whether the watch is OK, Needs repair (the page changed shape), Blocked (the site refuses Fimo) or Unstable (the prices keep changing), and when it last checked. A project can watch up to 10 pages. When Fimo cannot follow what you asked, such as comparing old and new values (“when the price goes up by 10%”), the agent tells you why and what it can do instead. For what Fimo cannot see as an event, such as traffic, rankings or errors, the agent offers a schedule instead: the routine runs at set times, checks it, and stops when there is nothing to do. Open the agent’s settings to see its Routines: each card shows the routine’s name, when it runs (the title of its event trigger, such as When an image changes, a schedule such as Every Monday at 08:00, or By hand), its next run, its last run and how it ended, and an Active switch. A new site’s default agents come with their routines on: most wake on changes (from five minutes after the site is created, so its setup starts no run), and the few with a schedule run at their own time of night; until a scheduled routine first runs, the agent’s row in the list says when its first check is. Turn the Active switch off to pause a routine. Select a card to open the routine’s page. You cannot edit a routine there:- What it does: one or two plain sentences on what the routine does for the site. Under it, Instructions opens the task the agent reads, sent as the message that starts every run. A routine created before descriptions existed shows its Instructions instead.
- Model: the model its runs use: Opus 5.5, marked as the default, unless you ask the agent to run it on another model.
- Triggers: By hand is always there; Run now starts a run right away and opens it. Schedule says when it runs, when it has one; times follow the timezone shown, and a routine runs at most every 15 minutes. The event trigger, when it has one, gets a short title from Fimo based on the words it was set with, such as After each publish, and shows those words. The run’s message lists what happened: the publication, or each entry that changed and which fields. Content changes that routines make never start a routine. Events that come in while a run is busy wait, then run together in one next run, which lists each of them; the run shows how many events it covered.
- Runs: every run, newest first, two lines each: how it ended, when it started and what started it (On schedule, On event, or By hand, with the name of the person or agent whose message started it), then the first sentence of what it told the agent. Quiet (nothing to report), Sent to agent (the agent was told something), Asked for a decision (the agent was told you must decide), Incomplete (the run could not check what it was asked to, such as a site it could not read; the second line says why, and the agent is not told), or Failed and Stopped, marked in red. Select one to open it.
- The Active switch in the header pauses the schedule and When something happens; Run now still works while paused. Deleting a routine (ask the agent) stops a run in progress, then removes the routine and its thread; what the agent said in the chat stays.
Send messages while a reply is in progress
You do not have to wait for a reply to finish. Write the next message and send it: it waits at the end of the chat, dimmed and marked Queued. When the reply in progress ends, chat answers the waiting messages one at a time, in the order they were sent. Each one gets its own reply. The queue belongs to the chat, so everyone on the site sees the same waiting messages, each with the name of the person who sent it. A waiting message runs with the model and the environment it was sent with.- Remove a waiting message. Select the cross next to it. Anyone who can write in the chat can remove any waiting message. A message that has started can no longer be removed.
- Stop. The stop button stops the reply in progress and the queue. The waiting messages stay where they are. Select the play button in the message box to continue, or send a new message: it goes behind the messages that already wait.
- Questions. When a reply ends with a question for you and messages wait, chat waits 30 seconds for your answer. Anything you send in that time runs first. If nobody answers, the waiting messages continue and the question stays open, so you can still answer it later.
Answer a question from chat
When your request has enough direction, chat starts the work without asking you to confirm routine details. If one missing answer prevents it from continuing safely, chat shows a short form and waits. A question can follow work already completed in the turn. Chat attempts to save that progress before waiting, and your answer continues the conversation. While the question is the last thing in the chat, the form stays pinned directly above the message box, so it does not scroll away while you read the conversation. Its place in the history reads “Waiting for your answer…”. You have two ways to answer:- Submit the form. This sends your selections on their own. Anything you have started typing in the message box stays there, unsent.
- Send from the message box. Your message goes out together with whatever you have already picked in the form, as one turn. If you have picked nothing, it is an ordinary message, and the question stays open.
Review work chat left for you
When chat saves work for you to look at, a strip appears directly above the message box, in the same place a question waits. It stays there while anything is waiting, however far you have scrolled. Collapsed, it names the work: Review Pricing page for one review, or 2 reviews waiting when several are open. Select it to list each one with what chat says it changed, View changes, and Open preview. The conversation keeps a one line record where the work was saved, with its own View changes link. Nothing on the strip decides anything. Opening a review does not approve it, and nothing merges or publishes from here. Decide on the review page, or ask for a change in the message box, which stays usable throughout. Closing the strip changes nothing about the saved work. A review leaves the strip once it has been merged or discarded. An unanswered question keeps priority: opening the strip folds the question down to its single line, and your answers are kept.Choose a model
When model choices are enabled for your site, use the picker beside the message box to choose Auto or a manual model. Auto selects a model for your request. Manual choices include Claude Opus 5.5 and GPT-6 Astra for demanding reasoning and coding work. GPT-6.1 Sol and GPT-6 Sol are options for everyday implementation and GPT-6 Luna and Claude Haiku 5.5 for inexpensive small changes. The models shown in the picker depend on your site’s Settings → Advanced settings → Models configuration. On a phone, the picker shows only the model icon. Point to it to read the model name, or select it to change the model. Site members who can manage the site can open Settings → Advanced settings → Models to choose which manual models everyone can use. Showing the picker is a personal browser setting, while the available model choices apply to the whole site. Chat may present site content, comparisons, assets, and analytics as interactive tables or visual summaries. These blocks use information available in the site. If the requested data or asset is unavailable, chat tells you instead of showing an estimate.Use connected tools
Chat can use the apps turned on for the site. If a request needs an app that is not on, chat says which app would help. An organization admin connects it in Apps and gives the site access, then you can ask again. Chat does not offer a connect button yet.Check remaining credits
If you have permission to view billing, your remaining credits appear beside the message box, including on phones. Select the balance to see the breakdown of monthly, purchased, and earned credits. When your organization’s credits are about to run out during a reply, chat stops starting new work, saves what it can, and tells you what is done and what remains. If the credits run out before the reply finishes, the message box says so. Add credits, then send the request again to continue.Handle overlapping changes
Studio chat works on changes in an isolated work session. Saving keeps that work available for a later message; merging applies it to the branch you are viewing. For an ordinary change request, chat should merge the result when it is ready. Media Library reads follow the branch being worked on, including assets added to an unmerged proposal. Chat can delegate part of the work to another agent in that same branch or let it work separately. Files attached to the conversation remain available as conversation context. Chat no longer delegates design requests to a separate Design Director. Describe the changes you want in the conversation; previous design briefs remain in your chat history. Ask chat to keep work separate when you want to compare proposals or review changes before applying them. You can return to the same conversation to continue. Successful workspace use keeps temporary sessions available for at least another 30 days, unless an existing deadline is later. Inspecting session details or receiving reminders does not extend that deadline. Ask explicitly for a lasting branch or proposal before starting when you need work kept without automatic expiry. Deleting a chat removes its messages without merging or discarding saved sessions, reviews, or unresolved merge conflicts. Temporary sessions keep their existing expiry. Automatic expiry cleanup waits while an active agent run is using a session. Once the run finishes, an expired temporary session becomes eligible for cleanup again. Chat attempts to save progress when a turn ends, including after an error or cancellation. This is not a guarantee: if its working environment disappears before a save succeeds, the code since the last successful save can be lost. If work overlaps with newer changes, chat can inspect and resolve conflicts. For each conflicting file, it sees the newer changes, who made them and why, such as a fix another agent routine already merged. Chat keeps those changes and combines them with its own. It asks you only when the two changes contradict each other. Submitting a resolution starts another merge attempt; the changes are applied only when that attempt succeeds. Each change chat saves or merges says why it was made, and a routine’s changes name the routine. Teammates and agents that later change the same files read that history. If more changes arrive before the retry, chat handles the new conflicts in the same way. A successful resolution may finish the merge without another merge request. If the merge succeeds but cleanup fails, retrying finishes cleanup rather than applying the work again. Asking to discard at that point does not undo changes already merged. Resolving or merging site changes does not publish the live website. Ask to publish when you want the changes live, or configure standing site instructions that name when publication is authorized. Without an applicable instruction, chat does not publish. Your current request can override standing instructions. Chat checks your publish permission and reports the publication result, including a failure if the attempt did not succeed. You can ask it to inspect publication status or logs.Use automation for repeatable work
Give an agent a routine when the same job should run again by hand or on a schedule. Use a scheduled command when one existing command should run on a cron.What’s next
Apps
Give chat access to external tools.
Scheduled commands
Run one site command on a recurring cron.
Automate your site
Compare Fimo’s automation options.