Use the terminal

Install the Fungi CLI, then open a terminal in your project folder. The fungi command opens an Agent conversation. Shed is different: it opens a shell on a Team Computer in your browser.

First run and models

Run fungi. You can skip setup choices and configure a model afterwards. Choose a Fungi hosted model or use your own provider key or subscription.

Illustrative: these commands need an installed CLI. Login can ask for an API key or browser authorization, depending on the provider you choose.

TERMINAL

fungi login --provider fungi
fungi doctor
fungi

fungi login --provider fungi opens Fungi browser sign-in and approval. Choose the Team that pays for model use. A single current Team is selected automatically. You need to belong to a funded Team. Inside the conversation, use /model to choose Fungi and a hosted model such as Luna. Login alone does not change the Session’s selected model.

fungi login offers the available providers. Choosing another provider uses that provider’s login. Use /thinking for the selected model’s supported levels. Use agent model clears a Session’s override. Model default leaves the thinking level to the provider. Changing a preference does not restart the conversation or prove that the next request will succeed.

Fungi models run through the selected Team and use its hosted billing. Your own provider key or subscription is billed by that provider. The conversation and local tools remain on your machine in either case. Hosted Computer operations have their own permissions and funding. Never paste keys into an Agent prompt.

If Fungi asks you to sign in again, repeat the Fungi login. If it asks for credits, fund the named Team. An unreachable or paused service requires a retry when available. A failed Fungi request does not switch to your other providers.

Give work and find it again

Type a task and press Enter. During a run, Enter sends steering and Tab queues a follow-up. Shift+Enter or Alt+Enter inserts a newline. An accepted prompt is saved work, not a completed result. Read the final reply and check the files.

Closing the terminal leaves the shared local service running and keeps saved Sessions. Return from the same project folder:

Illustrative: these commands need a project with saved local Sessions. Replace 1 with the number from your own list.

TERMINAL

fungi sessions list
fungi sessions resume 1

fungi resume opens the saved-Session picker. fungi resume --last opens the latest. Use -C /path/to/project to select another project. A full Session ID or a unique ID prefix can replace the list number.

fungi sessions status --json reads the latest Session’s state. fungi sessions show --last prints bounded history. fungi sessions watch --last follows live state. Status alone does not prove that a particular task succeeded.

Commands and recovery

Type / to discover commands. /help lists them and /keys shows keyboard bindings. Unknown or failed slash commands remain commands, not model prompts.

Action	What it does
Escape	Dismiss an open dialog first. Otherwise, withdraw a waiting prompt or cancel active work.
/cancel	Withdraw a waiting prompt or cancel active work while keeping the conversation.
/queue	Show accepted queued prompts.
/queue edit-last	Withdraw the last waiting follow-up into an empty composer if it has not started.
/retry	Resend the failed instruction. Check for partial changes first.
/continue	Send a new instruction to continue a stopped task.
/reconnect	Retry Session history observation. It does not repeat the task.
/exit	Close this terminal client.

Ctrl+C dismisses an open dialog first. Otherwise, it exits an idle terminal or one with a waiting prompt, leaving that prompt queued. During active work, the first Ctrl+C requests cancellation. A second Ctrl+C exits even if cancellation is still pending. From your shell, fungi stop stops the shared local service for all its clients. Saved Sessions remain, and the next launch starts the service again.

For a single automated prompt, use fungi run "your prompt", or pipe a prompt to fungi run. Configure a model interactively first. The command waits for its accepted task’s result and prints the final answer. Failed or cancelled work is not a successful completion.

Team Computers and local folders

Use fungi login --fungi-mcp <url> with your Team’s MCP endpoint to authorize Team Computer tools. The browser opens Fungi sign-in and approval and selects the Team for model billing. Model access and MCP share one Fungi account login. The project can remember the MCP endpoint, while credentials stay in the local credential store. The model’s billing Team and the project’s Computer endpoint are separate choices. Changing one does not retarget the other. fungi mcp show, fungi mcp use <url> and fungi mcp forget manage that project selection.

This connection does not sync your folder or let a hosted Agent run commands on your machine. For that, follow Attach a local folder, review the access prompt and keep the attachment command running. fungi computers lists the selected Team’s Computers. fungi computers start <name> asks to start an existing one.