Last week I launched AgentGrove, an open-source local workspace that runs AI coding agents (Claude Code, opencode, Kimi) in isolated git worktrees. Today’s release, v0.1.42, makes its database tooling much more useful: a DBeaver-style database tree.
What’s new
The left rail’s Database view now renders the full connection → databases → tables tree:
- Every database on the server, expandable and lazy-loaded — not just the one in your connection string
- One click switches the active database; the SQL editor and table browser immediately target it (the pane header shows which DB you’re on)
- A single filter box matches database names and table names
- Saved connections with an inline Test button (server version on success, the real error on failure)
- SQL editor with schema autocomplete — tables and columns of the active database, prefetched in the background, on top of CodeMirror with Ctrl/Cmd+Enter to run
- Table browser with column filters (=, !=, <, >, LIKE, ILIKE) and pagination
Under the hood the backend is a small Rust/tokio-postgres layer: SELECTs are wrapped with to_jsonb(...) so any row shape renders as JSON, and cross-database browsing is just the connection URL’s database segment swapped per request — no extra connection state to manage.
Why it matters here
Agents write a lot of SQL-shaped code, and debugging their output means looking at actual data. Having the database tree a click away from the agent chat — instead of alt-tabbing to DBeaver — keeps the review loop in one window: agent writes a migration, you inspect the affected tables right next to the diff.
Try it
git clone https://github.com/arnabk/agentgrove.git
cd agentgrove && just dev
Enter fullscreen mode Exit fullscreen mode
Point it at any Postgres (the first-run seed targets your local one; AG_DATABASE_URL overrides). Demo videos, including the DB editor, are on the README. What should the database view do next — edit rows inline? Run agent-proposed migrations with a one-click apply?
답글 남기기