ts session

List your active sessions, and show, terminate, or diagnose one of them.

Usage

ts sessions [--csv] [--no-trunc]
ts session <id>
ts session terminate <id> [--force]
ts session diagnostics <id>

Description

A session is an application running for you on a runner: your own machine or a cloud runner. ts sessions lists the signed-in account's active sessions, most recently active first — the session id, its application, its status, the runner it runs on, and when it was created and last active, in UTC. It does not list other people's sessions; every action here works only on sessions the signed-in account owns.

A session id is accepted with or without dashes.

ts session <id> prints one of your active sessions as ts sessions lists it: its id, status, and runner, when it was created and last active, in UTC to the minute, and then each application in it with that application's status. It only reads, so the session keeps its connection. A session that has ended, another account's session, and an id no session has are all answered the same way: You have no active session <id>. Use 'ts sessions' to list sessions.

ts session diagnostics prints the session's most recent launch diagnostic events, up to 200, oldest first, as JSON: each with its sequence number, UTC timestamp, level, source, event name, and message. It is the first thing to reach for when an application behaves badly and you need evidence rather than a description.

ts session terminate ends a session. The application stops, so this prompts unless you pass --force. Reach for it when a session is stuck or consuming resources it should not.

Options

Flag	Description	Default/Values	Notes
--force, -f	Terminate without confirming.		terminate only. Required when there is no terminal.
--csv	Tab-separated output, nothing truncated.		ts sessions only.
--no-trunc	Do not truncate columns.		ts sessions only.

Examples

# What is running right now?
ts sessions

# One session, with each of its applications
ts session 4f21c8e091a44b7d8e332a6f5c1d0b88

# Collect evidence before doing anything
ts session diagnostics 4f21c8e091a44b7d8e332a6f5c1d0b88

# End a stuck session
ts session terminate 4f21c8e091a44b7d8e332a6f5c1d0b88 --force

# Anything running longer than it should be?
ts sessions --csv

Output

Session:  4f21c8e091a44b7d8e332a6f5c1d0b88
Status:   Active
Runner:   Alice's laptop
Created:  2026-10-21 09:30
Activity: 2026-10-21 09:45
  app: Notepad++ (Active)

Runner is the runner's display name, or its id when it has none. Under --format=json the session comes back in the result envelope as result.session, with each application's launch id and start time as well.

Exit Codes

0 on success. -1 when no session id is given. -4 when no account is signed in, and when diagnostics names a session that does not exist or that the account does not own. -6 when ts session <id> names no active session of yours, and when terminate names a session that does not exist or that the account does not own. Terminating a session that has already ended succeeds.

Related Commands

• ts runner — The runners sessions run on.
• ts report — Historical session data, rather than what is live.