mcp.exec.RunOutcome
Rust
- Python Unavailable
- Ruby Unavailable
- Lua Unavailable
- TypeScript Unavailable
- Rust
- Go Unavailable
- Java Unavailable
- .NET Unavailable
- C++ Unavailable
- Swift Unavailable
-
How a run finished.
Split from the wait outcomes rather than shared with them: a run cannot match a pattern and a wait cannot report a missing shell, and a vocabulary carrying both would have an agent checking for answers that never come.
Members
-
The command ran to completion and reported its status.
-
The time the caller allowed ran out.
This ends the waiting, not the command. The pane stays reserved for it until it ends, so other pane input is refused;
send_keyswith keys["C-c"]alone interrupts it.
-
The pane stopped writing for good.
-
The client withdrew the request while the run was still going.
-
The pane never acknowledged the command.
The keys were sent but the opening sentinel never came back. That is what a pane looks like when it is not at a shell prompt: sitting in an editor or a REPL, or still running something an earlier call left behind. The text was typed into whatever is there.
The evidence is absence, so a deadline too short for the pane's shell to have echoed anything yet looks the same. Read it as "nothing came back in the time allowed" and check the pane with
snapshot_panebefore concluding it is stuck.