Linear

Mirror a PugBase plan as Linear issues. Whoever is assigned in Linear - a person or an agent - is pointed at the brief, and what PugBase learns flows back as comments.

Why

Teams plan and assign agents inside Linear (Cursor, Codex, Devin, Linear's own agent). PugBase does not compete with that board: it mirrors the plan into it, keeps the brief, the handoff and the Team Memory on the PugBase side where agents read it over MCP, and writes QA and review outcomes back onto the issue.

Connect (Pro and Team)

Settings > Integrations > Linear > Connect. Authorize the Linear workspace; PugBase stores the token encrypted for your account only.
Tokens are refreshed automatically; Disconnect revokes them.
The person who runs the first sync becomes the account PugBase comments as. Pick someone who stays on the team.

Mirror the plan

From any agent connected to PugBase, ask for linear_sync_plan with the Linear team (and optionally project). One issue per task note with a checklist; notes already linked are skipped, so you can run it again after the plan grows.

# in Claude Code / Cursor / Codex with the PugBase MCP server connected
"Mirror this plan into Linear team ENG (linear_sync_plan). Dry run first."

Each issue's description links the PugBase note, tells an agent to call get_note_spec before starting, and mirrors the checklist as it stood at sync time. The first sync also registers PugBase's webhook in your Linear organization.

What flows back

Progress is tracked in PugBase (ticks with evidence, reopens with reasons). Linear gets the summary as comments on the linked issue:

QA reopens a task        -> comment: Reopened by QA + the reason
A task note completes    -> comment: Done in PugBase (n/n)
An agent pushes a handoff -> comment: Handoff pushed, read it with get_note_spec
A PR opens for review    -> comment: Review requested + link
Someone is assigned in Linear -> comment: PugBase handoff (open items, last QA reason, where the brief is)

Agents assigned in Linear

When an issue linked to a task note is assigned or moved to a started state, PugBase comments the handoff: the open items, the last QA reason, and the exact get_note_spec call. get_note_spec itself pushes the spec, the latest handoff and the Team Memory rules for the files involved - so an agent that starts from Linear still starts from the plan.

Team Memory / Webhooks

Limits

One Linear organization per workspace (the connector's). Issues are created in the team you name; sub-issue nesting per feature is not created automatically.
Comments go one way: PugBase writes to Linear. Editing the checklist in Linear does not tick anything in PugBase.
If Linear is unreachable, PugBase still records the tick / reopen; the comment is skipped and the Audit log shows the failed write.