Sign In to Remote AI Providers
Connect subscriptions, API keys, and vendor CLIs to the right Fabric server profile without hunting for credential paths.
You do not need to log into the VM for every provider. API keys and Claude Pro / Max can be connected from Fabric. Direct CLI providers need their CLI installed and signed in on the execution server; Desktop can open the remote sign-in terminal for you. No graphical desktop on the VM is required.
Connect to your remote workspace first, then open Remote setup or Settings → AI → Remote setup. Check the displayed server name before adding an account. You do not need a Fabric cloud account.
Choose your sign-in method
| Method | Where you complete sign-in | Is an SSH terminal needed? |
|---|---|---|
| API key | Enter it in the remote workspace's Settings → AI → Add Connection | No |
| Claude Pro / Max | Start in Fabric, authorize in your computer's browser, then paste the authorization code into Fabric | No |
| ChatGPT subscription | Use the supported native Desktop sign-in flow | Not a browser-only flow; an OpenAI API key is the browser alternative |
| Cursor, Grok, Kimi, Droid, Antigravity, GrokBot CLI | Use the vendor CLI inside the selected server profile | Yes, for interactive CLI sign-in; Desktop SSH can open it for you |
The server token opens Fabric on the server. A provider account or API key pays for model calls. They are separate credentials.
Sign-ins belong to the selected server profile. Signing in on your laptop, or in another profile on the same server, does not sign in this profile. You do not repeat sign-in for each conversation; reauthenticate when the provider asks or when changing accounts.
Connect an API key or Claude subscription
- Select the remote workspace and open Settings → AI → Remote setup.
- Choose Connect an AI account and select the provider.
- For an API-key connection, enter your key in Fabric. It is stored in the execution server's encrypted credential store for that profile.
- For Claude Pro / Max, start sign-in, complete authorization in your own browser and paste the returned authorization code into Fabric. The headless server does not need a browser.
- Select the connection and model, then verify a reply.
The current Web UI cannot complete the native localhost-callback flow for ChatGPT subscription sign-in. Use the supported Desktop flow or add an OpenAI API key. A ChatGPT subscription and an API key are different options.
Connect a vendor CLI
The Fabric server archive does not bundle third-party vendor CLIs. An administrator must first install the chosen CLI on the server using its vendor's instructions. The executable must be discoverable by Fabric; see custom CLI paths if it is installed outside standard locations.
From Desktop over SSH
- Connect using Add Workspace → Connect to Remote Server → Connect using SSH.
- In that remote workspace, open Settings → AI → Remote setup → Connect an AI account.
- Choose the CLI provider and select Sign in on server. On supported SSH connections, Fabric opens a terminal for the selected profile.
- Complete the vendor's sign-in. Depending on the CLI, this may involve opening a URL on your computer, entering a device code or pasting a callback URL.
- Return to Fabric and choose Check again, then verify a reply.
If the terminal cannot open, use the copyable command shown in the dialog in a terminal on that server. Desktop URL/token connections do not necessarily have the SSH information needed to open a terminal automatically.
From a browser
The browser can configure the connection, but it cannot open your local SSH terminal. On your computer, connect as the account running the Fabric service:
ssh -t user@serverThen run this on the server. Replace user@server above with your host or
SSH alias; no profile path is needed:
curl -fsSLo install-server.sh https://agents.fabric.pro/install-server.sh &&
bash install-server.sh loginThe helper asks which provider to sign in to. When several managed profiles exist, it also asks you to select the profile. Choose the one shown in Fabric's Server details. The helper launches the CLI with that profile's isolated HOME and configuration; running a bare vendor login in your normal SSH shell can save credentials to the wrong place.
Keep install-server.sh for later use. To select a provider directly:
bash install-server.sh login cursor| Provider | Helper argument | Server executable |
|---|---|---|
| Cursor Agent | cursor | cursor-agent |
| Grok | grok | grok |
| Kimi | kimi | kimi |
| Factory Droid | droid | droid |
| Antigravity | agy | agy |
| GrokBot | grokbot | grokbot |
Use bash install-server.sh profiles to list managed profiles. To choose one
explicitly, use bash install-server.sh login cursor --profile PROFILE_NAME.
The login helper supports the six CLI providers above; use Fabric's account
connection UI for Claude Pro / Max and ChatGPT subscription sign-in.
From Docker Compose
From the directory containing your Compose file on the server, run:
docker compose run --rm -it server login cursorReplace cursor with an argument from the table. The command uses the service's
persistent profile volume. A CLI installed only on the Docker host is not
automatically available inside the container; its executable must also be
available in the container using your deployment's installation method.
Custom or older services without a recognized managed profile need an administrator-provided terminal with the service's HOME and configuration.
Verify a reply
- Return to the same remote workspace and open Settings → AI → Remote setup.
- Select the connection and model.
- Choose Send test message. This explicitly uses your provider plan and may use paid allowance.
- Wait for Reply received, then use Open check conversation to inspect the normal Explore conversation.
Check again checks CLI configuration and availability. It does not prove that the account can make a model call. A verified reply records what worked at that time; it does not guarantee remaining allowance or future sign-in validity. If the connection drops, return to the setup panel to recover the existing check before sending another test.
Resolve common sign-in problems
| What you see | What to do |
|---|---|
| CLI not found | Install it on the execution server, or inside the container, and check its configured executable path. Installing it on your laptop does not install it remotely. |
| Signed in through SSH, but Fabric still asks for sign-in | Repeat sign-in through the profile-aware helper or Desktop's Sign in on server action. Confirm the server/profile in the dialog. |
| Login completed for a different profile | Run bash install-server.sh login and select the profile displayed in Fabric. |
| Browser subscription option requires Desktop | Use the supported Desktop flow or that provider's API-key option. |
| Usage limit, billing or model-access error | Resolve the account's allowance or choose a model available to that account, then explicitly test again. |
| Permission request during a conversation | Review it in Fabric. A tool permission decision is separate from provider sign-in. |
| Server token is rejected | Follow server-token recovery; changing provider credentials will not fix server access. |
For Antigravity's headless callback and Linux keyring requirements, see the advanced CLI notes.
Remote agents read files on the remote server. A folder with the same name as a project on your laptop does not contain its files automatically. Clone or copy the project to the server through your normal workflow and select that remote directory before asking the agent to inspect it.