-
Notifications
You must be signed in to change notification settings - Fork 2.4k
feat: add support for 'cu' command in extension installation #3261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Add 'cu' to allowedCommands list in deeplink validation - Include 'cu' in shimPatterns for path resolution - Add 'cu' to binaryPathMap in both utils.ts and extensions.tsx - Fixes error: 'Invalid command: cu. Only docker, jbang, npx, uvx, goosed are allowed' This enables extensions using the 'cu' command to be installed via deeplinks in the Desktop application.
|
also @Kvadratni carine b on discord mentioned that on windows she's getting issues installing a few extensions. She believe it's because we need to add |
michaelneale
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, nailed it @blackgirlbytes - this is really a safety measure so it is fine to add this.
|
@michaelneale I actually think I caused a bug 😓 #3286 |
* update-to-v1.0.35: (57 commits) chore(release): release version 1.0.35 (block#3292) docs: enhanced code editing topic (block#3287) fix cu (block#3291) feat: Add environment variables to override model context limits (block#3260) chore(release): release version 1.0.34 (block#3285) fix(devcontainer): install protoc to fix build (block#3267) Enabling npx command to install on Windows Desktop (block#3283) Fix: Allow native Cmd+Up/Down cursor movement when user has typed text (block#3246) chore(release): release version 1.0.33 (block#3284) fix Windows Env Vars (block#3282) feat: bedrock image content support (block#3266) Add support in goose configure for streaming http mcp tools (block#3256) docs: add Alby MCP tutorial (block#3217) refactor(tests): make logging test in goose-cli less flaky on macos (block#3273) feat: cli can work with gui generated recipes (block#3254) Goose projects docs (block#3272) feat: add support for 'cu' command in extension installation (block#3261) Docs: Add cloudinary mcp tutorial (block#3268) fix: Enable agent to see instruction to use final output tool when it wasn't called (block#3253) Use command line to run sub agent and sub recipe (in sequence or parallel) (block#3190) ...
) Signed-off-by: Adam Tarantino <[email protected]>
) Signed-off-by: Soroosh <[email protected]>
) Signed-off-by: Kyle Santiago <[email protected]>
Container Use (cu) is featured in our content and Dagger's documentation:
However, when users try to install cu-based extensions via the documented deeplinks, they encounter this error:
Failed to install extension: Invalid command: cu. Only docker, jbang, npx, uvx, goosed are allowed.This PR solves that by adding :