This week’s SmythOS release focuses on stability and reliability. The team tackled three targeted bug fixes that restore expected behavior across the chat interface, Builder keyboard shortcuts, and API data extraction workflows. Sometimes the most valuable updates are the ones that simply make things work the way you expect.
Bug Fixes
Gemini Model Image Description 400 Error
Uploading an image and asking the Gemini model to describe it was returning a 400 Bad Request error. The root cause was traced back to the structure of the request payload when sent to the Gemini API.
Something in the argument formatting did not match what Gemini expected, which caused the API to reject the request outright. This has been corrected, and image descriptions now work as intended. You can drop an image into chat, ask Gemini what it sees, and get a proper response without the frustrating error message.
How this helps you:
- Get accurate image descriptions from Gemini without hitting errors.
- Use your chatbot with confidence for image-based queries.
- Restore full functionality to visual AI workflows in chat.
Redo Keyboard Shortcut Not Working in Builder
The redo shortcut in the Builder wasn’t doing anything. You could undo changes just fine, but when you tried to bring them back using the keyboard shortcut, nothing happened. This left you stuck manually recreating whatever you’d just undone, which gets old fast when you’re iterating on agent designs.
That’s fixed now. Redo works exactly as you’d expect, matching the behavior of undo and giving you full control over your edit history without needing to reach for your mouse.
How this helps you:
- Quickly restore changes you accidentally undid.
- Edit faster without recreating work from scratch.
- Trust that standard keyboard shortcuts behave consistently.
API Call Component: JSON Response Data Extraction Fails with Special Character Keys
The API Call component couldn’t extract data from JSON responses when keys contained special characters like @context, @type, or @id. If you tried to use a custom output expression such as Response.@context, you’d get undefined instead of the actual value sitting right there in the response.
This was particularly painful for anyone working with JSON-LD formatted data, which is common in semantic web applications, schema.org integrations, and various vendor-specific APIs that prefix their keys with special characters. The fix ensures these keys are now handled properly, so your extraction expressions return the data you’re actually looking for.
How this helps you:
- Extract data from JSON-LD and semantic web APIs without workarounds.
- Work with vendor-specific APIs that use prefixed keys.
- Build workflows that reliably handle real-world JSON structures.
Try These Updates
- Upload an image in chat and ask Gemini to describe it.
- Open the Builder, make a change, undo it, then redo it using the keyboard shortcut.
- Test an API Call component against a JSON-LD endpoint and extract values from keys like @context or @type.
For a deeper understanding and additional examples, refer to the official SmythOS documentation, which provides a more detailed exploration of these changes.