Common Issues

Solutions to frequently encountered problems.

Performance Issues

Slow Responses

Causes:

• Slow network

• Large file context

• Complex prompts

Solutions:

1

Check network

Run:

ping api.tabnine.com

2

Be more specific in prompts

Make prompts concise and targeted to reduce processing.

3

Reduce file references

Limit the amount of file content referenced in a single request.

4

Try a different model

Use the /model command to switch models.

High Memory Usage

Normal: 50-200 MB

If excessive:

1

Clear conversation

Run:

/clear

2

Restart Tabnine CLI

Restart the Tabnine CLI process to free memory.

3

Reduce context size

Limit context or file sizes referenced in prompts.

Connection Issues

Cannot Connect to API

Symptoms: "Failed to connect"

Solutions:

1

Check internet

Run:

ping api.tabnine.com

2

Check firewall

Ensure port 443 is allowed.

3

Check proxy settings

Verify proxy environment variables or client proxy configuration.

4

Try debug mode

Run:

DEBUG=1 tabnine

Proxy Issues

Solution: Set proxy variables:

export NODE_USE_ENV_PROXY=1
export HTTP_PROXY=http://proxy:8080
export HTTPS_PROXY=http://proxy:8080
tabnine

File Access Issues

Cannot Read Files

Symptoms: "Permission denied" or file not found

Solutions:

1

Check file permissions

Ensure the process has read permissions for the file.

2

Verify file path

Confirm the path is correct.

3

Check working directory

Ensure you're running commands from the intended working directory.

4

Use absolute paths

Try using absolute file paths to avoid path resolution issues.

Cannot Write Files

Symptoms: Cannot create or modify files

Solutions:

1

Check directory permissions

Ensure write permissions are available for the target directory.

2

Verify disk space

Confirm there is sufficient disk space.

3

Check file locks

Make sure the file is not locked by another process.

Feature Issues

Remote Code Search Not Working

Solutions:

1

Check enabled

Open settings: /settings → Tools → Remote Code Search

2

Verify account access

Ensure your account has the necessary access.

3

Check indexing

Confirm the codebase is indexed in Tabnine account settings.

Coaching Not Working

Solutions:

1

Check enabled

Open settings: /settings → Tools → Coaching Guidelines

2

Verify account access

Ensure your account has the necessary access.

3

Be specific in prompts

Try more specific prompts when requesting coaching.

Other Issues

Command Not Found

Symptoms: tabnine: command not found

Solutions:

1

Verify installation

Confirm Tabnine CLI is installed (see Installation Guide).

2

Check PATH

Ensure your PATH includes the installation directory.

3

Run with full path

Example:

~/.local/bin/tabnine

(Linux/macOS)

Unexpected Behavior

Solution: Enable debug mode:

DEBUG=1 tabnine

This shows detailed logs to help identify the issue.

Getting More Help

• FAQ - Frequently asked questions

• Debug Mode: DEBUG=1 tabnine

• Report Issue: Use /bug command in Tabnine CLI

Still having issues? (FAQ & reporting)

• See the FAQ: FAQ

• Enable debug logs:

DEBUG=1 tabnine

• Report an issue using the /bug command in Tabnine CLI.