foldrun 3.0.0 → 4.0.0
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/docs/security.md +10 -0
- package/docs/self-hosting.md +3 -0
- package/package.json +2 -2
package/docs/security.md
CHANGED
|
@@ -61,6 +61,16 @@ and the generated index of a knowledge bundle.
|
|
|
61
61
|
Refusals are counted per step and shown on the run page. Each one is a
|
|
62
62
|
wasted turn; a prompt that names the exact path brings the count to zero.
|
|
63
63
|
|
|
64
|
+
**A run does not change its own configuration or code.** What a step
|
|
65
|
+
writes to `AGENTS.md`, `agents/`, `flows/`, `tools/`, `hooks/`, `skills/`,
|
|
66
|
+
`evals/` or `scripts/` is not kept: the workspace keeps its own copy, and
|
|
67
|
+
the run page lists each such path under "Not kept". A prompt injection
|
|
68
|
+
cannot widen what later runs may do. Data comes back as before — `state/`,
|
|
69
|
+
`storage/`, `memory/`, `knowledge/`. The one exception is a step a person
|
|
70
|
+
approved before it ran (`!` or `approve: true`): the person read what it
|
|
71
|
+
would do, so its changes to configuration and code are kept, and listed
|
|
72
|
+
on the trail as "kept with approval". That is how an approved fix lands.
|
|
73
|
+
|
|
64
74
|
## Secrets
|
|
65
75
|
|
|
66
76
|
An agent names a secret in `secrets:`; the model never sees the value — it
|
package/docs/self-hosting.md
CHANGED
|
@@ -186,6 +186,9 @@ What is different from the platform, and why:
|
|
|
186
186
|
- **No sandbox by default.** Steps run as your user, in your workspace. Set
|
|
187
187
|
`FOLDRUN_RUN_ISOLATION=container` with Docker installed to get one hardened
|
|
188
188
|
container per step, the same executor the platform's single-box shape uses.
|
|
189
|
+
Without one, a step's file tools may not write the workspace's configuration
|
|
190
|
+
or code (`AGENTS.md`, agents, flows, tools, skills, evals, scripts), but its
|
|
191
|
+
shell is not confined: only a sandbox keeps those files out of a step's reach.
|
|
189
192
|
- **Gates wait in the terminal.** A `!` step parks the run; `foldrun run`
|
|
190
193
|
shows the approval and waits for your answer.
|
|
191
194
|
- **Budgets cap, and nothing meters.** `budget:` stops a run at its cap; the
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "foldrun",
|
|
3
|
-
"version": "
|
|
3
|
+
"version": "4.0.0",
|
|
4
4
|
"description": "Agents are just folders. Write them, check them, run them — on your machine.",
|
|
5
5
|
"license": "FSL-1.1-ALv2",
|
|
6
6
|
"type": "module",
|
|
@@ -11,7 +11,7 @@
|
|
|
11
11
|
"node": ">=22"
|
|
12
12
|
},
|
|
13
13
|
"dependencies": {
|
|
14
|
-
"@foldrun/core": "^
|
|
14
|
+
"@foldrun/core": "^3.0.0"
|
|
15
15
|
},
|
|
16
16
|
"files": [
|
|
17
17
|
"bin",
|