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

How to give coding agents a queue for the GPU instead of killing processes with Berth

Install the Berth skill so Claude Code or Codex asks for the card rather than killing GPU jobs.

Who it is forA developer who uses Claude Code or Codex on a machine with a local model or image pipeline, and whose agent kills GPU processes to free memory.

The problemAn agent frees VRAM by killing processes, which can interrupt someone else's model or render.

The outcomeThe agent asks Berth for the card, waits in line when another engine holds it, and reports the holder 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. Run berth skill install to teach your agent to ask Berth for the card.
  3. Ask the agent to start a GPU task through berth run instead of killing processes.
  4. Run berth status to confirm the agent's engine holds the lease.
  5. Use berth stop ENGINE if you need to drain an engine on purpose.

Prompt for your agent

On the machine with the Berth repo, run `berth skill install` and then `berth status`. Expected output: the skill is installed for the agent and the card's holder is listed. Verify that a GPU task started by the agent runs through `berth run` and does not kill other GPU processes.

Caveat. The skill teaches agents to ask Berth, but Berth only governs work that runs through it, so processes started outside Berth still show only as stowaways.

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