fimo 2.7.1-staging.4 → 2.8.0-staging.1
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-studio/references/agents.md +19 -5
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +21 -21
- 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
|
@@ -1,8 +1,22 @@
|
|
|
1
1
|
# Agents
|
|
2
2
|
|
|
3
|
-
Project agents
|
|
3
|
+
Project agents come from either the Fimo-managed library or the project's Git repository. Both use the same run history and change review. Check the selected agent's source before editing settings: library behavior is managed by Fimo; Git bundle behavior is edited in the repository.
|
|
4
4
|
|
|
5
|
-
##
|
|
5
|
+
## Enable a library agent
|
|
6
|
+
|
|
7
|
+
1. Open **Agents → Agents → Add agent**.
|
|
8
|
+
2. Choose a library agent and review its project access, connections, and requested secret keys.
|
|
9
|
+
3. Select **Accept and enable**. This enables the agent without starting a run.
|
|
10
|
+
|
|
11
|
+
Library instructions, examples, tone, and runtime configuration are shared. Do not create a local bundle or edit project files to customize a library agent. Project managers configure its schedules under **Settings** using Daily, Weekly, or Advanced cron and an explicit timezone. Schedules can be edited, paused, retried after wiring errors, and deleted. A saved schedule cannot run while the agent is blocked or disabled. Library webhook triggers are unavailable.
|
|
12
|
+
|
|
13
|
+
If a library edit expands access, **Review permissions** opens the new requirements. Only a project manager can accept them; do not approve access on the user's behalf through a tool or API. **Accept changes** keeps a disabled agent disabled. **Needs setup** links to project settings for missing connections or secrets.
|
|
14
|
+
|
|
15
|
+
Choose **Disable agent** to block new runs and cancel queued or active work. **Stopping** persists until cancellation settles; **Retry** retries incomplete stopping. Reports and captured changes remain reviewable. **Enable agent** resumes future scheduled ticks after current permissions and setup are satisfied; missed ticks are not replayed.
|
|
16
|
+
|
|
17
|
+
When Studio context identifies `definition_source: library`, address it with `activation_id`. `agent_display_name` is a label, not a Git bundle path or unique identifier. `view` identifies whether the user is reading Runs or Settings. Use the shared run detail when `run_id` is provided.
|
|
18
|
+
|
|
19
|
+
## Open a Git agent
|
|
6
20
|
|
|
7
21
|
1. Open the project and choose **Agents**.
|
|
8
22
|
2. Select **Agents** again to see the available bundles.
|
|
@@ -12,7 +26,7 @@ On a user Branch, the list also shows new bundles that exist only on that Branch
|
|
|
12
26
|
|
|
13
27
|
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.
|
|
14
28
|
|
|
15
|
-
## Run, stop, or resume
|
|
29
|
+
## Run, stop, or resume a Git agent
|
|
16
30
|
|
|
17
31
|
Choose **Run** to start an agent whose manual trigger is live.
|
|
18
32
|
|
|
@@ -22,7 +36,7 @@ A stopped agent shows **Paused** in the header. **Resume** makes the same trigge
|
|
|
22
36
|
|
|
23
37
|
Only project managers see Run, Stop, and Resume. Other project members can still see schedule timing, status, settings, and run history.
|
|
24
38
|
|
|
25
|
-
## Delete
|
|
39
|
+
## Delete a Git agent
|
|
26
40
|
|
|
27
41
|
Project managers can open **Agent actions** beside Run/Stop, choose **Delete agent**, and confirm. Deletion stops planned or running work and commits removal of the agent bundle from `main`. Recorded runs remain in history. Remove the bundle from a local checkout before deploying again, or that deployment recreates the agent.
|
|
28
42
|
|
|
@@ -30,4 +44,4 @@ If a run cannot be stopped or `main` changes before deletion commits, the defini
|
|
|
30
44
|
|
|
31
45
|
## Inspect runs
|
|
32
46
|
|
|
33
|
-
Open **Runs** on an agent to see only that
|
|
47
|
+
Open **Runs** on an agent to see only that agent's history. Select a run to read its status, report, captured changes, and any question or review state that needs attention.
|