Settings
Sidebar → Settings. The page subtitle shows where Jimothy stores its data (Data stored in …). Changes are applied when you click Save (enabled when something changed), except the remote-access switch, which applies immediately.
Settings are stored in settings.json in the data folder.
General
Section titled “General”| Setting | Default | Notes |
|---|---|---|
| Appearance | System | System follows your OS light/dark mode; Dark or Light force one. |
| Your name | me |
Recorded on approvals. Shown as “Approved by …” and available as {{steps.<id>.approvedBy}}. |
Execution
Section titled “Execution”| Setting | Default | Notes |
|---|---|---|
| Max concurrent runs | 3 | 1–32. Across all pipelines. Extra runs wait in the queue. A pipeline’s own Max concurrent runs can limit it further. |
| Workspaces folder | <data folder>/workspaces |
Where per-run worktrees and scratch folders are created. Each run gets run-<number>-<issue-key-slug>. The folder button opens a picker. |
| Delete a run’s workspace after it succeeds (branches are kept) | off | After a successful run, removes the worktree (git worktree remove --force) or the clone/scratch folder. Never touches Existing folder workspaces. Failed and cancelled runs keep their workspace for inspection and retry. |
| Extra PATH entries | empty | One directory per line. Searched first when launching harness CLIs (your login-shell PATH is picked up automatically). See Auto-detection. |
| Environment variables | empty | KEY=value per line, injected into every step (e.g. ANTHROPIC_API_KEY, GH_TOKEN). Lines without = are ignored. Project env and step env override these. |
Values in Environment variables are stored in plain text in settings.json, unlike harness API keys and tracker tokens, which are encrypted. They’re also not visible to harness detection and model fetching; see API harnesses.
Remote access
Section titled “Remote access”Serve the UI to your phone and other devices over Tailscale: Use Jimothy from your phone and other devices on your Tailscale network (applies immediately), Local port (default 7718) and Tailnet HTTPS port (default 7443). See Remote access.
Webhook server
Section titled “Webhook server”| Setting | Default | Notes |
|---|---|---|
| Receive trigger webhooks (Linear, Jira, GitHub, custom) for instant runs | off | Starts the local webhook server. |
| Listen address | 127.0.0.1 |
127.0.0.1 = this machine only (use a tunnel); 0.0.0.0 = your network. |
| Port | 7717 |
When running, the section shows Listening on http://127.0.0.1:7717/hooks/<trigger-id>. Changing the switch, address or port restarts the server on save. See Webhooks.
Settings not on this page
Section titled “Settings not on this page”- Data folder: set with the
FACTORY_DATA_DIRenvironment variable before launching the app. See Environment variables. - Harnesses, Accounts, Triggers and Notifications have their own pages.