Skip to main content

Project Pulse

The activity dashboard summarizing worktree and agent state across a project.

Updated
Reviewed

Project Pulse

Project Pulse is an activity heatmap, a personal view of your commit rhythm. It appears on the empty panel grid when no terminals are open for the active worktree, showing your git commit density over time alongside streak tracking and optional GitHub health signals.

Pulse reads directly from your local git log, so your commit history never leaves your machine. The optional GitHub Health Signals row does make API requests when a token is configured (see below), but the heatmap itself is entirely local.

The feature is on by default. To turn it off, go to Settings > General and toggle "Show activity heatmap on the empty panel grid". See Settings for more on that toggle.

Activity Heatmap

The heatmap renders your commit history as a grid of color-coded cells, arranged left to right from oldest to newest. Each cell is one day, with four heat levels for commit density: empty (no commits), low, medium, high, and full activity.

The pill toggle in the card header offers three ranges: 60 days (default), 120 days, and 180 days. Switching the range clears cached data and refetches from the git log.

Days before the repository's first commit are filtered out, so the heatmap starts at the actual beginning of the project rather than showing empty cells for dates that predate it. The most recent day with commits gets a subtle accent ring to help you orient. Hover any cell for a tooltip with the date and commit count.

Note

You may notice some zero-commit days highlighted with a red tint. These are missed day markers. They appear when a day with no commits is surrounded by activity within a 4-day window on either side, highlighting gaps in otherwise active periods rather than days you were simply away from the project.

Coach Line

A single line of motivational text sits below the heatmap, adapting to your current activity state:

ConditionMessage
Commits made today"3 commits today — nice." (actual count)
Active streak, no commits yet today"One small commit today keeps your streak going."
Active in last 7 days, no streak"Momentum's building: 4 active days this week."
Fallback"Make a tiny win: ship one small change today."

Summary Row

Below the coach line, a stats row shows metrics for the selected range:

  • Commit count in the selected range
  • Active days ratio (e.g. "47/60 active days")
  • Streak with flame icon and day count (when streak is longer than 1 day)
  • Uncommitted files with insertions/deletions count (when there are uncommitted changes)
  • Branch delta vs base branch showing ahead/behind commits, files changed, and insertions/deletions (only on non-default branches)

Streak

The streak counter tracks consecutive days with at least one commit. When your streak reaches 2 or more days, a flame icon appears in the summary row alongside the day count. The flame color shifts through tiers as the streak grows:

DaysColor
1–7Amber
8–14Light orange
15–29Orange
30–59Red
60–119Darker red
120–239Violet
240+Accent (legendary)

At milestone thresholds (30, 60, 120, and 240+ days), a short animated flame effect plays the first time you see the card that day. The animation respects prefers-reduced-motion and falls back to a static glow.

Tip

The streak is a nudge, not a target. It tracks your natural rhythm and is visible only to you. If the gamification isn't your thing, turning off Project Pulse in settings removes the streak display along with the rest of the card.

GitHub Health Signals

When the active project has a GitHub remote configured and a personal access token added in Settings > Integrations > Code Forge > GitHub subtab, a row of status chips appears on the Pulse card with live project health data:

  • CI status (passing, failing, pending, or no CI configured)
  • Open issues count
  • Open PRs count
  • Latest release tag with relative time
  • Security alerts count (Dependabot)
  • Merged PR velocity within the selected time range

Each chip links to its corresponding GitHub page. If no GitHub remote is configured, a hint prompts you to connect one. For token setup, see Code Forge.

Loading and Error States

While fetching data, the card shows a skeleton with a shimmer animation. If the repository has no commits yet, a placeholder reads "New repository — make your first commit to start tracking activity."

On fetch errors, Pulse retries automatically, up to 3 times with exponential backoff. A manual refresh button in the top-right corner of the card re-fetches both the heatmap data and the GitHub health signals at any time.