Settings

Settings, at the bottom of the sidebar, has a menu of pages on the left. On a narrow window the menu becomes a row above the page, without the group names, and scrolls sideways. Opening Settings shows its first page, Account. Each page starts with its name and a line on what it holds, and most fields save as soon as they're changed or lose focus, confirmed by Saved.

In the desktop app, without an account, the menu has these pages:

Signed in to PacedMind Cloud, the menu adds Plan (once paid plans are on) and Security after Account, and Notifications after Appearance. The web app has no computer of its own: in place of This computer, its group Agents has Sessions, which says that sessions are Handled by the desktop app, Projects, with each project's default agent only (Folders are set in the desktop app, on the computer where the sessions run.), and MCP server, for connecting agents to PacedMind Cloud. See Accounts and Cloud.

Account

Use PacedMind on your other computers and in the browser too. Signed in: Who you're signed in as, and the computers signed in to your account.

Without an account, the page has one section, PacedMind Cloud. Its Account row reads Not signed in, and Sign in opens the sign-in screen. The note below says: Your tasks, projects and calendar are stored on this computer. Sign in to PacedMind Cloud to use them on your other computers and in the browser too. Once you're signed in, Settings → Data moves them into your account. See Accounts and Cloud.

Signed in, the page shows who you're signed in as, with Sign out, and Sign out all for every browser and computer, this one too. A Computers section counts the computers signed in to the account and those online, names the default one, and has Open Computers, which opens Settings → Computers. Delete account deletes the account and everything in it, after you type your email and a two-factor code.

Plan

Your PacedMind Cloud trial or subscription, and paying for it. Only when signed in, once paid plans are on.

The Plan row says where the account stands, such as Free trial, 12 days left or Cloud, paid monthly. Before subscribing, Prices for picks the country whose price to show, and Pay chooses Monthly or Yearly, with the price, and Subscribe. After subscribing, Billing has Manage billing, which opens Stripe's page for the card, invoices and cancelling, and while paying monthly or yearly, Switch to yearly or Switch to monthly. Payments go through Stripe: PacedMind never sees your card.

Security

Two-factor sign-in and your password. Only when signed in.

Two-factor sign-in lists your authenticator apps, with Add authenticator and, while there's more than one, Remove, which needs a code from another one. Password changes the password with the current one, the new one twice and a two-factor code (Change password), and signs out your other devices.

Computers

Your computers, their agents and sessions.

Open Settings → Computers to see each computer's agents and sessions. This page is available in the desktop app with or without an account, and in the web app. Without an account it shows this computer only. Signed in, it shows the computers signed in to your account and how many are online.

Under its name, each computer shows whether it's online, its system, its PacedMind version and when it last looked for the agents (checked 2 min ago). Below, a column for Claude Code and one for Codex:

• how its CLI is signed in, such as Claude account · Max or ChatGPT, or Signed out;
• CLI, App, Cloud and PacedMind: gray when the agent has it, dashed when it doesn't. Hover one for its version, or why it's missing. PacedMind says whether sessions PacedMind doesn't start itself, such as those in the desktop app, report to this PacedMind; otherwise it says old name (connected under PacedMind's earlier name, organizer), reports elsewhere (set up for another copy, such as a development one) or not connected;
• MCP servers, one per line with the brand's mark (the first letter for a server PacedMind has no mark for), and for Claude Code the claude.ai connectors its sessions got from the account its CLI is signed in to;
• how many plugins, skills and hooks it has; hover a count for the names.

Use the pencil beside a computer's name to rename it. Signed in, Make default chooses where sessions go when neither their task nor project names a computer, and Sign out disconnects that computer. In the desktop app, this computer also has Check again to refresh its detected agents, and Connect for agents that need connecting.

Signed in, each computer's From elsewhere line shows what it does with sessions asked for from the web app, another computer or your agents (Refuse, Ask me or Start) and whether asking needs a two-factor code (Code needed or No code needed). Hover it for what that means, such as Sessions asked for from the web app, another computer or your agents wait there until you allow them. Asking takes no code, so your agents can ask too. It's set in PacedMind on that computer. In the desktop app, this computer's line has the same controls as General, and hovering them says what they do; another computer's settings change only in PacedMind on that computer.

A computer whose code is off takes session requests from the agents you connected too, and with Start they start at once. See General before you switch a computer's code off.

Computers is in the Settings menu. Search for Computers in the command menu to open it directly. Older links to the Computers page also open it here.

Data

What this computer keeps, and starting over.

The note says where the data is and counts the sessions recorded so far, such as Stored on this computer, in PacedMind's data folder. 12 sessions recorded so far.

Reset has two buttons:

