Repository navigation
docs(cli): add PowerShell curl examples for Windows users - #10
Open
terminalchai wants to merge 2 commits into
Open
terminalchai wants to merge 2 commits into
terminalchai wants to merge 2 commits into
Conversation
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.
What does this PR do?
Adds Windows PowerShell guidance to the CLI reference.
curl.exeand a UTF-8 file body avoid thecurlalias and native-command JSON quoting differences in Windows PowerShell 5.1 and PowerShell 7.The local example uses the development server's mock
/runendpoint. The deployed example uses the current authenticated/api/agents/:namespace/:name/runendpoint and explains its token, input-schema and model-key requirements. Current main has been merged, preserving its expanded CLI documentation.Validation: both exact documentation snippets were parsed and executed against a local HTTP capture fixture under Windows PowerShell 5.1 and PowerShell 7.6.5. The checks verified request paths, deployed Bearer authentication, nested JSON input, and non-ASCII UTF-8 bytes without a BOM. No live registry was called.
Checklist
pnpm buildpassespnpm test(not rerun for documentation-only changes)pnpm lint(the Windows checkout has existing CRLF formatting failures; checks with formatting disabled pass)Prepared with AI assistance and independently reviewed.