Repository navigation
[term] Warning Log Messed Up the TUI #2120
Description
Agent Diagnostic
Description
Hey team, I ran into a TUI layout glitch while debugging a sandbox issue with openshell term. I initially spun up a sandbox before installing any agents, which caused the build to fail. After installing opencode and returning to inspect that failed sandbox, the TUI completely broke/messed up.
$ opencode --version
1.17.13
$ openshell sandbox list
NAME CREATED PHASE
legendary-waxwing 2026-07-02 08:34:19 Error
ravishing-salmon 2026-07-02 08:58:41 Ready
maximal-margay 2026-07-02 08:59:11 Ready
Reproduction Steps
Step to reproduce the error:
- Use
openshell term, tap to the error sandbox - The warning log start popping out in wrong location of TUI
Environment
OS: Red Hat Enterprise Linux release 10.2 (Coughlan)
Version: openshell 0.0.74
podman version 5.8.2
Logs
$ podman ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
56890825c8c6 ghcr.io/nvidia/openshell-community/sandboxes/base:latest About an hour ago Exited (1) About an hour ago (starting) 0.0.0.0:37499->2222/tcp openshell-sandbox-legendary-waxwing
8ea19e49d781 ghcr.io/nvidia/openshell-community/sandboxes/base:latest 44 minutes ago Up 43 minutes (healthy) 0.0.0.0:43053->2222/tcp openshell-sandbox-ravishing-salmon
3110bbf701a8 ghcr.io/nvidia/openshell-community/sandboxes/base:latest 43 minutes ago Up 43 minutes (healthy) 0.0.0.0:40477->2222/tcp openshell-sandbox-maximal-margay
$ podman logs 56890825c8c6
openshell: log push RPC failed: code: 'Some requested entity was not found', message: "sandbox not found"
openshell: log push stream lost, reconnecting after backoff...
2026-07-02T08:34:19.326Z WARN openshell_sandbox: Policy fetch failed, retrying
openshell: log push reconnected (attempt 2)
2026-07-02T08:34:20.370Z WARN openshell_sandbox: Policy fetch failed, retrying
2026-07-02T08:34:22.375Z WARN openshell_sandbox: Policy fetch failed, retrying
2026-07-02T08:34:26.379Z WARN openshell_sandbox: Policy fetch failed, retrying
Error: × Policy fetch failed after 5 attempts: code: 'Internal error', message:
│ "sandbox has no spec"
Agent-First Checklist
- I pointed my agent at the repo and had it investigate this issue
- I loaded relevant skills (e.g.,
debug-openshell-cluster,debug-inference,openshell-cli) - My agent could not resolve this — the diagnostic above explains why
Activity
r3v5 commentedon Jul 6, 2026
Hey @dichn ! I am working on the fix.
fix(tui): route warning logs to status bar instead of stderr (#2210)
Chore/resync 20260820 (#4)