Skip to main content

​
Known Issues

Issue: Specode confirms changes but they don’t appearWorkaround: Always manually refresh the preview window after each change
Issue: Build or runtime errors occur but aren’t shown in the interfaceWorkaround: Ask Specode to check for errors if something seems wrong
Issue: Specode misinterprets unclear instructionsWorkaround: Be extremely specific - include exact component names, locations, and desired outcomes
Issue: Server stops but the interface doesn’t indicate itWorkaround: If unresponsive, manually restart the server using the Start Project button
Issue: Preview doesn’t load or shows connection errors in certain browsers.Specode’s preview uses web containers, which require a modern Chromium-based browser.Supported browsers:
  • Chrome
  • Edge
  • Brave
  • Arc
  • Opera
Unsupported browsers:
  • DuckDuckGo
  • Tor Browser
  • Firefox - inconsistent experience
  • Safari 16.4+ - inconsistent experience
Recommended browser: Chrome or any Chromium-based browser (Edge, Brave, Arc).If preview isn’t loading, try switching to Chrome or another Chromium-based browser.
Solution: Use the Time Machine tool (clock icon at the top of the editor) to restore your app to a previous point. Browse through saved snapshots and select the version you want to restore. This is useful when changes break something or data is accidentally removed.
Issue: Engineering or the AI has fixed an issue, but you still see the old error in your preview.Workaround: Clear your browser cache for Specode-related sites, or try opening the preview in a different browser (or incognito window). Cached assets from a previous broken state can persist even after the underlying issue is resolved.