This week’s SmythOS release brings a quality-of-life feature users have been asking for, plus a fresh visual update and tighter integration for voice testing. You can now paste images and files directly into chat, the entire app wears a new typeface, and voice embodiment testing lives right inside the sidebar where it belongs. The team also crushed a long list of bugs across debugging, chat, and the Builder interface.
New Features
Clipboard-Based Image and File Paste as Attachment
You can now paste images or files directly from your clipboard into any chat input area. No more hunting for the attachment button or dragging files around. Just copy something, paste it in, and you’ll see a preview appear automatically. Images display a thumbnail, and files are assigned an appropriate icon. You can remove attachments before sending if you change your mind.
For Chatbot embodiments, this feature respects your attachment settings. If you’ve disabled attachments, clipboard paste won’t work either. File size limits are capped at 5MB, which the system enforces automatically.
How this helps you
- Share screenshots and files faster without interrupting your workflow.
- Match the paste-to-attach behavior you’re used to from Claude and ChatGPT.
- Maintain security control in Chatbot embodiments through existing configuration settings.
Improvements
Vault Custom Model Modal with Collapsible Advanced Settings
The add/edit modal for custom models in Vault now groups advanced settings into a collapsible section. Fields like Context Window, Max Output Tokens, Fallback Model, and Features are tucked away by default. The primary fields you need most often, like Name, Model ID, Base URL, Provider, and API Key, stay front and center.
How this helps you
- Set up new models faster without scrolling past options you rarely touch.
- Access advanced configuration when you need it, without visual clutter when you don’t.
- Keep your focus on the essentials during initial setup.
Standardized Tooltips Across the Application
Every tooltip in SmythOS now uses the same component, based on what was already working well on the Vault page. The team audited existing implementations, built a reusable standard, and replaced all the variations. Visual appearance, behavior, and accessibility support are now consistent everywhere.
How this helps you
- Experience predictable tooltip behavior no matter where you are in the app.
- Benefit from improved accessibility if you use assistive technologies.
- Spend less mental energy adjusting to different tooltip styles on different pages.
Manrope Font Throughout the Application
The entire SmythOS interface now uses Manrope, a modern geometric sans-serif typeface from Google Fonts. Every heading, body text, label, button, input, and modal has been updated. The result is a cleaner, more cohesive look across all pages and components.
How this helps you
- Work in an interface that feels more polished and visually consistent.
- Read text that renders cleanly across different browsers and devices.
- Enjoy a refreshed aesthetic without any change to how things work.
Voice Embodiment Integrated in Test Sidebar
Voice embodiment testing now happens directly inside the Test sidebar instead of opening in a separate browser tab. You stay in context, with voice controls sitting alongside your other test options. No more jumping between tabs to check voice behavior.
How this helps you
- Test voice features without losing sight of your agent configuration.
- Reduce context switching during development and QA.
- Work efficiently across different screen sizes with the integrated layout.
Improved Spacing in Bulk Call UI
The Bulk Call page now has proper vertical spacing between the description text and the Upload CSV button. The gap was too tight before, somewhere around 10-20px, when it should have matched the standard design tokens used elsewhere. It’s fixed now.
How this helps you
- See a cleaner, more intentional layout on the Bulk Call page.
- Experience visual consistency with spacing patterns used across the rest of SmythOS.
- Trust that the interface reflects the same attention to detail as other areas of the app.
Bug Fixes
This sprint resolves a substantial list of issues affecting debugging, chat interactions, Builder navigation, and visual consistency throughout the platform.
Debugger Race Condition Corrupting Small Files
A timing issue caused Base64 encoding to break for text files 93 bytes or smaller when the debugger was enabled. The Get File component would produce corrupted or incomplete strings. Larger files worked fine, and disabling the debugger also worked around the problem. The race condition has been resolved.
How this helps you
- Process small files reliably through Get File while debugging.
- Trust the debugger output regardless of file size.
- Debug file processing workflows without workarounds.
Debug Step Mode Controls Disabled After Component Failure
When a component errored out during step-by-step debugging, all debug controls went gray. You couldn’t re-run the failed step or continue through the flow. The only option was to restart the entire session. Controls now stay active after failures.
How this helps you
- Retry failed steps immediately without restarting your debug session.
- Troubleshoot errors more efficiently by continuing from where things broke.
- Maintain debugging momentum when things go wrong.
Google Gemini 3 Function Call Missing thought_signature
Function calls through the chatbot interface failed when using Google Gemini 3 because the request was missing a required thought_signature field. This blocked function execution entirely. The field is now included correctly.
How this helps you
- Execute function calls with Gemini 3 through the chatbot interface.
- Build agents that use Gemini 3 for function-calling workflows.
- Avoid mysterious failures when switching between models.
Image Generation Failing for New Agents and Remixed Templates
Creating a new agent or remixing a template wasn’t generating images on the Staging environment. The image generation step silently failed. This has been fixed.
How this helps you
- Create new agents with proper image generation.
- Remix templates without missing visual assets.
- Move through agent creation workflows smoothly.
Agent Weaver Sidebar Not Displaying by Default
Opening an agent in the Builder was supposed to show the Agent Weaver sidebar automatically. Instead, the system remembered whatever sidebar you had open last, which meant Weaver often didn’t appear when you expected it. The default behavior is restored.
How this helps you
- See Agent Weaver immediately when you open an agent.
- Start working without manually switching sidebars.
- Experience consistent behavior when navigating between agents.
Color Code Truncated in Add Skill Input Dialog
Hex color codes in the Add Skill Input dialog were getting cut off, showing something like #F3506 instead of the full #f35063. The recent font change affected how the text container handled overflow. This is corrected now.
How this helps you
- See complete hex values when selecting colors.
- Copy accurate color codes without guessing the missing characters.
- Configure skills with confidence in your color choices.
Missing Thinking Message During Agent Skill Execution
When an agent skill ran in chat, there was no indication of what was happening. You’d just wait without knowing which skill was being called. The interface now shows feedback like “calling: [Skill Name]” so you know what’s in progress.
How this helps you
- Understand which skill is executing at any moment.
- Get transparency into what your agent is doing on your behalf.
- Follow along with complex multi-skill interactions.
Chat Interruption Feedback Issues
Two problems occurred when you stopped agent generation manually. First, the “Generation interrupted by user” message disappeared when you sent your next message. Second, the skill timer and loading indicator kept running even after you hit stop. Both issues are fixed.
How this helps you
- See persistent records of interrupted generations in your chat history.
- Trust that timers and loading states reflect reality after stopping.
- Maintain clarity about what happened during your session.
Missing Integrations Button in Builder Sidebar
The Integrations button was missing from its expected spot below the Components icon in the left sidebar. You couldn’t access the Integrations panel through normal navigation. The button is back.
How this helps you
- Access Integrations through the expected sidebar location.
- Manage integrations without hunting for alternative paths.
- Navigate the Builder with all expected controls in place.
Logo Button Opening Home in New Tab
Clicking the logo in the Builder header opened the home page in a new tab instead of navigating in the same tab. This cluttered your browser with extra tabs and didn’t match standard navigation patterns. It now navigates in the same tab.
How this helps you
- Navigate home without accumulating browser tabs.
- Experience consistent navigation behavior.
- Keep your browser organized while moving around SmythOS.
Stale Debug Input Values Persisting Between Runs
When debugging workflows with optional inputs, old values from previous runs stuck around in the UI. This made it look like those values were used in your current run, even when they weren’t. The debugger now clears previous execution data when you start a new run.
How this helps you
- See only the values that apply to your current debug session.
- Avoid confusion about which inputs were actually used.
- Debug optional input workflows with accurate feedback.
Last Component Missing Status Highlight and Log Button
The final component in a debug execution wasn’t showing success/failure colors or the log button after completing. It ran correctly and produced output, but you had no visual feedback or log access for that last step. Both are now displayed properly.
How this helps you
- Verify execution status for every component, including the last one.
- Access logs for the final step when troubleshooting.
- Get complete visual feedback across your entire workflow.
WebSearch Excluded Domains Tooltip Showing Wrong Format
The tooltip for Excluded Domains in the WebSearch component told users to enter domains one per line. The actual format is comma-separated. This mismatch caused parsing failures when users followed the tooltip instructions. The tooltip now shows the correct format.
How this helps you
- Configure domain exclusions correctly the first time.
- Avoid parsing errors from incorrect formatting.
- Trust that tooltips reflect actual requirements.
RAG Components Debug Mode Issues
RAG Remember, and RAG Forget had three problems in debug mode. They weren’t showing green/red execution status highlights. RAG Remember threw a “missing required inputs” error even when everything was filled in correctly. And the metadata field stopped accepting plain text, requiring JSON format only. All three issues are resolved.
How this helps you
- See clear execution status for RAG components during debugging.
- Submit valid RAG Remember configurations without false errors.
- Enter metadata in plain text or JSON format as needed.
Error Messages Disappearing from Chat History
When you stopped generation, the error message appeared but then vanished from history once you sent another message. You lost the record of what happened. Error messages now persist in your chat history.
How this helps you
- Maintain a complete record of your chat session.
- Review what happened during the interrupted generations later.
- Keep full context when scrolling through conversation history.
Space Invitation Link Reuse Causing Loading Loop
Reusing an invitation link you’d already accepted sent you into an infinite loading state with a 403 error. Your permissions were actually fine in the system, but the UI couldn’t handle the already-accepted link. This edge case is now handled gracefully.
How this helps you
- Reuse invitation links without getting stuck.
- Access your spaces through any path without errors.
- Avoid confusion when clicking old invitation links.
Chatbot CSS Classes Removed During Refactor
The recent chatbot modernization accidentally removed CSS classes and IDs that users and automated tests depended on. Selectors like div.chatbox, `button.chat-send`, and `div.chat-body` were gone, breaking tests and custom styling. These have been restored.
How this helps you
- Run automated tests against documented selectors.
- Apply custom CSS using the classes you’ve been using.
- Maintain enterprise customizations without rework.
Missing Error Message for Instructions Field Character Limit
Exceeding 5000 characters in the Agent Skill instructions field showed only a red border with no explanation. You had to guess what was wrong. A clear error message now tells you about the character limit.
How this helps you
- Understand immediately why your input was rejected.
- Know exactly how to fix the validation error.
- Configure Agent Skills without guesswork.
Fallback Model Name Not Shown in Production Logs
When an LLM component fell back to its backup model due to API errors or rate limits, the logs still showed the original model name. There was no indication that fallback happened. Logs now accurately reflect which model actually processed the request.
How this helps you
- Track which model handled each request in production.
- Debug issues with accurate information about what ran.
- Maintain proper audit trails for compliance requirements.
Builder Sidebar Animation Inconsistencies
The left sidebar opened smoothly while the right sidebar appeared abruptly. The right sidebar was resizable while the left wasn’t. These inconsistencies made the interface feel unfinished. Both sidebars now behave consistently.
How this helps you
- Experience polished, predictable sidebar behavior.
- Work in an interface that feels intentionally designed.
- Avoid the cognitive friction of inconsistent UI elements.
Logs Page Paginator Styling Issues
The active page indicator on the Logs page was green instead of the app’s blue theme, and border radius was inconsistent across page number buttons. The styling now matches the rest of SmythOS.
How this helps you
- Navigate logs with on-brand visual styling.
- Experience consistent design language across pages.
- Trust the professional appearance of every interface.
Scheduler Input Field Height Mismatch
Text inputs in the Scheduler’s “Fill in the required inputs” step were shorter than standard input fields elsewhere. The height now matches the rest of the application.
How this helps you
- See consistent input field styling in Scheduler workflows.
- Work with a polished, uniform interface.
- Avoid visual distractions from mismatched components.
Chat File Attachment Error for Auto-Converted Text
When you paste text longer than 4000 characters, SmythOS automatically converts it to a `.txt` file attachment. But submitting that attachment failed with a “Model does not support application/octet-stream” error. The auto-conversion workflow now processes correctly.
How this helps you
- Submit long text content through the chat interface.
- Use the auto-conversion feature as intended.
- Work with extended text input without errors.
Try These Updates
- Copy an image or file and paste it directly into any chat input.
- Open the Vault and add a custom model to see the new collapsible advanced settings.
- Notice the Manrope typography throughout the interface.
- Test voice embodiment directly in the Test sidebar without opening a new tab.
- Run a debug session and watch for accurate status highlights on the final component.
- Check that your custom chatbot CSS still works with the restored selectors.
You can find deeper guidance and examples in the official SmythOS documentation if you want to explore these changes in more detail.