Inheritance and overrides

Tasuku keeps one instance configuration and allows each repository to override selected categories.

Categories

Repository override flags exist for:

• agent provider, model, and reasoning effort;
• sandbox provider and settings;
• MCP servers;
• skills;
• agent behavior and custom instructions;
• review policy.

When a flag is off, the repository reads the current instance value. Tasuku does not copy a snapshot into repository state. Changing the instance default therefore changes every repository that still inherits that category.

Effective values

Repository configuration responses include:

• the effective value used for new work;
• overrides, the category switches;
• sources, reporting INSTANCE or REPOSITORY per category.

When updating through the API, send a complete valid effective configuration and set only the override flags you intend to own at repository scope.

{
  "overrides": {
    "agent": false,
    "sandbox": false,
    "mcp": true,
    "skills": false,
    "instructions": true,
    "review_policy": false
  }
}

Disabling an override immediately returns that category to the current instance setting.

Settings outside category inheritance

Repository enablement, issue pull request mode, automatic description behavior, selected pull request template, automatic approval, and repository secrets are repository-specific controls. They are not implied by an inherited agent, instructions, or sandbox category.

Secrets resolve separately

Configuration can refer to ${secrets.NAME}. Tasuku first checks repository scope, then instance scope. A repository secret with the same name shadows the instance secret without changing other configuration categories.