Repository navigation
Fill gaps from assistant conversations: Windows setup for Venice CLI - #568
Open
mintlify[bot] wants to merge 2 commits into
Open
mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This branch was successfully deployed
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.
Summary
Adds Windows guidance to the Venice CLI guide in English and all 8 translated versions. Assistant conversations showed that Windows users could not run the CLI after installing it globally.
Changes
$env:VENICE_API_KEY) next to the existing bashexportexample.venicecommand not found" troubleshooting section that covers npm's global binPATHand thenpxfallback.Context
Other buckets were not changed. Their answers either can't be verified from the repo (408 errors, dashboard plan credits, mobile apps, Goose) or are already covered by the docs. The SEO check and broken-link check found no issues.