---
title: "github-actions-pane"
url: "https://claudemods.dev/zh-tw/builds/github-actions-pane-70fad1"
source: "https://github.com/blackpaw-studio/claude-plugins/tree/main/plugins/github-actions-pane"
source_type: "github"
repo: "https://github.com/blackpaw-studio/claude-plugins/tree/main/plugins/github-actions-pane"
author: "blackpaw-studio"
author_handle: "blackpaw-studio"
stars: 1
category: "儀表板與 HUD"
categories: ["hud"]
tags: ["ci", "github-actions", "hooks", "pane", "polling", "statusline"]
permission_level: 2
scan_complete: true
install: "claude plugin marketplace add blackpaw-studio/claude-plugins\nclaude plugin install github-actions-pane@blackpaw-plugins"
added: "2026-10-10T20:06:33.088Z"
updated: "2026-10-10T17:20:43Z"
locale: "zh-tw"
content_locale: "zh-tw"
---

# github-actions-pane

一個 Claude Code mod（函式掛鉤外掛），會在執行期間在記錄旁的一個窗格中顯示您的 GitHub Actions 執行，像 GitHub 的執行檢視一樣繪製：每次執行及其作業、正在執行的作業的步驟、狀態圖示以及即時跳動的持續時間。

## Description

一個 Claude Code mod，會在記錄旁的一個窗格中顯示即時 GitHub Actions 執行。當您的分支上開始執行時，該窗格會自動開啟，顯示每次執行及其作業、正在執行的作業的步驟、狀態圖示和即時持續時間。失敗的作業會摺疊到失敗的步驟，完成的執行會短暫停留，當沒有可顯示的內容時，該窗格會自行關閉。在窗格無法放置的地方，會回退為狀態列。需要 Claude Code 2.1.296+、已登入的 gh CLI，以及具有 GitHub 遠端倉庫的簽出。透過 /plugin marketplace add blackpaw-studio/claude-plugins 安裝，然後 /plugin install github-actions-pane@blackpaw-plugins。命令：/actions、/actions commit、/actions branch、/actions repo。設定包括範圍、停留秒數、活動/閒置輪詢秒數以及自動開啟。

## Install

```
claude plugin marketplace add blackpaw-studio/claude-plugins
claude plugin install github-actions-pane@blackpaw-plugins
```

## Original README

# github-actions-pane

A Claude Code mod (function-hook plugin) that shows your GitHub Actions runs
in a pane beside the transcript while they are running, drawn like GitHub's
run view: each run with its jobs, the running job's steps, status icons, and
durations that tick live.

The pane opens by itself when a run starts on your branch. Finished runs stay
for a short linger, and the pane closes itself once nothing is left to show.
A failed job collapses to the step that failed.

## Screenshots

