Glance Claude Code mod: your Claude Code calendar, PRs and Slack on a line

Glance is a community mod by Hamza Zafar (hamzafer), part of his claude-code-mods collection. It turns the space above the Claude Code prompt into a Claude Code calendar and inbox line: one row of text that says what needs you right now. Up to four parts are shown, in this order: the next meeting, the most urgent pull request, a Linear issue you are working on, and the latest Slack message to you.

A line can read like 📅 Team standup in 18 min · 🔀 mods#19: CI failing +2 · 📋 ENG-1 In Review: Ship the thing +1 · 💬 Kim: "can @me look at the doc?" +2. The meeting turns yellow within 15 minutes and cyan while it is running, and a failing PR turns red. On a narrow terminal each part shortens in steps, Slack first and the meeting last. /glance refreshes everything and prints the full lists.

The install block above adds the author's marketplace and installs the plugin from it. Glance does not work on its own: connect the Google Calendar, Linear and Slack connectors in Claude Code, and sign in to the GitHub CLI (gh auth login). Any one of the four is enough to see a part of the line. The line appears after the first fetch, shortly after the next session start.

On session.start the mod registers /glance, starts a refresh in the background and a one-minute clock. Every 5 minutes at most, it fetches all four sources at once, and each one fails on its own. Connector calls go through $.mcp.call. This helper, from hooks/register.tsx, reads the JSON the connector returns:

// A connector's answer is JSON in its first text block.
async function mcp($: EngineInterface, server: string, tool: string, args: Record<string, unknown>) {
  const result: McpToolResult = await $.mcp.call(server, tool, args)
  const block = result.content.find(c => c.type === 'text') as { text?: string } | undefined
  if (result.isError || !block?.text) throw new Error(`${server} ${tool} failed`)
  return JSON.parse(block.text)
}

The calendar call is list_events on claude.ai Google Calendar. Linear is list_issues for your started issues. Slack uses slack_read_user_profile once and then slack_search_public_and_private twice, for DMs and for mentions. GitHub is one gh api graphql query that asks for review requests to you and your own open PRs with their CI state. hooks/pick.ts holds the pure ranking code: all-day, declined and finished events are skipped, a block running now that is longer than 3 hours does not hide the next meeting, and PRs are ranked review requests first, then failing CI, then changes requested. The line is drawn on the AbovePrompt render site, above whatever Claude Code and other mods draw there.

There are no options in /config. To change what is shown, edit the constants at the top of register.tsx: EVERY_MS for the fetch interval, TICK_MS for the countdown tick and SLACK_WINDOW_S for how far back Slack messages count. The queries and the ranking live in pick.ts. To use only some sources, simply do not connect the others.

We read every file the plugin can execute before running it: plugin.json, hooks/hooks.json, hooks/register.tsx, hooks/pick.ts, the type declarations and the tests. There is no package.json, install script, binary or bundled code. Here is what we found:

• Calls connectors ($.mcp.call): read-only requests to claude.ai Google Calendar (list_events), claude.ai Linear (list_issues), and claude.ai Slack (slack_read_user_profile, slack_search_public_and_private). These use the connectors you have already authorized in Claude Code. Calendar, issue and message titles, senders and text are read from them and drawn on screen.
• Runs a command ($.process.run): gh api graphql with a fixed query, as an argv array with no shell and a 20 second timeout. It reads your PRs through the GitHub CLI login you already have.
• No direct network access: the code has no fetch, sockets or hosts of its own, no telemetry, and it does not send the data it reads to any other service.
• No file writes, no daemons: it does not write files, settings, shell rc files or LaunchAgents. The fetched items live in host-held $.state atoms for the session. The only timer is $.clock.every, which stops with the session.
• No secrets read: no environment variables, tokens or keychains. Authentication stays with gh and the connectors.
• No prompt influence and no gating hooks: it adds no text to prompts or tool results, and does not block or rewrite any tool call. claude plugin validate listed no gating hooks.
• Privacy note: the line shows meeting titles, PR titles, issue titles and the first line of Slack messages. Anyone who can see your terminal, a screen share or a recording sees them too.
• License: MIT, with a LICENSE file in the repository.

claude plugin validate reported no errors or warnings, and the author's 17 tests passed on Claude Code 2.1.296. The tests use mocked connectors and gh, so they do not prove the real connector answers still have the shape the parser expects.

Checked with Claude Code 2.1.296 on macOS (validate and tests only; the mod was not run against real accounts). If the line does not show up:

• You have at least one source connected: run /glance and look for sections marked "couldn't reach it".
• gh auth status shows a signed-in account, since PRs come from gh api graphql.
• The connectors are named claude.ai Google Calendar, claude.ai Linear and claude.ai Slack. The mod looks them up by these names.
• The terminal is wide enough: on a very narrow window the line shortens to counts like 🔀 3 PRs.
• A survey is open above the input; the line returns after it closes.