Build & run configs

Define how to build and start your app, then launch it from GridTree or an agent.

Last updated Jun 06, 2026

A build & run config describes how to build and start your app. Once defined, you can launch it from GridTree with Ctrl+Shift+R, stop it, and read its logs — and an agent can do the same over the MCP server.

You create them in the app — open the project's settings and add a build & run config. GridTree saves them to .gridtree/launch.config in your repo, so they're shared with everyone who opens the project. You don't have to write that file by hand; the format below is just for reference.

.gridtree/launch.configjson

{
"buildRunConfigs": [
  {
    "id": "web",
    "name": "Web app",
    "buildCommand": "npm run build",
    "runCommand": "npm run dev",
    "showLogOnStart": true,
    "order": 0
  }
]
}

Field	Required	Description
`name`	yes	Label shown in the runner and the launch picker.
`runCommand`	yes	The command that starts the app.
`buildCommand`	no	Runs before `runCommand`; skip it if there's nothing to build.
`showLogOnStart`	no	Open the log view automatically when the app starts.
`id`	no	A stable id so a running instance is still recognized after a reload.
`order`	no	Sorts configs in the picker.

GridTree starts the app in the active worktree, tracks whether it's running, and captures its output so you can tail it without hunting for a terminal.

From an agent#

When the MCP server is set up, these same configs are what list_app_configs, start_app, stop_app, get_app_status, and get_app_output operate on — so an agent can start your dev server, check that it came up, and read the logs on its own. See MCP server.