T3 Linear Bridge

Recent runs

Linear → T3 → GitHub execution state

Issue	Repository	Workflow	Runtime	Updated

Durable queue lanes

Pending work, retries, age, and most recent successful processing

Queue	Source	Pending	Retrying	Oldest	Dead letters	Last success

Dead letters

Sanitized failures quarantined after permanent errors or bounded retries

Queue	Kind	Attempts	Error	Quarantined

Safe configurationChanges are validated, versioned, audited, and applied to new work immediately. Active runs stay pinned to their resolved policy and T3 environment.

General

Public links, upstream APIs, and reconciliation cadence

Public bridge URL Linear GraphQL endpoint GitHub API URL Active polling interval

Maximum CI repair attempts

Suggestion confidenceMinimum lead

Linear response chunk size

Two-way session sync

T3 prompts → Linear T3 responses → Linear

Session attention notifications

Aggregate unresolved T3 requests and notify every person tagged on the shared session

Mattermost

Enable notifications Aggregation window Mattermost URL Mattermost channel

Tagged T3 users are resolved to Mattermost accounts by email and exact display name. Requests answered before the window closes are suppressed.

Experimental PR session automation

Send failed checks, deployments, comments, and reviews to the T3 session already linked to the pull request

Experimental

Enable automation Aggregation window Mapping reconciliation Consecutive turn limit Maximum prompt context Excluded GitHub usernames

Usernames use case-insensitive exact matching. Automation starts disabled, establishes a baseline from current links, waits for an idle execution revision, and pauses after the configured turn limit.

Ticket-size execution profiles

Choose how every Linear complexity starts in T3 Code. Model overrides are optional; without one, the selected repository's model is used.

New runs only

Planning controls plan approval versus direct implementation.Access maps exactly to T3 Code runtime permissions.Model settings support provider-specific reasoning, speed, thinking, and future option IDs.

Custom Linear label overrides

Override selected execution fields when a Linear label matches. Rules run from top to bottom; later matching rules win only for fields they set.

Wildcards use * for any text and ? for one character.Inheritance keeps the size/repository value whenever a field is blank.Safety keeps Risk: High in Plan mode even if a rule requests direct implementation.

T3 environments

Execution capacity and project hosts

Repository routes

Allowlisted mappings from Linear issues to T3 projects

Default repository for unlabeled sessions

Explicit repository labels and unique team mappings always win. Leave this empty to restore Linear suggestions and blocking when no route matches.

Integration secrets

Write-only values encrypted with AES-256-GCM; leave blank to retain the current value

Linear API token Clear configured value Linear webhook secret Clear configured value GitHub token Clear configured value GitHub webhook secret Clear configured value Mattermost bot token Clear configured value

Authentication boundary

Integration health

Read-only authentication and orchestration probes

Run checks to verify Linear, GitHub, and every configured T3 environment.

Configuration audit

Immutable history of settings revisions and secret-field changes