First public script · Terminal Runtime Systems · v2.1
TRS Infinity is building a line of terminal scripts — this is the first one to ship publicly. It checks the client sites you are responsible for and reports status, response code and latency straight to your shell. Pair Telegram if you also want those failures to reach you away from the desk. No dashboard to log into, no subscription, no browser tab you forget to open.
$ ./trs.sh sites check [trs] checking 4 sites… ● client-shop.com 200 142ms ● api.startup.io 200 89ms ● docs.acme.dev 200 203ms ● old-landing.net 503 → alert sent [trs] 3 healthy · 1 failing · 0.4s
Your site list stays on your machine in a plain config file.
Works entirely from the shell; pair a device only if you want alerts.
Status, response code and latency in a single terminal line.
Every command works unattended in cron or CI pipelines.
01 Overview
The first TRS script — a bash toolkit you run yourself, on the machine you already work from. Many more tools are planned under the same brand.
Terminal Runtime Systems is not a single product — it is a growing library of scripts for people who work from the shell. The uptime monitor is the first release; others are already in development and will ship on their own schedules.
This script watches the sites you are responsible for. You run it locally, point it at the URLs you care about, and it takes over the part of the job nobody enjoys — remembering to check.
It was written for a specific situation: you already live in the terminal, you look after somewhere between five and twenty client sites, and adding another SaaS dashboard to your morning routine is not a solution. TRS stays quiet until something actually breaks.
Most of the people running it are freelance developers with a portfolio of client work, small studios with no dedicated operations team, and sysadmins who would rather stay in a shell than open a web console. A good number of them arrived after hearing about an outage from the client before hearing it from their own tooling.
When a check fails — a 5xx response, a timeout, an unexpected redirect — the failure is printed in the terminal with the URL, the status code and the time. If you have paired Telegram, the same line arrives there too. Nothing else competes for your attention.
Two additional modules ship with the same entry point. Domain Intel produces a reconnaissance report before you take on a new project: stack detection, DNS and certificate details, subdomains, archive history. Security Audit performs read-only probing for common misconfigurations on infrastructure you are authorised to test.
About the company
Two years in, TRS Infinity is starting from a clean slate.
The company was founded in 2024 by four engineers who were, between them, looking after close to eighty client sites. The checker began as a private script passed around that team, and for two years it stayed that way — run internally, extended whenever something broke, shared with a short list of clients and nobody else.
The reset was deliberate. Rather than keep extending a codebase shaped by four people's habits, the team rewrote the tooling around a single entry point, took a new name — TRS Infinity, where TRS stands for Terminal Runtime Systems — and prepared it for public release. The uptime monitor going live on 5 August is only the first script; the roadmap already lists many more. The version number carries on from the internal line; the code underneath does not.
There is no central office. Development happens in the open: releases are cut roughly every two weeks, each one with a full changelog, and a small security research group maintains the audit module's check list and reviews every new probe before it goes out.
02 Capabilities
The first TRS release is one entry point with four modules. Future scripts will ship
separately. Append help to any command for its full reference.
Register one URL or a hundred. TRS records HTTP status, availability and response time
on each pass. Run a one-off sweep with sites check, or leave
sites watch running in the background at whatever interval suits the project.
Sites can carry a label, so alerts read Client: Acme rather than a bare hostname. Bulk import from a text file is supported.
Every monitoring command works without it — this is purely for the times you are not
watching the terminal. Pairing takes one command: telegram setup prints a
code, you send it to @TRSinfinity_bot, and the device is linked. Each machine gets its
own code, so a laptop and a VPS can report independently.
Alerts fire on failure only. A healthy sweep produces no notification at all.
A single report covering CMS and framework fingerprints, CDN and analytics, nameservers, MX and SPF/DMARC records, certificate details, security headers, discovered subdomains, Wayback Machine history and WHOIS data.
Useful before quoting on inherited infrastructure. Reports are written to
data/reports/ for later reference.
Read-only checks for exposed .env and .git paths, forgotten
backups and admin endpoints, missing HSTS or CSP, permissive CORS, weak SPF and DMARC,
and stack traces leaking on 404 pages.
No exploitation, no brute force, no traffic floods. Intended for your own systems or clients who have given written permission.
03 Install
This is the first public TRS script. It needs bash, curl and Python 3 — all present on a standard macOS or Linux install. The first three steps are the whole product; the fourth is opt-in.
Copy or clone the folder, then make the entry point executable.
cd ~/Desktop/trs-company
chmod +x trs.sh
Register the URLs you want checked. Labels are optional.
./trs.sh sites add example.com
Results print to the terminal on every pass. That is monitoring done.
./trs.sh sites watch
Only if you want failures to reach you away from the terminal.
./trs.sh telegram setup
Terminal Runtime Systems · v2.1
The complete command list for all four modules, the Telegram pairing flow, where the config and report files are written, and what to do when a watch loop stops responding to input.