Engineering
Q
"What am I on the hook for this week?"
→
Three open Linear issues assigned to you — two in progress, one blocked since Tuesday. The blocked one is waiting on the auth review.
Open issues · LinearWork events · this week
Integrations · Linear
Halyard for Linear.
Your issue tracker knows what the team is actually doing. Halyard streams that activity in as work signals, so agents and teammates see live status without asking around.
01 · Connect
One OAuth flow.
Webhooks do the rest.
Halyard connects through Linear's standard OAuth flow and registers a signed webhook — no API keys to paste, no polling. Disconnect from either side at any time.
1
Open Settings → Integrations in Halyard.
Find the Linear tile and click Connect. You'll be sent to Linear's authorization screen.
2
Authorize the workspace.
A workspace admin approves the connection once — it covers the team, not each member individually.
3
Issue activity streams in.
Creates, status changes, and completions arrive as verified webhook events and land as work events in Halyard — no sync schedule to babysit.
02 · What Halyard captures from Linear
Work signals, not another copy of your tracker.
Linear stays the source of truth for issues. Halyard captures the activity stream — who's doing what, what changed, what's stuck — and folds it into the picture of your team's work.
→
Issue lifecycle events
Created, in progress, blocked, done — each transition lands as an attributed work event, so "what's the state of X" always has a current answer.
→
Open-work metrics
Halyard's open-task view aggregates Linear alongside your other trackers — open counts, idle time, and per-person load in one place.
→
Activity for agents
Agents answering "what did the team do this week" or "what's assigned to me" read the same event stream — grounded in the tracker, not guesses.
→
Not captured
Issue attachments and projects the webhook doesn't cover. Linear remains where you manage the work — Halyard just keeps everyone (and every agent) current on it.
03 · What your agents can answer now
Live status, zero standup.
Concrete scenarios where an AI tool that can see your tracker beats one that can't.
Product
Q
"What did the team actually ship last sprint?"
→
Issue completions grouped by project — realtime rollout closed out (6 issues), meeting capture polish (4), two carry-overs flagged.
Completed issues · LinearSprint summary
Manager
Q
"Is anything stalling right now?"
→
Open-task metrics show two issues idle past the team's usual cycle time, both in the same project — likely the same upstream blocker.
Open-task metricsIssue activity · Linear
Your tracker, part of the picture.
Connect Linear once. Status questions answer themselves.