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

How to connect your own app to a local model API with Slotstream

Run the Slotstream server and point an Ollama or OpenAI client at it.

Who it is forA developer building an app or script that calls an LLM and wants a local endpoint with no external API key.

The problemPrototyping an AI feature usually means paying for a hosted API and sending test data off the machine.

The outcomeA local server on the Mac that answers requests from Ollama-style or OpenAI-style clients.

What you need first

  • An Apple Silicon Mac with at least 16 GB of memory
  • macOS 14 or later
  • About 110 GB of free SSD space
  • An internet connection for the one-time model download
  • Terminal access to run the install command

Steps

  1. Run the Slotstream install command and then slotstream doctor.
  2. Run slotstream serve --prefix-cache-dir <folder> with a folder you choose for saved conversation prefixes. (inferred, check the README)
  3. Point your Ollama or OpenAI client at the local server address shown in the startup output.
  4. Send one test request from your app and confirm a reply comes back.
  5. Read the engineering guide for the API references and command options before going further.

Prompt for your agent

In the carloslfu/slotstream repo, run `slotstream serve --prefix-cache-dir <folder>` and send one OpenAI-compatible chat request to the local address printed at startup. Expected output: a JSON chat response from the local model. Verify that the response contains generated text and that the server log shows the request.

Caveat. The README notes that the server handles one generation at a time, so load tests with many simultaneous requests will queue.

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