Install Fulcrum Code and sign in
Install Fulcrum Code, authenticate with your Fulcrum account, launch it in a project folder, select a model and check your installation.
Install the application
- Open the Fulcrum Code website and use its current download or installation instructions. Choose your operating system and processor architecture.
- Follow the instructions for that download. Open a fresh terminal after changing your PATH.
- Run
fulcrum --version. A version response confirms that the launcher is on PATH; it does not test your account or model access.
Authenticate
fulcrum login
fulcrum whoamiThe login command opens the browser for Fulcrum authentication. Complete the flow with the account you intend to use. The managed platform supplies model access; normal setup does not require copying provider API keys into a configuration file. Sign-in credentials are stored separately in the operating system keychain.
Open a project
cd path/to/your-project
fulcrumChoose /models, then ask a read-only question such as “Summarise this project and identify its test command.” Check /status to confirm the working directory. Starting in the wrong folder gives the agent the wrong context and may affect the wrong files.
Update and check
fulcrum --check-update checks for an update. fulcrum --update installs the available release. Inside a session, /doctor runs diagnostic checks and /version reports the running version. Save work before replacing a running installation.
If setup fails
| Symptom | Next step |
|---|---|
| Command not found | Check the download's launcher location and PATH. Restart the terminal and retry the version command. |
| Browser signs in to the wrong account | Check the browser account before completing login, then verify with fulcrum whoami. |
| Session expired or revoked | Run fulcrum login again; do not paste credential files into a chat. |
| Slow startup around connected tools | Try fulcrum --skip-mcp to isolate MCP startup, then inspect the failing connection. |
| Model or allowance error | Check /whoami, /usage and the available catalogue with /models. |
For a support request, include the version, operating system, command and redacted error. Exclude account tokens, private source and full diagnostic dumps containing personal paths.
Last updated