Supabase & Git Feature Requests

[334ms-dev]

1. Missing Supabase Support

Description

Quests.dev currently lacks built-in support for Supabase as a database + authentication integration. This limits real-world app scaffolding and forces developers to wire it in manually.

Expected Behavior

• Supabase should be available as a selectable backend option.
• Core features like auth, database queries, and storage should be scaffolded automatically.

Actual Behavior

• Users must manually configure Supabase in every quest project.
• No out-of-the-box examples for Supabase usage.

Suggested Fix

• Add Supabase SDK integration into quest scaffolding.
• Provide prebuilt examples for:
  • User authentication (sign-up, login, password reset).
  • Row-level security & database queries.
  • File storage with signed URLs.

---

2. Missing Git Integration

Description

Quest projects do not automatically integrate with Git for version control and collaboration.

Expected Behavior

• New quests should initialize a Git repository automatically.
• File edits should be tracked with commit history.
• Optional integration with GitHub/GitLab for remote sync.

Actual Behavior

• Users must manually set up Git inside every quest workspace.
• No built-in version history, diffs, or commit tracking.

Suggested Fix

• Auto-init a Git repo when creating a new quest.
• Add commands for common Git operations (commit, branch, push).
• Provide optional GitHub app integration for PRs/issues directly from quests.dev.

---

[aortbals]

FYI - git is already used within Quests to commit automatically as the agent works. You can see versions based on commits in the versions tab of a project. You can also quickly switch between them to view the live preview across different versions, which makes it easy to compare across commits. We plan on adding more git integrations including a much easier and faster export of the core repo for each project.

As far as Supabase - we definitely understand the value of deploying projects and integrating with services like Supabase. In the short term we encourage folks to export projects that are intended to be deployed. There are a lot of different needs and preferences when it comes to deployment and we want to make sure we have a clear plan that addresses most users' needs before adding specific service providers.