Hi everyone - we’ve been shipping new features to Mongoose Studio quickly these past couple of weeks, and this update brings two of our most requested improvements: a completely redesigned JSON viewer and first-class support for enum fields in the editor. The goal is simple: make browsing, editing, and understanding your MongoDB data smoother and more intuitive, especially for large collections and deeply nested documents. Here’s what’s new.

New feature

New JSON View

The JSON viewer in Mongoose Studio just got a massive upgrade. Cleaner layout, collapsible fields, better readability, and smoother document browsing.

  • Introduced a fully interactive JSON tree view with collapsible nodes for easier navigation through deeply nested documents.

  • You can browse large collections much faster with lazy expansion and “show X more fields…” for long objects.

  • Hover actions + a new “Open this Document” button make it easier than ever to inspect individual records while still letting you copy parts of the document as text.

  • Improved readability with syntax-colored values (strings, numbers, booleans, nulls) and monospaced formatting.

  • Clicking documents feels more natural: better highlighting, smoother multi-select behavior, and cleaner interactions overall.

New feature

Enum Dropdowns

Added full enum support to string fields in Mongoose Studio - with a new editor UI for enum selection, null values, and custom entries. Enum in schema → dropdown in Mongoose Studio

  • Backend now exposes enum metadata for string paths across all document actions (getDocument, getDocuments, and streams).

  • New edit-string component automatically switches between text input and dropdown mode based on schema enum values.

  • Smart enum picker supports selecting enum values, null, or entering a custom “Other” value when needed.

New docs
New Content

New Blog Posts

  • Tries support prefix filtering breaks down once datasets get large or when autocompleting structured identifiers like user.address.city or $gte.

  • The post walks through implementing a trie in JavaScript, adding support for semantic “roles” (field names vs operators) - how we did it for Mongoose Studio’s autocomplete.

  • MongoDB query autocomplete requires understanding cursor context — whether the user is typing a field name or an operator — which can be inferred via lightweight regex.

  • The final system combines token extraction, context detection, and trie-based lookup to provide intelligent MongoDB query autocomplete (as used in Mongoose Studio).

  • Mongoose-native MongoDB GUI: Mongoose Studio reads your actual Mongoose schemas, giving you a UI that behaves exactly like your models — no connection strings, no mis-cast queries.

  • Secure, zero-credential setup: Local dev needs no auth; Studio Pro adds GitHub/Google SSO so teams never have to share connection strings again.

  • Queries that “just work”: Studio automatically applies Mongoose casting (dates, ObjectIds, etc.) and even lets you use inline JS in filters for dynamic queries.

  • Schema-aware autocomplete: Stops the guesswork when typing deep field paths or operators. Perfect for large codebases with many nested models.

  • Built-in dashboarding + AI: Generate charts, maps, and metrics using natural language - Mongoose Studio uses your schemas and codebase as context to write data analysis scripts for you.

  • Surprisingly mobile-friendly: Use the AI chat to inspect, fix, or update data directly from your phone - great for production emergencies.

  • Flexible deployment: Mount it in Express, run it locally, or deploy to Vercel/Netlify. Free for local dev; upgraded auth/workspaces in Studio Pro.

Get in touch

Keep reading

No posts found