Kepler Documentation

Settings

Last updated: October 2026

Use Settings to change how Kepler, your agents, and your tasks work. Settings has 15 pages. For what each setting on a page does, its default, and what changes when you change it, open that page’s reference from The Settings pages.

To open Settings, click the gear icon in the top bar, or press ⌘ , (Ctrl , on Windows and Linux). To close it, click the gear icon or press the same shortcut again.


Settings open on Repositories. The Settings sidebar starts with Search settings and Setup, then lists Account; Agents, Tasks, Repositories, Integrations and Actions; General, Notifications, Appearance, Voice input and Keyboard shortcuts; Remote environments and Remote Access; and Updates and Help, with Repositories' section links expanded under it.
Settings, open on Repositories.

The Settings pages

The Settings sidebar, down the left of Settings, starts with a Search settings field and Setup, a progress ring that reopens the first-run checklist. Below them, the sidebar lists the following pages, in this order:

Page What it covers
Account Who you’re signed in as, your organization, what your plan unlocks, and GitKraken AI credits
Agents Your agents, custom agents, MCP servers, agent tools, approvals, and usage limits
Tasks How new tasks start, including the default agent and the agent new sessions start with, and how a task’s page looks
Repositories The repositories folder, your repos and folders, worktrees and branches, and Projects
Integrations Issue tracker and Git host connections, and sessions started in your own terminal
Actions Preferred Actions per item kind, and the Action list
General Language, windows, the default editor, and keeping agents running
Notifications Which agent events notify you, on the desktop and in Kepler
Appearance Light or dark appearance and themes, the chat, the terminal font, code font size, and diff layout
Voice input On-device speech-to-text, its transcription engine, and learned words
Keyboard shortcuts Kepler’s keyboard shortcuts
Remote environments The machines your agents can run on, over SSH or WSL
Remote Access Opening this Kepler from another device
Updates The installed version and app updates
Help The docs, release notes, onboarding guides, and Kepler’s logs

Account is the only page about you rather than the app. The account menu opens it.

Find a setting

To find a setting by name, type in Search settings. Search matches section titles, control labels, help text, and common synonyms, so a word like theme or notifications finds the right section. With no match, the results read No settings match “{query}”.

To go straight to one setting, type @id: followed by its id, such as @id:terminal.font-size. Case does not matter. The results show that one setting under its page and section. Choose it to open the page on that control. If this version of Kepler has no setting with that id, the results read No setting has that id. Settings links use the same ids.


The Search settings field in the Settings sidebar holding @id:terminal.font-size beside its Clear search button, with a single result in place of the page list: Font size, under Appearance › Terminal.
Finding one setting by its id.

Ask Kepler and your agents can also search Kepler’s settings, and change one when you ask. They link you to a setting with a settings link. Some changes need your approval first. Settings that hold secrets, such as your account or integrations, can only be linked. See Finding and changing settings.

To jump to a section, use the section links the Settings sidebar shows under the page you have open. Under Agents, the sidebar also lists each supported agent below Your agents. A page with fewer than 2 listed sections shows no section links.

Sub-pages and unsaved changes

When you open an item to edit it, such as a repository, a project, a custom agent, an MCP server, or an Action, it opens as a sub-page inside its Settings page, with a breadcrumb back to the page.

If you leave a sub-page with unsaved changes, Kepler asks before it discards anything. It asks however you leave: Escape, Back, the form’s own Cancel, a page in the Settings sidebar, or a link elsewhere in the app:

  • A form that can save asks Save your changes?, with Cancel, Don’t save, and Save.
  • A form that has nothing to save yet, such as a step-by-step add flow, asks Discard your changes?, with Keep editing and Discard.

A form with a Save button keeps it in a footer with Cancel. While you have unsaved edits, the footer reads Unsaved changes. If a save fails, the footer shows why and keeps your edits on the form. When a save succeeds, Kepler confirms with Saved {name}.

Most fields outside those forms save themselves. Each one shows its own status beside it: Saving, Saved, or Unable to save with the reason. A switch shows only Saving and a failure. If a save fails after you’ve left the page, Kepler tells you which setting it was: Unable to save {label}.

