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

How to run FuXi on your own provider key and switch models with Fuxi

Connect your own API key and change models with /model to manage which provider handles your work.

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

Credentials. Your provider API key is stored in local config or an environment variable, so keep the config file out of shared repositories and logs.

Who it is forA developer who already pays for an LLM provider and wants FuXi to use that key instead of FuXi-managed models.

The problemTeams often want to control which provider and model handle their code, and to change models without restarting their workflow.

The outcomeFuXi sends requests to the provider you chose and lets you switch models in the middle of a session.

What you need first

  • A FuXi account (`fuxi login`) or your own LLM provider API key
  • A macOS, Linux, or Windows terminal
  • A local code repository to work in

Steps

  1. fuxi init
  2. Set your API key in ~/.fuxi/config.yaml or as an environment variable, as described in the usage guide.
  3. fuxi doctor
  4. fuxi
  5. Type /model in the session to pick a different model.

Prompt for your agent

Configure the FuXi repo at fuxicodex/Fuxi to use the API key for <provider-name> from the local environment, then start a session. Expected output: FuXi starts and answers a short test prompt using the provider you set. Verify that the request is billed to your own provider account and not to FuXi-managed models.

Caveat. The README does not list which LLM providers are supported, so check the environment variable reference before assuming your provider works.

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