Adopt CLI status and runtime UX fixes#627
Merged
Merged
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
1 participant
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.
Maintainer adoption of six narrow Spark CLI fixes from source PRs spark-cli#510, #504, #467, #461, #492, and #177. Scope: surface latest browser-use action receipt in status, let browser-use task parse options after normal goal text, preserve stored null values in spark config get, send a User-Agent for OpenAI-compatible provider calls, avoid first-run runtime-process false positives when no modules are expected, and keep autostart Telegram profiles in runtime verification. I did not adopt config locking, module-manifest corruption handling, installer-security, dependency, CI, auth, sandbox, or other trust-boundary changes in this batch. Verification run locally: full tests/test_browser_use_cli.py, focused new CLI regressions, full tests/test_cli.py, compileall, and git diff check. Credit and points note: do not credit this maintainer PR; evaluate source PRs #510, #504, #467, #461, #492, and #177 only if packet, account, team, duplicate, security, and scoring gates clear.