The Settings screen

Settings is where you set HarmFlow up on your Mac once it is installed: the daemon, the AI tools it found, the folders it keeps its files in, and the token of its local API. Open it with Settings in the sidebar, with ⌘5, or with ⌘,.

Its sections

The screen lists its sections on the left and shows the open one beside them. The list has three groups, then About on its own at the foot:

• Interface: General, Notifications, and Shortcuts.
• Execution: AI tools and Paths.
• This computer: Daemon, Storage, and Security.

What each section holds:

• General: the interface's language (see The interface's languages), the menu bar options, and whether an execution's detail shows a banner for each restriction its AI tool does not enforce.
• Notifications: the notification level (see the notification level) and, in the desktop app, an Allow notifications button that asks macOS for its permission.
• Shortcuts: HarmFlow's keyboard shortcuts, grouped by where they work.
• AI tools: the AI tools and the command-line tools the app found, and the share of each AI tool's quota HarmFlow may spend (see the quota share).
• Paths: the path variables a task's paths can use, and the folders, beside your home folder and the mounted volumes, where a task's paths may lead.
• Daemon: whether the daemon is running, and the autostart option.
• Storage: the disk space HarmFlow uses and the folders it keeps its files in. It also holds how long execution logs are kept and the clean-up of workspaces, which are topics of their own.
• Security: where the local API's access token is stored, and a button that replaces it.
• About: the versions of the desktop app and of the daemon.

The menu bar and autostart options

The menu bar options are in General, in its Menu bar panel:

• Show HarmFlow in the menu bar. With it on, closing the window only hides it.
• Keep HarmFlow in the menu bar when quitting with ⌘Q. With it on, ⌘Q only hides the window; with it off, ⌘Q closes the dashboard and the menu bar. It can be turned on only while HarmFlow shows in the menu bar.

The autostart option is in Daemon, in its Startup panel: Start the daemon automatically with the system. It is off by default. With it on, the daemon, and the menu bar if it is shown, start when you sign in to your Mac.

The daemon keeps running whichever way these options are set: closing the window or quitting the dashboard does not stop it. Daemon's Status panel says whether it is running, with its process ID and how long it has been up, and has a Stop daemon button; while the daemon is not running, the desktop app shows a Start daemon button instead.

What AI tools shows

AI tools has one card for each AI tool HarmFlow runs, Claude Code and Codex, and a Detect again button that looks for them once more.

• A detected tool shows its version and its path, and whether it is ready: Ready, or a status such as Not ready, with a diagnostic that says why when there is one. Its card also says where the path came from, the installations found, whether it is signed in, and when it was last checked. You can set its path by hand, or let the app detect it again. Claude Code's card can also have a field for a long-lived token.
• A tool that is not detected reads Not detected, with the status Not installed. The app never installs or updates an AI tool: install it, then use Detect again, or set its path by hand.

Below the AI tools, the Command-line tools panel shows the two tools HarmFlow uses for its GitHub work, Git and the GitHub CLI (gh): each with its version and its path when detected, and Not detected otherwise. Credentials are never shown.

The folders Storage shows

Storage shows the disk space HarmFlow uses, and lists the folders it keeps its files in, and its runtime file, each with its path, as the daemon reports them:

• HarmFlow folder
• Tasks
• State
• Logs
• Workspaces
• Execution directories
• Runtime file
• Built-in agents and skills

In the desktop app, each one has a Show in Finder button, which opens it in the Finder.

The access token

The dashboard talks to the daemon over a local API that asks for an access token. Security says where that token is stored: in the macOS Keychain, or in a file readable only by you.

The Replace API token button replaces it, after asking you to confirm. The daemon then refuses the old token, and the dashboard picks up the new one at once.