> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuneplane.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Every run of every experiment in one project, side by side, at /projects.

One card per project at `/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.

![TunePlane projects page](https://mintcdn.com/starforge/GatXR2rI5-_Vm4_H/images/console/projects.png?fit=max\&auto=format\&n=GatXR2rI5-_Vm4_H\&q=85\&s=70a3fd8a89f289584b0ad0dd79987fe0)

Projects: one card per project, with run count and latest status.

## What you see

| Region | What it shows |
| - | - |
| Project cards | Run count, latest status, best metric |
| A project's detail | The run list, a key-metric comparison table, and mini curves |
| Sweep annotations | Each variant labelled with its grid axis values, so which parameter set is which is visible without opening anything |
| Memory cards | Conclusions somebody wrote down |

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

| Action | Effect |
| - | - |
| Open a project | The run list and comparison grid |
| Select two to four runs | Opens [Review](https://docs.tuneplane.ai/en/console/review.md) on them |
| Diff two runs' configs | "What differs between these two" without reading YAML |
| Search, filter, pin a column | Narrow a grid of hundreds of runs |
| Write a memory card | Keeps a conclusion with the project |

## 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 the `get_project_memory` [MCP tool](https://docs.tuneplane.ai/en/console/mcp.md) 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](https://docs.tuneplane.ai/en/guides/teams.md).

## Next

[Review](https://docs.tuneplane.ai/en/console/review.md) · [Jobs](https://docs.tuneplane.ai/en/console/jobs.md) ·
[Experiments](https://docs.tuneplane.ai/en/guides/experiments.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.