Process and Chat

Manage the configured supervisor and run a foreground terminal session.

Supervisor lifecycle

tars start
tars status
tars logs
tars restart
tars stop

start registers the compiled supervisor with PM2 as tars-supervisor. restart first checks custom extension policies, opens the guided migration when an interactive decision is required, and then restarts active processes for the configured TARS_HOME without installing an update. Use tars update explicitly when you intend to change the package. logs follows the configured process. status reports process and active-session metrics; it does not prove that heartbeat, cron, or a particular task tick succeeded.

Use tars doctor for read-only health, security, task, extension, and brain diagnostics. Machine consumers can use tars doctor --json. tars repair plan lists applicable registered safe repairs; tars repair apply --yes applies and verifies that plan under the Tars-home mutation lease. Extension trust decisions remain in tars extensions migrate.

Use lifecycle commands from an operator shell. A running assistant should not stop its own process mid-response.

Terminal chat

tars chat --no-discord

This foreground mode starts the terminal channel without Discord, dashboard, heartbeat, cron, or other duplicate daemon services. It still uses the configured TARS_HOME, so avoid sending concurrent prompts to a running daemon. Press Ctrl+C to exit.

Updates and refresh

tars update
tars refresh
tars refresh --dashboard-only
tars refresh --extensions-only

update stages a newer npm package, runs the target release’s configuration preflight, installs it, refreshes packaged assets, and restarts processes that were active at the start. Do not stop Tars before a routine update. If a custom extension requires a policy migration, the update pauses before installation and directs you to tars extensions migrate.

refresh rebuilds packaged assets from the current installation using staged builds, atomic replacement, and rollback on failure.

Other diagnostics

tars quota
tars discord

quota reports tracked provider rate-limit information. discord prints setup instructions.

Named processes

tars start --name NAME --role ROLE can create a named PM2 process, but the convenience lifecycle and log commands are not all instance-aware. Do not point two processes at the same TARS_HOME; see Multiple Instances.