VNC access

tektona vnc connects to the desktop running inside a sandbox. The CLI brokers the connection through a local WebSocket proxy, so you don't need to expose ports or know the sandbox's IP.

Connect

tektona vnc <sandbox-id>

The default client (--type web) opens a browser tab pointed at a locally proxied noVNC viewer. Close the tab to disconnect.

Several sandboxes at once

Pass multiple IDs, or --all to connect to every running sandbox in the current context (capped at 20):

tektona vnc <id-1> <id-2> <id-3>
tektona vnc --all
tektona vnc --all --browser           # auto-open each tab

Start the desktop on demand

Sandboxes don't always have the desktop running. Start it as part of the connect step:

tektona vnc <sandbox-id> --start-desktop

Or manage the desktop directly:

tektona sandbox desktop start <sandbox-id>
tektona sandbox desktop stop <sandbox-id>
tektona sandbox desktop status <sandbox-id>            # active or inactive

sandbox desktop start needs an image that ships a desktop: the official desktop-x11 image, an image built from it, or your own image with a session script. It errors on any other image. tektona vnc itself needs no desktop image — it shows the text console when no desktop runs.

Combine with sandbox create

Create a sandbox and open a VNC session in one step:

tektona sandbox create tektona/desktop --egress-policy tektona/open --vnc --browser

Flags