Repository navigation
Simplify the docs and stabilize Qwen replay output - #79
Merged
Merged
Conversation
Pitot coding-agent E2EThese results come from this repository's CI at the commit shown below; the README links to the latest
Runtime capabilities
Source commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change contract
When: A developer starts using Pitot or looks up host setup and control boundaries.
Before: The README combines a long setup reference with images, and some examples overstate runtime telemetry or omit source-build pin limits. The Qwen CI fixture can select a pipe-output path that resolves before all output is collected.
After: A short, plain README links dedicated host, runtime and protocol references, prioritizes Codex, Qwen and DeepSeek, and introduces the offline supervisory-control example. The Qwen test fixture uses its supported terminal mode and rejects pipe fallback before its canary executes.
Boundaries preserved
Evidence
Failure and recovery
A missing terminal or incomplete agent trajectory still fails CI. Revert fixture changes and regenerate their authenticated capture together if recovery is needed.
Remaining limits
The earlier Linux failure's exact process event ordering was not retained. A synthetic event sequence demonstrates the pipe-output loss mechanism; local native probes did not reproduce that original failure. Finite replay tests do not establish universal host behavior or live provider availability. The supervisory replay example remains documented for macOS/Linux.