Configuration
Configuration
Section titled “Configuration”All Assemble configuration lives in .assemble.yaml at your project root.
Full configuration reference
Section titled “Full configuration reference”# Assemble configurationversion: "1.0"
# Target platforms — which AI coding tools to generate configs forplatforms: - cursor - claude-code - copilot - windsurf # See full list below
# Team profile — predefined set of defaultsprofile: startup # startup | enterprise | agency
# Governance level — oversight and checkpointsgovernance: standard # none | standard | strict
# Team language — language agents communicate inlangue_equipe: en # en | fr | es | de | pt | etc.
# YOLO mode — autonomous executionyolo: true # true | false
# Cross-session memory — persist context between sessionsmemory: true # true | false
# Metrics — track workflow performancemetrics: true # true | false
# Custom agents — extend the teamcustom_agents: - name: Athena alias: athena domain: privacy file: .assemble/agents/privacy.md keywords: - privacy - GDPR
# Custom workflows — add team-specific processescustom_workflows: - file: .assemble/workflows/design-review.yaml trigger: /design-reviewOptions reference
Section titled “Options reference”version
Section titled “version”Type: string | Required: yes | Default: "1.0"
Configuration file version. Currently only "1.0" is supported.
platforms
Section titled “platforms”Type: string[] | Required: yes
List of AI coding platforms to generate configuration files for.
IDE platforms:
cursor, windsurf, copilot, jetbrains, zed, trae, void, pearai, melty, codex, bolt, lovable, replit, cline, roo-code, tabnine
CLI platforms:
claude-code, aider, continue, augment, amp
profile
Section titled “profile”Type: string | Required: no | Default: startup
Team profile that sets sensible defaults:
| Profile | Governance | YOLO | Agents | Focus |
|---|---|---|---|---|
startup | none | true | All 34 | Speed and iteration |
enterprise | standard | false | All 34 | Oversight and compliance |
agency | standard | true | All 34 | Multi-client management |
governance
Section titled “governance”Type: string | Required: no | Default: none
Governance level. See the Governance guide for details.
none— no checkpointsstandard— decision gates at key transitionsstrict— full audit trail, RBAC, NIST mapping
langue_equipe
Section titled “langue_equipe”Type: string | Required: no | Default: en
Language that agents use for communication and deliverables. Technical terms, code, and commands remain in English regardless of this setting.
Supported: any ISO 639-1 language code (en, fr, es, de, pt, ja, zh, ko, etc.)
Type: boolean | Required: no | Default: false
Enable YOLO mode for autonomous execution. See the YOLO Mode guide for details.
memory
Section titled “memory”Type: boolean | Required: no | Default: false
Enable cross-session memory. When true, Jarvis maintains assemble-output/_memory.md with:
- Session log: key decisions, blockers, outcomes
- Active context: current project state
- Key decisions: important decisions with rationale
metrics
Section titled “metrics”Type: boolean | Required: no | Default: false
Enable workflow metrics tracking. When true, Jarvis logs workflow performance data to assemble-output/_metrics.md:
- Workflow name, timestamps, duration
- Steps executed, agents involved
- Success/failure status
custom_agents
Section titled “custom_agents”Type: object[] | Required: no
Register custom agents for Jarvis routing. Each entry:
| Field | Type | Required | Description |
|---|---|---|---|
name | string | yes | Display name |
alias | string | yes | @alias for invocation |
domain | string | yes | Expertise domain |
file | string | yes | Path to agent definition file |
keywords | string[] | yes | Routing keywords |
custom_workflows
Section titled “custom_workflows”Type: object[] | Required: no
Register custom workflows. Each entry:
| Field | Type | Required | Description |
|---|---|---|---|
file | string | yes | Path to workflow YAML file |
trigger | string | yes | /command to activate |
Generated file structure
Section titled “Generated file structure”After running npx cohesiumai-assemble or npx cohesiumai-assemble generate:
your-project/├── .assemble.yaml # This configuration file├── .assemble/│ ├── agents/ # Agent definitions (34 built-in)│ │ ├── spider-man.md│ │ ├── bruce-banner.md│ │ └── ...│ ├── workflows/ # Workflow definitions (15 built-in)│ │ ├── feature-development.yaml│ │ ├── bug-fix.yaml│ │ └── ...│ └── rules/ # Routing, teams, orchestrator│ ├── routing.md│ ├── teams.md│ └── orchestrator.md├── .cursorrules # Generated (if cursor in platforms)├── CLAUDE.md # Generated (if claude-code in platforms)├── .github/│ └── copilot-instructions.md # Generated (if copilot in platforms)└── assemble-output/ # Workflow deliverables ├── _memory.md # Cross-session memory (if enabled) └── _metrics.md # Workflow metrics (if enabled)Environment-specific overrides
Section titled “Environment-specific overrides”For different environments, you can create override files:
# .assemble.local.yaml — local development overridesyolo: truegovernance: none# .assemble.ci.yaml — CI/CD overridesyolo: falsegovernance: strictThe merge order is: .assemble.yaml (base) → .assemble.{env}.yaml (override).