tela

Documentation

Overview

tela files -- file sharing client.

Purpose:

Provides CLI access to file shares on connected machines. Requires
an active tela connect session. Communicates with the running tela
process via its control API, which proxies file share requests
through the WireGuard tunnel to telad port 17377.

Usage:

tela files ls -machine barn [path]
tela files get -machine barn <remote-path> [-o local-path]
tela files put -machine barn <local-path> [remote-name]
tela files rm -machine barn <remote-path>
tela files info -machine barn

tela -- Tela Client

Purpose:

Connects to a Tela Hub via WebSocket, performs a WireGuard key exchange
with the target daemon, and establishes an encrypted L3 tunnel.

Subcommands:
  tela connect  -- connect to a machine (ad-hoc or via profile)
  tela machines -- list registered machines and their services
  tela services -- list services on a specific machine
  tela status   -- show hub status summary

Service selection (connect):
  -ports    -- comma-separated port numbers or local:remote pairs
  -services -- comma-separated service names (resolved via hub API)
  -profile  -- load a named connection profile (multiple hubs in parallel)

Environment variables (provide defaults so flags can be omitted):
  TELA_HUB      -- hub WebSocket URL
  TELA_MACHINE  -- target machine ID
  TELA_TOKEN    -- authentication token

Network (per-session addressing):

Agent IP:  10.77.{N}.1/32   (N = session index, 1-254)
Client IP: 10.77.{N}.2/32