# Environment variables

The `.env` file is managed by the hosting platform — do not edit manually.

## Browser (build-time, `import.meta.env`)

| Variable                        | Purpose                       |
| ------------------------------- | ----------------------------- |
| `VITE_SUPABASE_URL`             | Supabase project URL          |
| `VITE_SUPABASE_PUBLISHABLE_KEY` | Public anon key (RLS applies) |
| `VITE_SUPABASE_PROJECT_ID`      | Project identifier            |

## Server (runtime, `process.env`)

| Variable                    | Purpose                                      |
| --------------------------- | -------------------------------------------- |
| `SUPABASE_URL`              | Same as above, server-side                   |
| `SUPABASE_PUBLISHABLE_KEY`  | Public key for user-scoped server clients    |
| `SUPABASE_SERVICE_ROLE_KEY` | **Bypasses RLS — server only, never expose** |

Read `process.env.X` **inside `.handler()`**, never at module scope.

## Secrets

Project-specific secrets (webhook secrets, third-party API keys) are managed via the hosting platform's secrets UI and read from `process.env` in server functions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hitl-01.gitbook.io/hitl-docs/reference/env.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.