Troubleshooting - Symbiotic Security

Quick reference

Issue	Solution
`command not found: symbiotic`	Ensure `~/.local/bin` is in your PATH and restart your terminal
Authentication fails	Verify your token is valid in the portal and hasn’t expired
Permission denied	Run `chmod +x ~/.local/bin/symbiotic`
Can’t go to the next line	Use one of these keybindings: `shift+return`, `ctrl+return`, `alt+return`, or `ctrl+j`

Installation issues

Windows

If you have trouble installing Symbiotic Code on PowerShell, try launching the install command with Git Bash, which you can download here. If the issue is related to PowerShell execution policy, run PowerShell as Administrator and execute:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Permission denied (macOS/Linux)

If you get a permission error when installing globally:

# Option 1: Use sudo
sudo npm install -g @symbioticsec/code

# Option 2: Configure npm to use a user directory
mkdir ~/.npm-global
npm config set prefix "~/.npm-global"
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc

Platform-specific issues

Copy/paste not working on Linux

Linux users need one of the following clipboard utilities installed for copy/paste to work. X11 systems:

apt install -y xclip
# or
apt install -y xsel

Wayland systems:

apt install -y wl-clipboard

Headless environments:

apt install -y xvfb
# and run:
Xvfb :99 -screen 0 1024x768x24 > /dev/null 2>&1 &
export DISPLAY=:99.0

Symbiotic Code will detect if you’re using Wayland and prefer wl-clipboard, otherwise it will try xclip then xsel.

Using Symbiotic Code in a Docker container

Download the script and Dockerfile here
Unzip the file
Launch Docker Desktop
Make the script executable:

chmod +x run-symbiotic.sh

Run the script:

./run-symbiotic.sh

You are now inside the container and can run the symbiotic command to launch the coding agent.

Network and connectivity

If you’re behind a corporate firewall or proxy, you may need to allowlist the following domains for Symbiotic Code to connect to the API:

api.symbioticsec.ai:443
llm-proxy.symbioticsec.ai:443

Proxy configuration: If behind a corporate proxy, configure npm:

npm config set proxy http://proxy.company.com:8080
npm config set https-proxy http://proxy.company.com:8080

npm registry blocked: If the npm registry is inaccessible:

Check proxy settings: npm config get proxy
Verify your firewall allows access to registry.npmjs.org:443
Contact IT to whitelist the npm registry

Health check script

Run the following command to verify that your system is ready for Symbiotic Code:

curl -fsSL https://raw.githubusercontent.com/SymbioticSec/mintlify-docs/refs/heads/main/assets/symbiotic-health-check.js | node

The script checks:

Node.js — Ensures Node.js is installed (v14+ recommended)
npm — Verifies npm is available
Global install permissions — Tests ability to install global npm packages
Execution policy (Windows only) — Checks PowerShell execution policy
Proxy configuration — Displays current proxy settings
npm registry access — Tests connectivity to registry.npmjs.org:443
Required endpoints — Tests connectivity to:
- api.symbioticsec.ai:443
- llm-proxy.symbioticsec.ai:443

Once all checks pass, install with:

npm install -g @symbioticsec/code

If issues persist, save the health check output and contact support:

node symbiotic-health-check.js > healthcheck-results.txt 2>&1

Need help?

Contact us using the dedicated Slack channel or email us at support@symbioticsec.ai with your health check results, OS version, and network environment.

​Quick reference

​Installation issues

​Windows

​Permission denied (macOS/Linux)

​Platform-specific issues

​Copy/paste not working on Linux

​Using Symbiotic Code in a Docker container

​Network and connectivity

​Health check script