sb Command¶
The sb command is a pure client tool for managing existing clients and terminals. It doesn't spawn any processes itself—it only connects to existing terminals.
Usage¶
Commands¶
sb attach (alias: a)¶
Attach to an existing terminal:
Flags:
--id <id>: Terminal ID (mutually exclusive with--name)--name <name>: Terminal name (mutually exclusive with--id)--socket <file>: Socket file path
sb detach¶
Detach from a client:
sb get¶
Query terminals, clients, and profiles:
# List terminals
sb get terminals
# List clients
sb get clients
# List profiles
sb get profiles
# Get specific terminal
sb get terminal <name-or-id>
# Get specific client
sb get clients <name-or-id>
# Get specific profile
sb get profile <name>
Flags:
-a, --all: Show all terminals/clients including exited ones-o, --output <format>: Output format (json, yaml, or human-readable)
sb prune¶
Prune stale clients and terminals:
A stale client is one that is no longer running. A stale terminal is one whose client is no longer running.
sb version¶
Show version information:
sb autocomplete¶
Generate shell completion:
Persistent Flags¶
These flags apply to all sb commands:
--config <file>: Config file (default:$HOME/.sbsh/config.yaml). See the Configuration guide for theConfigurationdocument schema.-v, --verbose: Enable verbose logging--log-level <level>: Log level (debug, info, warn, error)--run-path <path>: Run path directory
Examples¶
List Active Terminals¶
Attach to Terminal by Name¶
Attach to Terminal by ID¶
List All Terminals (Including Exited)¶
Get Terminal Details (JSON)¶
Get Profile Details¶
Prune Stale Terminals¶
Prune Stale Clients¶
Output Formats¶
Human-Readable (Default)¶
JSON¶
YAML¶
See Also¶
- sbsh Command - Interactive client + terminal
- Commands Overview - Command comparison
- Getting Started - Basic usage