Skip to content
Back to search

vibing-tv

MarketplaceWorks with Claude CodeGitHub

vibing-tv: watch Claude Code write code, live, with its reasoning alongside.

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/charlesra--vibing-tv/badge.svg)](/listings/charlesra--vibing-tv)

HTML

<a href="/listings/charlesra--vibing-tv"><img src="/api/listings/charlesra--vibing-tv/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.

One command, in your terminal:

claude plugin install vibing-tv --marketplace CharlesRA/vibing-tv

Or from inside a Claude Code session:

/plugin install vibing-tv --marketplace CharlesRA/vibing-tv

Then start a new Claude Code session. **Claude's first reply gives you the link** to the viewer (http://127.0.0.1:4317 by default). Open it and ask Claude to build something.

<details> <summary>Claude Code older than 2.1.292</summary>

claude plugin marketplace add CharlesRA/vibing-tv
claude plugin install vibing-tv@vibing-tv

</details>

**Requirements:** Claude Code 2.1.292 or later (tested with 2.1.327), and Node.js 22.18 or later on your `PATH`. The hooks are run with `node`; without it, the plugin does nothing.

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 · 18 lines
  1. {
  2. "name": "vibing-tv",
  3. "description": "vibing-tv: watch Claude Code write code, live, with its reasoning alongside.",
  4. "owner": {
  5. "name": "Charles Raimbault"
  6. },
  7. "plugins": [
  8. {
  9. "name": "vibing-tv",
  10. "source": {
  11. "source": "github",
  12. "repo": "CharlesRA/vibing-tv",
  13. "ref": "release"
  14. },
  15. "description": "Watch Claude Code write code, live, with its reasoning alongside."
  16. }
  17. ]
  18. }