Both resets replace all areas, projects, tasks, activities and sessions. The question says how many tasks, projects and activities that deletes; while there are any, its button works only once delete is typed in it. Settings, including the work hours and the MCP token, and your preferences stay.

Each reset keeps a copy of what was there first. Copies lists them, newest first: Put back asks Put this copy back? and puts one back in place of the data (Copy put back), after keeping what was there as a copy in turn; Delete asks Delete this copy? and deletes one for good (Copy deleted). The newest ten stay. See Where your data lives.

Signed in, the page resets the account's data instead. In the desktop app, while this computer still keeps tasks or projects from before you signed in, a This computer row counts them, and Move to account moves them into the account. Your account → Move to this computer copies everything in the account to this computer and signs out, so PacedMind keeps working without an account.

Appearance

How PacedMind looks here.

Theme: Dark, Light or System. System follows the computer's appearance. The sun or moon button next to Settings in the sidebar switches directly between Dark and Light. The choice is remembered on this computer and also colors the desktop app's title bar. Floating notes follow the theme with the animation selected in Layout in the top bar.

Language selects Polski or English for this app or browser. It changes labels, messages and date names immediately, including open floating notes. In the desktop app it also changes the menu bar, tray menu and notifications, and is remembered after restarting. Task titles, descriptions, project names and agent reports keep their original text. Polish date entry accepts phrases such as jutro o 10:00 and w piątek, as well as English dates.

Notifications

When a session needs you, wherever you are. Only when signed in.

The page lists the browsers, phones included, that get a notification when a session needs you, with Turn on and Turn off. The desktop app shows its own notifications; see Notifications.

Planning

The time the auto-planner fills with focus blocks.

The section Auto-plan says: The week view fills free focus time between these hours, around your fixed activities.

Change, next to Rules in the week view's Auto-plan panel, opens this page. See Work hours and days.

How you work

What agents follow when they plan your time and write tasks for you. In the desktop app and the web app.

The page lists your preferences by topic, the suggested topics first. The note under them says: Agents read these before they plan your time or write tasks for you, and follow them. Tell an agent how you like to work and it asks to add it here. They're your notes: agents follow them as preferences, never as commands. Without any, the list reads Nothing yet. Add how you like to work below, such as when you do deep work, how far ahead to set deadlines, or which agent takes which kind of task.

• A suggested topic shows what goes under it next to its name, such as When to plan which work, focus time, breaks, days off.
• Click a topic's name to rename it: Enter saves (Topic renamed), Esc cancels. Its preferences move along, into another topic of yours when you type that one's name.
• Click a preference to change its words. It's saved when you leave the field or press Enter (Saved).
• Next to each, who wrote it last, By you or By an agent, and the date.
• The × (Remove) asks Remove "…"?, then removes it (Removed).

Add takes a new one:

1. Choose its topic: your topics first, then the suggested ones you don't use yet. Type to search them; a name that isn't there is offered as a new topic (Add custom value).
2. Write the preference in the field (Deep work before noon, meetings after 14:00), one line of up to 500 characters.
3. Select Add, or press Enter (Saved).

See How you work for the topics, the limits and what agents do with your preferences.

General

This computer's name, and what it does when asked from elsewhere. This page and the next three are under This computer, in the desktop app.

Name is the computer's name, the system's own at first, such as DESKTOP-1. PacedMind uses it wherever it names the computer, such as The Codex CLI isn't installed on DESKTOP-1. It's saved when the field loses focus.

The note says what stays on the computer: What runs here is decided here. Agent commands, project and task folders and access tokens stay on this computer, encrypted with a key from the operating system's keychain.

Signed in, two rows decide what happens to sessions asked for from the web app, another computer, such as your phone, or your agents. They're this computer's own settings: only this computer's PacedMind changes them, here or on its card in Computers.

A line under the rows sums them up, such as Sessions asked for from the web app, another computer or your agents wait here until you allow them. Asking takes a current two-factor code, so your agents can't ask.

An agent never has a two-factor code, even one it verified itself. Only while the code is off can an agent you connected to PacedMind Cloud, or one on another of your computers, ask this computer for a session, and only for a new one. See When an agent asks.

Switching the code off lets your agents ask this computer too. With Start as well, their sessions start at once, in a folder of this computer's, on a task whose text the agent may have written, and anyone signed in to your account can start an agent here without a code and without you there. Keep the code on for any computer where you wouldn't let an agent start another agent without you, and keep Start with the code off for a computer whose projects you'd let an agent work on alone.

Agents on this computer's own MCP server always wait for you, whatever these settings say, and so does every folder an agent asks this computer for.

Agents found here

