Run Configuration
Most projects run with no setup — but when Fletch’s auto-detected command or port isn’t right, you can adjust how your project runs, per repository. Open these from the gear on the Run panel, which opens the Run configuration sheet.
Run configuration
Section titled “Run configuration”The sheet shows the detected values grouped into Environment, Scripts, and Server. You can override any field — for example the dev command or the port — when the auto-detected value isn’t right for your project.
- Apply & restart commits your changes and relaunches the process.
- Revert to detected returns a single field to what Fletch detected.
- Reset all clears every override.
How settings are stored
Section titled “How settings are stored”Overrides are saved per project and persist across sessions and agents, so every workspace for that repository picks up the same run configuration. They’re stored locally in Fletch’s database — see Settings and Storage.
The same run environment is also editable from the project’s settings (the gear on a project in the sidebar), which additionally let you rename the project’s display name, relocate it if you move the repo folder — running agents keep their existing checkouts; new agents use the new path — and delete the project, which permanently removes it with all of its agents, workspaces, and history. Project settings open with the project’s pulse: a year-long activity heatmap and lifetime totals for agents run, PRs opened and merged, lines changed, and tokens spent. App-wide preferences (theme, panels, providers, custom agents) live in Settings and apply everywhere.
Environment variables
Section titled “Environment variables”Your project’s .env never enters a sandbox — that’s the point of the isolation — so a
dev server that needs a secret won’t find it. The Environment variables section in
project settings is the opt-in: it lists the variables found in the project’s .env,
each with a share-with-sandbox toggle. Nothing is shared unless you switch it on.
Shared values are mirrored live from .env at launch, so there’s one source of
truth. Edit a value to override it instead — useful for pointing agents at a
disposable resource; {{agent_id}} in an override expands per agent (e.g. a per-agent
database name), and clearing the field reverts to the .env value. Override values are
kept in the macOS Keychain, never in Fletch’s database.