From 611e4119a12ed67d0c8332a3919756da108e3a4b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=EC=A0=95=EC=8B=9C=EC=9B=90?= Date: Thu, 7 May 2026 16:52:56 +0900 Subject: [PATCH] Document W&B notes/tag conventions in AGENTS.md 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) --- AGENTS.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 9f8dd97..72f0362 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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 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 - Prefer `rg`/`rg --files` for search.