Suna SOP

Appearance

Test ​

Status: PARTIAL (cloned; deps not installed) ​

Suna (kortix-ai/suna) is a full-stack open-source agent requiring Docker Compose with multiple services, a Supabase instance, and several API keys.

Previous status (desktop, 2026-06-30) ​

SANDBOX-NEEDED -- Docker and account required; no isolated environment available.

Hetzner (server) ​

Verify command run 2026-07-01:

bash
ssh -o BatchMode=yes -o ConnectTimeout=15 agent-runtime-hetzner-1 \
  'ls ~/browser-tools/repos/suna >/dev/null 2>&1 \
  && cd ~/browser-tools/repos/suna \
  && (pnpm list --depth=0 2>/dev/null | head -3 || echo cloned)'

Real output: (no output -- pnpm is not in PATH; command silently exits 0)

Supplementary verification (same session):

--- pnpm in PATH: NOT_FOUND
--- corepack pnpm version: 8.11.0
--- node_modules exists: NO
--- git remote: https://github.com/kortix-ai/suna
--- package.json name: "name": "kortix"

What the fix script did (fix-report-20260701-050652.md):

## 4. suna (pnpm monorepo, not python)
- PARTIAL suna cloned; pnpm install -> timeout: failed to run command 'pnpm': No such file or directory

Verdict: PARTIAL. The repo is cloned with a valid pnpm lockfile (pnpm-lock.yaml, 1 MB). corepack pnpm resolves to v8.11.0 (pinned by the repo's .npmrc). However node_modules are absent -- pnpm install was never completed because pnpm is not in PATH. The full Docker Compose stack has not been brought up.

What is still needed to reach PASS:

  1. Add pnpm to PATH: corepack enable pnpm (or symlink corepack pnpm -> /usr/local/bin/pnpm)
  2. Run pnpm install inside ~/browser-tools/repos/suna (may take several minutes)
  3. Configure .env files for backend and frontend per the Suna README
  4. docker compose up -d and confirm all containers running

Why full smoke test requires Docker ​

Suna requires at minimum:

  • Docker Compose to run the backend, frontend, Redis, and sandbox containers
  • A Supabase project (hosted or self-hosted) for auth and storage
  • API keys for at least one LLM provider and Supabase credentials
  • A Daytona or E2B sandbox account for code execution isolation

Smoke test procedure (inside isolated Docker environment) ​

Step 1: Start the full stack

bash
docker compose up -d

Step 2: Confirm all services are running

bash
docker compose ps

All containers must show running. Any container in exited or restarting indicates a missing credential or misconfigured .env.

Step 3: Frontend health check

bash
curl -o /dev/null -s -w "%{http_code}" http://localhost:3000

Expected output:

200

Step 4: Backend health check

bash
curl http://localhost:8000/health

Expected output:

json
{"status": "ok"}

Step 5: Browser check

Open http://localhost:3000. The Suna dashboard login page should appear.

Do not use until ​

A complete Docker Compose environment is configured with valid Supabase credentials, LLM API keys, and all containers confirmed running.