Skip to content

Reference ​

The Guide is the how — how to run an agent, wire up a channel, build a document. This section is the what: a screen-by-screen tour of Codeg's Settings, how the app is built, how it treats your data, and how to build it from source. Reach for it when you're staring at a specific toggle and want to know exactly what it does.

Some of Codeg's settings screens are big enough to have their own how-to in the Guide — MCP, Skills, Agents. The rest are configuration you set once and forget. The map below covers all of them, so you can always find where a screen is documented, then jump to it.

The Settings surface ​

Codeg gathers every preference into one Settings window (its sidebar is headed Preferences). Here's the whole surface, in the order the app lists it, and where each screen is documented:

Settings screenWhat it controlsDocumented in
AppearanceTheme mode & color, window zoom, fonts, desktop petAppearance
GeneralDefault terminal, command-output colour, rendering, what the close button does, desktop notifications & soundsGeneral
MCPModel Context Protocol servers — add, scan, enable per agentGuide → MCP Servers
SkillsWrite and edit your own agent skillsGuide → Skills
Skill PacksCurated bundles — Experts, Science, OfficeGuide → Skills
CollaborationDelegation between agents, and the in-conversation tools each agent is givenCollaboration
AgentsThe agent CLIs — connect, configure, run preflight, and register your ownGuide → Working with Agents
Model ProvidersAPI provider credentials for agentsGuide → Authentication & Models
BrowserThe built-in browser — where links open, site rules, what agents may see and do on a page (desktop only)Browser
Quick MessagesReusable message snippets for the composerQuick Messages
ShortcutsKeyboard shortcutsShortcuts
Version ControlGit executable, GitHub, GitLab and other Git accountsVersion Control
Chat ChannelsIM bots for notifications and remote controlGuide → Chat Channels
Web ServiceExpose Codeg to a browser — port, token, QR (desktop only)Web Service
Runtime LogsDiagnostic logs — level, live viewer, filesRuntime Logs
SystemUpdates, launch at login, network proxy, language, backup & restoreSystem

Opening Settings lands you on Appearance. Every screen is identical whether you run the desktop app or reach Codeg through a browser — with two exceptions, both dropped from the nav in a browser session: Web Service, because it's the screen that turns on browser access in the first place, and Browser, because there's no engine to embed in a browser tab and every link goes to your own browser instead.

Six screens have a full how-to in the Guide

MCP, Skills, Skill Packs, Agents, Model Providers, and Chat Channels are features you use, not just settings you tweak — so they're written up as task guides. The ten remaining screens are covered here, in reference form.

The map moves when the app does

Collaboration and Browser are new entries in 0.31.2, split out of General — delegation and the in-conversation tools onto one page, the built-in browser onto another. General is the app-behaviour screen it was always named for.

Architecture & Security ​

How Codeg is built, and how it handles what you give it.

  • Architecture — one Rust core, three binaries: the codeg desktop app, the standalone codeg-server, and the codeg-mcp companion that powers delegation. How the pieces fit, and how they drive external agent CLIs over ACP.
  • Privacy & Security — what stays on your machine, when the network is actually touched, and how agent credentials and web-service tokens are handled.

Contributing ​

  • Development — requirements, the build commands for each binary, and the dev loop for building Codeg from source.

Everything here describes the app you actually run — desktop or server. For the project itself — the people behind Codeg, the community, and the license — see About.