Settings
Settings open in a window over the page you were on. Open it with Settings (the gear) at the bottom of the sidebar, ⌘, (Ctrl+, on Windows and Linux), or the Settings commands in the ⌘K palette. Close it with the × button, Esc, ⌘, again, or by clicking outside it.
The window has six tabs:
| Tab | What’s on it |
|---|---|
| General | Your name, execution settings and the data folder. See below. |
| Appearance | Light/dark mode and color themes. See below. |
| Accounts & integrations | Your signed-in accounts, and the webhook server. |
| Harnesses | Every harness, its detection status and its models. |
| Notifications | Notification channels and recent activity. |
| Remote | Remote access from your phone and other devices, and the MCP server for AI assistants. |
Each tab with settings (except Appearance, which applies as soon as you pick) has its own Save button (enabled when something changed); changes apply when you click it. If you switch tabs or close the window with unsaved changes, Jimothy asks first: Discard unsaved changes?
Drag the window’s right edge, bottom edge or corner to resize it; double-click an edge to go back to the default size. The size is remembered. Over remote access on a phone, Settings open full-screen.
Older links such as #/accounts, #/harnesses and #/notifications still work: they open the matching tab.
Settings are stored in settings.json in the data folder.
General
Section titled “General”General
Section titled “General”| Setting | Default | Notes |
|---|---|---|
| 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 | One row per variable: a name and a value. Add adds a row. Injected into every step (e.g. ANTHROPIC_API_KEY, GH_TOKEN). Rows without a name are dropped on save. 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.
Values are hidden from AI assistants unless you click the eye. The eye button on each row decides whether assistants connected through the MCP server can read that value. It’s crossed out (hidden) by default; click it to let them read it. Steps get every value either way.
Data folder shows where Jimothy keeps pipelines, runs, accounts and settings. Open shows it in your file manager (desktop app only). Back this folder up to keep your setup. To use a different folder, set the FACTORY_DATA_DIR environment variable before launching the app; see Environment variables.
Appearance
Section titled “Appearance”Changes apply right away; there’s no Save button.
| Setting | Default | Notes |
|---|---|---|
| Mode | System | System follows your OS light/dark mode; Dark or Light force one. |
| Dark theme | Jimothy Dark | Used in dark mode. Also: One Dark Pro, Dracula, GitHub Dark, Monokai, Solarized Dark, Nord, Night Owl, Tokyo Night, Catppuccin Mocha, Gruvbox Dark, Material Palenight, Ayu Mirage, Rosé Pine. |
| Light theme | Jimothy Light | Used in light mode. Also: GitHub Light, One Light, Solarized Light, Catppuccin Latte, Gruvbox Light, Ayu Light. |
With System, Jimothy switches between your dark and light theme as your OS does.
Webhook server
Section titled “Webhook server”On the Accounts & integrations tab, below the accounts:
| 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 |
The card has its own Save button. When running, it 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.
Remote
Section titled “Remote”Use Jimothy from your phone, another computer, or Claude. The tab has two cards and one Save button, for the ports.
Remote access serves the UI to your phone and other devices over Tailscale: Use Jimothy from your phone and other devices on your Tailscale network (applies immediately, without Save), Local port (default 7718) and Tailnet HTTPS port (default 7443). See Remote access.
MCP server lets Claude and other AI assistants use Jimothy: Let Claude and other AI assistants use Jimothy… (applies immediately) and Port (default 7719, on 127.0.0.1). When it’s on, the card has the setup to copy for Claude Code, Claude Desktop, Codex, OpenCode, Cursor and Devin, and Disconnect all clients. See MCP server.
Settings that live elsewhere
Section titled “Settings that live elsewhere”- Triggers belong to projects: open a project’s Triggers tab, or All triggers in the ⌘K palette. See Projects.
- Project settings (workspace, commands, variables, environment) are on each project’s Settings tab.