How to Use the Linear Connector in Muse

1. The short answer

As of October 25, 2026, Linear is a live connector in Muse. Linear is the issue tracker: teams plan work as issues, group them into projects, and move them through states from backlog to done. The connector was in the in app list by September 29, 2026, as one of the business tools Meta named that day, and it was still listed in the October 15 in app check, which counted 54 connectors in the web app. There is no October change to how it works. One honest caveat belongs right here at the top: Meta has not published a detailed list of what the connector can do inside Linear, so this guide describes issue tracking in plain terms, tells you exactly what is confirmed and what is not, and shows you how to read the permission screen on your own account before you trust it with anything important.

Here is the honest version. The Linear connector matters because your backlog is where your plans already live, and most teams lose the thread of it. Issues get written, triaged, started, and then forgotten. Priorities shift in a meeting and nobody updates the tracker. By Friday, nobody can say what is blocked, what is due, or what slipped without anyone noticing. A connector that lets you ask those questions in plain words turns the tracker from a list you scroll into a briefing you read. The rest of this guide covers how to connect it, the triage prompt to run first, and the uses that are actually worth your time, with the limits stated plainly where the published record runs out.

Muse is invite only right now. Need an invite code? Click here to grab one free from the community pool. Waiting on a launch in your country? Join the waitlist and we will send you a fresh code on launch day. Muse is available in the United States, Canada, and Japan.

2. What you need

• Muse access. You need an account with access first, in the United States, Canada, or Japan, where Muse has launched.
• One Linear workspace. The connector works with the Linear workspace you connect, and only that workspace. Pick the one where your team plans its work.
• Your Linear sign in. You connect with your Linear account, the same way you sign in to Linear itself.
• Approvals set to ask me. Before you connect anything, set approvals so nothing is created, changed, or closed without your tap. This is the single most important step on this page, because an issue tracker is a shared record, and a change there is visible to the whole team.
• Team and project names. Know the names of your teams and projects as Linear spells them. Muse works from what you name, so a wrong name gets you the wrong project, and a vague name gets you a vague answer.

3. How to connect it, step by step

The connection itself takes a few minutes. The setup around it matters more, because neither vendor has published a full action list, so run the steps in order and read every screen before you accept it.

1. Open Muse and go to Settings. The connectors list lives there. What is printed there is what your account has, because rollout is staged and two accounts can see different lists on the same day.
2. Find Linear in the connectors list and open it. If Linear is not listed, your account has not received it yet. There is nothing to install and nothing you broke. Check again in a few days.
3. Click Connect and review the connection details. Read what Muse is asking for before you accept it. This screen is your source of truth for what the connector can do on your account, so read it slowly. If a scope surprises you, stop and check what it covers before continuing.
4. Sign in to Linear and authorize Muse. Use the Linear account tied to the workspace where your team works. Remember this is the one workspace the connector will use, so sign in with the right one the first time.
5. Open the connector settings and check each action. After you connect, look at the per action settings in Muse. Set anything that creates, changes, or closes issues to ask you first. If an action is listed that you do not want Muse to have at all, turn it off here rather than hoping you will remember later.
6. Set approvals to ask me. In Muse settings, set approvals so that anything that touches your issues waits for you. This is what stops Muse from ever closing an issue you have not reviewed.
7. Test with a read only request. Ask Muse to find an issue you know is there and describe its state. Read the answer against Linear. If it matches, the connection is good. Do not ask it to change anything on the first day.
8. Use it read only for a week. Finding, reading, and summarizing only. Once you trust what it reads and how it describes your work, start approving one small change at a time.

Copy this prompt

You are my planning assistant. Use my Linear connector only.
Rules: you never create, change, or close an issue without my explicit approval. You find, read, and summarize. I approve every change.
My team: [team name]. My projects: [project names].
Every morning, do this in order.
1. List what is blocked, with the issue name, the owner, and what it is blocked on.
2. List what is due this week, with the owner and the due date.
3. List what slipped last week: issues that were due and are still open.
4. Flag anything with no owner or no date, and say so plainly.
5. End with the 3 issues I should look at first today, in order.
6. If a status looks wrong, say so and show me what Linear says. Do not guess.

4. What it actually does

The connector earns its place with five uses. Everything else is a variation on one of them. One note of honesty runs through all five: the exact list of actions on your account is the one shown in your connector settings, because Meta has not published a full list for Linear. The uses below describe issue tracking as it works in practice, and the permission screen is the final word on your account.

Find an issue without scrolling the backlog

Ask Muse to find the issue about a named bug, the request from a named customer, or the task that mentions a deadline. This beats scrolling the backlog yourself when you remember what an issue is about but not its number, because Muse reads for meaning. It also beats searching by keyword when the words in the issue are not the words you would use to describe it. Use it when someone asks you for a status in a meeting and you need the answer in seconds, not after a search through three projects. Our Gmail connector guide covers the other half of this habit, finding the message that created the issue in the first place.

Triage the backlog before the week starts

Ask Muse on Monday for the shape of the backlog: what is new, what is blocked, what has no owner, and what has been sitting untouched the longest. This is the use that pays off before planning, because a backlog you have not looked at in a month holds surprises, and surprises found on Monday are cheaper than surprises found on Friday. A good triage tells you what to discuss, what to close, and what to push back on. It does not make those calls for you. Priorities are a team decision, and Muse can lay out the facts for it, but the call stays yours. Run the triage, read it, and then decide with the team, not before.

See what is blocked, and what it is blocked on

