Creating a Project Config

Use per-project config when one project needs a different effective view than the global default.

cd /path/to/project
bgng init

This creates:

<project>/.agents/bgng/config.json

Capabilities

Project config can:

• Enable or disable MCP servers for one project
• Add project-local MCP server definitions
• Enable extensions such as Parallel or Beads for one project
• Include or exclude skills during apply
• Enable or disable targets locally

Discovery

Project config is applied by bgng apply, bgng mcp list, bgng mcp apply, bgng status, bgng doctor, and extension status/doctor/setup commands.

Discovery walks upward from the current working directory and uses the nearest config file.

Example

{
  "version": 1,
  "extensions": {
    "parallel": {
      "enabled": true,
      "skills": true,
      "mcp": false
    },
    "beads": {
      "enabled": true,
      "targets": ["codex", "claude"],
      "includeSkill": true
    }
  }
}

Skill Include / Exclude

Lower-level skills.include and skills.exclude work for repo-native and package-backed skills. If both extension-derived includes and explicit excludes mention the same skill, skills.exclude wins.

Useful Workflow

bgng status
bgng apply --dry-run
bgng doctor