The query history is the unusual piece: a query you worked out in conversation can be pulled back later by id and dropped into code, instead of being retyped out of a scrollback. That is also why `queryDB` insists on a descriptive name — it is what makes the history readable a week later.
A TypeScript server giving read access to InstantDB. It loads your schema from the project directory and your credentials from that project's `.env`, then runs queries and keeps a record of them.
- A query run against InstantDB, which requires a descriptive `name` alongside the `query` itself — `queryDB`
- Pre-defined example queries by category, such as `basic_read`, `filtering` and `associations` — `get_examples`
- The history of queries run, with id, name, timestamp and structure — `list_queries`
- One earlier query fetched back by id, for reuse or for pasting into code — `return_query`
An InstantDB app: `INSTANT_APP_ID` and `INSTANT_APP_ADMIN_TOKEN`, read from the project's `.env` or passed in the client config. The schema is loaded dynamically from the usual locations relative to a project directory — `instant.schema.ts`, `src/instant.schema.ts` or `app/instant.schema.ts`. Build with `npm run build` and point the client at `build/index.js`. The interface is read-only, and permissions-file detection is listed as pending.