README.md · README · 145 lines
  1. # vibing-tv
  2. [![CI](https://github.com/CharlesRA/vibing-tv/actions/workflows/ci.yml/badge.svg)](https://github.com/CharlesRA/vibing-tv/actions/workflows/ci.yml)
  3. [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
  4. [![Release](https://img.shields.io/github/v/release/CharlesRA/vibing-tv)](https://github.com/CharlesRA/vibing-tv/releases)
  5. **A Claude Code plugin to watch Claude write code, live, with its reasoning alongside.**
  6. ![vibing-tv: Claude's edits typed live in a VS Code–style editor, with its explanations and steps on the right](docs/demo/demo.gif)
  7. vibing-tv is a live viewer for [Claude Code](https://docs.claude.com/en/docs/claude-code/overview). Every file Claude
  8. creates or edits is typed into a VS Code–style editor in your browser, character by character. Next to it, a feed shows
  9. what Claude said it was doing, and its checklist stays pinned at the top.
  10. Follow Claude the way you would watch a teammate code, and spend less time reading diffs afterwards.
  11. ## Why
  12. When an AI coding agent works on its own, you usually see a scrolling terminal and, at the end, a large diff. vibing-tv
  13. shows you what Claude Code is doing while it does it:
  14. - **See each change as it happens**, in context, instead of reviewing everything at the end.
  15. - **Know why a file changed**: each edit sits under the explanation Claude gave for it.
  16. - **Catch a wrong turn early**, and interrupt Claude before it builds on it.
  17. - **Show it to others**: pair programming with an agent, demos, teaching, or streaming a vibe coding session.
  18. ## Install
  19. One command, in your terminal:
  20. ```bash
  21. claude plugin install vibing-tv --marketplace CharlesRA/vibing-tv
  22. ```
  23. Or from inside a Claude Code session:
  24. ```
  25. /plugin install vibing-tv --marketplace CharlesRA/vibing-tv
  26. ```
  27. Then start a new Claude Code session. **Claude's first reply gives you the link** to the viewer
  28. (http://127.0.0.1:4317 by default). Open it and ask Claude to build something.
  29. <details>
  30. <summary>Claude Code older than 2.1.292</summary>
  31. ```bash
  32. claude plugin marketplace add CharlesRA/vibing-tv
  33. claude plugin install vibing-tv@vibing-tv
  34. ```
  35. </details>
  36. **Requirements:** Claude Code 2.1.292 or later (tested with 2.1.327), and Node.js 22.18 or later on your `PATH`. The
  37. hooks are run with `node`; without it, the plugin does nothing.
  38. ## Features
  39. - **Live typing.** New files are typed from the top; edits highlight the text that goes away, then type what replaces
  40. it. Only the part that really changes is animated.
  41. - **Claude's reasoning next to the code.** The feed groups edits under the sentence Claude wrote before them.
  42. - **Pinned steps.** Claude's markdown checklist (`- [ ]` / `- [x]`) shows as a progress list above the feed.
  43. - **Replay.** Click a file in the feed to replay that edit. Pause, skip, and change the typing speed from the controls
  44. above the editor, or from the keyboard: <kbd>Space</kbd> pauses, <kbd>→</kbd> skips, <kbd>S</kbd> picks a session.
  45. - **Every session.** One viewer for all your Claude Code sessions; it follows the latest one until you pick one yourself.
  46. - **Local and offline.** Everything stays on your machine. The viewer is bundled with the plugin and makes no request to
  47. any other site.
  48. ## How it works
  49. ```
  50. Claude Code ── hooks ──▶ capture ── append ──▶ ~/.vibing-tv/sessions/<session>.jsonl
  51. │
  52. local server (127.0.0.1:4317) ◀──┘ ── live stream ──▶ viewer in your browser
  53. ```
  54. - A `PostToolUse` hook records each `Write` and `Edit`: the file before and after, and the text Claude wrote before it.
  55. It runs in about a millisecond and never slows Claude down.
  56. - A `SessionStart` hook starts a small local server if none is running, and adds a short instruction to Claude's
  57. context: explain each group of edits in a sentence or two, keep a checklist for multi-step tasks, and give you the
  58. viewer's link in the first reply.
  59. - The server streams new edits to the viewer, which types them into [Monaco](https://microsoft.github.io/monaco-editor/).
  60. Details: [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
  61. ## Token usage
  62. The hooks, the server and the viewer never call the model. What does cost tokens:
  63. - **The injected instructions** (about 150 tokens). They stay in context and are normally served from the prompt cache.
  64. - **The explanations and checklists Claude writes** for the feed, as output tokens.
  65. On a small "build a todo app" task, this added about 500 to 650 output tokens and 2 to 6 % to the total cost. See
  66. [docs/token-usage.md](docs/token-usage.md) for the method and the numbers. To turn the extra text off, set
  67. `VIBING_TV_NO_COACH=1`: the code is still typed live, but the feed and the steps stay empty.
  68. ## Privacy
  69. - vibing-tv stores, on your machine only, the full content of each file Claude edits (before and after), in
  70. `~/.vibing-tv`. Logs are deleted after 7 days.
  71. - It never records `.env*`, `*.pem`, `*.key`, `*.p12` or `id_rsa*` files. Files over 1 MB are recorded without their
  72. content.
  73. - The server listens on `127.0.0.1` only. No telemetry.
  74. - **Uninstalling does not delete `~/.vibing-tv`.** Remove it with `rm -rf ~/.vibing-tv`.
  75. More in [SECURITY.md](SECURITY.md).
  76. ## Configuration
  77. Set these environment variables before starting Claude Code:
  78. | Variable | Default | Effect |
  79. | -------------------- | -------------- | ---------------------------------------------------------- |
  80. | `VIBING_TV_PORT` | `4317` | Port of the local server and viewer |
  81. | `VIBING_TV_DATA_DIR` | `~/.vibing-tv` | Where session logs are stored |
  82. | `VIBING_TV_IDLE_MS` | `1800000` | The server stops after this long without activity (30 min) |
  83. | `VIBING_TV_NO_COACH` | unset | `1`: don't ask Claude to explain its edits |
  84. | `VIBING_TV_NO_LINK` | unset | `1`: don't ask Claude to give the viewer's link |
  85. ## Troubleshooting
  86. - **Claude gave no link.** The link is only given at the start of a new conversation (not after `--resume`). Check that
  87. the server answers: `curl http://127.0.0.1:4317/health` should return `{"app":"vibing-tv",…}`.
  88. - **Another app uses port 4317.** vibing-tv leaves it alone, writes `port 4317 busy with another app` to
  89. `~/.vibing-tv/server.log`, and gives no link. Set `VIBING_TV_PORT` to a free port.
  90. - **Edits show up but the feed says "(explanation pending…)".** Claude Code writes its transcript in batches; the
  91. explanation usually appears within a few seconds.
  92. - **Nothing shows up at all.** Check that `node --version` works in the shell Claude Code starts from, then look at
  93. `~/.vibing-tv/server.log`. `claude --debug` shows how the hooks load and run.
  94. - **Two sessions use different `VIBING_TV_DATA_DIR`.** One server runs per machine; the second session keeps the
  95. running server and logs the mismatch. Use the same folder everywhere.
  96. ## Development
  97. ```bash
  98. npm ci
  99. npm run dev # builds dist/ and rebuilds on change
  100. claude --plugin-dir ./dist # in another terminal
  101. ```
  102. See [CONTRIBUTING.md](CONTRIBUTING.md).
  103. ## License
  104. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

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