Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qoder.com/llms.txt

Use this file to discover all available pages before exploring further.

Supabase is an open-source Firebase alternative that provides PostgreSQL databases, user authentication, file storage, and real-time data sync. Quest supports authorizing and connecting to Supabase projects directly, so you can handle frontend development and backend data management within the IDE — no switching between browser and editor. You can connect multiple Supabase projects simultaneously and preview database table schemas (Schema) directly in the IDE to stay on top of your backend data model. Core features:
  • Multi-project connections: Authorize and connect to multiple Supabase projects for quick switching between environments (development, testing, production) or different services.
  • Database schema preview: View database table structures of connected projects directly in the IDE — including table names, fields, types, and relationships — without opening the Supabase Dashboard.
  • Enhanced database capabilities: AI agents are aware of your database structure and can automatically generate table creation statements, data schemas, and query logic based on task requirements, ensuring frontend-backend data model consistency.
  • One-click authorization: Securely connect to Supabase through the OAuth flow — no need to manually configure API Keys or connection strings.
Supported Supabase services: After connecting a Supabase project, you can use the following services in Quest:
  • Database (PostgreSQL) — Full SQL support for storing and querying application data. AI can automatically generate the tables and data schemas you need. See Supabase Database docs.
  • Authentication — Securely manage user registration, login, and access control. Supports multiple auth methods including email/password and OAuth providers like Google and GitHub. See Supabase Auth docs.
  • Storage — Upload and manage images and other files through Supabase Storage, suitable for user avatars, file uploads, and static media resources. See Supabase Storage docs.
  • Realtime — Push data changes to your application in real time, supporting live chat, dynamic feeds, collaborative dashboards, and more. See Supabase Realtime docs.
How to use: When building a project in Quest, if the AI determines a Supabase connection is needed, it will prompt you in the chat panel. You can also connect proactively:
1

Prepare your Supabase project

Go to Supabase to register an account and create an organization and project.
2

Authorize

In Quest, click the Supabase tab at the top of the tool panel. Click the Authorize button, follow the prompts to complete the OAuth flow, select your Supabase organization, and confirm.
3

Connect a project

After authorization, the panel displays your organizations and projects. Find the target project and click Connect to link it to the current Quest project.
4

Start building

Once connected, you can preview database table schemas directly in the Supabase panel, and the AI will use this schema information to assist your development.
Qoder projects can only connect to active Supabase projects. To switch organizations, click the toggle button next to the organization name.
Use cases:
  • Full-stack app rapid scaffolding: Describe your application requirements in Quest, and the AI automatically generates the frontend UI and configures the Supabase backend — including database tables, authentication flows, and storage strategies.
  • Data model design and validation: Use the in-IDE schema preview to check whether AI-generated data models meet your expectations in real time, and adjust before continuing development.
  • Multi-environment management: Connect to both development and production Supabase projects simultaneously to easily view and compare data structures across environments.
AI-generated database operations (such as creating tables or modifying schemas) take effect directly on the connected Supabase project. For production environments, confirm operations carefully before executing.
  • Authorization security: The authorization process uses OAuth — Qoder does not store your Supabase password. Authorize only the organizations and projects you need, following the principle of least privilege.
  • Network dependency: Supabase integration requires a network connection to access Supabase cloud services. Ensure your network environment is working properly.