Telesis CLI setup and checks

Build the CLI

Build from the repository to use the new monitoring commands. Put the resulting binary on PATH, then inspect available runtimes.

git clone https://github.com/skunkworq/uptime.git
cd uptime
mkdir -p bin
(cd cmd/cli && go build -o ../../bin/telesis .)
export PATH="$PWD/bin:$PATH"
telesis doctor --output=json

Run a local check

Local HTTP, security, and technology checks do not need Telesis sign-in. Playwright needs Docker and a sandbox image. Inference needs provider credentials and a configured model.

• --type=all runs uptime, security, and technology detection. It does not run browser scripts or paid inference automatically.
• --output supports table, json, and yaml. Structured results contain an explicit status; inspect it when automating uptime checks.
• Failed Playwright checks and security threshold violations return a nonzero CLI exit code.

telesis check https://example.com --type=uptime --mode=local --output=json
telesis check https://example.com --type=security --scan-depth=deep --fail-on=high --timeout=60s

Choose the cloud organization

Sign in through the browser, list memberships, and pass the organization ID. Accounts with multiple organizations must select one explicitly. Local inference credentials are separate from Telesis sign-in.

telesis auth login
telesis auth status
telesis organization list --output=json
telesis service list --org-id=YOUR_ORGANIZATION_ID --output=json

Manage saved scripts and results

Use the monitor commands to inspect and update a saved Playwright check or read its persisted history. These commands return JSON and require cloud sign-in. Add --save-to-check=CHECK_ID to a local Playwright check to upload outcomes and recordings. Use monitor upload to retry an exported report without rerunning it. Artifact downloads require the same organization access as the result.

telesis monitor get CHECK_ID
telesis monitor update-script CHECK_ID smoke.spec.ts
telesis monitor results CHECK_ID --limit=20
telesis monitor result RESULT_ID
telesis monitor artifact RESULT_ID ARTIFACT_ID --output-dir=./downloads
telesis monitor upload CHECK_ID ./private-reports/run-EXAMPLE/result.json

Understand setup diagnostics

doctor reports Docker/image availability and whether each provider key and model are configured. It never prints key values. A ready prerequisite check is not proof that a script or provider request will succeed.

• Docker unavailable: start Docker and make the docker executable available to the CLI process.
• Sandbox image missing: build the image and set PLAYWRIGHT_SANDBOX_IMAGE to its tag.
• Inference not ready: configure TELESIS_LLM_<PROVIDER>_API_KEY and TELESIS_LLM_<PROVIDER>_MODEL in the executing process.
• Expired cloud sign-in: run telesis auth login again.