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

How to use Codex with a local model on your Mac with Slotstream

Launch Codex against the Slotstream model so code tasks stay on your machine.

Who it is forA developer who uses Codex and wants code tasks handled on a private local model.

The problemSending proprietary code to a remote model is not always allowed, and Codex needs a model it can reach.

The outcomeCodex connected to the local model through one launch command, with the server started automatically if none is running.

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. Install Codex separately, since it provides the agent interface and Slotstream provides the model.
  2. Run the Slotstream install command and then slotstream doctor.
  3. Run slotstream launch codex from the project folder you want to work in. (inferred, check the README)
  4. Give Codex a small task in that folder, such as adding a comment to one function.
  5. Check that the change appears in the file and that the reply came from the local server.

Prompt for your agent

In the carloslfu/slotstream repo, run `slotstream launch codex` from <project path>. Expected output: Codex opens connected to the local model. Verify by asking it for a one-line code explanation of <file name> and confirming it responds.

Caveat. The README says only one generation runs at a time, so other apps connected to the same server will share the model and wait their turn.

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