Before submitting
Area
apps/desktop
Problem or use case
Currently, starting a new thread in T3 Code requires manually copying/pasting context from Linear issues. This creates friction when working with Linear (which most teams using AI coding agents already rely on heavily).We want a first-class way to create a thread directly from Linear issues, attached to any added folder, similar to how Conductor handles it extremely well.
Proposed solution
Desired BehaviorWhen creating a new thread, add an option to "Import from Linear" (or "Create from Linear issue").
After authenticating with Linear (personal access token or OAuth), users should be able to:Search/browse their Linear issues (by team, project, assignee, labels, status, etc.).
Select one or multiple issues.
Choose any added folder as the target workspace/folder for the thread.
The selected Linear issue(s) should be imported cleanly into the new thread:Title + full description
Acceptance criteria / checklist
Labels, priority, assignee, linked PRs, etc.
(Nice-to-have: recent comments or attachments)
The imported content becomes the initial context/prompt for the agent in that thread.
Multi-Issue SupportUsers should be able to select multiple Linear issues and import them into a single thread.
Options could include:Combine them into one comprehensive task (with clear separators).
Treat them as related subtasks within the same thread.
Let the user decide the format in the composer before creating the thread.
Why this matters
Why Conductor Does This Right (Reference)Conductor has this flow nailed:"Create from..." dropdown (or ⌘I shortcut) lets you pick a Linear issue.
It instantly creates a workspace with the full issue context already loaded.
The agent starts with perfect context (title, description, acceptance criteria, labels).
This dramatically reduces context switching and copy-paste errors.
We want the same seamless experience in T3 Code, but with the added flexibility of:Choosing any added folder (not just a new isolated workspace).
Supporting multiple issues per thread.
Smallest useful scope
Proposed UX Flow (Desktop)
Click New Thread (or equivalent).
See option: Create from Linear (prominent button or in a dropdown).
Authenticate with Linear (if not already connected).
Search + multi-select issues.
Select target folder from the list of added folders.
Preview the imported content in the thread composer.
(Optional) Edit/refine the prompt before creating.
Thread is created with the Linear context pre-loaded.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/desktop
Problem or use case
Currently, starting a new thread in T3 Code requires manually copying/pasting context from Linear issues. This creates friction when working with Linear (which most teams using AI coding agents already rely on heavily).We want a first-class way to create a thread directly from Linear issues, attached to any added folder, similar to how Conductor handles it extremely well.
Proposed solution
Desired BehaviorWhen creating a new thread, add an option to "Import from Linear" (or "Create from Linear issue").
After authenticating with Linear (personal access token or OAuth), users should be able to:Search/browse their Linear issues (by team, project, assignee, labels, status, etc.).
Select one or multiple issues.
Choose any added folder as the target workspace/folder for the thread.
The selected Linear issue(s) should be imported cleanly into the new thread:Title + full description
Acceptance criteria / checklist
Labels, priority, assignee, linked PRs, etc.
(Nice-to-have: recent comments or attachments)
The imported content becomes the initial context/prompt for the agent in that thread.
Multi-Issue SupportUsers should be able to select multiple Linear issues and import them into a single thread.
Options could include:Combine them into one comprehensive task (with clear separators).
Treat them as related subtasks within the same thread.
Let the user decide the format in the composer before creating the thread.
Why this matters
Why Conductor Does This Right (Reference)Conductor has this flow nailed:"Create from..." dropdown (or ⌘I shortcut) lets you pick a Linear issue.
It instantly creates a workspace with the full issue context already loaded.
The agent starts with perfect context (title, description, acceptance criteria, labels).
This dramatically reduces context switching and copy-paste errors.
We want the same seamless experience in T3 Code, but with the added flexibility of:Choosing any added folder (not just a new isolated workspace).
Supporting multiple issues per thread.
Smallest useful scope
Proposed UX Flow (Desktop)
Click New Thread (or equivalent).
See option: Create from Linear (prominent button or in a dropdown).
Authenticate with Linear (if not already connected).
Search + multi-select issues.
Select target folder from the list of added folders.
Preview the imported content in the thread composer.
(Optional) Edit/refine the prompt before creating.
Thread is created with the Linear context pre-loaded.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution