When MCP tools return multiple content blocks (e.g., text + images),
the content was incorrectly split outside the FunctionResponse,
causing it to leak into separate user messages.
This fix ensures all content stays inside the FunctionResponse:
- Text parts are joined into response.output
- Media parts (inlineData/fileData) are placed in response.parts
Fixes#1520
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
- Change tool name format from 'toolName' to 'mcp__serverName__toolName'
- Prevents naming conflicts when multiple MCP servers have tools with same name
- Update tests to reflect new naming convention
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
- Automatically detect 'http' transport when commandOrUrl starts with http:// or https://
- Default to 'stdio' transport for non-URL commands
- Explicit --transport flag still takes precedence over auto-detection
- Update help text to indicate auto-detection capability
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Update the header info panel hint from '/auth to change' to '/model to change'
to better reflect that this command switches models rather than authentication.
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Add support for defining environment variables in settings.json files.
These variables are loaded with the lowest priority:
1. System/process environment variables (highest)
2. .env files
3. settings.env (lowest/fallback)
This allows users to configure default environment variables in their
user or workspace settings without conflicting with existing env vars
or .env file values.
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Remove duplicate useEffect that was causing suggestions visibility state
to diverge from the actual active completion. The original useEffect at
line 760 already correctly tracks activeCompletion.showSuggestions, which
dynamically selects the current active completion source (regular, reverse
search, or command search).
The removed useEffect used OR logic across all three completion sources,
which caused hasSuggestionsVisible in AppContainer to flip incorrectly
during command-search mode when background completion state changed.
This fix ensures Tab key blocking/unblocking happens at the correct times
on Windows.
- Add getNextPatchVersion() to calculate next patch version from npm latest
- Fix getNightlyVersion() to use npm latest + 1 patch instead of package.json
- Fix getPreviewVersion() to use npm latest + 1 patch instead of nightly version
- Add version info logging in workflow for dry-run verification
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Fixes#1728
When using @ to reference files/folders on Windows and pressing Tab for path completion, the Tab key was incorrectly triggering approval mode cycling instead of accepting the autocomplete suggestion.
This happened because Windows maps Tab to Shift+Tab functionality (due to Shift+Tab not working in some terminals), but this mapping didn't account for active autocomplete lists where Tab should be used for selection.
Changes:
- Add shouldBlockTab callback to useAutoAcceptIndicator hook to check if autocomplete is active
- Track autocomplete visibility state in AppContainer via hasSuggestionsVisible
- Add onSuggestionsVisibilityChange to UIActions interface
- Update InputPrompt to notify parent when suggestions visibility changes
- Update Composer to propagate suggestions visibility to AppContainer
- Add tests to verify Tab key behavior with and without autocomplete
Change all diagnostic/progress messages in sandbox.ts from
writeStdoutLine to writeStderrLine. This prevents integration
test failures in Docker where stdout buffering behavior differs
from the Console API.
Diagnostic messages like 'Checking for sandbox image' are
informational logs that should not interfere with program output
that tests or other tools may parse from stdout.
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
Fix the build order in build_sandbox.js to match build.js.
Previously used 'npm run build --workspaces' which doesn't respect
dependency order, causing vscode-ide-companion to fail when looking
for @qwen-code/webui types that weren't built yet.
Now builds packages in correct order:
1. test-utils
2. core
3. cli
4. webui (dependency for vscode-ide-companion)
5. sdk-typescript
6. vscode-ide-companion
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
- Remove dist/ directory requirement from workflow (CLI files are in package root)
- Update bundle-cli-from-npm.js to use package root directly instead of package/dist
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
- Fix SC2086: double quote variables to prevent globbing and word splitting
- Fix yamllint quoted-strings: wrap if conditions with double quotes
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
