Project Settings

Project Settings

Each project has its own settings: where its docs live, how agents are launched on it, which rules they follow, what they may spend, and how the Board, Design, Token Saver and Steward behave. Open Project › More › Settings. Each tab has its own URL (?tab=…).

Note

Everyone with access to the project can read its settings. Most changes need the project admin role. A viewer sees the same fields locked.

Tabs at a glance

flowchart LR
  S["Settings"] --> G["General"]
  S --> D["Docs source"]
  S --> R["Coding rules"]
  S --> O["Orchestrator"]
  S --> M["Members"]
  S --> B["Budget"]
  S --> P["Planner"]
  S --> DS["Design"]
  S --> BO["Board"]
  S --> T["Token saver"]
  S --> ST["Steward"]
  S --> SE["Sessions"]

Loading

General

• Display name of the project.
• Base branch override: the branch work targets, instead of the detected one.
• Ready label override: the label that makes an issue dispatchable for the fleet. Empty uses the label from the Code Sentinel config.
• Default runtime profile: the Claude Code profile on the runner that agents launch with by default.
• Merge approval: your intent that a person approves every fleet pull request before the orchestrator merges it. The orchestrator obeys the project's own config. Nautelle warns when the two disagree.
• A danger zone to remove the project.

Docs source

Where the project's specs, ADRs and roadmap live: an in-repo folder or a separate docs repository (owner/name). The Spec folder is relative to the docs root; card and plan specs are written there. Nautelle detects the source when you connect a project, and you can override it here.

Coding rules

The conventions every agent working on this project must follow.

• Each rule has a name and an instruction to the agent, in Markdown. Toggle a rule on or off, and use the arrows to change the order.
• Scan reads the conventions the project already states — CLAUDE.md, AGENTS.md, CONTRIBUTING.md, linter and formatter configs, .editorconfig — and proposes them as rules. The runner does the reading. Nothing is saved until you accept it, and a rescan does not duplicate existing rules. A new project is scanned when it is connected.
• Import takes a Markdown file: each list item becomes one rule, and a bold lead or a heading names it. Imported rules are enabled.

Every enabled rule goes into the prompt of each card worker, in order, as a ## Project coding rules block. Edits apply from the next run. An oversized rule set is cut with an explicit marker.

Orchestrator

How Nautelle starts the Code Sentinel orchestrator for this project:

• Runtime profile: none uses the project's default profile.
• Model.
• Permission mode: bypassPermissions lets the orchestrator run without asking. Only an administrator can choose it, and the choice is audited.

See Fleet and Orchestrator.

Members

The people with access to the project and their role on it. A role override changes a person's role for this project only. Removing a member asks for confirmation.

Budget

Spend limits for this project, per day, week or month. A budget alerts at thresholds, or stops new orchestrator and skill runs at the limit. See Budgets and Cost.

Planner

Specification output: how a feature task's specification reaches GitHub when an earlier plan is sent to the fleet.

• Docs pull request: one docs PR, in the docs repository when the docs live there.
• Issue body: the spec goes into the issue itself.

Design

• UI profile: the project's cached description of its UI, with a style kit that every mockup reuses. View it, edit it, rebuild it, or mark the project as having no user interface.
• Viewport presets: the sizes the design viewer offers. The defaults are Desktop 1440×900 and Mobile 390×844.
• Default design skills: the skills every new design uses, until a design's skills are edited by hand.

See Design and Stacks.

Board

Setting	What it controls
Issue / spec on Run	the defaults for creating a GitHub issue and a spec file when a card runs; a card can override them
Automatic work for terminal sessions	whether a card tracked from a terminal session commits, pushes and opens a PR when its session ends; off by default; a card can override it
Merge finished cards automatically	auto-merge of green, finished cards; defaults to on for a non-default base and off for the default branch
Workers at once	1–10 card workers at a time; a further Run is refused until one finishes
Background wait warning, minutes	how long a worker may wait on its own background task before it raises a warning and a notification
Capture	the opt-in reading of your manual sessions for Inbox suggestions, and the model on the runner that reads them; needs session content to be on

See Board and Cards and Card Workers and Shipping.

Token saver

A switch, on by default, and MCP servers agents load: the servers from the project's runtime profiles that agents may load. nautelle is always loaded. Off launches every agent exactly as before. See Token Saver.

Steward

A switch, on by default, plus:

• the silence threshold in minutes (1–240);
• the digest time;
• a checkbox per automatic action, each with its limit: nudge after an API or network error, dismiss known dialogs, resume a dead card session, hold pushes with a Claude trailer.

See Steward.

Sessions

• Terminal → Board: the checklist for connecting Claude Code sessions you start by hand, through the nautelle plugin.
• Keep session content: off by default, so only metadata is kept. On, it also keeps prompts, tool inputs and outputs, and responses. Redaction is pattern-based.
• Retention (days): content older than this is deleted every night.
• Purge content: deletes all session content of the project.

Capture and message previews of a session's questions need session content.

See also

• How Work Flows · Board and Cards · Design and Stacks · Token Saver · Steward

Decisions: ADR-0012 · ADR-0021 · ADR-0026 · ADR-0036 · Spec: #582, #584, #586, #359