Hi team, I've been using Typesense in production f...
# community-help
m
Hi team, I've been using Typesense in production for a while and love the simplicity of the API-first approach. One friction point I keep running into: most interactions happen via REST APIs or the dashboard, and there's no tooling inside the developer workspace itself. I'm thinking about building a VS Code extension — something like "Typesense Studio" — that lets developers: • Browse and manage collections • Run searches and debug queries • Explore schemas • CRUD documents All without leaving the editor. Similar to what MongoDB for VS Code or Redis for VS Code offer their ecosystems. A few questions before I invest time building this: 1. Would this be useful to others here? 2. Has anyone attempted something like this already? 3. Does this align with where the Typesense team sees developer experience heading? Happy to build this as an open-source contribution to the ecosystem. Just want to make sure I'm solving a real problem before diving in. Any thoughts?
a
Hey Mahidhar That's a cool idea 😄 To answer your questions: 1. Honestly, it's not something we see people ask for often. Most folks use the Typesense Cloud Dashboard or Postman for this kind of thing. But that doesn't mean there's no audience for it. 2. I don't think anyone has built a VS Code extension for Typesense yet, so you'd be the first. 3. I can't speak to the team's roadmap, but developer experience is definitely something we care about. My personal take: if it's useful for your own workflow, it's worth building, especially since you can get it off the ground really quickly with tools like Codex and Claude Code. And if you open-source it, there's a good chance others will find it useful too.