Summary
Environment
Repo: DenchHQ/ironclaw
Version: [email protected]
Next.js: 15.5.12
Runtime: Linux container (no systemd user bus)
Access path: local + ngrok tunnel
OpenClaw gateway reachable; WhatsApp linked
Summary
The UI shell renders, but the app is not functional.
Most actions remain stuck in loading state. Only some sidebar items (e.g., cron jobs) may appear.
Backend APIs intermittently hang/time out even when the web process is “running.”
Symptoms observed
/workspace renders shell, but “Enter app” / main app usage hangs.
Intermittent or frequent API timeouts:
/api/sessions
/api/skills
/api/chat/active
/api/workspace/* (e.g. context/tree/watch)
next-server process often runs high CPU and becomes non-responsive.
Multiple sessions showed:
HTTP 000 + curl timeout (12s/20s/90s)
UI still visible while backend is unresponsive.
Reproduction (from clean-ish start)
Build/start web:
cd /home/node/.openclaw/workspace/ironclaw
unset NPM_CONFIG_PREFIX
pnpm --dir apps/web build
pnpm --dir apps/web start
(also tested standalone and dev modes)
Open app (/workspace) locally or via ngrok.
UI appears, but app remains loading.
In parallel, API checks time out:
curl --max-time 12 http://127.0.0.1:3100/api/sessions
curl --max-time 12 http://127.0.0.1:3100/api/skills
curl --max-time 12 http://127.0.0.1:3100/api/chat/active
Relevant logs / observations
Frequent timeout behavior:
curl: (28) Operation timed out ... HTTP 000
High CPU stuck server:
next-server >50-100% CPU, app APIs not responding.
Inconsistent startup mode warning seen:
"next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
At times /api/profiles responds while core app endpoints hang.
What was tried
Restarting web process repeatedly
Killing stale next-server processes
Rebuilding app multiple times
Running:
standalone on 3000
dev mode on 3100
start mode on 3100
Restarting ngrok and hard-refresh/incognito
Gateway pairing/auth fixes (not root cause)
Anthropic/OpenAI auth setup verified (not root cause)
Expected
App endpoints should remain responsive after startup; UI should be fully usable, not shell-only.
Actual
UI shell often renders but backend APIs hang/time out, making app unusable.
Request
Guidance on the intended production runtime path for this repo (standalone vs next start vs dev), and investigation into API hangs/high-CPU stalls under this environment.
Steps to reproduce
Environment
Repo: DenchHQ/ironclaw
Version: [email protected]
Next.js: 15.5.12
Runtime: Linux container (no systemd user bus)
Access path: local + ngrok tunnel
OpenClaw gateway reachable; WhatsApp linked
Summary
The UI shell renders, but the app is not functional.
Most actions remain stuck in loading state. Only some sidebar items (e.g., cron jobs) may appear.
Backend APIs intermittently hang/time out even when the web process is “running.”
Symptoms observed
/workspace renders shell, but “Enter app” / main app usage hangs.
Intermittent or frequent API timeouts:
/api/sessions
/api/skills
/api/chat/active
/api/workspace/* (e.g. context/tree/watch)
next-server process often runs high CPU and becomes non-responsive.
Multiple sessions showed:
HTTP 000 + curl timeout (12s/20s/90s)
UI still visible while backend is unresponsive.
Reproduction (from clean-ish start)
Build/start web:
cd /home/node/.openclaw/workspace/ironclaw
unset NPM_CONFIG_PREFIX
pnpm --dir apps/web build
pnpm --dir apps/web start
(also tested standalone and dev modes)
Open app (/workspace) locally or via ngrok.
UI appears, but app remains loading.
In parallel, API checks time out:
curl --max-time 12 http://127.0.0.1:3100/api/sessions
curl --max-time 12 http://127.0.0.1:3100/api/skills
curl --max-time 12 http://127.0.0.1:3100/api/chat/active
Relevant logs / observations
Frequent timeout behavior:
curl: (28) Operation timed out ... HTTP 000
High CPU stuck server:
next-server >50-100% CPU, app APIs not responding.
Inconsistent startup mode warning seen:
"next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
At times /api/profiles responds while core app endpoints hang.
What was tried
Restarting web process repeatedly
Killing stale next-server processes
Rebuilding app multiple times
Running:
standalone on 3000
dev mode on 3100
start mode on 3100
Restarting ngrok and hard-refresh/incognito
Gateway pairing/auth fixes (not root cause)
Anthropic/OpenAI auth setup verified (not root cause)
Expected
App endpoints should remain responsive after startup; UI should be fully usable, not shell-only.
Actual
UI shell often renders but backend APIs hang/time out, making app unusable.
Request
Guidance on the intended production runtime path for this repo (standalone vs next start vs dev), and investigation into API hangs/high-CPU stalls under this environment.
Expected behavior
Environment
Repo: DenchHQ/ironclaw
Version: [email protected]
Next.js: 15.5.12
Runtime: Linux container (no systemd user bus)
Access path: local + ngrok tunnel
OpenClaw gateway reachable; WhatsApp linked
Summary
The UI shell renders, but the app is not functional.
Most actions remain stuck in loading state. Only some sidebar items (e.g., cron jobs) may appear.
Backend APIs intermittently hang/time out even when the web process is “running.”
Symptoms observed
/workspace renders shell, but “Enter app” / main app usage hangs.
Intermittent or frequent API timeouts:
/api/sessions
/api/skills
/api/chat/active
/api/workspace/* (e.g. context/tree/watch)
next-server process often runs high CPU and becomes non-responsive.
Multiple sessions showed:
HTTP 000 + curl timeout (12s/20s/90s)
UI still visible while backend is unresponsive.
Reproduction (from clean-ish start)
Build/start web:
cd /home/node/.openclaw/workspace/ironclaw
unset NPM_CONFIG_PREFIX
pnpm --dir apps/web build
pnpm --dir apps/web start
(also tested standalone and dev modes)
Open app (/workspace) locally or via ngrok.
UI appears, but app remains loading.
In parallel, API checks time out:
curl --max-time 12 http://127.0.0.1:3100/api/sessions
curl --max-time 12 http://127.0.0.1:3100/api/skills
curl --max-time 12 http://127.0.0.1:3100/api/chat/active
Relevant logs / observations
Frequent timeout behavior:
curl: (28) Operation timed out ... HTTP 000
High CPU stuck server:
next-server >50-100% CPU, app APIs not responding.
Inconsistent startup mode warning seen:
"next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
At times /api/profiles responds while core app endpoints hang.
What was tried
Restarting web process repeatedly
Killing stale next-server processes
Rebuilding app multiple times
Running:
standalone on 3000
dev mode on 3100
start mode on 3100
Restarting ngrok and hard-refresh/incognito
Gateway pairing/auth fixes (not root cause)
Anthropic/OpenAI auth setup verified (not root cause)
Expected
App endpoints should remain responsive after startup; UI should be fully usable, not shell-only.
Actual
UI shell often renders but backend APIs hang/time out, making app unusable.
Request
Guidance on the intended production runtime path for this repo (standalone vs next start vs dev), and investigation into API hangs/high-CPU stalls under this environment.
Actual behavior
Environment
Repo: DenchHQ/ironclaw
Version: [email protected]
Next.js: 15.5.12
Runtime: Linux container (no systemd user bus)
Access path: local + ngrok tunnel
OpenClaw gateway reachable; WhatsApp linked
Summary
The UI shell renders, but the app is not functional.
Most actions remain stuck in loading state. Only some sidebar items (e.g., cron jobs) may appear.
Backend APIs intermittently hang/time out even when the web process is “running.”
Symptoms observed
/workspace renders shell, but “Enter app” / main app usage hangs.
Intermittent or frequent API timeouts:
/api/sessions
/api/skills
/api/chat/active
/api/workspace/* (e.g. context/tree/watch)
next-server process often runs high CPU and becomes non-responsive.
Multiple sessions showed:
HTTP 000 + curl timeout (12s/20s/90s)
UI still visible while backend is unresponsive.
Reproduction (from clean-ish start)
Build/start web:
cd /home/node/.openclaw/workspace/ironclaw
unset NPM_CONFIG_PREFIX
pnpm --dir apps/web build
pnpm --dir apps/web start
(also tested standalone and dev modes)
Open app (/workspace) locally or via ngrok.
UI appears, but app remains loading.
In parallel, API checks time out:
curl --max-time 12 http://127.0.0.1:3100/api/sessions
curl --max-time 12 http://127.0.0.1:3100/api/skills
curl --max-time 12 http://127.0.0.1:3100/api/chat/active
Relevant logs / observations
Frequent timeout behavior:
curl: (28) Operation timed out ... HTTP 000
High CPU stuck server:
next-server >50-100% CPU, app APIs not responding.
Inconsistent startup mode warning seen:
"next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
At times /api/profiles responds while core app endpoints hang.
What was tried
Restarting web process repeatedly
Killing stale next-server processes
Rebuilding app multiple times
Running:
standalone on 3000
dev mode on 3100
start mode on 3100
Restarting ngrok and hard-refresh/incognito
Gateway pairing/auth fixes (not root cause)
Anthropic/OpenAI auth setup verified (not root cause)
Expected
App endpoints should remain responsive after startup; UI should be fully usable, not shell-only.
Actual
UI shell often renders but backend APIs hang/time out, making app unusable.
Request
Guidance on the intended production runtime path for this repo (standalone vs next start vs dev), and investigation into API hangs/high-CPU stalls under this environment.
OpenClaw version
latest
Operating system
mac sonoma 14.7
Install method
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Summary
Environment
Repo: DenchHQ/ironclaw
Version: [email protected]
Next.js: 15.5.12
Runtime: Linux container (no systemd user bus)
Access path: local + ngrok tunnel
OpenClaw gateway reachable; WhatsApp linked
Summary
The UI shell renders, but the app is not functional.
Most actions remain stuck in loading state. Only some sidebar items (e.g., cron jobs) may appear.
Backend APIs intermittently hang/time out even when the web process is “running.”
Symptoms observed
/workspace renders shell, but “Enter app” / main app usage hangs.
Intermittent or frequent API timeouts:
/api/sessions
/api/skills
/api/chat/active
/api/workspace/* (e.g. context/tree/watch)
next-server process often runs high CPU and becomes non-responsive.
Multiple sessions showed:
HTTP 000 + curl timeout (12s/20s/90s)
UI still visible while backend is unresponsive.
Reproduction (from clean-ish start)
Build/start web:
cd /home/node/.openclaw/workspace/ironclaw
unset NPM_CONFIG_PREFIX
pnpm --dir apps/web build
pnpm --dir apps/web start
(also tested standalone and dev modes)
Open app (/workspace) locally or via ngrok.
UI appears, but app remains loading.
In parallel, API checks time out:
curl --max-time 12 http://127.0.0.1:3100/api/sessions
curl --max-time 12 http://127.0.0.1:3100/api/skills
curl --max-time 12 http://127.0.0.1:3100/api/chat/active
Relevant logs / observations
Frequent timeout behavior:
curl: (28) Operation timed out ... HTTP 000
High CPU stuck server:
next-server >50-100% CPU, app APIs not responding.
Inconsistent startup mode warning seen:
"next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
At times /api/profiles responds while core app endpoints hang.
What was tried
Restarting web process repeatedly
Killing stale next-server processes
Rebuilding app multiple times
Running:
standalone on 3000
dev mode on 3100
start mode on 3100
Restarting ngrok and hard-refresh/incognito
Gateway pairing/auth fixes (not root cause)
Anthropic/OpenAI auth setup verified (not root cause)
Expected
App endpoints should remain responsive after startup; UI should be fully usable, not shell-only.
Actual
UI shell often renders but backend APIs hang/time out, making app unusable.
Request
Guidance on the intended production runtime path for this repo (standalone vs next start vs dev), and investigation into API hangs/high-CPU stalls under this environment.
Steps to reproduce
Environment
Repo: DenchHQ/ironclaw
Version: [email protected]
Next.js: 15.5.12
Runtime: Linux container (no systemd user bus)
Access path: local + ngrok tunnel
OpenClaw gateway reachable; WhatsApp linked
Summary
The UI shell renders, but the app is not functional.
Most actions remain stuck in loading state. Only some sidebar items (e.g., cron jobs) may appear.
Backend APIs intermittently hang/time out even when the web process is “running.”
Symptoms observed
/workspace renders shell, but “Enter app” / main app usage hangs.
Intermittent or frequent API timeouts:
/api/sessions
/api/skills
/api/chat/active
/api/workspace/* (e.g. context/tree/watch)
next-server process often runs high CPU and becomes non-responsive.
Multiple sessions showed:
HTTP 000 + curl timeout (12s/20s/90s)
UI still visible while backend is unresponsive.
Reproduction (from clean-ish start)
Build/start web:
cd /home/node/.openclaw/workspace/ironclaw
unset NPM_CONFIG_PREFIX
pnpm --dir apps/web build
pnpm --dir apps/web start
(also tested standalone and dev modes)
Open app (/workspace) locally or via ngrok.
UI appears, but app remains loading.
In parallel, API checks time out:
curl --max-time 12 http://127.0.0.1:3100/api/sessions
curl --max-time 12 http://127.0.0.1:3100/api/skills
curl --max-time 12 http://127.0.0.1:3100/api/chat/active
Relevant logs / observations
Frequent timeout behavior:
curl: (28) Operation timed out ... HTTP 000
High CPU stuck server:
next-server >50-100% CPU, app APIs not responding.
Inconsistent startup mode warning seen:
"next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
At times /api/profiles responds while core app endpoints hang.
What was tried
Restarting web process repeatedly
Killing stale next-server processes
Rebuilding app multiple times
Running:
standalone on 3000
dev mode on 3100
start mode on 3100
Restarting ngrok and hard-refresh/incognito
Gateway pairing/auth fixes (not root cause)
Anthropic/OpenAI auth setup verified (not root cause)
Expected
App endpoints should remain responsive after startup; UI should be fully usable, not shell-only.
Actual
UI shell often renders but backend APIs hang/time out, making app unusable.
Request
Guidance on the intended production runtime path for this repo (standalone vs next start vs dev), and investigation into API hangs/high-CPU stalls under this environment.
Expected behavior
Environment
Repo: DenchHQ/ironclaw
Version: [email protected]
Next.js: 15.5.12
Runtime: Linux container (no systemd user bus)
Access path: local + ngrok tunnel
OpenClaw gateway reachable; WhatsApp linked
Summary
The UI shell renders, but the app is not functional.
Most actions remain stuck in loading state. Only some sidebar items (e.g., cron jobs) may appear.
Backend APIs intermittently hang/time out even when the web process is “running.”
Symptoms observed
/workspace renders shell, but “Enter app” / main app usage hangs.
Intermittent or frequent API timeouts:
/api/sessions
/api/skills
/api/chat/active
/api/workspace/* (e.g. context/tree/watch)
next-server process often runs high CPU and becomes non-responsive.
Multiple sessions showed:
HTTP 000 + curl timeout (12s/20s/90s)
UI still visible while backend is unresponsive.
Reproduction (from clean-ish start)
Build/start web:
cd /home/node/.openclaw/workspace/ironclaw
unset NPM_CONFIG_PREFIX
pnpm --dir apps/web build
pnpm --dir apps/web start
(also tested standalone and dev modes)
Open app (/workspace) locally or via ngrok.
UI appears, but app remains loading.
In parallel, API checks time out:
curl --max-time 12 http://127.0.0.1:3100/api/sessions
curl --max-time 12 http://127.0.0.1:3100/api/skills
curl --max-time 12 http://127.0.0.1:3100/api/chat/active
Relevant logs / observations
Frequent timeout behavior:
curl: (28) Operation timed out ... HTTP 000
High CPU stuck server:
next-server >50-100% CPU, app APIs not responding.
Inconsistent startup mode warning seen:
"next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
At times /api/profiles responds while core app endpoints hang.
What was tried
Restarting web process repeatedly
Killing stale next-server processes
Rebuilding app multiple times
Running:
standalone on 3000
dev mode on 3100
start mode on 3100
Restarting ngrok and hard-refresh/incognito
Gateway pairing/auth fixes (not root cause)
Anthropic/OpenAI auth setup verified (not root cause)
Expected
App endpoints should remain responsive after startup; UI should be fully usable, not shell-only.
Actual
UI shell often renders but backend APIs hang/time out, making app unusable.
Request
Guidance on the intended production runtime path for this repo (standalone vs next start vs dev), and investigation into API hangs/high-CPU stalls under this environment.
Actual behavior
Environment
Repo: DenchHQ/ironclaw
Version: [email protected]
Next.js: 15.5.12
Runtime: Linux container (no systemd user bus)
Access path: local + ngrok tunnel
OpenClaw gateway reachable; WhatsApp linked
Summary
The UI shell renders, but the app is not functional.
Most actions remain stuck in loading state. Only some sidebar items (e.g., cron jobs) may appear.
Backend APIs intermittently hang/time out even when the web process is “running.”
Symptoms observed
/workspace renders shell, but “Enter app” / main app usage hangs.
Intermittent or frequent API timeouts:
/api/sessions
/api/skills
/api/chat/active
/api/workspace/* (e.g. context/tree/watch)
next-server process often runs high CPU and becomes non-responsive.
Multiple sessions showed:
HTTP 000 + curl timeout (12s/20s/90s)
UI still visible while backend is unresponsive.
Reproduction (from clean-ish start)
Build/start web:
cd /home/node/.openclaw/workspace/ironclaw
unset NPM_CONFIG_PREFIX
pnpm --dir apps/web build
pnpm --dir apps/web start
(also tested standalone and dev modes)
Open app (/workspace) locally or via ngrok.
UI appears, but app remains loading.
In parallel, API checks time out:
curl --max-time 12 http://127.0.0.1:3100/api/sessions
curl --max-time 12 http://127.0.0.1:3100/api/skills
curl --max-time 12 http://127.0.0.1:3100/api/chat/active
Relevant logs / observations
Frequent timeout behavior:
curl: (28) Operation timed out ... HTTP 000
High CPU stuck server:
next-server >50-100% CPU, app APIs not responding.
Inconsistent startup mode warning seen:
"next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
At times /api/profiles responds while core app endpoints hang.
What was tried
Restarting web process repeatedly
Killing stale next-server processes
Rebuilding app multiple times
Running:
standalone on 3000
dev mode on 3100
start mode on 3100
Restarting ngrok and hard-refresh/incognito
Gateway pairing/auth fixes (not root cause)
Anthropic/OpenAI auth setup verified (not root cause)
Expected
App endpoints should remain responsive after startup; UI should be fully usable, not shell-only.
Actual
UI shell often renders but backend APIs hang/time out, making app unusable.
Request
Guidance on the intended production runtime path for this repo (standalone vs next start vs dev), and investigation into API hangs/high-CPU stalls under this environment.
OpenClaw version
latest
Operating system
mac sonoma 14.7
Install method
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response