DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to point Talk with Me at a remote LLM with an API key with Talk with Me

Connect the chat app to a hosted OpenAI-compatible LLM while keeping the key out of settings.yaml.

Authorization notice. Talk with Me is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Your API key is sent in each LLM request, and remote usage may incur costs, so keep llm_api_key out of version control and watch your bill.

Who it is forA user whose local hardware is too small for a good model and who wants to use a hosted LLM from a provider they trust.

The problemLocal models may be too slow or weak, and the app needs a credential that must not sit in a config file.

The outcomeChats go to the remote LLM, with the Authorization header sent on each request and the key never shown in the UI or logs.

What you need first

  • Python 3.10 or newer
  • A locally running llama.cpp server with an OpenAI-compatible API (the README mentions the --api flag)
  • A clone of the TalkWithMe repository and its dependencies installed from requirements.txt

Steps

  1. Run cp llm_api_key.example llm_api_key in the project root.
  2. Open the llm_api_key file and replace your_key_here with your API key.
  3. Run chmod 600 llm_api_key to keep the key readable only by you.
  4. Set llm.base_url in settings.yaml to your provider's OpenAI-compatible URL, using https://.
  5. Run uvicorn app.main:app --host 0.0.0.0 --port 8000 --reload and send a test message.

Prompt for your agent

Use the TalkWithMe repo to connect to the remote LLM at <llm-base-url> using the key in llm_api_key. Send the test message <test-message> and report the reply and the startup log line saying whether a key is configured. Verify that the key value itself does not appear in the log or the UI.

Caveat. The README warns that only remote LLMs you trust should be connected, and that cleartext http:// URLs expose chats and the key.

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