Halon's terminal and browser

Halon now has a sandbox of its own, with a terminal and a real browser, in chats and in investigations. It starts the first time Halon needs it.

Terminal. Halon runs shell commands and scripts when one tool call is not enough, such as counting the errors in a large log or grouping a hundred CI runs by the test that failed. Scripts can call your connected tools through Firefight, as the person who asked, and kubectl and the Northflank command line work against your connections. Each command shows as a Run command step. See Halon's terminal.

Checks from outside. Halon can check an address the way a user reaches it, with its DNS records, how long each part of the request took, and its certificate and how many days are left on it.

Browser. For questions about what people see, such as "the checkout button does nothing", Halon opens the page in Chromium on a desktop and a phone screen, follows the steps a person would take, and reports the status, timings, console errors, failed requests and a screenshot. For pages behind a login, an admin saves a test account on the Test logins page under Halon. See Halon's browser.

Your keys stay out, changes ask first. The sandbox holds no key, token or password of yours, since every call goes through Firefight, which adds the key itself and records the call. A command that changes something asks you first. In the browser, looking around never asks, and a step that would send data, such as submitting a form, stops and shows you exactly what it would send before anything leaves.