Repository navigation
Fix setup diagnostics for Codex, Qwen and DeepSeek - #73
Merged
Merged
Conversation
Pitot coding-agent E2EIntelligence Flow is the verification source; Pitot's public README carries 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 checks Codex, Qwen or DeepSeek setup with
pitot doctor --host HOST.Before: Qwen could return success without inspecting its setup, Codex could pass on a wiring witness despite missing dependencies, and the first DeepSeek failure hid other setup problems.
After: Doctor reports component diagnostics and fails for missing, disabled, malformed or unsupported setup. It distinguishes static setup, selected-runtime health and unverified live enforcement. Explicit
--fixruns diagnostics after its wiring step.Boundaries preserved
Evidence
b51e43bf48a1Failure and recovery
Diagnostics return a nonzero exit for actionable failures and unresolved supported configuration checks. Review the named component; use native
/hooksinspection for session-specific uncertainty. Reverting this PR restores the previous diagnostic behavior.Remaining limits
Static success does not prove an agent action reached a Controller. Codex normalized trust hashes, managed/cloud policy and invocation overrides require native inspection. Dynamic Qwen shell forms, per-hook environment overrides and session bootstrap behavior are not evaluated by executing them. No live model calls are used by these diagnostic tests.