---
name: vnc-purpose
description: "VNC on shadow exists to keep persistent browser login sessions for X (Twitter) and NotebookLM, not for general desktop use"
metadata:
node_type: memory
type: project
originSessionId: 71d40fa2-b151-4c81-9821-f0dfeb7a0f66
---

The VNC server (`vncserver@1`, `Xtigervnc :1`, xfce4 desktop, novnc on
tailscale `100.115.94.5:6080`) on shadow is used specifically to **keep
real browser sessions logged into services where headless automation
loses cookies / 2FA quickly** — primarily X (Twitter) and NotebookLM.

**Why:** The auto-learning crons (`idle-learn.sh yt`, `idle-learn.sh x`,
both currently `TEMP_DISABLED_CLAUDE_TOKEN_STOP`) presume an
already-authenticated browser they can drive. VNC + a sticky xfce4
browser session is the cheapest way to keep those credentials warm.

**How to apply:**
- Do not stop `vncserver@1`, `novnc`, `websockify`, `Xtigervnc`, or the
xfce4 panel/systray on this host.
- `lightdm` and `unity-greeter` were stopped+disabled 2026-05-15 — they
are the GUI *console* login (tty7), separate from VNC, and unused on
a server. If something seems to want them back, check with the user
before re-enabling.
- If user says "the browser is logged out / X session expired," they
are talking about this VNC desktop, not anything headless.