Install the Fungi CLI

Run an Agent in your project folder. Use Fungi hosted models or bring your own provider key or subscription.

Install

Fungi CLI needs Linux x64/arm64 with glibc 2.35+. macOS is coming soon. Windows and Alpine Linux (musl) are not supported.

Install with npm and Node 22.13 or newer:

Illustrative: this command needs the CLI’s npm release and installs it globally.

TERMINAL

npm i -g @fungi.computer/cli

Keep npm optional dependencies enabled; they supply the native runtime. You do not need a separate Bun installation. On an unsupported machine, the Node launcher exits before loading native code and prints:

TEXT

Fungi CLI needs Linux x64/arm64 with glibc 2.35+. macOS is coming soon.

Run fungi doctor to see the detected platform and glibc version. On supported Linux, it also checks saved Fungi sign-in, model readiness and connectivity. It reports a missing login with fungi login --provider fungi as the next step and never displays credentials. On unsupported platforms, sign-in is left unchecked; doctor exits with the same platform requirement.

If native dependencies are missing, reinstall with:

TERMINAL

npm install -g @fungi.computer/cli --include=optional

If your shell cannot find fungi, check that npm’s global executable directory is on your PATH and open a new terminal. Run fungi --version to check which installation it finds.

First run

Open a terminal in your project folder and run fungi. Setup walks you through choosing a model and starting a local Agent Session. You can connect a Fungi Team or stay local. Every step can be skipped.

fungi login --provider fungi opens Fungi browser sign-in and approval, then selects the Team that pays for models. With one current Team, selection is automatic. You need a funded Team to run hosted models. Use /model inside the conversation to choose Fungi and a hosted model such as Luna. Login alone does not change the Session’s model.

fungi login offers the available providers. Your own key or subscription uses that provider’s billing. Fungi models use the selected Team’s hosted billing. Local files, tools and Session storage stay on your machine in either case.

Inside a conversation, /model chooses a model and /thinking chooses a level that model supports. MCP and models share one Fungi account login, while the project’s Computer endpoint and model billing Team are separate selections. Skipping login lets you inspect setup, but does not make a model available.

Use your editor

Use Fungi in your editor (ACP) to connect Zed or another ACP client. The editor shares your local login and saved Sessions with the terminal.

Handy commands

Illustrative: these commands need an installed CLI, and login may require a terminal and your provider account.

TERMINAL

fungi login --provider fungi
fungi doctor
fungi --version

fungi --yes skips prompts and saves local-only setup. Piped input never opens setup prompts. For automation use fungi run "your prompt" after configuring a model in a terminal. Login requiring a key or browser code needs a terminal.

Resume and stop

Run fungi resume in the same project folder to choose a saved Session, or fungi resume --last for the latest. Closing the terminal leaves the shared local service running. fungi stop stops that service for all local clients without deleting saved Sessions.

Remove Fungi

Stop the shared service with fungi stop, then run npm uninstall -g @fungi.computer/cli. Uninstalling the executable does not delete your project .fungi/ directories or your home .fungi/ configuration and credentials. Keep those if you want to resume work after reinstalling.