forest start
Set up Forest from scratch: log in, create a project, start its back-end locally, and give your coding agent the Forest skills to build on it.forest start chains other CLI commands and prints each one before running it, so every step stays visible and reproducible by hand.
Usage
Options
Flows
forest start first logs you in with forest login (skipped when a session is active), then asks how you want to run Forest.
Each flow waits for the back-end to start and send its schema to Forest before going further.
The
standalone and demo flows generate the project in a new directory. The inapp flows run in your application’s directory: run forest start from its root. For Node.js, the CLI writes FOREST_ENV_SECRET and FOREST_AUTH_SECRET to the .env file, without overwriting values already set there.
After the back-end starts
In an interactive terminal,forest start keeps the back-end running and offers next steps:
- Demo: create a real project on your own database, keep exploring, or stop.
- Other flows: install the Forest skills for your coding agent with
forest skills:init, deploy to production through your coding agent, open the documentation, or keep exploring.
Requirements
- Node.js 18 or later
- macOS or Linux. On Windows, run
forest startin WSL - For the
inappRails flow: Bundler and a Rails application
Examples
In the commands it shows,
forest start replaces your database URL and your environment secret with <redacted>.