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

How to let games take the GPU while you play and resume AI after with Berth

Berth drains AI engines when a supported game launches and returns the card when you quit.

Who it is forA gamer who also runs local AI models on the same NVIDIA card and wants the game to get the memory.

The problemAI engines hold VRAM while a game starts, so the game stutters or fails to load.

The outcomeAI engines drain while the game runs and the card is returned when the game exits, with the state visible in `berth status`.

What you need first

  • An NVIDIA GPU on Linux, or Windows 10/11 (experimental)
  • Go installed for `go install`, or a release binary from the Install section
  • At least one local engine, such as llama-server, ComfyUI or llama-swap

Steps

  1. Install Berth and run berth service install --harbor.
  2. Confirm the daemon is running with berth status.
  3. Launch a supported game from Steam, Lutris or gamescope on Linux, or Steam, Epic, GOG, EA, Ubisoft, Xbox or Battle.net on Windows.
  4. Run berth status during play to see the game holding the card.
  5. Quit the game and run berth status again to see the card returned to the AI engines.

Prompt for your agent

On the machine with the Berth repo, run `berth service install --harbor` and then `berth status`. Expected output: the card and any leases are listed. Verify by launching a supported game and confirming `berth status` shows the game as the holder while AI engines are drained.

Caveat. Game detection is limited to the launchers the README lists, and if your game is not on that list, add a `[[claim]]` rule in `berth.toml` or use `berth hold`.

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