Troubleshooting
Fixes for common Assumer problems: sign-in errors, install and upgrade issues, MCP connection failures, language servers and where to report bugs.
“Sign in to Assumer to start using models”
Models run through your Assumer account. Run:
assumer login
Approve the sign-in in your browser, then start assumer again. /status in the terminal UI shows the account you are signed in with.
assumer: command not found
Make sure your package manager’s global bin directory is on your PATH, then reinstall:
npm i -g @4born-solutions/assumer
Update or remove
assumer upgrade
assumer uninstall
An MCP server won’t connect
assumer mcp list
assumer mcp debug <name>
Remote servers may need assumer mcp auth <name>. Local servers need their command (for example npx) to be available.
Language server problems
assumer debug lsp
Still stuck?
- Check the changelog for a newer version.
- Report bugs and request features on GitHub.
- Or contact us.