Skip to content

Conversation

@amaan-bhati
Copy link
Member

@amaan-bhati amaan-bhati commented Jan 16, 2026

What has changed?

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).
  • Documentation update (if none of the other choices apply).

How Has This Been Tested?

Please run npm run build and npm run serve to check if the changes are working as expected. Please include screenshots of the output of both the commands. Add screenshots/gif of the changes if possible.

  • Ran npm run build nothing breaks, the build was successful! adding screenshot for reference:
Screenshot 2026-01-16 at 4 31 43 PM
  • Ran npm run serve, screenshot for reference:
Screenshot 2026-01-16 at 4 33 36 PM

UI Peview:

  • Preview for the changes/additions, we now have a native tab for the windows support with the updated instructions in a new windows native tab:
Screenshot 2026-01-16 at 11 23 58 PM Screenshot 2026-01-16 at 11 24 08 PM

Checklist:

  • My code follows the style guidelines of this project.
  • I have performed a self-review of my own code.

@amaan-bhati amaan-bhati changed the title feat: update docs for the new windows native support feat: update docs for the windows native support Jan 16, 2026
2. Run as Admin: Open your terminal as **Administrator**.
3. Troubleshooting: If you face issues, ensure `cmd.exe` and `powershell.exe` (default paths in Windows) are in your system environment variables.

### 5. Verify Installation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please mention a step to Verify the installation by running: keploy or keploy --version for below output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants