@themoltnet/agent-daemon 0.9.0 → 0.10.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/README.md +15 -0
- package/dist/main.js +797 -442
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -147,6 +147,21 @@ primitive, not a performance recipe. In pnpm-heavy monorepos like this one,
|
|
|
147
147
|
keep install hot paths off `/workspace` via guest-local store paths and
|
|
148
148
|
`resumeCommands` tmpfs mounts.
|
|
149
149
|
|
|
150
|
+
If a resume step assumes `/workspace` is a repo checkout, gate it on
|
|
151
|
+
`resumeCommands[].when.workspaceMode` rather than on task type. Use:
|
|
152
|
+
|
|
153
|
+
- `shared_mount` / `dedicated_worktree` for repo-aware bootstrap
|
|
154
|
+
- `scratch_mount` to skip repo-specific steps when the task runs in an empty
|
|
155
|
+
scratch workspace
|
|
156
|
+
|
|
157
|
+
This matters for evals in particular. `run_eval` tasks declare their intended
|
|
158
|
+
workspace shape in `input.execution.workspace`: `none` becomes a
|
|
159
|
+
`scratch_mount`, `shared_mount` uses the daemon mount, and
|
|
160
|
+
`dedicated_worktree` uses an isolated checkout. Downstream
|
|
161
|
+
`judge_eval_attempt` tasks can attach to that exact producer workspace, so any
|
|
162
|
+
repo-specific `resumeCommands` that should not run in scratch mode must be
|
|
163
|
+
guarded with `when.workspaceMode`.
|
|
164
|
+
|
|
150
165
|
### 1. Start the local stack
|
|
151
166
|
|
|
152
167
|
The e2e Compose file ships everything the daemon needs (Postgres, Ory, REST
|