Work on changes in parallel
Give each change its own Git worktrees and local ports. Keep one stack running while you develop and test another.
Independent local stacks for every change
Develop in parallel.
Review locally.
Run independent local copies of your codebase at the same time. Develop and test multiple changes in parallel, then review each one end to end before you share it.
Your worktrees. Your machine. Share when ready.
Press Play or NextNo stacks created
Illustrative demo. No commands are executed.
A clear local workflow
From config to running stack
Choose a step to see the command. This example is illustrative and does not control your machine.
npm run cli -- add /path/to/projectConfiguration reviewedWhat Stack Manager takes care of
Separate changes. Working stacks.
Share the big folders
Link reusable folders such as node_modules into your worktrees instead of installing a copy for every change. Share only when dependencies match.
Choose flags per stack
Enable or disable configured feature flags for each stack. Stack Manager passes those choices to your app as environment variables.
Allocate and manage ports
Stack Manager allocates and tracks ports for each stack. You must configure your services to use those ports, through env vars or command arguments.
A tool your AI can use
Your coding agent can create, start and inspect stacks through the CLI and read JSON results. You can check their status in the local dashboard.
Check service health
Use process or HTTP readiness checks before starting dependent services. Check component health from the CLI or local dashboard.
Wire up the environment
Render local service addresses and copy declared private env files into each worktree. Keep each stack pointing at its own services.
Review before you share
Run the frontend and backend together and review your change locally, end to end. When you are finished, review and approve the cleanup steps.
Opinionated about local development
Built around the way your code runs
Git worktrees
Each change lives in its own checkout. Develop and test without switching the code out from under another running stack.
One repo or several
Configure separate frontend and backend repositories, or a monorepo with a command that runs its services.
Environment variables and flags
Your app reads service addresses and feature flags from env vars. You declare the wiring in a project config.
Tested with Firebase
Tested with Firebase emulators for local Google Cloud Firebase backends. Your config controls service endpoints and data isolation.
Develop. Run. Review.