Skip to main content
Version: 0.1.125 – latest

Project settings

Settings are per project. This page covers what a project owner changes in the normal course of work; the deployment-level configuration behind them — registries, gateways, credentials on the host — belongs to whoever installed the platform, and is covered in Install with Docker Compose.

Controls only an owner can use say so, rather than failing when you click them.

How work lands: merge mode​

The single most consequential setting.

  • DIRECT — feature branches merge into the project's integration branch.
  • PR mode — feature branches become pull requests against your own base branch, tracked in the Pull Requests view.

An existing project can be migrated from DIRECT to PR mode. Note that a feature merged before the switch keeps saying which branch it actually merged into — the history is not rewritten to match the new mode.

Implementation gates​

What has to be true before an implementation is accepted. Each is a switch, and together they decide how much the platform insists on before it calls a feature done:

  • unit tests, and a coverage threshold
  • a false-positive review of passing unit tests — off by default, and worth turning on where green tests are not trusted
  • UI, API and database-schema checks
  • scenario-drift detection
  • implementation planning, and scenario-by-scenario implementation
  • a maximum number of review cycles

Numeric settings are bounded, so a value that would make no sense is refused at the point you set it.

Models and agents​

Agent Defaults is a table with one row per agent the product runs. Per agent you can set:

  • the model it runs with, and the advisor model that reviews its work
  • its timeout
  • how long its prompt cache lives, and what that has cost
  • whether it gets a browser
  • what memory it captures, uses and is given

A per-run model an operator picks for one launch overrides the row for that run only.

Providers​

How agent calls reach a model. A new project defaults to direct dispatch; the routed modes are available where your deployment enables them:

  • Anthropic API directly
  • Vertex AI, running Claude models in your own GCP project
  • Gemini, and other providers, through the translation gateway

Provider and memory smoke tests are on this page: run them after changing anything here rather than finding out on your next implementation.

Integrations​

  • GitHub / Azure DevOps — a personal access token, repository creation, and branch pushes. The link maintains itself: it pushes on creation, syncs both ways, and pushes again at merge time.
  • Team Foundation Server — including trusting a private certificate authority, or skipping TLS verification for one connection.
  • Source repositories — for a project combining several, managed here.
  • Package registries — where agent jobs, test containers and scaffolding resolve dependencies from. Set these for an air-gapped or proxied network.

The code index​

Two checkboxes decide whether the code index runs. The page reports what state the index is in and lets you rebuild it. It is what lets agents answer questions about the codebase without reading all of it, so a stale or missing index shows up as agents that seem not to know their way around.

Web IDE sessions​

The context window a session's assistant runs with, and how it signs in. See The web IDE.

Team​

Who can see and change this project. Editors can do the work; viewers can read it. Some controls are owner-only.