Skip to main content

COLLECT DAILY LINEAR ACTIVITY FOR A STANDUP REPORT

This guide shows you how to record one Linear user's activity for a day as a linear_activity resource that a standup or end-of-day report can read. The guide uses @mgreten/linear-activity.

Prerequisites

  • A Linear personal API key stored in a vault named linear under the key api-key (see Vaults). The activity recorded is that of the user who owns the key.
  • The keys of the Linear teams to include, such as ENG

Pull the extension

swamp extension pull @mgreten/linear-activity

You will see output like:

INF extension·pull: Pulling "@hivemq/linear"@"2026.03.30.14"
INF extension·pull: Identity verified: "@hivemq/linear"@"2026.03.30.14"
INF extension·pull: Pulled "@hivemq/linear"@"2026.03.30.14"
INF extension·pull: Extracted 6 files:

Set up the behavior

Create a behavior named linear-activity of type @mgreten/linear-activity (see Create and Run a Behavior). Set apiKey to a vault expression and teamKeys to the teams to report on:

globalArguments:
  apiKey: "${{ vault.get('linear', 'api-key') }}"
  teamKeys:
    - ENG
    - OPS

To cover every team the key can see, set teamKeys to an empty list.

Record today's activity

swamp behavior run linear-activity daily_activity

This command gathers the key owner's activity for today in the configured teams. It covers issues completed, issues moved to In Review, issues created, comments written and current in-flight assignments, and writes them as a linear_activity resource.

Record activity for an earlier date

To review an earlier day, such as yesterday's work before a morning standup, pass the date:

swamp behavior run linear-activity daily_activity --input date=2026-10-14

This command gathers the same activity for 2026-10-14 and writes it as a linear_activity resource for that date.

To read the recorded activity from a report or script, query the linear_activity data (see Query and Manage Data). To record it every working day, call daily_activity from a workflow on a schedule (see Run Workflows on a Schedule).