Installation help — start here #4
Unanswered
DivyamTalwar
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
If an install did not go the way the README said it would, open a reply here rather than an issue — installation problems are almost always environment, not a defect, and they are faster to resolve in conversation.
Run the smoke test first and paste its output. All four commands are offline; none of them calls a model or spends a token.
Also include:
codex --versionand/orclaude --version, if they are installed at allThings that are expected, not bugs
verify.shreports a different number than the docs. The count moves with your environment; the verdict does not. 154 is the floor on a machine with neither CLI installed, which is what CI asserts. With the Claude CLI onPATHan optional manifest validator also runs and you get 155.preflightsays nothing is installed on a clean machine. That is the correct answer.preflightdiagnoses an install; it does not create one. Runsetupfirst.claude plugin detailsreportsAgents (0). Both agents do load. The inventory counter walks the defaultagents/directory and misses manifest-declared paths, which is this layout.The
flashandglmlanes will not resolve out of the box. They need a provider that speaks the OpenAI Responses API, pinned with onemodel_providerline in the lane profile. Until one is configured those lanes are unavailable — and an unavailable lane is a blocker to report, never a reason to silently route its work elsewhere.A refused run (exit 69) may still have changed your files. Routing is proven after a lane runs. If the lane had a write-capable sandbox, inspect or discard the workspace changes before continuing. The refusal is a stop signal, not a rollback.
All reactions