Problem

The Remind Me feature (shipped Jan 2023) lets users set reminders on issues, documents, projects, and initiatives — but it's only accessible through the UI. There is no corresponding GraphQL mutation to create, update, or delete reminders programmatically.

I confirmed this by searching the public schema (schema.graphql) and the generated SDK documents (_generated_documents.graphql). The word "reminder" only appears in read-only notification fields (emailedAt) and project/initiative update frequency settings. No createReminder, issueReminderCreate, or equivalent mutation exists.

The only reminder-adjacent mutation exposed today is createProjectUpdateReminder, which is scoped to project update cadence — not arbitrary reminders on issues or documents.

Why this matters

For human developers and integrations

• Workflow automation: Teams using Linear's API to build triage bots, SLA monitors, or on-call rotations cannot programmatically say "remind the assignee about this issue in 3 days."
• Cross-tool sync: Users who manage schedules across Linear + Calendar + Slack have no way to set Linear reminders from external triggers.

For AI agents — an increasingly first-class Linear use case

Linear positions itself as the Mission Control Plane for AI agents. Tools like Cursor, Factory AI, and OpenClaw already interact with Linear via API and MCP to read issues, create PRs, and update status. But agents today cannot schedule follow-ups on their own work.

Concrete scenario: an AI agent is assigned an issue, opens a PR, and needs to check CI results in 30 minutes. Today it has no way to set a reminder via API — it either polls indefinitely or loses track entirely.

As the pattern of managing fleets of AI agents through kanban boards matures (see Vibe Kanban, Claude Code Tasks), reminders become a critical primitive. Agents need the same self-scheduling capabilities humans have.

For the official Linear MCP server

The Linear MCP server currently supports 21 tools (issues, projects, comments, labels, etc.) but no reminder operations. Exposing reminders in the API would naturally extend to MCP, giving both human-in-the-loop and autonomous agent workflows access to time-based follow-ups.

Proposed API surface

# Mutations
createReminder(input: ReminderCreateInput!): ReminderPayload!
updateReminder(id: String!, input: ReminderUpdateInput!): ReminderPayload!
deleteReminder(id: String!): DeletePayload!

# Input
input ReminderCreateInput {
  issueId: String      # one of these
  documentId: String   # should be
  projectId: String    # provided
  initiativeId: String
  remindAt: DateTime!
}

# Query
reminders(filter: ReminderFilter): ReminderConnection!

This would follow the existing pattern of entity-scoped mutations (createComment, createProjectUpdate, etc.) and keep the schema consistent.

MCP extension

Once the API mutations exist, adding create_reminder, list_reminders, and delete_reminder tools to the official MCP server would be straightforward and high-value.