fimo 2.14.1-staging.1 → 2.14.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.
@@ -22,7 +22,7 @@ fimo preview url --json # cu
22
22
  - **Publish only when the user says to publish, ship, or go live.** Publishing makes the site public.
23
23
  - Local changes to go live: `fimo deploy --publish`. The revision already on Fimo is the release: `fimo publish` (it never pushes).
24
24
  - Check the reported source commit and warnings before you report success. If local work is not in the build, or the built commit is unknown, follow the hint.
25
- - A failed publication usually gives its id (`error.details.publication_id`; else find it with `fimo publish list`). Run `fimo publish inspect <id> --json` for the status and cause, then `fimo publish logs <id> --json` for the build log. The hosting provider can delete old logs: then report that, and do not publish again only to get logs. Older attempts: `fimo publish list --cursor <cursor>` or `--all-pages`.
25
+ - A failed publication usually gives its id (`error.details.publication_id`; else find it with `fimo publish list`). Run `fimo publish inspect <id> --json` for the status and cause, then `fimo publish logs <id> --json` for the build log (a Studio chat agent cannot run it; it reads the cause from `publish inspect`). The hosting provider can delete old logs: then report that, and do not publish again only to get logs. Older attempts: `fimo publish list --cursor <cursor>` or `--all-pages`.
26
26
 
27
27
  ## A failed preview deploy
28
28
 
@@ -34,7 +34,7 @@ A new page an agent leaves for a person shows as a `drafts` block in the chat: o
34
34
  - In an agent, the header shows its name alone and the message box reads **Message <name>**. An empty default agent greets in its own words and offers starter requests; its description stays in its settings. A starter is sent as shown, by anyone who can send messages.
35
35
  - Ask the agent to change its instructions; it uses its `agent` tool, and the chat shows **Updated instructions** with **View change** (before and after).
36
36
  - The agent's settings have **Summary** and **Instructions** (shared with everyone; empty means none) and an **Instruction history**, where **Restore previous** puts back the text a change replaced.
37
- - A default agent is Fimo's: its name, summary, instructions and portrait cannot change on any plan. Fimo's routines on it can be switched off and on, or deleted (a deleted one stays deleted), but not changed (`routine_is_default`). On Pro, the team can add routines of its own to a default agent or to an agent of its own (`routine_needs_pro` below Pro); any chat can create one on the agent whose work it is. A routine Fimo retires stops running and leaves the list.
37
+ - A default agent is Fimo's: its name, summary, instructions and portrait cannot change on any plan. Fimo's routines on it can be switched off and on, run less often than Fimo set them (see Pace in `ai-chat/routines`), or deleted (a deleted one stays deleted); nothing else about them changes (`routine_is_default`). On Pro, the team can add routines of its own to a default agent or to an agent of its own (`routine_needs_pro` below Pro); any chat can create one on the agent whose work it is. A routine Fimo retires stops running and leaves the list.
38
38
  - In text, an agent links another as `[Name](agent://id)`, shown as a chip that opens it.
39
39
 
40
40
  ## Default agents
@@ -4,7 +4,9 @@ A routine is saved instructions that an agent runs in a thread of its own: by ha
4
4
 
5
5
  ## Create and change
6
6
 
7
- Any chat, an agent's or a regular one, creates, changes, runs and deletes the project's routines with its `routines` tool. A person asks in any chat ("check the prices every Monday", "run after each publish", "pause the link sweep"), and the routine goes on the agent whose job it is. Studio only shows routines. Routines of your own need Pro; a default routine can only be switched off and on, or deleted.
7
+ Any chat, an agent's or a regular one, creates, changes, runs and deletes the project's routines with its `routines` tool. A person asks in any chat ("check the prices every Monday", "run after each publish", "pause the link sweep"), and the routine goes on the agent whose job it is. Studio only shows routines. Routines of your own need Pro; a default routine can only be switched off and on, run less often, or deleted.
8
+
9
+ **Pace:** an agent fits a routine's schedule to what its runs find. After some weeks of scheduled runs that find nothing new, the routine tells its agent, and the agent makes the schedule slower on its own, keeps the earlier schedule in its memory, and tells the team in one sentence ("I now check your search results once a month, because nothing changed for five weeks"). The routine's page shows the new schedule and next run. The agent puts the earlier schedule back when a run finds work again or a person asks. It never adds runs on its own, by a tighter schedule or a new trigger: it proposes them and waits for a person. A default routine's schedule can be made slower on any plan, never faster than Fimo set it (`routine_is_default`).
8
10
 
9
11
  ## Triggers
10
12
 
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "bundled": true,
3
3
  "bundler": "esbuild",
4
- "bundledAt": "2026-11-11T17:10:05.324Z",
4
+ "bundledAt": "2026-11-13T09:25:36.887Z",
5
5
  "cliVersion": "2.14.0",
6
6
  "external": [
7
7
  "oxc-parser",