claude-gpu-panel
A Claude Code panel for people who share a GPU server: which cards are busy and who is on them, your training jobs, plan limits and context — under the prompt. | GPU 서버를 나눠 쓰는 사람을 위한 Claude Code 패널.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/tom0266--claude-gpu-panel)HTML
<a href="/listings/tom0266--claude-gpu-panel"><img src="/api/listings/tom0266--claude-gpu-panel/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Needs Claude Code 2.1.287 or later.
claude plugin marketplace add tom0266/claude-gpu-panel claude plugin install gpu-panel@claude-gpu-panel
Then `/reload-plugins` in an open session, or start a new one.
GPU and job fields appear only when the machine can produce them:
- **GPU** needs `nvidia-smi` on your `PATH`. Without it the field is hidden, so the panel still works on a laptop. - **Jobs** needs `~/.claude/statusline-jobs.txt`, one pattern per line. A line matches if it appears anywhere in a process's command. Blank lines and lines starting with `#` are ignored.
# ~/.claude/statusline-jobs.txt train.py finetune optuna
Only your own processes are counted, and identical command lines are counted once.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 16 lines
- {
- "name": "claude-gpu-panel",
- "owner": {
- "name": "tom0266"
- },
- "plugins": [
- {
- "name": "gpu-panel",
- "source": "./gpu-panel",
- "description": "A panel under the prompt for shared GPU servers: which cards are busy and who is on them, your running training jobs, plan limits and context, with effort/model/compact buttons."
- }
- ],
- "metadata": {
- "description": "A Claude Code panel for people who share a GPU server."
- }
- }
README.md · README · 139 lines
- # gpu-panel
- 
- [](LICENSE)
- 
- 
- A Claude Code panel for people who share a GPU server.
- One line under your prompt shows which GPUs are busy, how many training jobs you
- have running, and how much of your plan is left. Click `gpu` and a pane opens
- with every card, who is using it, and your jobs with their elapsed time.
- [한국어](README.ko.md)
- 
- A real session. Cards 2 and 3 are busy at 13%; the other two are free and stay out of the line.
- Most panels like this live above the prompt and show plan usage. This one sits
- below the prompt, next to the hint line, and its first concern is the machine
- you are sharing with other people.
- ## What it shows
- **The line under your prompt**
- | Field | Meaning |
- |---|---|
- | session name | from `/rename`, or the auto-generated title |
- | `5h` `7d` | plan usage with a bar and the time until reset |
- | `ctx` | how full the context window is |
- | `gpu` | busy cards only, as `index:utilization` or `index:memory`; `free` when none |
- | `job` | how many of your watched training jobs are running; hidden at zero |
- | `agents` | running subagents by model, plus done and failed counts |
- | buttons | switch effort, switch model, run `/compact` |
- The model buttons learn their version numbers from models you actually use, so
- `opus` becomes `opus 5.5` once you have run it, and the version is remembered
- between sessions. Nothing is hardcoded, so it does not go stale.
- Below 110 columns the panel drops its border, bars and labels and fits in two
- lines. Three cards wide in a split pane still works.
- **The `gpu` pane** — click the `gpu` field or run `/gpu`
- ```
- GPU
- 0 ━━━━━━━━ 0% 0/45G 31°C
- free
- 2 ━ 15% 1/48G 54°C
- you 1G, alice 22G
- Jobs
- 2733273 4-02:11:08 python train.py --fold 3
- ```
- <img src="assets/gpu-pane.png" width="360" alt="The real GPU pane on an idle four-card server: each card at 0% and marked free">
- The block above shows the layout with example accounts. This is the pane itself, on a server where all four cards happen to be free.
- Every card with its utilization, memory, temperature, and **the account using
- it**, so you can see at a glance whether the card you want is free or someone
- else's run is on it. Under that, your own watched jobs with PID and elapsed
- time. The pane refreshes every ten seconds while it is open, and runs no queries
- at all while it is closed.
- ## Install
- Needs Claude Code 2.1.287 or later.
- ```bash
- claude plugin marketplace add tom0266/claude-gpu-panel
- claude plugin install gpu-panel@claude-gpu-panel
- ```
- Then `/reload-plugins` in an open session, or start a new one.
- GPU and job fields appear only when the machine can produce them:
- - **GPU** needs `nvidia-smi` on your `PATH`. Without it the field is hidden, so
- the panel still works on a laptop.
- - **Jobs** needs `~/.claude/statusline-jobs.txt`, one pattern per line. A line
- matches if it appears anywhere in a process's command. Blank lines and lines
- starting with `#` are ignored.
- ```
- # ~/.claude/statusline-jobs.txt
- train.py
- finetune
- optuna
- ```
- Only your own processes are counted, and identical command lines are counted
- once.
- ## Commands
- | | |
- |---|---|
- | `/gpu` | open the GPU and jobs pane |
- Everything else is a click.
- ## What it costs
- The panel reads plan usage and context from events Claude Code already raises,
- so those are free. On a timer it runs `nvidia-smi` and `ps` every ten seconds,
- and greps the session transcript for its title every thirty. It makes no network
- requests and calls no model.
- ## Configuration
- Set these when you install, or later with `claude plugin configure gpu-panel@claude-gpu-panel`.
- | Option | Default | What it does |
- |---|---|---|
- | `language` | `en` | Language of the usage toast, the `/gpu` description and the pane's empty states: `en` or `ko`. The panel's own labels (`5h`, `ctx`, `gpu`) do not change |
- | `palette` | `dark` | `dark` uses fixed colors tuned for a dark terminal. `theme` follows the Claude Code theme, so it also reads on a light background |
- | `fiveHourThreshold` | `80` | Toast once per window when 5-hour usage reaches this percentage |
- | `sevenDayThreshold` | `70` | The same for the 7-day window |
- | `hideQuietStatus` | `false` | Hide status lines from other mods that only say nothing is wrong (`no active cases`, `waste≈0`). Warnings always stay. Off by default, because it removes another mod's output |
- A threshold outside 1 to 100 falls back to its default.
- ## Limits
- - Drawn in the terminal and the Desktop app's Code tab. `claude -p` and cloud
- sessions run the hooks but draw nothing.
- - The GPU pane shows accounts, not people. On a machine where everyone shares
- one account it tells you less.
- - Effort is tracked by watching `/effort` and the panel's own buttons. Claude
- Code does not expose the current level, so if it is changed another way the
- highlight can fall out of step until the next change.
- ## License
- MIT
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.