Right now we emit a message like

T: Error: Unable to find cluster information
T: No current-context set. Please use the --context option to 
T: explicitly set the context.

This is all fine, but some higher-level explanation would be helpful as well, probably linking to documentation:

T: Telepresence uses kubectl/oc to access your Kubernetes/OpenShift
T: cluster. Ple

I think it would be good to describe/list the capture technologies Wireguard is using for each platform. e.g. Windows it using wintun.net driver, Linux it is using /dev/tun etc.

Likely an advanced topic.

It would be nice to have an example standard non-Docker systemd script, for the benefit of those running this outside a container.

Would be nice to have a "Clear Logs" button on the dashboard.
Great tool by the way, very useful.