App Settings

App-level settings control Trinity's global behavior — preferences that apply across every project. Access them by clicking Settings in the sidebar's Hub section.

The page is organized into four tabs: General, Git & Branching, AI Models, Membership.

General Tab

Theme

Seven theme options:

Timezone

Affects:

• Recap date groupings (daily / weekly / monthly / etc.)
• Metrics dashboard time axes
• Timestamp displays throughout the UI

Timestamps are stored UTC server-side — timezone conversion happens at display time. Set Auto to use the browser's detected timezone.

Automation Defaults

Defaults applied to every project unless overridden. Full cascade: Global → Team → Project → Entity (story/release) → Job. These defaults sit at the Global layer.

Toggles available:

• Auto PR — open PRs automatically when a story finishes
• Auto-merge — merge PRs automatically when checks pass
• Squash merge — squash commits on merge
• Delete branch after merge — clean up story branches after merging
• Skip asset check — bypass the missing_assets gate
• Skip business details check — bypass the missing_business_details gate
• Auto-release to base — auto-merge release branches to the base branch on approval (when release branches are enabled)
• Delete release branch after merge — clean up release branches
• Auto-approve quality checkpoints — run the full checkpoint pipeline but skip the human gate (release-level release_approval is always manual regardless)

Help Assistant Toggle

The floating help chat (bottom-right corner of every page) answers questions about using Trinity from the built-in user guide. Toggle it off here if you prefer a clean canvas. Supports image uploads for asking about specific UI elements.

Auto-Update

Trinity checks for updates every 4 hours:

• Available update → pill in the title bar with an Update Trinity button
• Auto-Update on → install automatically once Trinity is idle (no jobs running or claimed)
• Trinity never interrupts an active run — if jobs are in-flight it waits for them to finish
• Manual install respects the same rule: if execution is active you'll see a "waiting for execution" warning

Git & Branching Tab

Project branching defaults (applied when a new project is created — per-project overrides live in Project Settings → Git). See Project Settings for the full shape of branching configuration.

AI Models Tab

Default models per tier — the global baseline that team / project / story overrides can replace.

You can't assign a model with a lower intelligence level than the tier requires — e.g., you can pick a Sonnet model for the Fast tier but not a micro model for Reasoning.

Providers

Supported ModelProvider values: anthropic, deepseek, moonshot, zai, qwen, ollama. Configure provider API keys in the same tab.

See AI Model Configuration for the deeper tier explanation.

Membership Tab

Your subscription status and storage pool:

• Subscription status (active / trialing / comp / etc.) and trial countdown
• Sponsored-seat management (owners can sponsor other users; recipients accept/decline from the Requests inbox)
• Storage quota display — your 5 GB base + any 10 GB add-on packs you've purchased

How Settings Sync

Global settings live in the user_settings table on the website sync DB and sync across every device signed into your account. The desktop never caches or overrides them locally — every read and write hits /api/user-settings via the @/user-settings barrel.

Exception: the settings table in the local desktop SQLite file holds cache-only values (skill template hash, schema doc hashes) — not user-facing preferences.

Data & Disk Layout

Trinity's desktop stores only machine-local state. Project data (PRDs, stories, knowledge, tags, stack, activity, recaps, releases, assets, secrets, user + team settings, etc.) lives in trinityailabs.com's Turso DBs and is reached over HTTP — there's no longer a sync DB on the desktop.

What lives in ~/.trinity/ on disk:

~/.trinity/
├── trinity-{slot}.db          Machine-local SQLite — worktrees, workers, coordinator,
│                              chat sessions, tasks, device_config, local_project_bindings,
│                              local_job_state. Never syncs.
├── accounts-{slot}/           Per-account auth + manifest cache ({slot} = dev | prod)
│   └── {accountId}/
│       ├── auth.json          Access/refresh tokens
│       └── manifest.json      Workspace manifest cache
├── active-account-{slot}.json Pointer to the active account
└── projects/                  Trinity-owned clones + git worktrees for parallel execution

The {slot} suffix (dev | prod) keeps development and production state isolated. Signing into localhost or dev.trinityailabs.com uses -dev; signing into www.trinityailabs.com uses -prod.

Reset

If you need to start fresh:

1. Stop all execution
2. Delete ~/.trinity/trinity-{slot}.db (and/or the accounts-{slot}/ folder to sign out)
3. Restart Trinity — the local DB runs its migrations and regenerates empty; auth re-mints on next sign-in; project data is untouched because it lives on the server

Refresh Intervals

What polls and how often:

• Metrics dashboard — 30 s (useMetrics hook)
• Run page — live updates as stories progress (React Query with short refetchInterval)
• Knowledge base — loaded on navigation; knowledge-scope cache invalidated on writes
• Release selector — refreshed on release transitions

Keyboard Shortcuts

Trinity uses standard web-app navigation. No custom keybindings are user-configurable today — navigation is through the sidebar and in-page controls.

Resource Usage

Trinity runs a Next.js server (Node.js) with a small local SQLite. Resource usage scales with:

• Number of parallel workers (each worker spawns a Claude CLI process)
• Active project size (via the codebase map + worktree files)
• Agent operations in flight

For most projects, Trinity runs comfortably on a standard development machine.