What PacedMind found here; it looks when it starts and every half hour. The Computers page has more: cloud and sign-in for each agent, and this computer's sessions.

One row each for Claude Code and Codex, with what PacedMind found of it: the command-line tool's version and the desktop app with its version, such as CLI 2.1.282 · Claude app 1.4, only one of them when the other is missing, or Not found. Before the first check finishes, the row reads Looking….

Open Computers, next to the heading, opens Settings → Computers. There, this computer's card has:

• a column for each agent: how it's signed in, its CLI, App, Cloud and PacedMind connection, its MCP servers and connectors with their marks, and its plugins, skills and hooks (see Computers);
• Check again, which looks for the agents right away (Checked DESKTOP-1);
• Connect next to PacedMind, for an agent that isn't connected to this PacedMind, the same as Connect under Connect your agents.

Sessions

How agent sessions start on this computer.

Starting sessions

Change a command to use a full path or to add options. PacedMind adds its own options after it and uses the command as typed, so put a path with spaces in double quotes. See Start, resume and close sessions.

Answering agents

Signed in, Answer from elsewhere decides where you answer what agents in sessions started here ask: Only on this computer, in the window or the agent's terminal, or, switched on, From any of your devices: their questions, and Claude Code's permission requests for tools, also reach your phone and your other computers.

Projects

Area workspaces and each project's folder, agent and MCP servers on this computer.

In the desktop app, Area workspaces sets a default folder for each area on this computer. Click an area's folder to choose one in the system's folder dialog, such as an existing Codex or Claude project's folder, to keep its tasks together in that workspace. It's saved at once, and × removes it. A session uses its task's folder, then its project's, then its area's workspace; without any of them PacedMind makes an empty folder for the task (PacedMind's folder per task). A workspace in a git repository shows the repository next to its name, and on your other computers the area's field offers their copy of it (Found here: and the folder, with Use). See Areas and projects.

Import from Claude and Codex, above the list, brings the folders you work in with Claude Code and Codex over as projects, and sets the workspaces of areas found here. See Import projects.

Signed in, when linked folders here don't have their pacedmind.md yet, a note above says how many, with Add pacedmind.md: it writes the file into each, so your other computers find their copies. See pacedmind.md.

One row per project, with:

