Skip to content
Back to search

claude-tui-dashboard

MarketplaceWorks with Claude CodeGitHub

TUI dashboard for claude code

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kevteg--claude-tui-dashboard/badge.svg)](/listings/kevteg--claude-tui-dashboard)

HTML

<a href="/listings/kevteg--claude-tui-dashboard"><img src="/api/listings/kevteg--claude-tui-dashboard/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.

At the prompt of a Claude Code terminal session:

/plugin install tui-dashboard --marketplace kevteg/claude-tui-dashboard

From a shell:

claude plugin install tui-dashboard --marketplace kevteg/claude-tui-dashboard

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 · 19 lines
  1. {
  2. "name": "claude-tui-dashboard",
  3. "owner": {
  4. "name": "kevteg"
  5. },
  6. "metadata": {
  7. "description": "Dashboards drawn in the terminal, beside the Claude Code chat",
  8. "version": "0.1.0"
  9. },
  10. "plugins": [
  11. {
  12. "name": "tui-dashboard",
  13. "source": "./",
  14. "description": "A dashboard pane beside the chat that Claude builds and updates with a render_dashboard tool: metrics, bar charts, pie charts, sparklines, tables and callouts",
  15. "version": "0.1.0",
  16. "category": "productivity"
  17. }
  18. ]
  19. }
