# AI use cases for Vibepulse (niclasvestlund-YT/vibepulse) Repo: [niclasvestlund-YT/vibepulse](https://github.com/niclasvestlund-YT/vibepulse) | Use cases: 4 | Page: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/ VibePulse is an open-source ESP32-S3 AMOLED desk screen, with a local macOS or Windows host service, that shows Claude Code and Codex quota, live agent activity, and NEEDS YOU alerts. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Glance at Claude and Codex quota from across the room: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/glance-claude-codex-quota-on-desk-screen/ - Get alerted when a coding agent is stuck waiting for your input: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/get-alerted-when-coding-agent-waits-for-you/ - Answer a supported Claude or Codex prompt with a tap on the glass: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/answer-claude-or-codex-prompts-from-panel/ - Track OpenRouter API spend and budget on a desk panel: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/track-openrouter-spend-on-desk-panel/ ## How to glance at Claude and Codex quota from across the room with Vibepulse Repo: [niclasvestlund-YT/vibepulse](https://github.com/niclasvestlund-YT/vibepulse) | Difficulty: Intermediate | Time: 2 hours | Basis: From the README Put live Claude and Codex usage on a shelf screen so you see remaining quota before a long task dies. **Who it is for:** A developer running Claude Code or Codex all day who keeps hitting usage limits mid-task and wants to see remaining quota without opening a terminal. **The problem:** Quota is invisible until a long agent task fails halfway through, because the numbers sit in a terminal window you are not watching. **The outcome:** A panel on your desk shows Claude's weekly and heaviest-model weekly quota and Codex's weekly quota, each with a reset countdown and today's burn. ### Steps 1. Read What you need in the README and confirm you have an ESP32-S3 AMOLED board or will use the simulator. 2. Follow the Setup, the vibecoder way section with your coding agent, one verified step at a time. 3. Run the host service on your Mac or Windows PC and connect the panel to the same Wi-Fi network. 4. Check the Usage page on the glass and confirm Claude and Codex weekly quota with reset countdowns appear. 5. Leave local mode on so agent activity stays on your LAN and no VibePulse account is needed. ### Prompt to paste into your agent ```text Using the niclasvestlund-YT/vibepulse repo, help me set up the Usage page for following the Setup, the vibecoder way section. Expected output: a panel showing Claude weekly and Codex weekly quota with reset countdowns. Verify that the Usage page updates after one real Claude Code or Codex request. ``` ### Caveat The README says the Windows core and physical answer loop were verified only at the v1.0.0 host runtime, so check the host support matrix before relying on a Windows setup. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/glance-claude-codex-quota-on-desk-screen/ ## How to get alerted when a coding agent is stuck waiting for your input with Vibepulse Repo: [niclasvestlund-YT/vibepulse](https://github.com/niclasvestlund-YT/vibepulse) | Difficulty: Intermediate | Time: 2 hours | Basis: From the README Turn the whole screen into a NEEDS YOU alert when Claude or Codex asks a question and sits idle. **Who it is for:** A developer who runs agents in another window and loses long stretches of time when an agent quietly waits on a yes or no question. **The problem:** An agent asks one question and then sits idle, often for twenty minutes, because you are in a different window and cannot see it. **The outcome:** When an agent blocks on your input, the screen switches to a full-screen NEEDS YOU alert in that provider's colour, naming the project it is waiting on. ### Steps 1. Set up the panel and host service as described in the Setup, the vibecoder way section. 2. Keep the panel within reach of your desk so the alert is visible from across the room. 3. Start a Claude Code or Codex task that needs a yes or no answer from you. 4. Confirm the NEEDS YOU alert names the correct project and shows the provider colour. 5. Tap the panel to dismiss the alert, or use the answer flow if you have enabled the Needs You bridge. ### Prompt to paste into your agent ```text In the niclasvestlund-YT/vibepulse repo, trigger a test NEEDS YOU alert by running a Claude Code or Codex task that asks for a confirmation. Expected output: the panel turns into a full-screen NEEDS YOU screen naming the project. Verify the alert appears on the glass within a short time after the agent blocks. ``` ### Caveat The README describes the NEEDS YOU alert as part of the core loop that was physically exercised on macOS and Windows, but alert timing on your own setup still needs your own check. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/get-alerted-when-coding-agent-waits-for-you/ ## How to answer a supported Claude or Codex prompt with a tap on the glass with Vibepulse Repo: [niclasvestlund-YT/vibepulse](https://github.com/niclasvestlund-YT/vibepulse) | Difficulty: Advanced | Time: 3 hours | Basis: From the README Use the opt-in Needs You bridge to answer a waiting agent from the panel without switching windows. **Who it is for:** A developer whose agent is blocked on a yes or no question and who wants to reply from the panel, optionally from a different network than the computer. **The problem:** Even after an alert, you still have to walk to the computer and switch windows to answer a question that needs one tap. **The outcome:** On a supported prompt, you tap the NEEDS YOU alert on the panel and the decision goes back to the waiting agent. ### Steps 1. Complete the basic panel and host setup so the NEEDS YOU alert works first. 2. Read the Answer Claude or Codex from the panel section of the README to confirm which prompts are supported. 3. Enable the Needs You bridge through the setup described in the README, which is off by default. 4. If the panel and computer are on different networks, decide whether to enable the optional encrypted interaction relay, which is also off by default. 5. Trigger a supported prompt and tap the alert on the glass to confirm the agent receives your answer. ### Prompt to paste into your agent ```text In the niclasvestlund-YT/vibepulse repo, enable the optional Needs You bridge for following the answer section of the README. Expected output: a supported Claude Code or Codex prompt that can be answered by tapping the panel. Verify that the agent continues after the tap and that no relay is enabled unless I opt in. ``` ### Caveat The README limits answering to supported prompts only, so an agent that asks an unsupported question will still need an answer at the keyboard. Risk, credentials: The optional encrypted interaction relay and status relay involve relay setup and the pinned Python cryptography dependency, so keep any relay credentials out of agent prompts and shared logs. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/answer-claude-or-codex-prompts-from-panel/ ## How to track OpenRouter API spend and budget on a desk panel with Vibepulse Repo: [niclasvestlund-YT/vibepulse](https://github.com/niclasvestlund-YT/vibepulse) | Difficulty: Advanced | Time: 4 hours | Basis: From the README Show daily, weekly and monthly OpenRouter spend against a monthly display budget on the glass. **Who it is for:** A developer who uses OpenRouter API keys and wants to watch spend and remaining key allowance without a Claude Code or Codex account. **The problem:** API spend builds up quietly across keys, and checking the provider dashboard interrupts work. **The outcome:** The panel shows an OPENROUTER spend page with daily, weekly and monthly totals, a monthly display budget, and remaining key allowance. ### Steps 1. Read the OpenRouter-only installation guide linked from the README section on OpenRouter spend and budgets. 2. Build the firmware from the release source with the -DTORGET_OPENPULSE=ON build option. 3. Run the separate OpenPulse service on your Mac, where API keys are kept in Keychain. 4. Enable OPENROUTER under SETTINGS, then LABS, then MORE, then MORE, and tap RESTART NOW. 5. Tap the bottom page indicator to switch between spend and details, and confirm dashes or NO DATA appear only when expected. ### Prompt to paste into your agent ```text Using the niclasvestlund-YT/vibepulse repo, build firmware with -DTORGET_OPENPULSE=ON and follow the OpenRouter-only installation guide for a panel. Expected output: an OPENROUTER spend page showing daily, weekly and monthly spend. Verify that the Mac service is running and that the panel reaches it over Wi-Fi. ``` ### Caveat The README calls this a macOS source-build preview with no automatic service startup and no OpenRouter relay, and physical acceptance is pending on the square 2.16 board. Risk, credentials: OpenRouter API keys are held in Keychain by the separate Mac service, so do not paste keys into agent prompts, config files you share, or logs. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/track-openrouter-spend-on-desk-panel/