Issue and Sub-Issue Updates

Linear organizes engineering work as issues with states, assignees, labels, and priorities. A Beam agent watches for new bug reports or status changes, reads the issue details, and applies a team-approved rule: setting priority from severity keywords, assigning to the owning squad, or adding labels that fit the affected area. It posts a short comment noting what it changed. When an issue is ambiguous, spans several teams, or lacks reproduction steps, the agent leaves it untouched and asks a triage lead to make the call before anything moves forward in the workflow.

Cycle Planning

Cycles are Linear's time-boxed sprints that group issues a team commits to finishing. A Beam agent reviews the active cycle, reads scope changes and remaining estimates, and applies planning rules the team set: moving unfinished low-priority issues to the next cycle, flagging issues with no estimate, or nudging owners on items past their due date. It summarizes cycle health in a comment for the standup. Decisions about cutting scope, changing commitments, or reassigning heavy work stay with the engineering manager, whom the agent notifies with the specifics for a final decision.

Project Roadmap Status

Projects in Linear collect issues under a larger deliverable with a target date and health status. A Beam agent watches issue completion across a project, reads progress against the milestone, and updates the project status field using the team's thresholds: marking a project at risk when open issues outnumber the days left, or noting a blocker in the update feed. It drafts the weekly project update from real issue movement. Judgment calls about scope, deadlines, or whether to greenlight the next phase route to the project lead for sign-off.