Back, or your mouse’s back button, steps back through each page, sub-page, and search result you opened in Settings. To leave Settings in one click from any page or sub-page, use the back arrow in the Settings header, the gear icon, or ⌘ , (Ctrl ,). Each one returns you to what you were doing before you opened Settings.

Settings in a remote window

In a window connected to a remote environment, Settings shows that machine’s settings, and its header names the machine. Under its title, each page says where its settings are saved:

  • Saved on {machine}: on the remote machine.
  • Saved on this machine: on your own computer. Its tooltip reads Applies to every Kepler window on this machine, whichever machine it’s connected to.

A section that saves somewhere other than its page has its own badge. To change this machine’s own settings from a remote window, click Open this machine’s settings in the header. The same page opens in a local window.

Some settings are kept on your own computer, such as the language, the default editor, the themes, the terminal and code fonts, and the diff layout. When Ask Kepler or an agent in a remote window changes one of these, the window applies the change on your computer, the same as its Settings page would. A notification names the change, with Undo. See Finding and changing settings.

Deep links and section anchors

Every section has a stable anchor id. A link of the form /settings/<page>#<section-id> opens that page and scrolls to the section.

/settings on its own opens the last page that window had open, or Agents if it had none. Older links of the form /settings#<section-id> still work: Kepler finds the page that owns that section and keeps the hash. An id that no page owns anymore, such as general, windows-and-notifications, keyboard-shortcuts, or features, opens Agents.

The following table lists each page’s path with its section anchors, in page order:

Page path Section anchors, in page order
/settings/account account, plan-features, ai-credits
/settings/agents agents, ask-kepler, custom-agents, mcp-servers, agent-git-tools, approvals, usage-limits
/settings/tasks new-tasks, default-agent, task-page
/settings/repositories repositories-root, repositories, worktrees, projects
/settings/integrations provider-integrations, agent-options
/settings/actions preferred-actions, action-list
/settings/general language, windows, default-editor, keep-running
/settings/notifications system-notifications
/settings/appearance appearance, transcript, terminal, code, diff-view
/settings/voice voice, voice-engine, voice-dictation, voice-learned
/settings/keyboard-shortcuts shortcuts-general, shortcuts-navigation, shortcuts-dashboard, shortcuts-task-page, shortcuts-chat, shortcuts-changes
/settings/remote-environments remote-environments, found-machines, remote-windows
/settings/remote-access remote-access
/settings/updates updates
/settings/help onboarding-help, logs

A few anchors work differently, and some items have anchors of their own:

  • default-agent is inside New tasks, not a section of its own.
  • ask-kepler is not a section of its own either. It marks the default agent picker for Ask Kepler at the top of the Agents page.
  • From the Settings sidebar or search, worktrees opens the Worktrees and branches sub-page instead of scrolling to its row.
  • Each agent has an anchor on the Agents page, agent-<agent-id>, for example agent-claude-code. Each custom agent has custom-agent-row-<id>.
  • Each setting’s control has the anchor setting-<id>, where <id> is the setting’s id, for example /settings/appearance#setting-terminal.font-size.

When search, a link, or a pointer on another page sends you to one setting, Kepler waits for its control to load, highlights it, and moves focus to it. The highlight then fades. If the control is in a collapsed part of the page, such as an agent’s program and data folder, Kepler opens that part first. If the control does not appear, Kepler explains why instead:

  • An agent setting the agent’s card does not show reads This agent shows that setting only when it is turned on and supports it.
  • A setting that depends on something else reads This setting appears once what it depends on is set up.
  • Otherwise, Kepler fills Search settings with @id:<id>, so you can see where the setting lives.

Settings links

A kepler:// link opens Settings from anywhere: another app, a terminal, or an agent’s reply in Kepler, where it’s clickable.

Link Opens
kepler://settings Settings
kepler://settings/<id> Settings on one setting’s control, for example kepler://settings/terminal.font-size

A setting id is a list of lowercase words separated by dots, and a link matches it in any case. A settings link only opens Settings: it never changes a setting, and a value added to the link is ignored. A link to an id this version of Kepler does not have opens Settings with That setting isn’t in this version of Kepler.


Have feedback about this article? Did we miss something? Let us know!
On this page