• Open the Terminal tab and check what's running
• Start your dev server: npm run dev -- --host 0.0.0.0 --port 8080
• Or for Python: uvicorn main:app --host 0.0.0.0 --port 8080 --reload
• Check the log below for crash details, then ask pChisel to fix it

▲ Next.js 16.2.6 (Turbopack)
- Local:         http://localhost:8080
- Network:       http://172.17.0.11:8080
✓ Ready in 368ms
⚠ Slow filesystem detected. The benchmark took 295ms. If /workspace/.next/dev is a network drive, consider moving it to a local folder.
See more: https://nextjs.org/docs/app/guides/local-development

 GET / 200 in 3.8s (next.js: 2.9s, application-code: 857ms)
 GET / 200 in 283ms (next.js: 12ms, application-code: 271ms)
 GET / 200 in 106ms (next.js: 2ms, application-code: 104ms)
 GET / 200 in 164ms (next.js: 1441µs, application-code: 163ms)
 GET / 200 in 114ms (next.js: 3ms, application-code: 112ms)
 GET /api/github/status 404 in 93ms (next.js: 24ms, application-code: 69ms)
 GET /api/v1/health 404 in 46ms (next.js: 3ms, application-code: 43ms)
 GET /api/v1/health 404 in 43ms (next.js: 3ms, application-code: 41ms)
 GET / 200 in 109ms (next.js: 2ms, application-code: 107ms)
 GET /api/v1/health 404 in 49ms (next.js: 3ms, application-code: 46ms)
 GET /api/v1/health 404 in 47ms (next.js: 1930µs, application-code: 45ms)
 GET /api/v1/health 404 in 42ms (next.js: 2ms, application-code: 39ms)
 GET /api/v1/health 404 in 39ms (next.js: 1831µs, application-code: 37ms)
 GET / 200 in 154ms (next.js: 1399µs, application-code: 153ms)
 GET /api/github/status 404 in 89ms (next.js: 2ms, application-code: 87ms)
 GET /api/v1/health 404 in 35ms (next.js: 1903µs, application-code: 33ms)
 GET /robots.txt 404 in 37ms (next.js: 3ms, application-code: 34ms)
 GET /sitemap.xml 404 in 36ms (next.js: 1919µs, application-code: 34ms)