# mcp.exec.WaitOutcome.PresentAtEntry

- **Module:** mcp.exec.WaitOutcome
- **Package:** tmux-mcp
- **Language:** Rust
- **Kind:** constant
- **Source:** https://github.com/libtmux/libtmux-rs/blob/f0e37052c232636b61d095817046e6bfc8f2ca40/crates/tmux-mcp/src/exec.rs#L101
- **Page:** https://libtmux.org/en/rs/latest/mcp/reference/mcp-exec-waitoutcome-presentatentry/

A wanted pattern was already in the pane's output before this began watching, on a row above the one still being typed into, and is not a line this server itself submitted moments earlier.

A wait only sees what a pane writes after it starts, so this is never
folded into [`Self::Matched`]: the same pattern printed moments
earlier -- an earlier command's own output, say -- can already be
sitting there, and a caller that treated that as a fresh match would
act on something that happened before this call, not because of it.
A line this server typed and submitted with `send_keys` is discounted
rather than reported here or as [`Self::Matched`], for a short time
after it was submitted.