What's missing from your current VS Code PostgreSQL workflow?

We’re gearing up to launch NexQL—an AI-native PostgreSQL extension built entirely inside VS Code to replace bloated standalone clients and fragmented extensions. We've integrated everything from a fluid tree explorer and interactive SQL notebooks to visual schema designers and live dashboard monitoring directly into your editor.

But here's the thing: we don't want to build this in a vacuum. We want to build it for your daily engineering workflows.

Whether you are optimizing massive multi-tenant data pipelines, tuning query performance, or just trying to quickly visualize a schema layout, we want to know what hurts the most about your current local or cloud database setup.

We’d love to hear your thoughts on:

• What is the single biggest missing feature or annoyance in your current VS Code database extension?

• How do you prefer to interact with AI when writing or debugging complex raw SQL queries?

• What kind of real-time monitoring metrics or operational dashboards do you actually look at on a daily basis?