CLI to authenticate with Tero, manage API keys, and send messages to agents.
curl— used by the install command andinstall.shto download the CLI binary
Create a GitLab personal access token with access to this repository and these scopes:
read_repository— fetchinstall.shfrom the repositoryread_api— download CLI binaries from the GitLab package registry
Export it as GITLAB_TOKEN before running the install command.
GITLAB_TOKEN=glpat-xxx curl -fsSL -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"https://gitlab.abstracta.us/api/v4/projects/350/repository/files/src%2Fcli%2Finstall.sh/raw?ref=master" | bashSet TERO_VERSION to install a specific release (e.g. 0.1.0) or the latest master build (dev):
GITLAB_TOKEN=glpat-xxx curl -fsSL -H "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"https://gitlab.abstracta.us/api/v4/projects/350/repository/files/src%2Fcli%2Finstall.sh/raw?ref=master" | TERO_VERSION=dev bashAdd GITLAB_TOKEN as a secret/variable in your pipeline and run:
script:
- curl -fsSL -H "PRIVATE-TOKEN: $GITLAB_TOKEN" "https://gitlab.abstracta.us/api/v4/projects/350/repository/files/src%2Fcli%2Finstall.sh/raw?ref=master" | bash
- tero --versionInteractive browser login:
tero login --url "https://tero.abstracta.us"Stores the URL and token in ~/.tero/config.json.
tero create-api-key --name "ci-key"Save the printed apiKey value and use it as TERO_API_KEY.
tero ask --agent-id 23 --message "Hello, help me with this issue"Save the reply to a file using --output <path>:
tero ask --agent-id 23 --message "Summarize the release" --output ~/reports/report.md
tero ask --agent-id 23 --message "Summarize the release" --output ~/reports/report.htmlIf the path ends in .html, the output is rendered as a self-contained HTML with code highlighting, tables, echarts, and bare @startuml diagrams (fenced plantuml blocks stay as code). Any other extension saves raw markdown. Intermediate directories are created automatically.
TERO_URL: Tero base URL (used when no URL is saved from login).TERO_API_KEY: API key value returned bycreate-api-key.