An Eve agent for Linear operations across Linear, Slack, and scheduled runs.
Linear Operations Agent is an eve agent that keeps Linear as the operational source of truth while meeting your team where work actually starts. You mention or delegate to it inside Linear Agent Sessions, mention or DM it in Slack threads, or let six built-in schedules run digests for triage, cycle health, backlog hygiene, project summaries, P0/P1 monitoring, and weekly initiative updates.
All Linear reads and writes go through a single Linear MCP connection to https://mcp.linear.app/mcp with an explicit tool allow-list: eleven read tools such as list_issues, get_issue, and list_cycles, and six write tools such as save_issue, save_comment, and save_status_update. A dynamic approval policy gates every sensitive write, so issue creation, priority changes, reassignments, and bulk actions always require human sign-off first.
It ships ten skills covering triage, duplicate detection, clarification, decomposition, incident support, Slack intake, and project, initiative, cycle, and backlog reporting. Two included evals verify the safety contract: triage produces evidence-backed proposals without calling save_issue, and initiatives outside LINEAR_OPS_COVERED_INITIATIVES never receive automated status updates.
Mention the agent on a vague bug report and it reads the issue and comments through MCP, checks for duplicates, proposes type, priority, labels, and next steps with cited evidence, then asks for approval before applying anything with save_issue.
Mention the agent in a Slack discussion and it summarizes the thread since its last reply, separates discussion from decisions, drafts a Linear issue or links the thread to an existing one like ENG-123, and requests approval before creating anything.
Weekday triage and cycle-health digests plus Monday backlog and project summaries flag issues stuck in triage, missing owners or priorities, stale updates, and blocked work, each delivered read-only to its own configurable Slack channel with concrete next steps.
For initiatives you explicitly list in LINEAR_OPS_COVERED_INITIATIVES, the agent writes a weekly status update directly to Linear every Monday with no approval round-trip. It refuses unlisted initiatives, and an included eval verifies that refusal.
Run npx shadcn@latest add @evex/linear-operations-agent in an existing Eve app, then pnpm install. After configuring the connectors, pnpm info should list the linear and slack channels, one MCP connection named linear, six schedules, and ten skills, with no custom Linear SDK tools.
The agent is defined in agent/agent.ts with model openai/gpt-5.4-mini. Change the model string there to any model your Eve deployment supports; instructions, skills, and the approval policy are model-agnostic.
Almost never. Reads, non-destructive save_comment proposals, and weekly initiative updates for explicitly configured initiatives run without approval. Everything else, including issue creation, state, priority, assignee, project, cycle, and relationship changes, any priority 1 or 2 write, project and document writes, and deletes, is approval-gated.
Set LINEAR_OPS_COVERED_TEAMS and LINEAR_OPS_COVERED_PROJECTS to filter which Linear events wake the agent, and LINEAR_OPS_READ_ONLY_TEAMS to keep it propose-only for certain teams. Empty values mean all teams and projects are covered.
Bulk actions are capped by LINEAR_OPS_MAX_BULK_ISSUE_COUNT, defaulting to 10 issues. All six cron schedules are overridable via env vars and evaluated in UTC, for example daily triage at 0 7 on weekdays and weekly initiative updates at 0 9 on Mondays.
npx shadcn@latest add @evex/linear-operations-agent