docs(mobile): fix kilo run argument order in workflow launch command#4601
Open
iscekic wants to merge 1 commit into
Open
docs(mobile): fix kilo run argument order in workflow launch command#4601iscekic wants to merge 1 commit into
iscekic wants to merge 1 commit into
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryDocumentation-only reordering of the Files Reviewed (1 files)
Reviewed by claude-sonnet-5 · Input: 20 · Output: 3.2K · Cached: 354.6K Review guidance: REVIEW.md from base branch |
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.
The orchestrator launch example in
MOBILE_WORKFLOW.mdpasses--file <handoff> "<message>".kilo run --fileis an array option, so it consumes the trailing message positional as a second file path and the command exits withFile not found: <message>(reproduced on kilo 7.4.9). Moving the message positional before the flags makes the documented command work as written; a note explains why the order matters.