Top Feature Requests for Pgcli: Taking the Postgres CLI to the Next Level

The terminal window waits, blinking. You type a query and Pgcli fires back with instant, colorful results. But something’s missing.

Pgcli is one of the best Postgres CLI tools available. It’s fast. It’s autocomplete is sharp. The syntax highlighting saves time and prevents mistakes. Still, the community knows it can go further. Feature requests are the lifeblood of open source. They shape roadmaps, sharpen edges, and push performance past limits.

The top Pgcli feature requests today fall into clear clusters. First: better integration with modern workflows. Engineers want hooks for cloud-based secrets management. They want Pgcli to connect directly to managed Postgres instances without hacking connection strings.

Second: advanced result formatting. Pgcli’s table output works, but some users want JSON export, Markdown-ready tables, and CSV streaming without piping to another tool. Direct formatting options would cut friction and keep results clean.

Third: performance optimization for massive datasets. Autocomplete speed is strong now, but in large schema environments it still stalls. Requests for asynchronous loading and smarter caching have been consistent.

Fourth: richer scripting support. Pgcli already runs queries from files, but native scripting with variables, conditional logic, and reusable macros would move it deeper into daily automation work.

Feature requests work best when they’re specific, reproducible, and focused on value. That’s what maintainers respond to, because it’s what makes code better, faster. If Pgcli ships even half the most-requested features, it will be more than a CLI—it will be a critical layer in Postgres operations.

Want to see some of these ideas in action without waiting on a merge? Try hoop.dev. Connect your database, run queries, and test enhanced workflows live in minutes.