# Topics

Source: https://libtmux.org/en/kotlin/latest/topics/

> Reason about coroutine execution, resource ownership, and bounded observation.

Kotlin handles combine local captured properties with suspending operations that
contact tmux. These topics explain the boundary, including the Java client
underneath the wrapper and the lifetime of each collected flow.

Start with the [object model](https://libtmux.org/en/kotlin/latest/concepts/server-session-window-pane/) and
[complete examples](https://libtmux.org/en/kotlin/latest/examples/) for runnable programs. Use these topics to
choose cancellation, concurrency, and recovery behavior for a larger application.

- [Client ownership and captured state](https://libtmux.org/en/kotlin/latest/topics/ownership/): Keep borrowed daemons and owned Kotlin client scopes distinct.
- [Coroutines and command execution](https://libtmux.org/en/kotlin/latest/topics/execution/): Understand suspend calls, admission bounds, and cancellation after dispatch.
- [Flows and event loss](https://libtmux.org/en/kotlin/latest/topics/observations/): Collect within the client scope and handle gaps without assuming replay.