README.md · README · 177 lines
  1. # TUI Dashboard 🥧
  2. Tired of staring at walls of numbers? Bored of tables that are longer than your
  3. daily standup? Look no further! TUI Dashboard turns whatever Claude finds
  4. into bar charts, sparklines and, yes, real round pie charts, right in your
  5. terminal, next to the chat.
  6. No browser tabs. No spreadsheets. No headaches.
  7. <img width="1248" height="708" alt="dashboard-example" src="https://github.com/user-attachments/assets/e17f74f1-59de-4ad9-85c1-8ebf57f49e56" />
  8. It's a Claude Code plugin that gives Claude a dashboard pane beside the chat. Ask
  9. for a dashboard of anything Claude can look up, such as logs, query results or
  10. files, and Claude draws it with metrics, charts, tables and callouts. Ask again
  11. to refresh it with new numbers.
  12. ## Install
  13. At the prompt of a Claude Code terminal session:
  14. ```
  15. /plugin install tui-dashboard --marketplace kevteg/claude-tui-dashboard
  16. ```
  17. From a shell:
  18. ```
  19. claude plugin install tui-dashboard --marketplace kevteg/claude-tui-dashboard
  20. ```
  21. ## Use
  22. - Ask Claude for a dashboard, e.g. "make me a dashboard of the errors in this log file by hour".
  23. Claude calls its `render_dashboard` tool and the pane opens beside the chat.
  24. - The pane opens by itself when the terminal is wide enough. Type `/tui-dashboard` to open it at
  25. any width.
  26. - To keep it updated, ask Claude to refresh it, or loop it: `/loop 30m refresh the dashboard`.
  27. ## What Claude can draw
  28. | Component | For |
  29. | ------------ | ---------------------------------------------------------- |
  30. | `metrics` | A row of headline numbers |
  31. | `bar_chart` | Horizontal bars, several series side by side or stacked |
  32. | `pie_chart` | Shares of a whole, with a legend of values and percentages |
  33. | `sparklines` | Trends over time, one line per series |
  34. | `table` | Rows of values, sized to fit the pane |
  35. | `callout` | Something that needs attention: info, success, warning, error |
  36. | `heading`, `text` | Titles and notes |
  37. Claude chooses the layout: the pane width it asks for, and a width per component (`full`,
  38. `two_thirds`, `half`, `third`) so smaller charts sit side by side. A width you drag the pane to
  39. yourself wins.
  40. ## Live dashboards
  41. Claude can give a dashboard a refresh command: a script that prints the next dashboard as JSON
  42. (`{ "title"?, "subtitle"?, "components": [...] }`). The pane then re-runs it on a timer, at most
  43. once a minute, and redraws without asking Claude again.
  44. The pane never runs a command on its own: it shows you the exact command and waits until you
  45. press **Start auto-refresh**. A different command needs a new Start, and **Stop** turns it off.
  46. The command runs on your machine as you, with your credentials.
  47. Approval also covers the code the command runs: when you press Start, the pane notes the size and
  48. modification time of the program and of any script file in the command (`.py`, `.js`, `.sh` and
  49. the like). If one of them changes, auto-refresh stops before the next run and asks you to press
  50. Start again. Data files the script reads are not watched, since they change between runs by
  51. design. Files the script imports are not watched either, so still keep refresh scripts somewhere
  52. only you write to.
  53. The plugin includes a `live-dashboards` skill that teaches Claude how to write a good refresh
  54. script: what to print, how often to run, and how to cache the expensive parts.
  55. ## Saving dashboards
  56. Press **Save** next to the dashboard's title to keep it, with its refresh command and Claude's
  57. notes on how the data was gathered. Bring it back in any later session:
  58. - `/tui-dashboard <name>` puts it back in the pane right away, no Claude needed
  59. - `/tui-dashboard list` (or the **Saved…** button in the pane) shows your saved dashboards as a
  60. list: ↑/↓ to move, Enter to open one, Esc to go back to the prompt
  61. - `/tui-dashboard delete <name>` removes one
  62. - Or ask Claude: it can list and open saved dashboards, and uses those notes to update them
  63. A saved refresh command still waits for you to press Start in each new session.
  64. Saved dashboards are kept in one plain file, `~/.claude-dashboards/saved.json`, shared by every
  65. session and every copy of the plugin. To move them to another machine or share one with a
  66. teammate, copy that file (or one entry in it). Saved refresh commands point at scripts on your
  67. machine, so share those along with it.
  68. ### Example: build it once, bring it back tomorrow
  69. **Today**, in a Claude Code session:
  70. ```
  71. > Make me a live dashboard of the error lines in /var/log/myapp/app.log, per hour,
  72. and keep it updated every 5 minutes
  73. ```
  74. Claude writes a small refresh script, runs it once, and draws the dashboard. In the pane:
  75. 1. Press **Start auto-refresh**: the pane shows the exact command first. From now on it redraws
  76. every 5 minutes by itself.
  77. 2. Press **Save** next to the title. A toast confirms the name, here `app-log-errors-per-hour`.
  78. **Tomorrow**, in a brand-new session (`claude` in a new terminal, or `/clear`), there are two ways
  79. back.
  80. Without Claude doing anything, type `/tui-dashboard list`. The pane lists what you saved:
  81. ```
  82. Saved dashboards
  83. ↑/↓ to move · Enter opens it · Esc goes back to the prompt
  84. ❯ App log errors per hour · saved Nov 12, 7:15 PM · live
  85. Signups this week · saved Nov 10, 9:02 AM
  86. ```
  87. Press Enter on one, or type its name directly: `/tui-dashboard app-log-errors-per-hour`. The pane
  88. shows the dashboard as you saved it. Press **Start auto-refresh** again and it is live.
  89. Or ask Claude, when you want something changed too:
  90. ```
  91. > Open my app log errors dashboard and add a pie of errors by module
  92. ```
  93. Claude finds it with `list_saved_dashboards`, opens it with `open_saved_dashboard`, reads the
  94. recipe (where the data comes from and where the script lives), changes the script and redraws.
  95. Press **Save** again to keep the new version under the same name.
  96. ## What the plugin does on your machine
  97. TUI Dashboard is a mod: its code (`hooks/register.tsx`) runs inside Claude Code. This is
  98. everything it does outside drawing the pane.
  99. - **Its own tools.** It adds three tools, `render_dashboard`, `list_saved_dashboards` and
  100. `open_saved_dashboard`, and answers calls to them itself; there is no server behind them. It
  101. answers no other tool's calls.
  102. - **One command.** It adds `/tui-dashboard`, and handles only that command.
  103. - **One file it writes.** It reads and writes `~/.claude-dashboards/saved.json`, and only when you
  104. press **Save**, open or delete a saved dashboard, or Claude lists or opens one. It reads `HOME`
  105. from the environment to find that folder. On first use it also copies dashboards that an earlier
  106. version kept in the plugin's private store into that file. It writes no other file, and nothing
  107. that other tools run or obey.
  108. - **One program it runs: your refresh command.** When a dashboard has a refresh command, the pane
  109. runs that exact command on a timer, at most once a minute, with a 5-minute timeout, and only after
  110. you press **Start auto-refresh**. Claude writes the command when it builds the dashboard, and the
  111. pane shows it to you in full before you start it. It runs on your machine as you, in the
  112. session's working directory, with your environment, so it can use whatever credentials and files
  113. you can. The plugin reads only what the command prints on stdout (the next dashboard) and the
  114. last line of stderr (shown if it fails). It stops when you press **Stop**, when the command
  115. changes, or when its program or script file changes.
  116. - **Nothing sent anywhere.** The plugin makes no network requests and sends no data out, including
  117. your conversation, which it never reads beyond the tool calls above. A refresh command you
  118. approve can do anything a program you run can do, so read it before you press Start.
  119. ## Limits
  120. - The pane shows one dashboard at a time; drawing a new one replaces it (Save it first to keep it).
  121. - Charts are drawn with Unicode block characters, so they are as sharp as your terminal font.
  122. - Without a refresh command, the numbers stay as drawn: they change only when Claude redraws the
  123. dashboard. Opening a saved one shows it as it was when saved.
  124. ## Development
  125. ```
  126. claude plugin validate .
  127. claude plugin test .
  128. ```
  129. ## License
  130. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.