Summary
The VS Code extension connects to Tower successfully (status bar shows "Tower: connected") but does not display builder terminals in the sidebar. Builders are visible in afx status and the Tower web UI, but the extension's builder list is empty.
Environment
- Tower running on port 4100, showing active builders
afx status shows builders correctly- Tower web UI shows builders and allows interaction
- VS Code extension shows "Tower: connected" but "Tunnel: disconnected"
- Extension sidebar shows no builders
Expected Behavior
The VS Code extension should list all active builder terminals from Tower and allow interaction (attach, send message, view output).
Notes
The "Tunnel: disconnected" status may be related — if the extension relies on the tunnel for terminal streaming rather than the Tower's SSE/API endpoints, builder discovery could fail silently when the tunnel is down.
Workaround
Use Tower web UI at http://localhost:4100 to view and interact with builders.
Summary
The VS Code extension connects to Tower successfully (status bar shows "Tower: connected") but does not display builder terminals in the sidebar. Builders are visible in
afx statusand the Tower web UI, but the extension's builder list is empty.Environment
afx statusshows builders correctlyExpected Behavior
The VS Code extension should list all active builder terminals from Tower and allow interaction (attach, send message, view output).
Notes
The "Tunnel: disconnected" status may be related — if the extension relies on the tunnel for terminal streaming rather than the Tower's SSE/API endpoints, builder discovery could fail silently when the tunnel is down.
Workaround
Use Tower web UI at
http://localhost:4100to view and interact with builders.