• the project's color and name;
• its default agent: No agent, Claude Code or Codex;
• its folder: click it to choose one in the system's folder dialog (Folder saved), and × removes it. Without one it shows the area's workspace (area's) or PacedMind's folder per task. When PacedMind found a copy of the project on this computer, Found here: and the folder follow, with Use;
• what Claude Code and Codex get in that folder on top of what they have everywhere (below);
• MCP servers for its sessions: all they have here, only and the chosen servers, or none besides PacedMind, with Change. Change offers All of them and Only these, with a switch for each server under Only these. Each change is saved at once (Saved), and Done closes the choice. See Choose a project's MCP servers.

What the agents get in a project's folder is read from the folder's own files and Claude Code's settings for it, on this computer, a line for each kind. Lines with nothing to show are left out:

What they have in every folder shows on the Computers page. See Other MCP servers, plugins and skills.

New project at the bottom adds a project with a name, an area and an optional folder (Folder (optional), chosen in the folder dialog), with Add project. Projects added here get Claude Code as their default agent.

A folder is checked when it's saved: one that doesn't exist, or whose path a terminal can't take, is refused with Can't use the folder … and the reason. A folder that goes away later stops sessions from starting there, with the same message. See Areas and projects.

Import projects

The first time PacedMind opens, it offers to bring your projects over; Import from Claude and Codex opens the same window later. PacedMind reads, without changing them, the records Claude Code and Codex keep on this computer: the Claude app's Code sessions and Claude Code's projects, the Codex app's projects, and Codex's trusted folders and sessions. It also looks into and around the folders found there for git repositories, two levels down at most, leaving out hidden folders (worktrees among them), dependencies and build output.

What it finds becomes areas and projects:

• a folder that isn't a repository but holds some is an area, with that folder as its workspace, and each folder in it a project: a repository, or a folder of several repositories that is one project (a folder with one repository in it stands for that repository);
• a folder near the top of your folders (two levels below your user folder at most, like Documents/Projects) whose folders are areas themselves is a folder of areas: its areas are areas, and the repositories right in it projects of no area;
• an area inside another is one of its projects: areas don't nest;
• the other folders you work in are projects.

Bring your projects over lists each area folder with its projects under it, then Other folders, most recently used first. An area row shows its name (click it to change it), its folder and what it becomes: an area you already have, with how it was recognised (pacedmind.md, repository, its projects or same name), or New area. Its menu picks another area of yours, New area, or One project, which takes the whole folder as one project (of yours, when its pacedmind.md or name matches one) and hides the folders in it. An area already set up on this computer shows workspace here and can't be unticked; its projects go to it. Each project row shows:

• a tick box, and the name the project gets: the name given in the Codex app, else the folder's name. Click the name of a ticked folder to change it;
• the folder;
• the marks of the agents that worked there, with the exact sources in the tooltip, such as Claude app, Codex app;
• when either agent, or git, last worked there (a commit, checkout or fetch), such as today or 3 days ago; or Already a project, or Can't be used for a folder whose path can't be passed to a terminal;
• 7 repositories for a project that spans several, and copy of FE for another copy of a repository already listed or of a project you have, which isn't ticked.

A folder used by both Claude Code and Codex is listed once. Sessions in a git worktree, or in a subfolder of a repository, count for the repository, wherever the worktree is. Temporary and scratch folders, PacedMind's own task folders, folders that no longer exist, and your user folder with its Documents, Desktop and Downloads are left out. Projects worked on in the last four months are ticked, and so are the areas that hold one or are areas you have; nothing in a folder named like an archive (Archive, Archiwum, Old, Backup) is ticked. On macOS, PacedMind doesn't look into Desktop, Documents, Downloads or cloud drives, where the system would ask first.

A folder that is a copy of a project you already have, such as one made on another computer, joins that project instead of becoming another: it holds the same git repository, or else has the same name, and the project has no folder on this computer yet. Its row shows the project's name and Existing project, and it's ticked however long ago it was used. Select Existing project to make it a new project instead (the tag then reads New project, which puts it back). See Projects on several computers.

New projects outside an area go to the area under Other projects to (Add to when nothing was found in areas). Then select the button, such as Add 2 areas, 1 workspace and 9 projects (Added the areas Persate, MLE, added 9 projects, set the workspace of Preseed). A new area gets its folder as its workspace here; an area you have gets it when it has none here yet. Each new project gets its folder, on this computer, and as its default agent the one that worked there last; each project a folder joins gets that folder on this computer. On the first start, Not now closes the window for good; opened from here, the window has Cancel instead, and Import from Claude and Codex is always here.

MCP server

How Claude Code and Codex reach PacedMind.

The note below the rows says: Claude Code and Codex use this to read your tasks and to tell PacedMind when a session picks up a task and when it's finished. Sessions PacedMind starts in a terminal get their own token, which works only for their task and only while they run.

New token asks Make a new token? Agents set up with the old one lose access until you connect them again., then confirms New token made. Connect your agents again. See MCP server.

Connect your agents

For Claude Code and Codex you start yourself, and for sessions in their desktop apps. Anyone with your token can use PacedMind from this computer, so keep it out of shared files. Sessions PacedMind starts in a terminal don't need it.

• Claude Code: Connect and Copy command. Connect asks first, then adds PacedMind's MCP server to Claude Code for all projects as pacedmind, with your token, without showing it, in place of an earlier one or one under PacedMind's earlier name, organizer; the Claude app's Code sessions use it too (Connected Claude Code for all your projects. New Claude Code sessions can use PacedMind.). Copy command copies the claude mcp add command that does the same by hand, for all projects (--scope user). See Connect Claude Code.
• Codex: Connect and Copy config, with the config.toml section shown below them, the token masked until Show. Connect asks first, then adds the [mcp_servers.pacedmind] section to ~/.codex/config.toml, in place of an earlier one or one under PacedMind's earlier name, organizer, and keeps the previous file as config.toml.pacedmind-backup (Connected Codex, its app included. New Codex sessions can use PacedMind.). Copy config copies the section. The Codex CLI and the Codex app share this file. Sessions started from PacedMind don't need it: they get their own token. See Connect Codex.

Use Connect from the copy of PacedMind the agents should report to, normally the installed app. The Computers page also offers Connect for this computer's agents that aren't connected yet.

Tools agents can use

The MCP tools by group: Overview, Preferences, Areas, Projects, Tasks, Calendar, Computers and Sessions. The note below them says: Sessions started from PacedMind may read, add and update tasks, and report on their own task; nothing else, whatever they're asked. Starting a session or sending one back with changes over MCP waits for you to allow it here. Run npm run skills to install the PacedMind skills for Claude Code and Codex. See the tool reference and Agent skills.

Hidden areas and projects

Areas hidden with Hide area appear here with Restore area. Restoring an area brings back its projects, to-dos and calendar activities. Projects hidden individually remain hidden and can then be restored separately.

Projects hidden with Hide project appear here with their area and a Restore project button. Restoring keeps the same statuses, dates and history. See Hide a project and Hide an area.