integration with tidewave, which allows for AI agent driven UI development.

[tptodorov]

What

https://tidewave.ai/ is a tool that allows integration between AI agents and React development so that UI can be interactively modified via the agent while looking at the ui changes.

Ask me for a demo.

Testing

---

Note

Adds Tidewave integration (Vite plugin + proxy) and documents AI-powered development with Tidewave.

• UI build/config:
  • Add Tidewave Vite plugin tidewave() and import in redisinsight/ui/vite.config.mjs.
  • Configure dev server proxy for "/tidewave" to http://localhost:5540.
• Tooling:
  • Add tidewave to devDependencies in package.json.
• Docs:
  • Introduce AI-Powered Development section in README.md with Tidewave overview, key features, quick start, and link to docs/development/ai-tools.md.

^{Written by Cursor Bugbot for commit f722e35. This will update automatically on new commits. Configure here.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cursor]

Bug: Tidewave proxy points to wrong backend port

The proxy configuration routes /tidewave requests to http://localhost:5540, which is the RedisInsight API server port, not the tidewave backend. Tidewave runs its own separate backend service that needs to be proxied. This hardcoded port conflicts with the existing RedisInsight API and will cause tidewave requests to fail since the RedisInsight API doesn't handle tidewave endpoints.

 

[github-actions]

Code Coverage - Integration Tests

Status	Category	Percentage	Covered / Total
🟢	Statements	81.66%	16282/19938
🟡	Branches	64.63%	7346/11366
🟡	Functions	70.63%	2285/3235
🟢	Lines	81.3%	15319/18841

[pawelangelow]

Suggested change

	"/tidewave": `http://localhost:5540` // your backend port
	'/tidewave': 'http://localhost:5540'

[cursor]

Bug: Incorrect Vite proxy configuration format

The proxy configuration uses a string value directly instead of an object with a target property. Vite's proxy configuration expects an object format like { target: 'http://localhost:5540' }. The current string format may cause the proxy to fail or behave unexpectedly during development.