coolguy/coorl-lost-cities
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Document W&B notes/tag conventions in AGENTS.md

Browse Source 
Brief guidance on roles (notes = purpose, tags = filter categories)
plus three anti-patterns to avoid. Otherwise free-form.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
coolguy
2026-05-07 16:52:56 +09:00
co-authored by Claude Opus 4.7
parent 54a5fdab2e
commit 611e4119a1
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+13
View File
@@ -307,6 +307,19 @@ W&B is purely additive — `metrics.jsonl` remains the source of truth, and
`analyze` reads `metrics.jsonl`, not W&B. Disabling W&B never breaks `analyze` reads `metrics.jsonl`, not W&B. Disabling W&B never breaks
training, resume, or analysis. training, resume, or analysis.
### Notes and tags
Use `--wandb-notes` for the run's *purpose* (free-form prose) and
`--wandb-tag` for *categories you might filter on later* (short kebab-case
keywords, repeatable). Otherwise use them however you like. Just avoid:
- Tags that duplicate `config` (`lr-1e-4`, `traversal-280`) — W&B already
indexes config fields.
- Tags that are unique per run (`test-1`, `2026-05-07`) — that's the run
name and timestamp's job.
- Tag-as-sentence (`tested-bigger-traversal-with-lcfr`) — that belongs in
`--wandb-notes`.
## Notes For Future Agents ## Notes For Future Agents
- Prefer `rg`/`rg --files` for search. - Prefer `rg`/`rg --files` for search.