![Two runs in flight](docs/running.png)
![A failed deploy beside a running CI](docs/failure.png)
![A run from start to finish](docs/demo.gif)
![This repository's own CI run, captured from a real session](docs/real-run.png)

In the main-screen layout (`CLAUDE_CODE_NO_FLICKER=0`) the pane sits above
the prompt:

![Inline above the prompt](docs/inline.png)

Where the pane cannot seat, the status line says what is running:

![Status line fallback](docs/status-line.png)

## Requirements

- Claude Code 2.1.296 or later (the build it was tested on).
- Function-hook plugins (mods) are early access, and the API may change
  between releases.
- [`gh`](https://cli.github.com), logged in (`gh auth login`), and a
  checkout with a GitHub remote.

## Install

From this marketplace:

```shell
/plugin marketplace add blackpaw-studio/claude-plugins
/plugin install github-actions-pane@blackpaw-plugins
```

## Use

There is nothing to run. Push, or start a workflow, and the pane opens on the
next poll.

| Command | |
|---|---|
| `/actions` | Open the pane by hand, or close it. Opened by hand, it stays until you close it, and with nothing running it shows the latest run. |
| `/actions commit` | Watch the runs for HEAD only, for this session. |
| `/actions branch` | Watch the runs on the current branch, for this session. |
| `/actions repo` | Watch every active run in the repository, for this session. |

Click a run's name to open it on github.com (`gh run view --web`).

If you close the pane, it stays closed for the runs already in flight, and a
new run opens it again.

## Settings

These are the plugin's options. Set them when you enable it, or in `settings.json` under
`pluginConfigs["github-actions-pane"].options` (`scope`, `lingerSeconds`,
`activePollSeconds`, `idlePollSeconds`, `autoOpen`).

| Setting | Default | |
|---|---|---|
| Scope | `branch` | `commit` (HEAD), `branch` (falls back to the commit on a detached HEAD) or `repo` |
| Linger seconds | 30 | How long finished runs stay before the pane closes; 0 closes at once |
| Active poll seconds | 10 | Poll interval while a run is active; at least 5 |
| Idle poll seconds | 60 | Poll interval while nothing is active; at least 15 |
| Open automatically | on | Off: no pane opens by itself, and the status line shows what is running |

## Behaviour

- **Polling:** each poll makes one `gh run list` (20 runs, filtered to the
  scope), plus one `gh run view --json jobs` for each active run shown. When
  those 20 are all newer than a run still going, two more lists
  (`--status in_progress`, `--status queued`) find it. A run that is
  `waiting`, `requested` or `pending` and older than the newest 20 is not
  found until it moves to queued or in progress. A
  finished run's jobs are read once and then cached. A `git push`,
  `gh workflow run`, `gh pr create` or `gh run rerun` through Claude's Bash
  tool polls at once, then at the active rate for two minutes.
- **Pushes from any terminal:** every 5 seconds a local `git rev-parse` reads
  the remote-tracking ref of the branch in scope (its push target, else
  `origin/<branch>`, re-read on every poll and on every look while it is only
  guessed, so a first `git push -u <remote>` is seen; under `repo` scope the
  current branch's). When it moves,
  the same kick happens: a poll at once, then the active rate for two
  minutes. No GitHub calls are made while idle, and the watch is off when
  there is no repository or the HEAD is detached.
- **What shows:** runs that are active, plus the runs this session saw
  finish, for the linger window. A run that had already finished when it was
  first seen does not open the pane.
- **Jobs and steps:** passed jobs take one line. A running job lists its
  steps, and a failed job lists only its failed steps. A run with more than
  eight jobs folds the passed ones into "N jobs passed". When the pane is
  short, the finished steps of running jobs fold into "N steps" around the
  current one. Then older finished runs drop out, and anything still left
  over ends in "+N more".
- **Where it draws:** a pane that opens by itself seats from 144 columns,
  or from 110 once you have opened it there yourself. Narrower, it waits
  and the status line shows `◐ 2 running · ✗ 1 failed` instead. A pane
  you open with `/actions` seats at any width. In the main-screen layout it
  draws inline above the prompt, with the body capped at 96 columns.
- **Rate limits:** a rate-limited `gh` drops polling to the idle rate, and
  the header shows `rate limited` until a poll succeeds. When the data is
  more than two polls old, the header shows `stale · 40s`.
- **Off quietly:** outside a git repository, without `gh`, logged out of
  `gh`, or with no GitHub remote, nothing opens and `gh` is not polled.
  `/actions` says which one applies. A Bash `cd` into a repository starts
  watching again.
- **Terminal only:** the pane's body is drawn only in the terminal.

## Limitations

- A run stays active until `gh` says completed, so a run's header can keep
  ticking for up to one poll after its last job finished.
- A push is detected within about 5 seconds from any terminal, by the
  remote-tracking ref moving. A push that leaves the ref alone, to a remote
  other than the branch's push target, is only seen on the next idle poll.
- The linger and the stale note use your local clock, measured from when a
  poll saw the change, not from GitHub's timestamps.
- Some terminal setups (inside tmux, for one) do not support OSC 8
  hyperlinks, so the run name is a button that runs `gh run view --web`
  rather than a link.

## Development

```sh
claude plugin validate plugins/github-actions-pane
claude plugin test plugins/github-actions-pane
```

CI (`.github/workflows/ci.yml`) runs both, plus the marketplace validation,
on every pull request. It skips `tsc`, because the declarations below need a
logged-in session to be written.

Type-checking needs the declarations the engine lays into
`.claude-plugin/types/` when it loads the mod from a folder you own (a
`--plugin-dir` or the session's mods folder). Run `tsc -p` on the
plugin folder.

`gh` fixtures in `src/testing/gh-fixtures.ts` are real `gh` output from
`cli/cli`. `dev/capture-fixtures.sh` refreshes them with read-only calls.

### The demo

The screenshots and GIF come from a real Claude Code session. That session
watches a scripted timeline that a fake `gh` (`dev/demo/bin/gh`) replays: CI
#482 with four jobs, and Deploy #77 failing at "Upload artifacts". Nothing
reaches GitHub. The demo polls at the floors (5 s active, 15 s idle).

```sh
dev/demo/record.sh full150 fullscreen 150 40 100   # also: main, other sizes
dev/demo/render.py still full150 42 docs/failure.png --crop 86,0,150,30
dev/demo/render.py gif full150 -12 92 docs/demo.gif --crop 86,0,150,35 --speed 2
```

`record.sh` runs Claude in a throwaway tmux session inside a scratch repository,
records it with asciinema, and saves `tmux capture-pane -e` frames each
second under `dev/demo/out/<name>/`. `render.py` turns a recording into
stills and a GIF with `agg` and `ffmpeg`.