Refine research workflows and remove Agent Computer

This commit is contained in:
Advait Paliwal
2026-03-24 11:01:27 -07:00
parent b712f89580
commit 8fd06b9299
23 changed files with 137 additions and 299 deletions

View File

@@ -9,14 +9,13 @@ Design a replication plan for: $@
## Workflow
1. **Extract** — Use the `researcher` subagent to pull implementation details from the target paper and any linked code.
2. **Plan** — Determine what code, datasets, metrics, and environment are needed. Be explicit about what is verified, what is inferred, and what is still missing.
2. **Plan** — Determine what code, datasets, metrics, and environment are needed. Be explicit about what is verified, what is inferred, what is still missing, and which checks or test oracles will be used to decide whether the replication succeeded.
3. **Environment** — Before running anything, ask the user where to execute:
- **Local** — run in the current working directory
- **Virtual environment** — create an isolated venv/conda env first
- **Docker** — run experiment code inside an isolated Docker container
- **Cloud** — delegate to a remote Agent Computer machine via `/delegate`
- **Plan only** — produce the replication plan without executing
4. **Execute** — If the user chose an execution environment, implement and run the replication steps there. Save notes, scripts, and results to disk in a reproducible layout.
4. **Execute** — If the user chose an execution environment, implement and run the replication steps there. Save notes, scripts, raw outputs, and results to disk in a reproducible layout. Do not call the outcome replicated unless the planned checks actually passed.
5. **Report** — End with a `Sources` section containing paper and repository URLs.
Do not install packages, run training, or execute experiments without confirming the execution environment first.