zhyx12/projtool

zhyx12/projtool

Command

Power off (or release) the AutoDL instance for the current experiment to stop billing.

zhyx12/projtool

Command

Start a training run on the current experiment branch. Provisions an instance if needed, syncs code, and launches in tmux.

zhyx12/projtool

Command

Show the status of all in-flight runs and instances for this project.

zhyx12/projtool

Command

Adopt a pre-registry docs layout (plans/, exp/) into the research-thread registry — scan for drift, dry-run the migration proposal, confirm the mapping WITH THE USER, then apply. Never guess history.

zhyx12/projtool

Command

Read the experiment record (journal, findings, reports, run table) and propose the next 1-3 experiments with rationale and cost — the user decides, then execution goes through startruns/starttraining.

zhyx12/projtool

Command

Start a new analysis report in the independent docs repo, prefilled with frontmatter from the cited runs (single branch or cross-branch summary).

zhyx12/projtool

Command

Distill this work session's experiment outcomes into the experiment's findings.md (what was tried, what failed and why, what's now established) and commit it to the docs repo.

zhyx12/projtool

Command

Close a research thread — conclude it with an evidence-citing conclusion.md, or abandon it with a one-line reason. Terminal is terminal; to revive, open a successor thread with a supersedes edge.

zhyx12/projtool

Command

Open a new research thread (a research line) in the docs registry — pick a slug, create the record + idea.md/plan.md skeletons, interview the user to fill them, and point forward to the first experiment.

zhyx12/projtool

Command

Babysit every active run to completion — staged polling, auto-finalize, progress report; no raw SSH loops.