---
title: Assistant Settings
slug: assistant-settings
description: Configure the assistant's models, tools, memory, voice, channels, skills, and coding-agent access.
productSlug: cedros
productLabel: Cedros
sectionKey: settings
sectionLabel: Settings
---
# Assistant Settings

The Assistant settings page is the control board for your site's primary assistant. Use it to review readiness, choose how models are provided, approve tools, manage memory and skills, shape the assistant's voice, connect chat channels, and configure coding-agent access. To talk to the assistant, see [Assistant Chat](assistant-chat.md).

## Before you start

- Editing shared assistant settings requires the **data:settings:write** permission. Without it, those controls are read-only and the header says **Missing data:settings:write permission**.
- **Memory**, **Skills**, and the **Voice & character** subpage require assistant memory access. If that access is disabled, those destinations are hidden and old direct links return to **Overview**.
- Some workspaces use **Cedros Providers** to manage model routing. In that mode, Cedros owns the routing configuration, so **Jobs** and **Autonomous tasks** are hidden. Switch **Provider source** to **Your API keys** to manage those settings on the site again.

## What's on this page

The top-level tabs are **Overview**, **Tools**, **Jobs**, **Memory**, **Skills**, and **MCP**. **Jobs** is available only when the site owns its provider routing. **Memory** and **Skills** appear only when memory access is allowed.

Most controls backed by the shared AI settings save automatically after you stop editing. **Memory**, **Skills**, **MCP**, and **Channels** use their own APIs and show their own save or status feedback instead of the shared draft indicator.

### Overview

The default tab combines the assistant's status and core controls:

- **Assistant status** summarizes the active model, business context, approved tools, voice, autonomous tasks, and connected channels. Every tile is an **Open →** link to its corresponding control or subpage. If no intelligence provider is ready, the page shows an **Assistant setup needs attention** notice.
- **Processing loop** shows how each request is prepared, routed, enriched with context, answered, and learned from. When the site owns routing, you can toggle optional steps, choose their models, and apply the recommended setup. With Cedros Providers, this is a read-only explanation of the managed flow.
- **Default model** contains the **Provider source** switch when Cedros Providers is installed. In self-managed mode, it also shows the default provider and model. In managed mode, Cedros chooses the routing and the site-level provider and model fields are hidden.
- **Provider fallback** is available in self-managed mode so you can choose backup providers.
- **Voice & character**, **Autonomous tasks**, and **Channels** open focused, bookmarkable subpages with their own breadcrumb and page title. The parent Assistant title and tabs are hidden on these routes.
- **Health checks** review approved context and tool access. The full test creates temporary records, reads them back, and removes them. When a flow is blocked only by tool access, the summary at the top offers to raise the areas that own the missing tools — the same areas and levels the Tools tab shows — and asks first when that would allow publishing or widen a sensitive area.

#### Voice & character

This subpage edits the active personality's `soul.md` document: its character, tone, boundaries, and default behavior. The footer shows save state, an estimated token count, and the personality archetype. It requires memory access.

#### Autonomous tasks

This subpage configures task execution models, evaluator and escalation models, retry limits, and the owner edit window before work starts. It is available only when the site owns provider routing.

#### Channels

This subpage connects Telegram and Discord to team chat, personal direct messages, and Council. Each platform has its own token or secret, enable and test controls, account links, and channel bindings. Saved secrets are write-only and are never displayed again.

### Tools

The Tools tab controls how far the assistant can go. One access level — **None**, **Read**, **Edit**, or **Publish** — applies to the whole site from the top card, and twelve areas of responsibility can each be set lower or higher underneath it. Areas that change how the site runs (settings, team accounts, data, backups and security) are grouped separately. Search finds which area owns a given tool. Tool access still respects each tool's permissions and write mode.

### Jobs

The Jobs tab assigns providers, models, prompts, context sources, fallback chains, and plan access to background assistant jobs. Live Assistant Chat is intentionally excluded. This tab is hidden while Cedros Providers owns routing and returns when **Provider source** is set to **Your API keys**.

### Memory

The Memory tab lists what the assistant has saved across conversations. Search, create, inspect, edit, or delete memories; the list is paged at 25 items. This tab requires memory access and uses its own save actions. See [Memory](memory.md) for the runtime experience.

### Skills

The Skills tab lists installed service, workflow, and custom skills. Filter or search the list, enable or disable a skill, add a custom skill, or open a skill to edit its instructions and review permissions, capabilities, allowed jobs, and workflow steps. Skill changes use their own save actions. See [Skills](skills.md) for more detail.

### MCP

The MCP tab connects Codex, Claude Code, and other compatible coding agents to this site's MCP endpoint and coordination tools.

- Generate, list, and revoke personal MCP API keys. A newly generated key is shown only once, so copy it immediately.
- Copy a setup prompt containing the site's MCP connection details into a supported coding client.
- Review client setup status and use agent mail to coordinate registered coding sessions.

## Common tasks

### Choose who manages model routing

On **Overview**, use **Provider source**:

- Choose **Cedros Providers** to let Cedros manage routing. Site-level **Jobs** and **Autonomous tasks** controls disappear because changes there would not take effect.
- Choose **Your API keys** to restore site-owned provider, model, fallback, job, and task controls.

The Provider source switch appears only when Cedros Providers is installed and active. If the extension is unavailable, the site manages its own providers as usual.

### Apply recommended model settings

In self-managed mode, open **Processing loop** on Overview and choose **Use recommended setup**. The action is disabled until enough provider configuration is available for the recommendations.

### Approve tool access

Open **Tools** and pick one level for the whole site, then adjust individual areas. On a new site, **Use the recommended setup** lets the assistant draft everyday work for review and keeps it read-only on the sensitive areas. Choose **Publish** deliberately: it lets the assistant make changes go live.

### Configure voice, tasks, or channels

Use the linked status tiles on **Overview** to open the relevant subpage. Choose **Back to Overview** when finished. The **Voice & character** tile requires memory access, and **Autonomous tasks** is hidden when Cedros Providers owns routing.

### Connect a coding agent

Open **MCP**, generate an API key, and copy it while it is visible. Then copy the setup prompt into your coding client and follow the resulting instructions. Revoke keys you no longer use.

## Troubleshooting

- **Every shared setting is disabled?** You need **data:settings:write**. Ask an administrator for access.
- **Memory, Skills, or Voice & character is missing?** Assistant memory access is disabled for this site.
- **Jobs or Autonomous tasks is missing?** Cedros Providers currently owns routing. On Overview, change **Provider source** to **Your API keys** if the site administrator intends to manage providers directly.
- **An old Jobs or Autonomous tasks link opens Overview?** Managed mode intentionally blocks those inactive controls, including stale direct links.
- **Assistant setup needs attention?** Connect an intelligence provider or switch to a provider source that is ready.
- **Use recommended setup is disabled?** Finish configuring the required providers first.
- **A Memory, Skill, MCP, or Channel change does not appear in the shared draft indicator?** Those destinations save through their own APIs and display their own status.
- **A new MCP key disappeared after leaving the page?** Keys are shown only once. Generate a new key and revoke the old one if it was not copied.
