ingest-linear

You can ingest Linear activity into a markdown vault by running a command that captures team or project issues, comments, and status changes, writing them as daily markdown files to feed your knowledge graph.

Automating Linear data ingestion involves orchestrating Linear API calls to capture recent activity and delegating normalization to write deterministic, frontmatter-based markdown files into your vault for downstream processing.

Daily Linear ingestion handles duplicates through idempotency by writing one file per scope per day to a specific date path, overwriting the existing file if the ingestion is run again on the same day.

Yes, you can capture Linear project status changes for specific date ranges by invoking the ingestion command with a scope argument and specifying the number of recent days to include.

Linear issues imported into a decision log require a deterministic, frontmatter-based markdown format stored under External Inputs, ensuring the data can be queried by downstream knowledge graph and session closure layers.

Limitations include writing data only at a daily granularity per scope and relying on the Linear MCP for data retrieval, which restricts ingestion to recent activity rather than real-time streaming or historical archives beyond the specified days.