fimo 2.5.1 → 2.6.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/agent-templates/broken-link-sweeper/config.yaml +0 -1
- package/assets/skills/fimo-cli/references/agents.md +1 -4
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +4 -4
- package/package.json +8 -8
- package/release.json +2 -2
- 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
|
@@ -62,12 +62,10 @@ Declare a `runtime` block in `config.yaml` to gate where a bundle runs and bound
|
|
|
62
62
|
runtime:
|
|
63
63
|
cloud: true
|
|
64
64
|
dev: false
|
|
65
|
-
long_running: false
|
|
66
65
|
max_credits: 5000
|
|
67
66
|
```
|
|
68
67
|
|
|
69
68
|
- `cloud` / `dev` — declared boolean environment flags for where the bundle may run.
|
|
70
|
-
- `long_running` — same capability as the `runtime:long_running` token: lets the run exceed the default time limit.
|
|
71
69
|
- `max_credits` — the run's own credit ceiling (integer, credits ≥ 1) and the one limit to tune. The default scaffold
|
|
72
70
|
template ships `max_credits: 5000` as a visible starter limit; raise, lower, or remove it to fit the agent's work.
|
|
73
71
|
Unset: the run may spend up to the organization's available credits at admission.
|
|
@@ -76,7 +74,7 @@ runtime:
|
|
|
76
74
|
scaffolding a bundle, and do not reach for it to control spend — tune `max_credits` instead. Unset: no step cap;
|
|
77
75
|
`max_credits` (or the organization's balance) and the plan's agent-hours bound the run.
|
|
78
76
|
|
|
79
|
-
All
|
|
77
|
+
All four keys are optional; an absent `runtime` block behaves as if every key were unset. There is no platform step cap
|
|
80
78
|
and no platform per-run cost ceiling — the only stops are these author-owned limits, the organization running out of
|
|
81
79
|
credits (`insufficient_credits`), and the agent-hours allowance. A limit that fires records a truthful terminal reason
|
|
82
80
|
(`max_steps`, `budget_exceeded`, `insufficient_credits`, or `finish_run_missing` when a run ends without calling
|
|
@@ -242,7 +240,6 @@ webhooks, and schedules; remove entries when an agent should have less access.
|
|
|
242
240
|
| `fimo:deploy` | Trigger a production deploy | Critical |
|
|
243
241
|
| `net:fetch` | Make outbound HTTP requests | Medium |
|
|
244
242
|
| `agent:delegate` | Invoke declared sub-agents | Medium |
|
|
245
|
-
| `runtime:long_running` | Run beyond the default time limit | High |
|
|
246
243
|
| `runtime:auto_merge` | Auto-merge trivial proposed branches | Critical |
|
|
247
244
|
|
|
248
245
|
If a public Fimo capability is missing and the work is genuinely blocked, the agent can request it through `ask_user`.
|