Skip to main content

​
Run nagare doctor

The first step is always:
The result lists each check with details. See the meaning of each item at CLI Reference.

​
Common Errors

The $HOME/.local/bin directory is not in your PATH. See Add to PATH.
The gateway is not running. Open a terminal and run nagare gateway start, keep that terminal open.
The gateway is not running or is using a different port. Check the NAGARE_GATEWAY_PORT variable and make sure port 9832 is not occupied by another program.
Nagare cannot access the operating system’s keyring. On Linux, a Secret Service daemon (for example GNOME Keyring or KWallet) must be running and unlocked.
The memory module is not installed. Run the installation script again.
The token has expired (60 hours) or the key in the keyring has changed. Run nagare web to log in again, or create a new token with nagare auth token and paste it on the login page.
  • Check that you have added a model provider and selected Default model in Settings → General.
  • Check your API key and Base URL. Use the model list feature to test the connection.
  • Check the gateway logs at ~/.nagare/logs/app.log.
The tool needs approval but no channel is available to receive the request. Open the conversation in the web interface or use Telegram so you can approve it.
  • Check the logs at ~/.nagare/logs/plugins/<package_name>.log.
  • Check that any environment variables the plugin needs (for example NAGARE_TELEGRAM_TOKEN) were set before starting the gateway.
  • Executable checksum mismatch: reinstall the plugin package.
The package was modified after signing, or was signed with a different key than the one in ~/.nagare/trusted. See Plugin Signing.

​
Logs

​
Reporting Issues

Open an issue at github.com/smtdfc/nagare/issues, including the output of nagare doctor and the relevant log excerpt.