fimo 2.7.0-staging.1 → 2.7.0-staging.2
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.
- package/assets/skills/fimo-cli/references/agents.md +1 -1
- package/assets/skills/fimo-studio/references/agents.md +2 -0
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +2 -2
- package/package.json +8 -8
- package/templates/astro/package.json +2 -2
- package/templates/nextjs/package.json +3 -3
- package/templates/react-router/package.json +4 -4
- package/templates/sveltekit/package.json +2 -2
- package/templates/vite/package.json +4 -4
|
@@ -286,7 +286,7 @@ fimo agents report <name> [--session <id>] [--branch <branch>] [--project <id>]
|
|
|
286
286
|
|
|
287
287
|
## How triggers get wired
|
|
288
288
|
|
|
289
|
-
Agents are not Branch-scoped: they belong to the project, are read from `main`, and their triggers are global.
|
|
289
|
+
Agents are not Branch-scoped: they belong to the project, are read from `main`, and their triggers are global. Studio shows the deployed main agents on every Branch. When the selected Branch contains a new bundle that is not on main yet, Studio also shows it as disabled and explains that it becomes available after merge. Its triggers remain inactive until the bundle reaches main.
|
|
290
290
|
|
|
291
291
|
Pushing `.fimo/agents/<name>/config.yaml` (or a legacy root bundle) to `main` is the whole enablement act — `fimo deploy` does it. The server reconciles the file into its trigger rows on every push: a `schedule` trigger gets a cron, a `webhook` trigger gets its path, and `manual` becomes runnable. Removing a trigger from the file deletes it (cron torn down, path released) on the next deploy; deleting the agent's directory removes the whole deployment.
|
|
292
292
|
|
|
@@ -8,6 +8,8 @@ Project agents are versioned bundles from the project's repository. Studio lets
|
|
|
8
8
|
2. Select **Agents** again to see the available bundles.
|
|
9
9
|
3. Choose an agent to open its **Runs** and **Settings** tabs.
|
|
10
10
|
|
|
11
|
+
On a user Branch, the list also shows new bundles that exist only on that Branch. Their cards are disabled; open one to see that the agent and its triggers become available after the Branch is merged into main.
|
|
12
|
+
|
|
11
13
|
When the agent has a live schedule, its next run appears first in **Runs**, marked **Scheduled**. The row uses **Next** for its projected ID, a relative date such as **Tomorrow at 11:00 AM**, and **—** for changes and duration until it starts. **Settings** shows the bundle's declared capabilities and trigger wiring; it is read-only because the repository remains the source of truth.
|
|
12
14
|
|
|
13
15
|
## Run, stop, or resume
|