Admin features
tealc admin inspects server configuration and state or changes the runtime log level. It is intended for administrators and is rarely needed during a normal operator session.
Prerequisites
Configure the server URL and admin token in the client, and ensure the operator’s source IP is permitted by the server’s allowed-ips setting. See Client authentication and Access control.
Quick reference
| Command | Result |
|---|---|
tealc admin config | Sanitized running server configuration |
tealc admin dump | Detailed connected-agent information |
tealc admin state | Full server state |
tealc admin log-level LEVEL | Change the server’s runtime log level |
Add --json to config, dump, or state for machine-readable output.
Inspect the running configuration
tealc admin config
Representative output:
age-private-key: '[REDACTED]'
http-domain:
- goauld.example.com
sshd-listen-addr: 0.0.0.0:2222
tls: true
allowed-ips:
- 203.0.113.10/32
access-token:
- '[REDACTED]'
admin-token:
- '[REDACTED]'
The response contains the complete resolved server configuration. Consult the generated server configuration for the complete field reference.
Inspect connected agents
tealc admin dump
Representative output:
- id: 1ec1bd83de498e7da8852efe6d8c16c5
name: user@host
SSHMode: WS
lastUpdated: 2026-03-09T17:31:43Z
lastPing: 2026-03-09T17:32:22Z
platform: darwin
architecture: arm64
remoteAddr: 203.0.113.20
socketIO:
connected: true
ssh:
SSHListeners:
- 127.0.0.1:56749
Actual output can include transport internals, addresses, paths, identifiers, and active SSH connection information.
Change the server log level
tealc admin log-level debug
The level is required, for example debug, info, warn, or error. The change applies to the running server process and does not rewrite its configuration file.
Inspect full server state
tealc admin state
This combines the running configuration with current agent state. Use tealc admin state --json when another tool must process the result.
Security and output handling
The server sanitizes known credentials in configuration output, but state and agent dumps can still reveal hostnames, usernames, addresses, paths, ports, and connection metadata. Store or share this output as sensitive operational data and review it before attaching it to an issue.