Settings

Click the gear icon in the header (or use the header menu → Settings) to open the Settings dialog.

General

Appearance

Choose between Light, Dark, or System theme. The System option follows your operating system's preference.

Language

Switch the interface language. Currently supported: English and Magyar (Hungarian).

The language setting affects all UI text — menus, buttons, dialogs, and system messages. It does not change the language the assistant responds in (that depends on the language you write in).

Tool Approvals

Configure how the assistant's tool calls are approved. See Permissions for full details.

Key options:

• Default approvals mode — what a new conversation starts in: Ask, Auto, or Always allow. Change it per conversation from the Approvals control next to the composer (or F4 in the TUI).
• Deny rules — block specific operations automatically
• Allow rules — auto-approve specific operations
• Operator rules — what your administrator configured, shown read-only

Your rules and your default mode are stored against your account on the server,
so every browser and the TUI see the same thing.

Shared Conversations

Manage your shared conversation links. See Sharing for details.

Models

Available when the administrator has enabled thinking modes. Every mode is a
card — what it answers with, the effort it starts at, and a relative cost — and
Set default picks the one your new conversations start in. Below the
cards, the role map says which model each background role resolves to, and
Connections (when Model Profiles is enabled) is where you add your own
endpoints. See Thinking modes. The composer's
"Manage modes…" opens this pane.

User Secrets

Available when the administrator has enabled the User Secrets extension. Use this pane to store API keys, tokens, and other credentials that plugins and tools need on your behalf — encrypted at rest and never shown to the assistant.

Secrets. Give each one a short name (letters, digits, _-), paste the value, and optionally describe what it is. After saving, the value is hidden; you can overwrite it by editing the secret, and you can delete or rename it at any time. Plugin configuration that contains the placeholder ${secret:<name>} will substitute your value at the moment the plugin needs it.

Shell-tool env bindings. If you want the assistant to be able to run a command-line tool that expects an environment variable (for example gh looking for GITHUB_TOKEN), add a binding: pick the secret, pick the env var name. The next shell command the assistant runs will see the variable set, but the value does not appear in the conversation and the assistant can't read it.

Expose to agent (advanced). Each binding has an "expose to agent" switch. Turning it on also sets the variable in the assistant's own process environment for the duration of your turn. Only enable this if you are running Codumentor locally for yourself — in a shared deployment the environment is visible to concurrent turns.

Extensions

View and configure settings for installed extensions. Extensions that expose configurable options will appear here automatically.

If no extensions have settings, this tab will be empty. This is normal — not all setups include configurable extensions.

Google Workspace

Here you connect your Google account so the assistant can work with your Gmail, Calendar, Docs, Sheets, and Drive.

First time only: set up Google. Google has to know about your Codumentor before anyone can connect. In a personal install the extension is already switched on, but you register it once with Google yourself (about ten minutes, no cost):

1. In Google Cloud Console, create a project, enable the Google APIs, and create an OAuth client ID of type Web application.
2. Register this redirect URI for it, exactly as written: http://127.0.0.1:2638/oauth/callback/google. Use 127.0.0.1, not localhost; Google treats them as different addresses.
3. Put the client ID and secret into your ~/.codumentor/config.yaml, then restart Codumentor.

The Google Cloud setup guide walks through every click, including what to do when Google shows an error. If Codumentor runs on a server rather than your own computer, the redirect URI is different; the guide covers that too.

Connecting. Pick which products to grant (and whether each is read-only or read-and-write), then click Connect. Google's consent screen opens in the browser.

You can later change those choices or disconnect. Sending mail, changing a calendar, or editing a Doc/Sheet still asks for approval in the chat, the same way a shell command does.

In a shared installation, if you do not see this section, your administrator has not enabled the extension, or your role cannot manage OAuth connections.

Personal Recall

Controls whether the assistant looks through your own earlier conversations at the start of a turn, how eagerly it does so, and whether it stays inside the workspace you are working in. The three settings, and what recall can and cannot see, are explained in Organizational Memory → Your own earlier conversations.

If you do not see this section, your administrator has not enabled the extension, or has turned automatic recall off for this deployment — the assistant can still search your history when it decides to.