DEDUPED Hot AI repos, turned into use cases Get the Monday 5

What you can do with 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.

Trended earlier

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.

4 use cases

  • Glance at Claude and Codex quota from across the room

    Put live Claude and Codex usage on a shelf screen so you see remaining quota before a long task dies.

    View prompt
    Using the niclasvestlund-YT/vibepulse repo, help me set up the Usage page for <my board model or simulator> 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.
  • Get alerted when a coding agent is stuck waiting for your input

    Turn the whole screen into a NEEDS YOU alert when Claude or Codex asks a question and sits idle.

    View prompt
    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.
  • Answer a supported Claude or Codex prompt with a tap on the glass

    Use the opt-in Needs You bridge to answer a waiting agent from the panel without switching windows.

    View prompt
    In the niclasvestlund-YT/vibepulse repo, enable the optional Needs You bridge for <my agent and panel> 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.
  • Track OpenRouter API spend and budget on a desk panel

    Show daily, weekly and monthly OpenRouter spend against a monthly display budget on the glass.

    View prompt
    Using the niclasvestlund-YT/vibepulse repo, build firmware with -DTORGET_OPENPULSE=ON and follow the OpenRouter-only installation guide for a <round 1.75 or square 2.16> 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.

How to use Vibepulse

  1. Check you have what it needs: An ESP32-S3 AMOLED board with a core, or the simulator for a no-hardware run; A Mac or Windows PC to run the pure-stdlib Python host service; A Claude Code or Codex account whose usage you want to monitor.
  2. Open niclasvestlund-YT/vibepulse on GitHub and read the README and license.
  3. Read What you need in the README and confirm you have an ESP32-S3 AMOLED board or will use the simulator.
  4. Follow the Setup, the vibecoder way section with your coding agent, one verified step at a time.
  5. Run the host service on your Mac or Windows PC and connect the panel to the same Wi-Fi network.
  6. Check the Usage page on the glass and confirm Claude and Codex weekly quota with reset countdowns appear.

These steps come from our top use case, Glance at Claude and Codex quota from across the room, which also has a copy-paste agent prompt.

Vibepulse alternatives · Best AI repos for Personal productivity

About this repo

  • Who it is forDevelopers who build with Claude Code or Codex and want quota, agent status, and waiting-for-input alerts on a shelf screen, with optional hardware-based answering and OpenRouter spend tracking.
  • Why it is hot
  • LanguageC
  • Sourcegithub.com/niclasvestlund-YT/vibepulse · Back to Hot repos

Requirements

  • An ESP32-S3 AMOLED board with a core, or the simulator for a no-hardware run
  • A Mac or Windows PC to run the pure-stdlib Python host service
  • A Claude Code or Codex account whose usage you want to monitor
  • Wi-Fi shared by the computer and the panel for local mode

Add this badge to your README

Maintain Vibepulse? Show readers where to find these use cases. Use cases on Deduped

Markdown

[![Use cases on Deduped](https://dedupedai.com/badge/niclasvestlund-YT/vibepulse.svg)](https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/?utm_source=github&utm_medium=badge&utm_campaign=niclasvestlund-YT-vibepulse)

HTML

<a href="https://dedupedai.com/use-cases/niclasvestlund-yt-vibepulse/?utm_source=github&amp;utm_medium=badge&amp;utm_campaign=niclasvestlund-YT-vibepulse"><img src="https://dedupedai.com/badge/niclasvestlund-YT/vibepulse.svg" alt="Use cases on Deduped" height="20"></a>

A static image, no tracking script. About the badge

Questions about Vibepulse

What is 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. It is an open-source project on GitHub: https://github.com/niclasvestlund-YT/vibepulse.

Who is Vibepulse for?

Developers who build with Claude Code or Codex and want quota, agent status, and waiting-for-input alerts on a shelf screen, with optional hardware-based answering and OpenRouter spend tracking.

What can I do with Vibepulse?

4 use cases so far, for example: Glance at Claude and Codex quota from across the room; Get alerted when a coding agent is stuck waiting for your input; Answer a supported Claude or Codex prompt with a tap on the glass. Each has steps and a copy-paste agent prompt.

What do I need to run Vibepulse?

An ESP32-S3 AMOLED board with a core, or the simulator for a no-hardware run; A Mac or Windows PC to run the pure-stdlib Python host service; A Claude Code or Codex account whose usage you want to monitor; Wi-Fi shared by the computer and the panel for local mode.

What are alternatives to Vibepulse?

Other hot AI repos in Personal productivity: Graybox, Needle, Pocket Strike, Lossless Memory, Hermes Bot Forge.

Is Vibepulse safe to run?

Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.