Project Settings
Project settings let you configure how Trinity manages your project's git workflow, repository structure, and business details.
Accessing Settings
Navigate to Settings in the sidebar, then select the project settings tab.
General
- Project name — display name used throughout the UI
- Description — brief summary of the project
Repositories
Projects can contain one or more git repositories. Each repo is configured independently:
- Name — identifier for the repo (e.g., "web", "api", "mobile")
- Path — relative path from the workspace root
- Enabled — toggle to include/exclude from execution
For monorepos, you'll typically have one repo entry pointing to the root. For polyrepos, each repository gets its own entry.
Per-Repo Branch Configuration
Each repo can have its own branching rules:
- Story branch template — pattern for naming story branches (e.g.,
feature/{story_slug}) - Base branch — the branch stories merge into (e.g.,
main,develop) - PR target — where pull requests are opened against
Template variables available:
{prefix}— configurable prefix{prd}— PRD number{phase}— phase slug{epic}— epic slug{story}— story ID{slug}— story slug{story_slug}— full story slug{phase_slug},{epic_slug},{prd_slug}— hierarchical slugs
Per-Repo Merge Configuration
- Merge strategy — how branches are merged (merge commit, squash, rebase)
- Delete branch after merge — automatically clean up merged branches
- Auto-merge — merge PRs automatically when checks pass
GitHub Collaborators
Manage who has access to your project's GitHub repositories directly from Trinity. The Collaborators card appears in project settings when your project has a GitHub remote.
Viewing Collaborators
The card shows all current collaborators with their GitHub avatar, username, and role. For poly-repo projects, a repository selector lets you switch between repos.
Inviting Collaborators
Enter a GitHub username and choose a permission level:
| Permission | Access |
|---|---|
| Read | View code and clone |
| Write | Push commits and manage issues |
| Maintain | Manage repo without admin access |
| Admin | Full repository access |
If you're on a team, the username field shows autocomplete suggestions from your team members — just start typing to filter by name, handle, or GitHub username.
Removing Collaborators
Click the remove button next to any collaborator to revoke their access. Pending invitations can also be cancelled before they're accepted.
Repository Permission Gating
In team scope, Trinity checks your actual GitHub permission level on the project's repositories. Actions that require higher permissions are disabled with an explanation:
| Permission Level | Can do |
|---|---|
| Read | View project, browse knowledge base |
| Write | Run stories, respond to gates, manage collaborators |
| Maintain | All Write actions plus project settings |
| Admin | Full access including danger zone operations |
If you don't have sufficient permissions on GitHub, the corresponding buttons and actions are disabled. In personal scope, all actions are available.
Branching Configuration
Project-level branching defaults that individual repos can override:
- Default story template — branch naming pattern applied to all repos unless overridden
- Default base branch — the integration branch
Release Branches
Optional feature for projects that need release isolation:
- Use release branches — when enabled, checkpoint stories create release branches instead of merging directly
- Release template — naming pattern for release branches
- Auto-release to base — automatically merge release branches to the base branch on approval
- Delete release branch — clean up release branches after merging
Business Details
Business information used by execution gates and story content:
- Company name
- Contact email
- Phone number
- Address
- Tagline
- Social media links
These are initially extracted from onboarding conversation but can be edited here at any time. Stories that need company branding or contact information will check these fields — if they're missing, an execution gate pauses the pipeline.
Skip Checks
- Skip asset check — bypass the missing assets gate (useful for text-only projects)
- Skip business details check — bypass the missing business details gate
- Auto-approve quality checkpoints — quality checkpoints run full QA but skip human approval; only release checkpoints pause
Workers
Configure parallel execution capacity:
- Max workers — how many stories can execute simultaneously
- Worker timeout — how long a worker can run before being considered stale
Targets
View and manage project target platforms. Targets are set during onboarding but can be adjusted here:
- Each target has a type (Web App, Mobile, Desktop, CLI, API, Website) and a label
- Multiple targets can share the same type with different labels (e.g., two Mobile targets: "Client App" and "Driver App")
Storage
Configure where project assets (images, documents, uploaded files) are stored:
| Option | Description |
|---|---|
| Local Only | Files stored on disk. Not available for team projects since assets must be accessible to all members. |
| Trinity Cloud | Managed storage via Trinity's R2 infrastructure. No configuration needed. Default for team projects. |
| BYO S3-Compatible | Bring your own S3-compatible storage — AWS S3, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, MinIO, etc. |
Storage Limits (Trinity Cloud)
Every Pro seat includes 5 GB of managed cloud storage. For teams, storage is pooled across seats — a 5-seat team gets 25 GB shared.
If you need more space, add-on storage packs are available:
| Pack | Price |
|---|---|
| 10 GB | $5/month |
Packs stack — buy as many as you need. BYO S3 users are not subject to any Trinity storage limits since files are stored in your own bucket.
BYO S3 Configuration
For BYO S3, configure:
- Endpoint URL — the S3-compatible API endpoint
- Region — bucket region (use
autofor Cloudflare R2) - Bucket name — the storage bucket
- Access Key ID and Secret Access Key — credentials (encrypted at rest)
Stack
The stack card shows every technology decision tracked for this project — frameworks, databases, ORMs, auth providers, and other architectural tools. Items come from several sources:
| Source | When |
|---|---|
| Onboarding | Technologies chosen during the greenfield wizard or detected during import |
| Planning | The dependency mapper assigns pending stack items to the story that will first install them |
| Post-merge | After each story merges, Trinity scans for newly introduced tools and flags them as suggestions |
| Scan | Use the "Scan a branch" field to detect tools added outside Trinity (e.g., manual commits) |
Item Status
| Status | Meaning |
|---|---|
| Active | Accepted and in use |
| Pending Review | Suggested by an agent — accept or dismiss |
| Deprecated | Superseded by another tool (shows replacement link) |
| Removed | No longer part of the stack |
Assignment Tracking
Each stack item shows which story is responsible for installing it:
- pre-existing — already in the codebase (imported projects)
- unassigned — not yet assigned to a story (shown in amber)
- story 1:2.3.1 — assigned to a specific story by the planning pipeline
During planning, the dependency mapper automatically assigns unassigned items to the story that will first configure them. After execution, the post-merge scanner verifies assignments and flags mismatches.
Branch Scanning
Enter a branch name and click Scan for new tools to detect technologies added outside Trinity's execution pipeline. Found tools are added as suggestions for your review.
Secrets
Manage encrypted API keys and credentials:
- View configured secrets (values are masked)
- Add new secrets
- Update or delete existing secrets
- Import from
.envfiles
Secrets are injected as environment variables when agents execute stories. They're encrypted at rest using AES-256-GCM.
Danger Zone
High-impact project operations are grouped at the bottom of project settings:
Move Project
Transfer a project between personal and team scopes. Available when you have teams:
- Move to Team — transfers a personal project to a team scope. All data syncs to the team's Turso database. If using Trinity Cloud storage, assets are migrated to the team's R2 bucket.
- Move to Personal — transfers a team project back to your personal scope. Assets migrate accordingly.
Moving requires typing the project name to confirm. Storage migration runs automatically — no manual file moves needed.
Approval workflow: If the team has transfer policies requiring approval, the move creates a request instead of executing immediately. Owners and managers can approve or reject requests from the Requests page. Once approved, the move executes on the requester's next sync. See Teams for transfer policy details.
Delete Project
Permanently archives the project. Requires typing the project name to confirm. Team owners control who can delete projects via the Delete Projects permission.