Troubleshooting

Solutions to common issues you might encounter while using Sypha CLI.

Common Issues

"Command not found: sypha"

Symptoms:

• Running sypha returns command not found
• The installation appeared to succeed

Solution:

1. Ensure your global npm bin directory is in your $PATH.
2. Run npm bin -g to find the directory.
3. Add it to your shell profile (~/.bashrc or ~/.zshrc):

export PATH="$(npm bin -g):$PATH"

Authentication Errors

Symptoms:

• 401 Unauthorized errors
• "Invalid API Key" messages

Solution:

1. Verify your API key is correct and not expired.
2. Ensure the environment variable name matches the provider (e.g., ANTHROPIC_API_KEY for Claude, OPENAI_API_KEY for GPT).
3. If using Sypha Enterprise, check that you are logged in via /login.

Git Integration Failing

Symptoms:

• /commit or /add commands fail
• "Not a git repository" error

Solution:

1. Sypha requires the current directory to be a git repository. Run git init if it's a new project.
2. Ensure you have git installed and available in your $PATH.
3. Check permissions on the .git directory.

Slow Responses

Symptoms:

• AI takes a long time to reply
• Streaming pauses frequently

Solution:

1. Check your internet connection.
2. Verify that the selected model provider is not experiencing an outage.
3. Try switching to a faster model (e.g., claude-haiku-3 or gpt-3.5-turbo) using /model.

Error Codes

Debugging

If you are experiencing persistent issues, enable debug mode to see detailed logs.

Enable Debug Mode:

export SYPHA_CLI_DEBUG=true

Run Sypha again, and you will see verbose output indicating network requests, config loading, and internal state changes.

Log File:

Logs are typically written to:

• Mac/Linux: ~/.sypha/cli/logs/sypha.log
• Windows: %USERPROFILE%\.sypha\cli\logs\sypha.log

Getting Help

If you cannot resolve the issue, please reach out to our support channels.