Scripts and the secure terminal

Chronos gives you two safe ways to run commands in a session — predefined scripts and a secure terminal. Both run in the session’s isolated environment, and both are recorded.

Predefined scripts

Scripts are named commands your project defines — such as setup, run, or your verification steps. Because they are part of your project’s settings, your team decides what each one does and reviews changes to them. You trigger them by name; there is no free-form command running behind a button.

Common scripts:

Script	Purpose
setup	Prepare the session (install dependencies, etc.)
run	Start the app
verify / qa	Your checks — shown in the Checks tab

Run them:

chronos session run <id> setup
chronos session run <id> run

In the dashboard, the Setup and Run tabs trigger the matching script and show its output.

When you start an app with run, Chronos gives each session its own port, so parallel sessions never collide.

The secure terminal

The session terminal runs inside the session’s isolated environment and records every command. Type a command and press Enter; output streams back.

chronos session term <id> "ls -la"

Approval for sensitive actions

Anything potentially destructive — deleting large amounts of data, force-pushing, installing software from the network — requires approval before it runs. In the dashboard the command is flagged as “approval required”; someone with the right permission can then approve it. Nothing with serious side effects happens silently.

Why it works this way

• No surprises — everything runnable is either a reviewed script or an approved, recorded command.
• Reproducible — scripts live with your project, so a session behaves the same for everyone.
• Isolated — commands only affect the session, never your wider system.

Next, see Pull requests, approvals, and merge.