# LibTmux.Mcp.WaitOutcome.PresentAtEntry

- **Module:** LibTmux.Mcp.WaitOutcome
- **Package:** LibTmux.Mcp
- **Language:** .NET
- **Kind:** constant
- **Source:** https://github.com/libtmux/libtmux-dotnet/blob/320dc64f4b8b7815842471327a5e6b84a1499bf8/src/LibTmux.Mcp/Results/Observations.cs#L88
- **Page:** https://libtmux.org/en/dotnet/latest/mcp/reference/libtmux-mcp-waitoutcome-presentatentry/

A wanted pattern was already on screen when the wait began, and nothing new arrived before time ran out.

This is what a plain <see cref="Timeout" /> would otherwise report
here, with the returned tail visibly containing the very text the
wait says it never found: only output arriving after the call counts
as new, by design, so calling this right after the command that
produced the text - the first thing most callers try - would time out
holding a tail that contradicts it. <see cref="WaitResult.MatchedPattern" />
names what was already there.