Can't import CLI generated recipes

[blackgirlbytes]

Describe the bug

If you create a recipe in yaml and then convert it to a deeplink, you can't import the deeplink. Instead you get an error that says "Failed to import recipe: Invalid deeplink or recipe format"

To Reproduce
Steps to reproduce the behavior:

1. Create a yaml recipe
2. run goose recipe deeplink [recipe-path]
3. past deeplink into import recipe box
4. Press import recipe

Expected behavior
Should import the recipe

Screenshots

Please provide following information:

• OS & Arch: Mac OS
• Interface: [UI/CLI]
• Version: 1.0.35
• Extensions enabled: Developer
• Provider & Model: Claude Sonnet 4

[DOsinga]

@jsibbison-square is this related to the thing you fixed?

[jsibbison-square]

If I remove the %3D%3D at the end of the deeplink it imports. Exploring further.

[DOsinga]

ah, I guess this goes back to @alicehau exploration about how we were not using url safe base64 encoding and then instead url-encoded the results and so then = for padding as base64 does then becomes %3D and becomes a problem

[jsibbison-square]

Put up a fix ☝️ , just exploring further.

[jsibbison-square]

Ah I think you are saying we should be using a different base64 generation method so its urlsafe out of the box

[jsibbison-square]

Seems like even with base64::engine::general_purpose::URL_SAFE we still want to encode it for maximum interoperability. Eg. %3D is = which would break if this was part of a query url or form submit.

[jsibbison-square]

This is the short term fix and I left some notes about future areas of change but we need to wait for the new UI to land to do anything more extensive. #3446

[angiejones]

is this fixed now? can we close?

[DOsinga]

yes