# Convex Env

> Set and wire Convex deployment env vars / secrets for the app.

Set and wire Convex deployment env vars / secrets for the app.

- Page: https://ss33.ai/skills/convex/convex-env-7934525182
- Publisher: convex
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [DevOps & cloud](https://ss33.ai/skills/category/software-development-t44z8z/devops-and-cloud-unkt50)
- License: Apache-2.0
- Source: https://github.com/convex/agent-skills/blob/191a5c33a7e7a22ec9d5ff13930f84748bbcf8f8/skills/convex-env/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/convex/convex-env-7934525182

<!-- GENERATED from convex-agents content/capabilities/env.json — do not edit by hand. -->

# Manage env vars + secrets

Store secrets as Convex deployment env vars (npx convex env set), read them with process.env in actions, never commit them.

## Workflow

1. `npx convex env set KEY value` (per deployment).
2. Read via process.env.KEY inside actions (not queries/mutations).
3. Never hardcode or commit secrets; add to .env.local only for local.
4. Confirm it's set with `npx convex env list --names-only`, which lists names without printing the secret values.

## Rules

- Secrets live in Convex env vars, never in code or git.
- process.env only in actions ('use node' if needed), not queries/mutations.
- Different deployments need their own values.
- Check what is set with `npx convex env list --names-only`; never print secret values into the conversation.
