Local, remote and CI/CD for every project, discovered from the repo and always yours to correct. The three tabs sit under ENVIRONMENTS in the sidebar.
A run config is a named set of the project's apps and services, declared in grid.toml as [run.<name>]. Starting it brings the whole set up on the worktree you pick: an app with a declared port gets a port of its own per worktree, and a service, such as a container from the project's compose file, runs once on its configured port. Expand it for each part: its port, its URL, how long it has been up, its logs, and start, stop, restart or kill on its own. A card's run panel shows the same configs narrowed to that card's worktree. See grid.toml for the keys.
Worktrees share whatever database the project already runs. Grid does not create, seed or migrate one per card; the seed key only copies seed files into a fresh worktree. See worktrees.
Remote lists each environment of the project: its name, the version deployed (read from a probe or from CI, with the commit), its URL, and the last deploy: how long ago, through which pipeline and from which ref. CI/CD groups the pipelines per repository, with each one's state and its last runs.
Remote only reports, and deploys go through your pipeline or the deploy step you configured. CI/CD can also Re-run a failed pipeline, and Ignore one you do not care about.
Discovery lives on the project's page, under Projects in the sidebar: each section (repositories, local environment, tests, remote environments, CI/CD) has Discover or Rediscover. It reads the declaration files the repo already has (package.json, the Makefile, compose files, GitHub Actions, GitLab CI, Jenkins and CircleCI files and the like), refines what it found with one model pass, and shows you a proposal to apply, rediscover or turn into a card. Values that look like passwords, secrets or tokens are scrubbed before anything is sent to the model.
Each tab here also has a Discover button. Today it opens the project's grid.toml editor, where you correct by hand what discovery got wrong.
Agents often need a login for a staging admin or a test key. The Remote tab's ACCOUNTS & SECRETS list shows each account the project declares in grid.toml ([account.<name>]) and whether it is signed in, expiring or missing, proved by a command that exits 0, an environment variable that is set, or a file that exists, plus an expiry date if you give one. Grid stores no value.
Secrets held as references to your password manager or Grid's own vault, never the value, with which environments may use each one and whether it asks you first, and agents asking Grid to fill a login or start a command with the value set. None of it is built.