> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roomote.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Start new users at /index, then /self-hosting to choose and prepare a host, including home networks at /homelab or infrastructure providers at /self-hosting/platforms. Continue through /first-task. Use Local development only when the user intends to modify Roomote itself.
> When an agent is asked to follow /self-hosting or install Roomote autonomously, read and follow /self-hosting/agent-installation as the normative automation contract even though it is intentionally hidden from side navigation.
> Use the one-command Linux installer for both evaluation and production. On macOS or Windows, create or reuse a full Ubuntu VM and run the same installer inside it; do not replace the installer with the repository's development Compose files.
> For a local VM, prepare a stable public HTTPS domain before connecting providers. Use a named tunnel with internal origin TLS or public DNS with ports 80/443 forwarded to the Linux host. Cloudflare Quick Tunnels do not support the Server-Sent Events Roomote uses; do not use them for the complete setup path.
> Run automated installs with --no-setup-url so the bootstrap token is not captured in the agent transcript. Let the user obtain the setup URL in a trusted terminal, enter credentials, and complete browser authorization.
> Proceed through safe, reversible setup and pause for privileged host or VM changes, public tunnel creation, credentials or browser authorization, durable external-account changes, destructive operations, existing-state conflicts, or when no documented safe default applies.
> A setup is not complete when the services merely start. Follow /first-task to verify sign-in, repository sync, and a real Roomote task that can clone and run a command. A saved environment is optional for a repository task. Verify branch or pull-request delivery and previews when configured; Slack and other communications providers are optional.

# Snowflake

> Let Roomote query and explore your Snowflake warehouse during a task.

Connect Snowflake when Roomote needs warehouse context to answer data-heavy
questions or support an investigation.

## When to use it

* Inspect schemas or tables related to a task
* Query warehouse data while debugging a product or operations issue
* Connect engineering work to the analytics warehouse your team already uses

## How setup works

Admins connect Snowflake from the **Integrations** page with an account
identifier, username, role, and PKCS8 PEM-encoded private key. Add the matching
public key to the Snowflake user first. Supply the private-key passphrase too
when the key is encrypted.

Generate a dedicated encrypted RSA key on a secure operator machine. Keep the
private key out of shell arguments, repositories, chat, and logs. For example,
run `umask 077`, then use `openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:3072 -aes-256-cbc -out roomote_snowflake_key.p8` and enter the passphrase interactively. Export only the public key with `openssl pkey -in roomote_snowflake_key.p8 -pubout -out roomote_snowflake_key.pub`.

> [!WARNING]
>
> The `execute_sql` tool can run any statement permitted by the configured
> Snowflake role, including statements that change data or schema. Use a
> dedicated least-privilege role, preferably read-only when tasks only need
> warehouse context.

## Rotate from an existing credential

1. Install the new public key in Snowflake's unused `RSA_PUBLIC_KEY_2` slot and verify its fingerprint before changing Roomote.
2. Enter the encrypted PKCS8 private key and passphrase in **Integrations > Snowflake**. Leave both fields blank on later edits to keep the stored key.
3. Run a Roomote task that calls `list_databases`, `list_schemas`, and `execute_sql` with `SELECT CURRENT_USER(), CURRENT_ROLE(), CURRENT_WAREHOUSE()`. Confirm the configured role can read only the intended data.
4. Review Roomote and Snowflake login logs for a successful JWT login without credential material. A saved connection is not proof that Snowflake accepted it.
5. After an observation window, revoke the previous public-key slot and verify a fresh Roomote task still connects.

## What to expect

Snowflake provides shared data warehouse context inside Roomote tasks.
Engineering changes and approvals still happen through your normal task and
repository review flow.

## Recipes using this

* [Triage customer issues](https://docs.roomote.dev/cookbook/support-channel)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.