Venice plans, writes, runs and fixes code on its own. It is on when Venice is picked in Code settings. Venice is called directly (not through the VPN lane); the code runs only in the separate worker container (own VPN, kill switch, none of Jarvis's keys). It stops after a few tries, 15 minutes, or when you press Stop.
Private research and site scraping, through a VPN lane. What are we digging up?
Ultron's web traffic goes out only through this lane. If the VPN drops, he has no way out (kill switch). His chat with Claude itself is not in the lane.
Chat and pictures from Venice. Ultron's Venice chat and pictures go out only through the VPN lane above; if the lane is down, they are not made. Code (Jarvis Code and Ultron Code) uses this key too, but calls Venice directly.
The worker is its own Proxmox container, walled off from Jarvis. Do this once:
modprobe wireguard./etc/wireguard/wg0.conf (the endpoint must be an IP address).setup.sh and ultron_worker.py.http://192.168.1.50:8765), press Save, then Test run.The token below is the worker's own password. It is not a Jarvis key.