DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a hand-tracked overlay in an OBS scene with Barehands

Mirror the glass board into OBS as a transparent layer over your camera for streams and recordings.

Who it is forA streamer or video creator who records demos or tutorials in OBS and wants hand-driven glass cards over their camera feed.

The problemShowing interactive on-screen objects in a recording usually needs green screens or manual editing in post.

The outcomeThe render page composites the glass cards over your camera in OBS with real transparency, and you can switch to vertical 9:16 for short-form video.

What you need first

  • A webcam
  • Google Chrome
  • Python 3 (on Windows, run.bat finds a working interpreter)
  • An internet connection on first run, because the page loads MediaPipe and three.js from CDNs

Steps

  1. Run git clone https://github.com/jaredrhod/barehands and then cd barehands.
  2. Start the app with python3 server.py and open the tracker page at http://127.0.0.1:8794/stage.html in Chrome, which owns your camera.
  3. In OBS, add a browser source pointed at http://127.0.0.1:8794/stage.html?role=render.
  4. Add &cursors=0 to hide the finger rings, or &ss=2 to render at 2x for sharper cards.
  5. Add ?portrait=1 to the tracker page to flip the rig to vertical 9:16 for Shorts and TikTok.

Prompt for your agent

In the barehands repo, start server.py and confirm that http://127.0.0.1:8794/stage.html?role=render loads without errors. Expected output is a page load with no console errors in Chrome. Verify the cards are transparent when placed in an OBS browser source.

Caveat. The README says the tracker page owns the camera, so the page must stay open in Chrome while the render page is used in OBS.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page