# libtmux::Client

- **Module:** libtmux
- **Package:** libtmux-cxx
- **Language:** C++
- **Kind:** class
- **Source:** https://github.com/libtmux/libtmux-cxx/blob/393d4b0ad666f18a6581f1eb281741a75a7503f0/include/libtmux/entities.hpp#L982
- **Page:** https://libtmux.org/en/cxx/latest/reference/libtmux-client/

One attached client, as one listing saw it.

The shortest-lived of these: a client goes away with its terminal, so a handle outlives what it names more often than the others do. It is named by its tty rather than by an id tmux issues.

## Members

- `kNoun` (attribute)
- `kFields` (attribute)
- `Client` (method)
- `name` (method): A client is named by its terminal path, which is the only stable handle tmux gives; there is no client id format.
- `session_name` (method)
- `read_only` (method)
- `tty` (method)
- `width` (method)
- `height` (method)
- `created` (method)
- `last_activity` (method)
- `terminal` (method)
- `control_mode` (method): A control-mode client is a program driving tmux, not a terminal.
- `session` (method)
- `switch_to` (method): Point this client at another session, leaving it attached.
- `detach` (method)
- `refresh` (method): Redraw, and tell tmux the size this client is now, which matters for a control-mode client whose size tmux cannot otherwise observe.