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

How to switch Ever Room's Agent to a real model provider with Ever Room

Set the Pi runtime and provider variables so the Agent uses a real model instead of the fake runtime.

Credentials. The Pi runtime needs an API key for your model provider, so store it outside committed files and rotate it if it leaks.

Who it is forA developer who has an OpenAI-style API key and wants the workspace Agent to produce real answers instead of fallback output.

The problemThe default fake runtime lets the app open without credentials, but it cannot test real agent work. The user needs the Pi runtime connected to a model.

The outcomeThe desktop starts with the Pi runtime, and Agent sessions call the configured model.

What you need first

  • A Mac, since macOS is the current development target
  • Node.js 22 or newer
  • pnpm 11.15.1 or a compatible pnpm 11 release
  • Optional: an API key for an OpenAI-style provider, only needed for the Pi runtime

Steps

  1. Add the NXCORE_AGENT_RUNTIME, NXCORE_AI_PROVIDER, NXCORE_AI_MODEL, NXCORE_AI_BASE_URL, NXCORE_AI_API, and NXCORE_AI_API_KEY values from the README dotenv block to the development environment. (inferred, check the README)
  2. Put the API key in your environment or a local secret store, not in a committed file. (inferred, check the README)
  3. Run pnpm dev and start an Agent session from a Room.
  4. Send a short test prompt and confirm the reply comes from the configured model rather than the fake runtime.

Prompt for your agent

Using the EverRoom repository at <repo path>, read the Run with a real Agent model section of README.md and list the environment variables needed for the Pi runtime. Output them as a dotenv template with empty values for secrets. Verify that no real API key is written into the output.

Caveat. The README says the default runtime is fake so the app opens without credentials, and Pi runtime behavior is still evolving.

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