| name | twinmind-multi-env-setup |
| description | Configure TwinMind across development, staging, and production environments with separate accounts and API key management.
Use when implementing multi env setup,
or managing TwinMind meeting AI operations.
Trigger with phrases like "twinmind multi env setup", "twinmind multi env setup".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(curl:*), Grep |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","twinmind","deployment"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
TwinMind Multi-Environment Setup
Overview
Configure TwinMind across development, staging, and production environments with separate accounts and API key management. TwinMind uses the Ear-3 speech model (5.26% WER, 3.8% DER) for transcription, with GPT-4, Claude, and Gemini for AI summarization.
Prerequisites
- TwinMind account (Free, Pro $10/mo, or Enterprise)
- Chrome extension installed and authenticated
- API access (Pro/Enterprise tier)
Instructions
Step 1: Enterprise Configuration
TwinMind Enterprise supports on-premise deployment, custom AI models, and unlimited context tokens.
const config = {
apiKey: process.env.TWINMIND_API_KEY,
model: "ear-3",
aiModels: ["gpt-4", "claude", "gemini"],
};
Step 2: Role Configuration
const twinmind = {
ssoProvider: "okta",
teamSharing: true,
customModels: ["gpt-4-turbo"],
onPremise: true,
};
async function configureTeam() {
const team = await twinmind.createTeam({ name: "Engineering", members: ["user1", ] });
.(, team.);
}