Work — issues, projects, cycles and initiatives, with agents as assignees

Work is an issue and project tracker: team-scoped workflow states you can rename freely, sub-issues and relations, labels, threaded comments, projects with milestones and health updates, cycles that roll unfinished work forward, and initiatives above them. Two things are different from the trackers you know: an agent can be the assignee of an issue — with a person always named as accountable for it — and anyone can be named on an issue, including someone who only has an e-mail address, without that giving them access to anything.

Turn the block on

Under Blocks, enable Work. The card lists the price of every operation before you enable it. Then open Work → Settings → Teams and set up one of your account's teams for work: give it a key (the ENG in ENG-123). The team gets one workflow state per category — triage, backlog, to do, in progress, done, canceled — which you can rename, add to and reorder; the category is what reports and filters use, so renaming "In progress" to "Building" changes nothing else.

Issues

New issue on Work asks for a title and a team; the rest is optional and sits under More. Assign it to a member, a team, an agent, or an e-mail address. When you pick an agent, the form asks who is accountable — the person who answers for the agent's work — and will not save without one.

The list filters by state, assignee (me, agents, unassigned, an address), priority and text; More filters adds labels, projects and the active cycle. Save a filter as a view: views keep a stable key, and a relative date ("created in the last two weeks") stays relative. The board shows a team's issues by state; move a card with its state menu.

An issue's page has the description, sub-issues, relations (blocks, related), links (the same URL twice updates the link), comments with one level of replies and reactions, and the history of every change — including which agent made it and for whom.

Triage and requests from outside

With triage on, new requests from outside land in the team's triage list: accept (into the team's default state, or one you pick), decline, or snooze. Triage responsibility either assigns requests round-robin over a list of people or notifies everyone on it. A request from a form or another system comes in through POST /v1/accounts/{account}/work/intake with your API token; an e-mail comes in through an inbound e-mail connection and an agent subscribed to it, which files it with the sender as the requester.

People named on work who have no account get the updates that concern them by e-mail — every e-mail has an unsubscribe link that works without signing in.

Planning

Projects span teams and carry a lead, dates, milestones and updates; each update states its health (on track, at risk, off track) and the project's health is the latest one. Progress counts finished work plus a quarter of work in progress, over the total estimate. Cycles are per-team sprints: when one closes, what was unfinished moves to the next and the list of what was left is kept. Initiatives group projects.

Automations and SLAs

An automation is a trigger (created, updated, either), a condition written as a filter, and actions (set a state, assign, label, comment, notify). Choose when the condition starts matching and a rule fires once on the change that made it true — never again on its own edit. An SLA rule gives matching issues a deadline in hours, days, business days or weeks; the first matching rule wins and changing a rule never moves existing deadlines.

Webhooks, import and export

Settings → Webhooks sends issue and comment events to an https:// endpoint, signed with HMAC-SHA256 in the X-Connect0-Signature header (t=<unix seconds>,v1=<hex HMAC of "<t>.<body>">). The secret is shown once. Failed deliveries retry for a day; five failures in a row turn the webhook off with the reason.

Settings → Import / export reads Linear's CSV export (or its API JSON): map Linear's teams to yours, run the preview — it is the real import, rolled back — then import. People are matched by e-mail. Export gives you everything you can read as JSON, or issues as CSV.

Agents

Through MCP, agents read work (work.list_issues, work.get_issue, work.search, work.list_views, work.run_view) and change it (work.create_issue, work.update_issue, work.comment, work.transition, work.assign). work.run_view gives an agent exactly the set a person sees for a saved view. work.delete_issue, work.merge_duplicate and work.bulk_update ask for confirmation, and an agent cannot delete or merge.