Security

​

Password Protection

# Basic auth
GITAGENT_PASSWORD=mysecret gitagent --voice --dir ~/assistant

# With custom username (defaults to "admin")
GITAGENT_USERNAME=alice GITAGENT_PASSWORD=mysecret gitagent --voice --dir ~/assistant

• All HTTP routes show a login page instead of the UI
• WebSocket connections are rejected without valid auth cookie
• /health endpoint remains open (for load balancers)
• Cookie: HttpOnly, SameSite=Strict, 24-hour expiry
• Token is SHA-256 hash (password never stored in cookie)
• GITAGENT_USERNAME sets the login username (defaults to “admin”)

​

Best Practices

​

HTTPS Setup

server {
  listen 443 ssl;
  server_name agent.example.com;

  location / {
    proxy_pass http://localhost:3333;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
  }
}

cloudflared tunnel --url http://localhost:3333

​

E2B Cloud Sandbox

1. Cloud VM isolation — Agent runs inside an E2B cloud sandbox — fully isolated from your local machine.
2. Filesystem isolation — The sandbox has its own filesystem. Your host files are not accessible unless explicitly mounted.
3. Remote repo support — Use —sandbox-repo to clone a repository directly into the sandbox environment.
4. API token required — Set E2B_API_KEY in your environment — the E2B SDK reads it directly. —sandbox-token is a Git token for cloning the repository (falls back to GITHUB_TOKEN / GIT_TOKEN).

# Run agent in an E2B cloud sandbox
gitagent --sandbox --dir ~/assistant

# Clone a remote repo into the sandbox
gitagent --sandbox --sandbox-repo https://github.com/user/repo --dir ~/assistant