Neon ships a Postgres pane for a terminal workspace built to hold coding agents

Neon's blog carries a release post for Neon for Herdr, a plugin that renders a developer's Neon projects as a pane next to whatever they are already doing, so creating a branch, grabbing its connection string, or suspending a compute is a keypress away ^[1]. The database features are ordinary; the venue is not. Herdr is described as a terminal workspace manager for developers and coding agents, where the editor, shells and agents all live as panes inside one persistent workspace, and plugins can add their own panes and actions ^[2].

The pane itself is a terminal dashboard built with Ink, Effect and the Neon TypeScript SDK ^[4], published as a repo at neon-solutions/neon-herdr ^[3]. The project list shows every project you can reach with its region, Postgres version and storage ^[5]. Pressing `/` opens a fuzzy search over project name, organization, ID and region that ranks a cached list rather than firing a request per keystroke ^[6]. Open a project and you get branch state, whether a branch is default or protected, the selected branch's databases and roles, and the last four operations Neon ran ^[7]. The author says the line he reads most is the compute line: active or idle, the autoscaling range, and the suspend timeout for the selected branch ^[8].

Then it gets blunt about mutation. `c` creates a branch, `n` renames, `d` deletes, `x` resets from parent ^[9]; `s` starts or suspends the compute, `R` restarts it, `e` edits min CU, max CU and suspend seconds in place ^[10]; `y` fetches a connection string, masked on screen and placed on the clipboard ^[11], pooled or direct depending on a `pooledConnections` setting ^[12]. That is eight single keystrokes that either change infrastructure state or hand over a credential ^[24]. The worked example in the post is the honest one: you are about to run a migration you do not trust, you want a copy of production, its connection string, and then the copy gone, without leaving the editor for a browser tab ^[23].

The plumbing is CLI-grade rather than bespoke. Auth is authorization code with PKCE against Neon's OAuth host, with a temporary callback listener on 127.0.0.1 and refresh tokens that rotate without reopening the browser ^[15]. The default `oauthClientId` is `neonctl`, the public Neon CLI client, which is why the flow works on install, and the post tells anyone packaging their own build to ask Neon for a dedicated client identifier first ^[17]. Config lives in a `config.json` you create yourself at mode 600, the plugin ignores your `.env`, and `?` prints the settings actually in force with their origin and the path to edit ^[20][21]. Herdr plugins cannot declare keybindings, so you supply your own in `~/.config/herdr/config.toml` ^[19].

Worth noting what is absent. Every documented entry point is a human keystroke; nothing in the post exposes these actions to the agent sharing the workspace ^[25]. The shift here is about where the surface lives, not who drives it: the pane is next to the agent, not available to it.

Watch whether Herdr grows a way for plugins to declare keybindings and for panes to expose actions to agents ^[19], and whether Neon hands out dedicated OAuth client identifiers to third-party builds or keeps the CLI client as the default path ^[17].