Skip to content

v0.1.2 — Hosted API Providers

Choose a tag to compare

@tawhid-rahman-aetex tawhid-rahman-aetex released this 06 Oct 15:08
· 2 commits to main since this release

BuddyChat XP can now talk to hosted models, not just your local
llama.cpp server.

This release adds a Provider dropdown to the Connection pane. Pick a
hosted API, paste your key, and chat — the same retro XP interface, the
same memory and history features, now backed by OpenAI, Groq,
OpenRouter, or any OpenAI-compatible endpoint you point it at.

Highlights

  • Eight built-in providers. Local (llama.cpp), OpenAI, OpenRouter,
    Groq, Together, DeepSeek, Mistral, and Custom. The Custom option
    takes any OpenAI-compatible URL — self-hosted vLLM, LocalAI, a
    company gateway, a personal proxy.

  • Per-provider configuration. Your choice of provider, API key, and
    model name are all stored separately. Switching between Local and
    OpenRouter keeps both configurations intact. Switch back and
    everything restores.

  • Smart request headers. Local requests keep using
    Content-Type: text/plain to avoid a CORS preflight. Online requests
    switch to application/json with an Authorization: Bearer header.
    OpenRouter also gets HTTP-Referer and X-Title so the app shows
    up in their rankings.

  • Better error messages. The Test button now distinguishes between
    a bad API key (HTTP 401/403) and an unreachable endpoint, and tells
    you which provider it was checking.

The provider table

Provider Endpoint Default model
Local (llama.cpp) http://localhost:8080/v1 (whatever llama serve loads)
OpenAI https://api.openai.com/v1 gpt-4o-mini
OpenRouter https://openrouter.ai/api/v1 openai/gpt-4o-mini
Groq https://api.groq.com/openai/v1 llama-3.3-70b-versatile
Together https://api.together.xyz/v1 meta-llama/Llama-3.3-70B-Instruct-Turbo
DeepSeek https://api.deepseek.com/v1 deepseek-chat
Mistral https://api.mistral.ai/v1 mistral-small-latest
Custom (any URL) (any model name)

Security note about API keys

API keys are stored in your browser's localStorage on the same origin
as the page. They are not encrypted. Anyone with access to your
browser profile or dev tools can read them.

This is fine on a personal machine. It is not fine on a shared computer,
a public kiosk, or a machine you don't fully control. The UI shows a red
warning under the API Key field when an online provider is active.

To remove a saved key, clear the field and blur it.

Internet Explorer 8 and 9

Online providers are not available in ie.html. IE8/IE9's
XDomainRequest cannot send Authorization headers, so authenticated
cross-origin requests are impossible without a proxy. The Provider
dropdown in IE mode shows only Local (llama.cpp).

The IE pipeline continues to work perfectly with a local model. If you
want the retro XP experience with hosted models, use the modern page.

Also in this release

  • Migrated settings shape: the old v1 server field is auto-migrated
    to a new localServer key on first load. Existing users lose
    nothing.
  • XP.getServer() renamed to XP.getEndpoint(). If you were calling
    the old function from outside the app, switch to the new one.
  • Corrected llama.cpp repository links from ggerganov/llama.cpp to
    ggml-org/llama.cpp throughout the README and landing page.
  • New "Online Models" section on the landing page, new "Online API
    providers" section in the README.

Breaking changes

XP.getServer() has been removed. Use XP.getEndpoint() instead.

The localStorage settings shape has changed to store per-provider
keys and model names. The v1 shape is auto-migrated on first load, so
existing users do not need to do anything.

Requirements

  • llama.cpp running as an OpenAI-compatible server (for Local), or an
    API key for whichever hosted provider you want to use
  • Python 3, Python 2, or Node.js on the machine serving the files
  • Any of: modern browser, MyPal, Firefox 3.5+, Chrome 4+ (IE8/IE9 for
    Local only)

Install

Windows (PowerShell):

irm https://aetex.is-a.dev/buddyxp/install.ps1 | iex

macOS / Linux:

curl -fsSL https://aetex.is-a.dev/buddyxp/install.sh | sh

Then run buddyxp.

If you're upgrading from v0.1.1, just re-run the installer. Your
settings, conversations, and memory survive.

See the README for the full
provider documentation, memory and history docs, and Windows XP
instructions.

License

MIT © 2025 AeteX Interactive