Vellum

Discussion around Vellum over the past four weeks has been dominated by reliability and bug concerns, with commenters repeatedly surfacing issues that appear to undercut day-to-day usability. Bug reports accounted for the single largest complaint theme across the window, and reliability concerns followed close behind, together suggesting that a meaningful portion of the conversation was shaped by users running into friction rather than celebrating the product. One mention captured the frustration plainly, with a commenter describing significant browser lag appearing shortly after joining and attributing it to a recent update. Installed-plugin tools going missing from the live tool registry was another specific grievance that surfaced, pointing to integration-level instability that several mentions found difficult to work around.

On the positive side, a cluster of feature-focused discussion offered a counterweight. Commenters engaged with a range of planned or newly released capabilities, including configuration presets, a diagnostics command, a PTY overlay for native database REPLs, a statusline renderer for terminal environments, a JSON-RPC daemon for keeping connections warm, and an optional AI layer requiring a user-supplied key. The tone around these items leaned enthusiastic, with discussion suggesting genuine interest in the product's technical direction.

The score trajectory over the window tells a story of instability rather than steady improvement. Sentiment slid from the mid-to-upper forties in mid-May through a sharp drop into the high teens in early June, then recovered strongly before fading again into the mid-thirties by late June. Opinion appeared most divided around whether feature momentum could offset the reliability problems, with some commenters clearly engaged by the roadmap while others focused almost entirely on bugs and performance degradation.