Troubleshooting

Solutions for common issues in Kodezi Create, including preview errors, slow responses, update problems, dependency issues, and saving failures.

The Troubleshooting Guide helps you quickly identify and resolve common issues while working in Kodezi Create. If something isn’t working as expected, whether it’s the preview not loading, code not updating, or dependencies failing, use this guide to get back on track.

1. Preview Not Loading

If the preview window is blank or stuck, try the following:

Solutions

  • Check the terminal for errors: Review the terminal for build or runtime errors that may stop the preview from loading properly.

  • Verify the development server is running: Ensure the development server is active and hasn’t crashed, as the preview depends on it.

  • Check for port conflicts: Make sure no other application is using the same port, since a port conflict can block the preview from starting.

  • Refresh the preview pane: Reload the preview window or the IDE to clear temporary glitches and reinitialize the preview.

2. Slow Response Times

If Chronos-1 replies slowly or takes longer than usual:

Solutions

  • Simplify your prompt: Use a shorter and clearer prompt to help Chronos-1 process your request faster.

  • Break requests into smaller steps: Divide large or complex tasks into smaller pieces to improve response time and accuracy.

  • Check your internet connection: Verify your network stability, as slow or unstable internet can delay responses.

  • Check your credit balance: Make sure you have enough credits available, since low or exhausted credits may affect performance.

3. Code Not Updating

If recent changes aren’t appearing:

Solutions

  • Check for file locks: Confirm whether the file is temporarily locked because Chronos-1 may still be editing it.

  • Wait for Chronos-1 to complete editing: Allow the model to finish processing changes before expecting updates in the preview.

  • Manually refresh the preview: Reload the preview window to ensure the latest code changes are displayed.

  • Check terminal for build errors: Look for compilation or runtime errors in the terminal that may prevent updates from appearing.

4. Installation or Dependency Errors

If the project fails to install packages or build:

Solutions

  • Ask Chronos-1 to reinstall dependencies: Request a fresh installation of required packages to resolve dependency issues.

  • Check the terminal for exact error messages: Identify which package or command is causing the failure by reviewing terminal output.

  • Clear and reinstall packages: Remove the node_modules folder and reinstall packages to fix corrupt or incomplete installations.

  • Check Node.js version compatibility: Ensure your Node.js version matches the requirements of the project or its dependencies.

5. File Changes Not Saving

If file updates aren’t saving properly:

Solutions

  • Wait for auto-save: Allow the editor time to complete the automatic save process before expecting changes to appear.

  • Check if the file is locked: Verify whether the file is currently locked because Chronos-1 may be editing it.

  • Manually save (Ctrl/Cmd + S): Use manual save to immediately write changes if auto-save is delayed.

  • Check write permissions: Ensure you have the necessary permissions to edit and save files in the project.

6. General Troubleshooting Checklist

If you’re unsure what’s wrong, follow this quick checklist:

Steps

  • Check the terminal: Review the terminal for warnings or errors that explain the issue.

  • Try again: Repeat the action or adjust your prompt to see if the issue resolves itself.

  • Undo recent changes: Revert modifications to return to a stable working state if something breaks.

  • Ask Chronos-1 for help: Describe the issue directly in chat so Chronos-1 can diagnose or fix it.

  • Contact Support: Reach out via the Help Center or email support@kodezi.com for further assistance.