Hand Copilot a problem, one Compass found or one you describe, and it files a Linear issue written the way your team already writes them. You see the full draft before anything is created, and Copilot checks your Linear workspace for issues that already cover the same problem.
Availability & Usage:
đ Needs the Linear integration connected
đ§âđź Every role except Viewer can ask Copilot to file an issue. Connecting Linear and choosing its teams needs the Admin, Publisher, or Engineer role
đ Filing from a friction point needs Compass; filing from your own words doesn't
âď¸ Choose teams on the Linear Integration page, under "Where and how Copilot files issues" (rolling out to all accounts over the next few weeks)
Ask Copilot to file an issue
File a problem the moment you spot it, without leaving your conversation.
From a friction point: ask Copilot to file it, for example, "file this friction point in Linear." The issue carries Copilot's write-up of the problem and its recommended fix, with a footer showing what Chameleon detected so your team can trace it back.
From your own words: describe the problem, for example, "file a ticket about the billing page being slow." Copilot writes the title and description from the conversation.
âšď¸ Asking again about a friction point Copilot already filed points you to that issue instead of filing a second one.
Review the draft before it's filed
Nothing is created in Linear until you say so. Copilot shows you the title, the description, the team it would file into, and any likely duplicates, then asks for a go-ahead. Answer its questions, ask for changes, or say "file it."
If you don't name a team, Copilot uses your default team (or your only one), or asks you to pick from the teams it files into. It sets a priority only if you name one, and files the issue unassigned. To assign someone, ask once it's filed.
Avoid filing duplicate issues
Before filing, Copilot searches your Linear workspace for issues that already cover the problem and tells you why each one may or may not be a match. You can file anyway or, for a friction point, ask Copilot to link it to the existing issue instead.
If Linear can't be searched right then, Copilot checks Chameleon's last synced copy of your workspace instead and says so. You can still file.
Add screenshots to an issue
Ask Copilot to attach a screenshot you've shared in the conversation. It lists the ones it will include in the draft, and they're added to the issue only once you approve it.
Choose which teams Copilot files into
Copilot files only into the teams set for it, so issues land where your team triages them. Until you choose, it uses the teams Chameleon identified as building your product when it read your Linear workspace.
On the Linear Integration page, turn on each Linear team you want Copilot filing into, up to 10. With two or more on, you can set a default team, used unless you name another. With no default, Copilot asks which team to use each time.
If Chameleon can no longer see a team you chose because its access was removed or the team was deleted in Linear, Copilot keeps filing into your other teams. To restore access, revoke Chameleon's access in your Linear settings, then reconnect and select that team on Linear's Team access screen.
Control how Copilot writes for each team
Each issue matches how its team already writes, using the first of these that applies:
Memories you saved | Memories for that team come first, then memories for every team |
The team's Linear template | Used when the team has one |
A style learned from the team | Learned from recent issues people on that team wrote, when there's no template |
Chameleon's own format | Used when none of the above apply |
Click a team on the Linear Integration page to see what Copilot writes from, turn the team on or off, and edit its memories. A memory can apply to one team or to every team, for example, "APP issues start with the area in brackets." You can also save one from chat ("remember thatâŚ"). Each memory can be up to 500 characters, and Copilot keeps up to 5 per team and 10 for every team.
After the issue ships
When a friction issue Copilot filed is completed in Linear, Chameleon checks whether the friction actually stopped, comparing the share of users who hit it over equal periods before and after.
It posts the result as a comment on the issue: stopped, down but still happening, still happening, or not enough usage yet to tell. Chameleon only comments; it never reopens, edits, or relabels the issue.