Classic Configuration

.comet/config.yaml is a project-level configuration, with a global copy. This page only covers the Classic related parts: the shared entry field and the default values of classic.*. The meaning of the native.* field can be found in Native Configuration The following text uses <classic-root> to represent the current Classic OpenSpec root directory: The default for new projects is docs/openspec/, and for projects that retain the old layout, it is openspec/. The actual location is determined by classic.artifact_layout. For details, please refer to Project File structure

Complete example

When two sets of workflows are enabled simultaneously and Chinese is selected, project-level installation will generate a similar configuration (from the Classic perspective, only shared fields and classic: blocks are concerned) :

schema: comet.project.v1
default_workflow: classic
workflows:
  - native
  - classic
ambient_resume: true

classic:
  artifact_layout: docs
  language: zh-CN
  context_compression: off
  review_mode: standard
  auto_transition: true

Shared entry field

Configuration item	Allowable value	Meaning
`schema`	`comet.project.v1`	The current structured project configuration version is managed by Comet
`default_workflow`	`native` \| `classic`	By default, `/comet` enters which set of permanent skills
`workflows`	`native`, `classic` or both	The workflow that the project has enabled; The default workflow must be included
`ambient_resume`	`true` \| `false`	Whether to allow the Agent to automatically run the recovery probe for ordinary natural language continuation requests
`hook.allow_paths`	Project-relative directory list (empty by default)	Directories the Agent may write during protected phases; matching uses path prefixes and cannot unlock protected artifact areas. See Allowing Hook writes.

Modifying default_workflow only changes the entry of /comet without migrating any changes.

Hook write release

hook.allow_paths is a shared write release policy: when it is empty by default, writes within the project (outside the product area) are determined according to the Classic’s own phase and guard rules. After configuration, writes to the matching directory and its subdirectories will be directly allowed. A typical application is to enable the implementation code directory (such as src/) to be modified at any stage, avoiding triggering interception during non-coding phases.

hook:
  allow_paths:
    - src
    - apps/web

The openspec and superpowers product roots of .comet (Runtime state) and Classic are always protected and cannot be released through this configuration. Path out-of-bounds or format errors will report an error during the comet doctor check.

”Classic field”

artifact_layout is the project-level directory selection. The remaining four items will be snapshots to .comet.yaml of the new Classic change when it is created:

Configuration item	Allowable value	Default value	Meaning
`classic.artifact_layout`	`legacy` \| `docs`	The default is `docs`; When upgrading, it was detected that the root directory `openspec/` already existed, so it was added to `legacy`	Select the OpenSpec root directory: `openspec/` or `docs/openspec/`
`classic.language`	`en` \| `zh-CN`	The Skill language mapping selected by `comet init`; `--yes` defaults to `en`	The main language for controlling workflow products such as OpenSpec, Superpowers, verification reports, and archived instructions
`classic.context_compression`	`off` \| `beta`	`off`	Control the context compression during the handover from design to build. For details, please refer to Context Compression mechanism
`classic.review_mode`	`off` \| `standard` \| `thorough`	`standard` (full workflow default)	Control the intensity of code review. For details, please refer to Code Review Mechanism
`classic.auto_transition`	`true` \| `false`	`true`	Whether the next stage Skill is automatically called after the stage is advanced. For details, please refer to Automatic Propulsion mechanism

Classic project defaults snapshot when creating the new change to .com et. The yaml; Subsequent modifications will not retrospectively change the existing changes.

Directly modifying classice.artifact_layout will only change Comet The directory read will not move existing products. When switching layouts for existing projects, should be used comet classic root move docs —dry-run check the current status, conflicts and blocking items, and then use comet classic root move docs —apply to perform migration.

The difference between product language and Skill language

The “Skill language” in comet init will determine whether to install the Chinese or English version of Comet Skill. The product language of Classic is written in classic.language:

init selection	Installed Skill	`classic.language`
`English` / `--language en`	English Skill	`en`
`Chinese`/`--language zh`	”Chinese Skill”	`zh-CN`

When creating a new Classic change later, Comet will snapshot the project-level classic.language to <classic-root>/changes/<name>/.comet.yaml. OpenSpec proposal, design, tasks, Superpowers Design/Plan, verification report and archive description are all based on this snapshot as the output language.

Project-level and change-level language values only accept en or zh-CN. zh is only used for comet init - language zh CLI options, not .com et/config yaml legal values.

Configuration priority

The following priorities only describe the Classic language, context_compression, review_mode and auto_transition:

change level.comet.yaml field > Environment variables > Project level.comet/config.yaml > Global language default > Built-in default values

Hierarchy	Explanation	Setting method
”change grade `.comet.yaml`	Highest priority. change is created from a project configuration snapshot and then flows through `/comet`	Written by the Skill of the `/comet` stage
Environmental variable	It only takes effect when the change-level field is empty and is suitable for CI/CD temporary overwriting	`export COMET_AUTO_TRANSITION=true` / `export COMET_LANGUAGE=zh-CN`
Project-level `.comet/config.yaml`	Fallback when the change level is empty and the environment variable is not set	Handwritten or generated by init
Global `~/.comet/config.yaml`	Only provide cross-project default for `language`; Project configuration priority	Global init/update generation
Default value	Finally, go back	See the table above

Detailed Explanation of auto_transition

Whether the next Skill is automatically called after the control phase of auto_transition advances.

value	”Behavior”
`true` (Default)	After guard advances `phase`, it outputs `NEXT: auto` and automatically invokes the next stage Skill
`false`	After guard advances `phase`, it outputs `NEXT: manual`, prints the HINT, and you can manually run the next Skill

phase advance must occur - guard - updated phase apply always The field is independent of auto_transition. auto_transition only affects whether the next one is automatically called “Skill. User decision points (confirming proposals, choosing execution methods, etc.) regardless of auto_transition Anything can block.

Environment variable coverage (only effective when the change level is empty) :

export COMET_AUTO_TRANSITION=true

Environmental variable

Environmental variable	Purpose	Applicable scenarios
`COMET_LANGUAGE`	Overwrite language (effective when the change level is empty)	CI/CD or temporarily specify the product language of the new change
`COMET_AUTO_TRANSITION`	Overwrite auto_transition (effective when the change level is empty)	CI/CD or temporary overwrite
`COMET_CONTEXT_COMPRESSION`	Override context_compression (effective when the change level is empty)	Temporarily test the compression mode
`COMET_REVIEW_MODE`	Override the default resolution (resolver layer) of review_mode	Temporarily designate the review mode
`COMET_FORCE_PHASE`	When `=1` is used, direct `set phase` is allowed (an escape hatch for state repair and troubleshooting only)	Status repair and troubleshooting
`COMET_OPENSPEC`	Specify the openspec CLI path (default `openspec`)	Customize the installation location of OpenSpec

COMET_LANGUAGE、COMET_AUTO_TRANSITION、COMET_FORCE_PHASE、 COMET_OPENSPEC are environment variables available to users. COMET_CONTEXT_COMPRESSION and COMET_REVIEW_MODE exists in the parsing layer but is not officially recorded in the user documentation. It is mainly used internally and for testing.

How to configure

Configure the default values of the project

Editor: .comet/config.yaml

schema: comet.project.v1
default_workflow: classic
workflows:
  - native
  - classic
ambient_resume: true
classic:
  language: zh-CN
  context_compression: beta
  review_mode: thorough
  auto_transition: true

When submitted to the repository, new changes for team members will use these default values.

Temporary coverage (environment variable)

export COMET_LANGUAGE=zh-CN
export COMET_AUTO_TRANSITION=false

Affect the current session and do not modify the file.

Next step

State management -.comet.yaml field Full table and state machine hard constraints
Context Compression mechanism ](/en/concepts/context-compression) - Detailed Explanation of the off/beta Mode of context_compression
Detailed Explanation of the Code Review mechanism - off/standard/thorough of review_mode
Detailed Explanation of the behavior of the automatic propulsion mechanism ](/en/concepts/auto-transition) - auto_transition
Project file structure - Where are the configurations and products placed respectively

Understand Comet Classic

Five-phase workflow

Presets

Recovery and troubleshooting

Practical scenarios

Classic Configuration

Complete example

Shared entry field

Hook write release

”Classic field”

The difference between product language and Skill language

Configuration priority

Detailed Explanation of auto_transition

Environmental variable

How to configure

Configure the default values of the project

Temporary coverage (environment variable)

Next step

​Complete example

​Shared entry field

​Hook write release

​”Classic field”

​The difference between product language and Skill language

​Configuration priority

​Detailed Explanation of auto_transition

​Environmental variable

​How to configure

​Configure the default values of the project

​Temporary coverage (environment variable)

​Next step

Complete example

Shared entry field

Hook write release

”Classic field”

The difference between product language and Skill language

Configuration priority

Detailed Explanation of auto_transition

Environmental variable

How to configure

Configure the default values of the project

Temporary coverage (environment variable)

Next step