FeaturesLinear

Delegate the ticket. Get the pull request.

Install fctl's app in your Linear workspace and fctl turns up wherever you hand out work. Delegate an issue to it, and a session starts in the project that takes the issue's team, as you, on your Claude plan. The ticket moves to In Progress, the agent answers in its thread, and the pull request comes back linked.

Connect Linear How it works

shop#231 as it started: Tomás delegated SHOP-419, Danish translations for the shop, to fctl in Linear, and fctl moved the ticket to In Progress.

Aiko's delegated ticket, DEL-97, at the top of its session on a phone.

Delegate Like a teammate

Assign the issue to fctl, or mention @fctl in a comment. You stay its assignee; fctl does the work.

Explore A plan first

Label it explore, and the agent comes back with a plan and a size, and changes nothing until you say go.

Reply In the thread

The agent answers where the ticket's people talk. Reply there, and your message reaches it at its next step.

Link Ticket to merge

Branches carry the ticket's key, so Linear's GitHub integration links the pull request and moves the ticket as it merges.

Not sure yet? Ask for a plan.

Some tickets need thinking before typing. Jonas wanted to know what gift boxes for companies would take, so he labelled the ticket explore and delegated it. The agent read how the shop orders and how the platform invoices, built nothing, and answered in the ticket with four pieces of work, a size, and the three questions that would change it.

A reply there with the answers starts the work, in the same session, with everything it read.

SHOP-398In Progressexplore

Gift boxes for companies

Three companies asked whether they can send boxes to their staff for Christmas. Explore what it would take: ordering for many addresses at once, invoicing the company, a card with a message. Don't build it yet: I'd like a plan and a rough size first.

Jonas Weber delegated the issue to fctl · 6 days ago
fctl · Exploring this in fctl session shop#212, as Jonas Weber.
fctl replied · 6 days ago

A plan for gift boxes for companies, and a rough size. Nothing is built yet.

1. Company orders (platform, about 4 days)
2. An address list (shop, about 3 days)
3. One invoice (platform, about 4 days)
4. A card in each box (shop and packing, about 2 days)

Size: about three weeks for one person. Before I start: invoice only, or card as well? One box for everyone? Homes only, or the office too?

Linear sees the gist. You see everything.

In Linear, the agent's steps show as it works, its to-do list as the session's plan, and its last message of each turn as a reply. Each step says what the agent does without what could hold a secret: a command's description, not the command.

The fctl session has the rest: every command, every edit, and a line for each thing fctl did in Linear, so nobody wonders whether the ticket heard.

The end of shop#212: the agent's plan for gift boxes, and fctl's note that it replied on SHOP-398 in Linear.

One team, one project, a few switches.

A workspace's admin connects Linear once. Each project then picks the team whose tickets it takes, or one of the team's Linear projects, and decides whether delegated tickets move to In Progress and which label asks for an exploration.

As the person who asked. Sessions start as whoever delegated, while they may start sessions in the project.
On GitHub instead? Projects can take their repositories' GitHub issues as tickets the same way.
Agents use tickets too. They read, file and comment on them with fctl ticket, where the project allows.

The Shop project's tickets: Linear, the Shop team, delegated tickets moved to In Progress, and explore as the label for an exploration.

A delegated ticket's session on a phone.

In the docs

Connecting Linear, linking people's accounts, and what goes back to the ticket.

Start a factory tonight.

curl -fsSL https://fctl.sh/install | sh

Get started Open the app