/projects. A project is the name in your tuneplane.yaml, so every
run of every experiment in that directory lands here: sweep variants, iterations, stages.
Projects: one card per project, with run count and latest status.
What you see
The comparison grid is dense on purpose: the job name and status stay fixed while the metric and
config columns scroll. Columns that are identical across every run are hidden by default and
available from the Columns panel — a column where nothing differs tells you nothing.
What you can do
Project memory
A memory card is a written conclusion: “lr 2e-6 with KL 0.05 is the most stable”, “the reward ceiling moved after data v2”. It stays with the project, so whoever picks the work up does not have to reconstruct it from chat history. It is also what theget_project_memory MCP tool reads, so an assistant
proposing a next run starts from what the team already learned.
Naming
Project names need not be globally unique. The grouping key is@<username>/<project>, so two
people with a project called support-agent never collide. Sweep variants inside a project are
separated by their sweep_id.
A run’s project is attached at submission and frozen on the row. Moving a project between teams
does not rewrite last quarter’s usage — see teams.