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

How to cap memory and keep the GPU off on a shared machine with Janas

Start Janas-LLM with a memory limit or without the GPU so it does not take over a shared computer.

Who it is forA user on a shared or work machine who wants a local model without it filling the memory or touching the GPU.

The problemThe engine fills free memory with its expert cache and can use the GPU, which may disturb other work on the same machine.

The outcomeA chat session that keeps to a set memory limit and runs on the CPU only.

What you need first

  • Linux x86-64 (Ubuntu 22.04, Debian 12 and later) or Windows 10 (1903 or later) or 11, x86-64
  • A terminal on the machine
  • Enough free disk space for the model you pick; the README lists Qwen3-Next-80B at 48.4 GB
  • A machine with 32 GB of RAM is the one the README measured on; other machines are untested

Steps

  1. Run the chat with the GPU off (inferred): JANAS_GPU=0 ./janas-chat (inferred, check the README)
  2. To cap memory, start the chat with the --cache option set to a limit of your choice (inferred flag form, check the value the README gives in docs/chat.md)
  3. Watch the desktop responsiveness during the first replies
  4. Stop a reply with Ctrl-C if the machine slows down

Prompt for your agent

In the janas repo, run JANAS_GPU=0 ./janas-chat and ask one short question. Report the reply and confirm from the output that no GPU was used. Verify that the process ended cleanly after Ctrl-D.

Caveat. The README warns that using a GPU has once caused a driver reset that took the desktop with it, so keeping the GPU off is the safer choice on a machine you cannot afford to lose.

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