Configuration

AI Business OS keeps its configuration in a small number of plain text files inside the workspace. /setup fills in most of them the first time you run it, and you can change your own files at any time. This page lists each file, what it controls and how /update treats it.

The Configuration Files

File	What it controls	Who owns it	What /update does
.claude/CLAUDE.md	The master instructions Claude reads in every session	You	Never touched
.claude/company/	Your organisation, team, audiences, voice, brand and industry	You	Never touched
.claude/config/integrations.json	Calendar, email, meetings, storage and other connections	You	Never touched
.claude/rules/content-defaults.md	English variant, tone and formatting	You and the engine	Merges your edits with the new version
.claude/settings.json	Claude Code permissions and the safety hooks	The engine	Merges, keeping what you added
.claude/settings.local.json	Your personal Claude Code settings on this computer	You	Not in the workspace’s git history
.mcp.json	MCP servers the workspace registers	The engine	Not in the engine’s file list
.vscode/extensions.json	Extensions VS Code recommends	The engine	Merges your edits with the new version
.claude/engine-manifest.json	The list of engine files and their tiers	The engine	Replaced
.claude/suite-registry.json	Versions and dependencies of the PRIMA products	The engine	Replaced

CLAUDE.md

.claude/CLAUDE.md is the main instructions file. /setup replaces its placeholders with your company name, industry, workspace ID, GitHub repository and cloud storage path, and dates the customisation log. You can edit it freely afterwards, and CLAUDE.md and AGENTS.md Files explains how it is organised.

Company Files

The six files in .claude/company/ describe your organisation, and every skill reads them for context. /setup asks a question for each one, and Company Context Files describes what each file should hold.

integrations.json

.claude/config/integrations.json records which outside services the workspace uses. Until /setup runs, many values hold a list of options, such as "google-calendar | outlook-calendar | apple-calendar | notion-calendar | none". /setup replaces the calendar, storage and company values with your answers.

Section	What it records	What reads it
client	Company name, setup date, operating system, main computer	/setup fills in the company name and setup date. You fill in the rest
calendar	Provider, MCP server, whether it is on, access level, calendar names	/day, which lists events for the next seven days when enabled is true and the calendar’s MCP server is available. PRIMA CRM, if installed
email	Provider, MCP server, whether it is on, access level, address	PRIMA CRM, if installed
meetings	Video meeting provider and MCP server	PRIMA CRM, if installed
storage	Cloud storage provider and the path to your synced folder	Written by /setup
collaboration	Slack and Microsoft Teams details	No base command reads it
projectNumbering	Prefix, separator and digit count for project IDs	PRIMA Project Management. The base /newproject takes the format from the project register instead
projectManagement	Other project tools you use	No base command reads it
security	Sign-in method, data residency, compliance needs, backup frequency	No base command reads it
features	On and off flags such as morningBriefing and calendarIntegration	Written by /setup. No base command reads them
deployment	Version and customisation notes for support	No base command reads it

PRIMA CRM treats a value still holding the list of options as not connected. See How Project IDs Are Formed for project numbering.

Content Defaults

.claude/rules/content-defaults.md sets the English variant, tone and formatting for everything Claude writes. Because /setup fills in the English variant only, open the file and replace the remaining placeholders yourself.

- **Default tone:** [TONE_DESCRIPTION — e.g., Professional but approachable]
- **Formality:** [FORMALITY_LEVEL — e.g., Formal for external, conversational for internal]
...
| Emails | [CLIENT_EMAIL_STYLE] |

For example, Example Consulting might set the tone to “Clear and friendly”, the formality to “Formal for clients, relaxed for internal notes”, and the email style to “Short, first names, no sign-off slogans”. The file is customisable, so /update keeps your values, and the Content Defaults section of the Rules Reference describes the rest of the rule.

settings.json

.claude/settings.json is the Claude Code settings file for the workspace, and in version 3.0.2 it does two things.

• Permissions. It pre-approves Claude’s core tools, so Claude does not ask before each action. These are Bash, Edit, Write, Read, Glob, Grep, WebFetch, WebSearch, Task, Skill and NotebookEdit. The deny and ask lists are empty.
• Hooks. It registers the engine guard on the Edit, Write and MultiEdit tools and the safety guard on Bash. See Hooks Overview.

During /setup, Claude adds permissions for the calendar tools you connect, such as the three Google Calendar tools for listing calendars, listing events and reading an event.

This is a critical engine file, so the engine guard stops Claude editing it. When /update changes it, the update merges the two versions. It combines the permission and hook lists from both, and where the two disagree on any other setting, your value wins. The Engine Health check counts the file as intact while it still holds every engine permission and hook.

Note

Pre-approving tools does not mean Claude acts without limits. Claude still stops before anything that changes scope, commitments or client-facing work, under the Autonomy Levels rule, and the safety guard still blocks destructive commands.

settings.local.json

.claude/settings.local.json holds Claude Code settings that apply only on your computer. The workspace .gitignore excludes it, so it is never committed or shared through git. Put personal permissions and any hooks of your own here.

.mcp.json

.mcp.json at the workspace root registers MCP servers for the workspace. Version 3.0.2 ships one entry, prima-memory, which starts PRIMA Memory from .claude/mcp-servers/prima-memory/. That folder exists only after you install PRIMA Memory, and the .gitignore excludes it. See PRIMA Memory.

VS Code Extensions

.vscode/extensions.json recommends five extensions, which VS Code offers when you first open the workspace. They are Claude Code, OpenAI Codex, Ollama, Live Preview and Bearded Icons. Only Claude Code is needed to use AI Business OS.

Engine Manifest and Suite Registry

.claude/engine-manifest.json lists every engine file and its tier, the engine version and the release date. /update reads it to know which files it may change, and the engine guard and the pre-commit hook read it to know which files are critical. .claude/suite-registry.json records the versions, dependencies and install methods of the PRIMA products. Both are critical files that /update replaces, so do not edit them. See Engine Protection.

To see which engine version you run, ask Claude, or run this from the workspace folder.

jq -r '.engineVersion' .claude/engine-manifest.json

Environment Variable

Variable	Effect
AIBOS_ENGINE_UPDATE=1	Skips the pre-commit hook for one commit, if you have installed it

See Hooks Overview.