Settings
Per-repo settings
Section titled “Per-repo settings”These settings are stored in .cate/workflows.json and configured during setup. Edit the file directly or re-run setup to change them. See the workflows.json reference for the full schema.
| Setting | Field | Default | Description |
|---|---|---|---|
| Default autonomy | autonomy.default | "full" | Default autonomy level. See Autonomy levels. |
| Branch pattern | git.branchPattern | "task/ISSUE-{number}-{description}" | Naming pattern for agent work branches. |
| Commit format | git.commitFormat | "conventional" | Commit message format. "conventional" uses feat(scope): description. |
| Default branch | git.defaultBranch | "main" | The branch agents target for PRs. |
Issue tracker settings
Section titled “Issue tracker settings”Tracker connection settings — project board identifier, status column IDs, and authentication credentials — are configured during setup. To update them:
- Credentials (tokens, API keys): Settings -> Issue Tracker in the Cate dashboard. See Credentials.
- Board configuration (project number, status IDs): edit
.cate/workflows.jsondirectly. See Issue tracker setup.
Agent permissions
Section titled “Agent permissions”Agent tool permissions live in .claude/settings.json at your repository root. This file controls what shell commands and tools agents can run without prompting for your approval.
During setup, Cate writes a recommended set of permissions that pre-approves routine operations: git commands, build tools for your detected stack, and Cate’s internal tools. You can customize this file at any time.
Enterprise or organization-level Claude Code settings always take precedence over project-level settings.