Assign the Linear issue to Echelar. Get back a pull request.

Anyone in your workspace can assign an issue to Echelar. A Session works it in an isolated sandbox where the issue's followers can watch every step, and the pull request comes back attached to the issue for your team to review.

  1. Issue assigned
  2. Repository resolved
  3. Session visible
  4. Pull request attached
  5. Board untouched
Bring one ticket from your backlogWatch the demonstration

Thirty minutes with the founder. One repository, read-only, is all it needs.

Why the backlog outgrows the sprint

Small fixes wait behind big work

The two-hour change is six months old because it never wins planning.

Quick wins are never quick

Whoever picks one up pays the context switch.

The ask gets rewritten three times

In a ticket, in a thread, in standup — before anyone opens the code.

Demonstration

Assigned issues

Assign the issue. Watch the Session. The pull request attaches.

Assign a Linear issue to Echelar. It resolves the repository from the team mapping, a Session does the work with each tool call visible, and pull request #263 attaches to the issue. The board column stays where it was: by default Echelar leaves issue states alone, and moves them only through an Automation you author.

Demonstration — authored data · the board moves only through an Automation you author
Starts when visible

Sequence description

  1. Issue BILL-248, Usage-based invoice credits, sits in Todo on the Billing board.
  2. A person on the team assigns the issue to Echelar.
  3. Echelar resolves the repository from the team mapping: Billing to acme/billing-console.
  4. A Session reads the repository architecture and billing conventions at the current commit.
  5. The Session edits the credit application path and its test.
  6. The Session checks the billing credits spec, and it passes.
  7. Pull request 263 opens in acme/billing-console and attaches to the issue as a comment with the link.
  8. The board column does not move. The pull request is attached and the board is unchanged.

Demonstration on a fictional Acme workspace — authored data.

How Echelar works a Linear issue

Sent to the right repository
Your Linear team, project, and labels tell Echelar which repository the work belongs in. When that is unclear, it asks a person instead of guessing.
Visible while it works
The Session shows its tool calls, changed files, and checks. Anyone following the issue can watch.
The pull request attaches to the issue
The result comes back where the work started, carrying the requester's name.
Your board moves only if you say so
By default Echelar leaves issue states alone: progress streams as Agent Session activity on the issue, and the pull request attaches when the work is done. If you want the board to move, you author that as an Automation and a person enables it.

Linear tickets, before and after Echelar

Without EchelarWith Echelar
The ticket nobody startsSits in the backlog for another quarter.Assigned to Echelar; a pull request comes back for review.
Where progress is visibleAsk in standup.In the Session, and on the issue.
Who mergesWhoever finally picked it up.Your team, from a pull request with the evidence attached.

Same job, on your repository.

Bring one ticket from your backlog

Linear agent FAQ

What do we need to connect?

The Linear integration for your workspace, the GitHub App on the repositories, and a mapping from teams, projects, or labels to repositories.

What kinds of issues work?

Scoped changes with a clear outcome: a bug with reproduction steps, a small feature with acceptance criteria. Ambiguous issues get a question back, not a guess.

How do we stop it if it heads the wrong way?

The Session is live; you see each step and can reply on the issue. Code stays in the sandbox until it returns as a pull request.

Do I need to be an engineer to assign a ticket?

No. Anyone in the workspace can assign an issue.

What does it cost?

Echelar is launching now. Early teams work directly with the founder and agree pricing together.

Bring a real ticket.

Pick a small, scoped issue that has been sitting for months. We assign it to Echelar live, and you watch every step until the pull request attaches for your team to review.

Bring one ticket from your backlog

Not ready to book? Read how access and approvals work first.

One team of agents. Four more jobs.