Skip to main content Configure Mistral AI across development, staging, and production environments.
Use when setting up multi-environment deployments, configuring per-environment secrets,
or implementing environment-specific Mistral AI configurations.
Trigger with phrases like "mistral environments", "mistral staging",
"mistral dev prod", "mistral environment setup", "mistral config by env".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill mistral-multi-env-setup ai automation claude-code devops mcp ai-agents
Mistral AI Multi-Environment Setup
Overview
Configure Mistral AI across development, staging, and production with per-environment API keys, model selection, rate limits, and secret management via GCP Secret Manager, AWS Secrets Manager, or Vault.
Prerequisites
Separate Mistral API keys per environment (from console.mistral.ai )
Secret management solution configured
CI/CD pipeline with environment variables
Environment Strategy
Environment API Key Default Model Rate Limit Cache Development Dev key (low quota) mistral-small-latest 10 RPM Off Staging Staging key Same as prod 60 RPM On Production Prod key (full quota) Optimized per task Full RPM On
Instructions
Step 1: Configuration Structure // config/mistral/base.ts
export interface MistralEnvConfig {
apiKey: string;
defaultModel: string;
timeoutMs: number;
maxRetries: number;
debug: boolean;
cache: { enabled: boolean; ttlMs: number };
rateLimits: { rpm: number; tpm: number };
}
export const baseConfig: Omit<MistralEnvConfig, 'apiKey'> = {
defaultModel: 'mistral-small-latest',
timeoutMs: 30_000,
maxRetries: 3,
debug: false,
cache: { enabled: true, ttlMs: 300_000 },
rateLimits: { rpm: 60, tpm: 500_000 },
};
Step 2: Per-Environment Configs // config/mistral/environments.ts
import { baseConfig, type MistralEnvConfig } from './base.js';
const configs: Record<string, Partial<MistralEnvConfig>> = {
development: {
debug: true,
cache: { enabled: false, ttlMs: 60_000 },
rateLimits: { rpm: 10, tpm: 100_000 },
},
staging: {
cache: { enabled: true, ttlMs: 300_000 },
},
production: {
timeoutMs: 60_000,
maxRetries: 5,
cache: { enabled: true, ttlMs: 600_000 },
},
};
export function getMistralConfig(): MistralEnvConfig {
const env = detectEnvironment();
const envConfig = configs[env] ?? {};
// API key sourced from environment
const apiKeyVar = {
development: 'MISTRAL_API_KEY_DEV',
staging: 'MISTRAL_API_KEY_STAGING',
production: 'MISTRAL_API_KEY',
}[env] ?? 'MISTRAL_API_KEY';
const apiKey = process.env[apiKeyVar] ?? process.env.MISTRAL_API_KEY;
if (!apiKey) throw new Error(`Mistral API key not set for ${env} (expected ${apiKeyVar})`);
return { ...baseConfig, ...envConfig, apiKey } as MistralEnvConfig;
}
Step 3: Environment Detection type Environment = 'development' | 'staging' | 'production';
function detectEnvironment(): Environment {
// Explicit override
if (process.env.APP_ENV) return process.env.APP_ENV as Environment;
// Platform-specific detection
if (process.env.VERCEL_ENV === 'production') return 'production';
if (process.env.VERCEL_ENV === 'preview') return 'staging';
if (process.env.CLOUD_RUN_JOB) return 'production';
if (process.env.K_SERVICE) return 'production'; // Cloud Run
// NODE_ENV fallback
if (process.env.NODE_ENV === 'production') return 'production';
if (process.env.NODE_ENV === 'staging') return 'staging';
return 'development';
}
Step 4: Secret Management import { SecretManagerServiceClient } from '@google-cloud/secret-manager';
const sm = new SecretManagerServiceClient();
async function getMistralApiKey(env: string): Promise<string> {
const [version] = await sm.accessSecretVersion({
name: `projects/my-project/secrets/mistral-api-key-${env}/versions/latest`,
});
return version.payload?.data?.toString() ?? '';
}
import { SecretsManager } from '@aws-sdk/client-secrets-manager';
const sm = new SecretsManager({ region: 'us-east-1' });
async function getMistralApiKey(env: string): Promise<string> {
const { SecretString } = await sm.getSecretValue({
SecretId: `mistral/${env}/api-key`,
});
return SecretString!;
}
jobs:
deploy-staging:
environment: staging
env:
MISTRAL_API_KEY_STAGING: ${{ secrets.MISTRAL_API_KEY_STAGING }}
deploy-production:
environment: production
env:
MISTRAL_API_KEY: ${{ secrets.MISTRAL_API_KEY_PROD }}
Step 5: Environment Isolation Guards function requireEnvironment(required: Environment, operation: string): void {
const current = detectEnvironment();
if (current !== required) {
throw new Error(`"${operation}" requires ${required} but running in ${current}`);
}
}
// Protect dangerous operations
async function createFineTuningJob(params: any) {
requireEnvironment('production', 'createFineTuningJob');
// ... fine-tuning logic
}
// Prevent production data in dev
async function processUserData(userId: string) {
const env = detectEnvironment();
if (env === 'development') {
console.warn('Using test data in development');
userId = 'test-user-001';
}
// ... processing logic
}
Step 6: Feature Flags by Environment interface FeatureFlags {
useAgentsAPI: boolean;
enableBatchProcessing: boolean;
enableVisionModels: boolean;
maxConcurrentRequests: number;
}
const FLAGS: Record<Environment, FeatureFlags> = {
development: {
useAgentsAPI: true,
enableBatchProcessing: true,
enableVisionModels: true,
maxConcurrentRequests: 2,
},
staging: {
useAgentsAPI: true,
enableBatchProcessing: true,
enableVisionModels: true,
maxConcurrentRequests: 5,
},
production: {
useAgentsAPI: false, // Gradual rollout
enableBatchProcessing: true,
enableVisionModels: true,
maxConcurrentRequests: 10,
},
};
export function getFlags(): FeatureFlags {
return FLAGS[detectEnvironment()];
}
Error Handling Issue Cause Solution Wrong environment Missing APP_ENV Set explicitly in deployment config Secret not found Wrong secret path Verify secret manager and IAM permissions Cross-env data leak Missing guards Add requireEnvironment() checks Config mismatch Env var naming Use consistent naming convention
Resources
Output
Multi-environment config with type-safe overrides
Environment detection for Vercel, Cloud Run, and K8s
Secret management integration (GCP, AWS, GitHub Actions)
Environment isolation guards
Feature flags per environment
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