Ask Muse for every blocked issue, with the owner and the thing it is waiting on. This is the single most useful question in issue tracking, because blocked work is invisible work: it sits in a state that looks like progress and quietly eats the week. A blocked list with reasons tells you where to unblock, who to chase, and what to escalate. Run it daily if you run a team, and twice a week if you work solo. The follow up question is the one that matters: for each blocked issue, what is the next action, and who owns it. An issue that is blocked with no next action is not blocked. It is abandoned, and the honest thing is to say so.

Prep for the team check in from the tracker

Before a team check in, ask Muse what changed since the last one: what moved, what slipped, and what is due before the next one. This turns the check in from a round of memory into a review of facts, which is what it is supposed to be. Pair this with the notes side: our Notion connector guide covers project context in docs, and Linear covers the state of the work itself. The combination is a prep note that takes a minute to read and makes you the person who knows where things stand, which is a rarer skill than it sounds.

Link the work to the context around it

An issue on its own is a title and a state. The context lives elsewhere: the email that asked for it, the doc that scoped it, the meeting where it was agreed. Ask Muse to pull those threads together for one issue, using the connectors you have already added. The value is not in any single source. It is in the join: what was asked, what was decided, and what is the state now, in one short brief. Our connectors list shows the other tools Muse can reach when the context for an issue lives in more than one place. Keep the brief short, check it against Linear before you share it, and treat it as a starting point for the conversation, not the last word on it.

5. What it cannot do

The limits are honest and worth knowing before you lean on the connector.

• It cannot tell you its full action list from a public page. Meta has not published a detailed list of what the connector can do inside Linear. The permission screen on your own account is the source of truth. If an action matters to you, check that screen before you plan around it, and do not assume a use exists because another connector has it.
• It cannot see workspaces outside the one you connected. Issues in another Linear workspace, another tracker, or a spreadsheet are invisible to it. It reasons from what you connected, nothing more.
• It cannot guarantee a status is right. A status can be out of date, an owner can have changed, and a due date can have moved without the issue being updated. Check anything you plan to report to someone else against Linear itself before you say it out loud or put it in writing.
• It cannot replace the team agreeing on priorities. Muse can lay out what is blocked, what is due, and what slipped, but the call about what matters most is a human one. A triage that nobody discusses is a list. A triage the team argues about for ten minutes is a plan.
• It cannot fix a tracker nobody updates. If issues sit in the wrong state for weeks and nobody closes what is done, Muse will summarize the mess faithfully. The answers get dramatically better once the team keeps states honest. A tracker you trust beats a tracker you have to double check every time.

6. What to watch for

As of October 25, 2026, Linear is a settled connector: in the in app list by September 29, and still listed in the October 15 in app check. There is no October update to how it works, so the habits around it still matter. The most important habit is the verification habit. An issue tracker is a shared record, and a wrong status reported with confidence is worse than no status at all, because the team acts on it. Check the answer against Linear for the first week, especially any state, owner, or date. A wrong date acted on fast is worse than a slow read you verified.

There is also a second route worth knowing about, and it is worth stating clearly so the two do not get confused. A Reddit user showed Muse building a custom Linear connector in under a minute, using a Linear API key, that could list teams, search and create issues, and update their status, with the key going into secure storage and the agent never seeing it. That was a custom connector Muse built on the spot, not the directory connector this guide covers. If the directory connector is not on your account yet, the custom route is a real fallback, and any service with a public API can be connected that way. But do not quote the demo as proof of what the directory connector does. They are two different doors into the same app, and the permission screen on your account tells you which one you are using.

Be careful with sensitive work. Roadmap plans, hiring issues, security work, and anything with customer data deserve a human read before any change goes out, even a small one. A status change is a small change with a visible audience, because the whole team sees the tracker. Set a rule for yourself: Muse finds and drafts, you read, you approve. The moment you start approving without reading is the moment the connector stops being an assistant and starts being a risk.

Check your data controls. In Muse settings, open Data controls and look at the switch for helping improve the models. If you do not want your chats used for training, turn it off before you start asking Muse to read your issues. That switch controls whether Meta may use your chats to train future models. And keep the tracker honest, because the connector rewards honesty more than any other connector on this site. States that match reality, owners that are real people, and dates that mean something. A tidy tracker turns Muse from a search box into a colleague who knows where the work stands. A stale tracker turns it into a colleague who keeps reporting last month as this week.

Get started

Frequently asked questions

What can Muse do with my Linear issues?

Muse can find issues by meaning, triage the backlog, list what is blocked and what is due, and brief you before a team check in. The exact list of actions on your account is shown in the connector settings, because Meta has not published a full public list for Linear. Read that screen before you plan around any action.

Which Linear workspace does Muse see?

Only the one you connect. Muse works with the issues available through that Linear workspace and the access you authorize. Work in another workspace stays invisible to it, and you can manage or disconnect the integration at any time.

Can Muse close an issue for me?

Not without your approval when your approvals are set to ask me. Set anything that creates, changes, or closes issues to ask first, and read every change before you approve it, because the whole team sees the tracker.

What if Linear is not in my connectors list?

Check again in a few days, because rollout is staged. As a fallback, you can ask Muse to build a custom Linear connector from the Linear API, which one user demoed in under a minute. That is a separate route from the directory connector, with its own permission screen.

Can I use the Linear connector outside the United States, Canada, and Japan?

Not yet. Muse itself has launched in the United States, Canada, and Japan only. Join the waitlist and we will send you a fresh code on launch day in your country.

What happens if I disconnect Linear?

Muse loses access to those issues. Your work stays in Linear, and nothing Muse planned is carried out after you disconnect. You can reconnect the same workspace or a different one later.

Built with Muse is an independent community project. Not affiliated with or endorsed by Meta.