Use cases
Git Treeline provisions complete environments per worktree: ports, databases, routing, env, lifecycle hooks. These guides show what that means for real workflows.
For full depth on each pillar, start with Isolation, Networking, Workflows, or AI Agents; use this page when you already know which problem you are solving.
Start here
Install gtl, run gtl install, and walk through every section of the config — ports, databases, env files,
commands, hooks, aliases, and editor integration. Ends with your first running worktree.
One redirect URI, any branch. Start hooks claim the alias per-session.
Clone from a PostgreSQL template, seed from hooks, or copy a SQLite file.
{resolve:…} tracks the right branch
across projects automatically.
Treeline reserves common ports so OAuth, Stripe, and CORS never break.
One command gives Redis Commander, pgAdmin, or Mailhog a named HTTPS URL.
Ports, database, env, dependencies, and a running server under a minute.
gtl review stands up an isolated worktree with a
branch URL.
MCP server and --json flags give agents structured
worktree context.