1. Go to your GitHub repository that you forked, it should have the name “codespace-executor”.
  2. Click on the Settings tab (you need admin access)
  3. In the left sidebar, click Secrets and variables
  4. Click Codespaces

​
Add Repo Secrets

  1. Click New repository secret
  2. Enter the secret name with KEYBOARD_ prefix in the following format KEYBOARD_APPNAME_API_KEY (e.g. KEYBOARD_TYPEFORM_API_KEY)
  3. Enter the secret value (your actual API key)
  4. Click Add secret
Tips
  • Once you’ve added the secrets you will have to reset any codespaces already running (you can ask Keyboard to delete existing codespaces)
  • In Claude desktop ask what environment variables Keyboard has access to in order to confirm the connection worked
  • Start asking Claude to perform tasks in your connected apps once it confirms it has access to

​
Security overview

​
What does Keyboard have access to?

Keyboard does not have access to the API keys you input. Those are stored in your private GitHub repo. Keyboard only knows that the environment variable is available to point Claude to when ready to execute a task. By default you will always have the ability to to approve or deny any task before Claude goes and executes a task leveraging the API key (you can also turn this final approval off if you want).

​
Best practices for AI-driven environment variable naming

Do:
  • Use uppercase names with the KEYBOARD_ prefix
  • Include the service name in the variable name
  • Use consistent naming patterns across your project
Examples of environment variable names: 
# Third-Party Integration Secrets
KEYBOARD_TYPEFORM_API_KEY
KEYBOARD_STRIPE_SECRET_KEY
KEYBOARD_STRIPE_PUBLISHABLE_KEY
KEYBOARD_SENDGRID_API_KEY
KEYBOARD_SENDGRID_FROM_EMAIL
KEYBOARD_ASANA_API_KEY
KEYBOARD_GOOGLE_SLIDES_API_KEY
KEYBOARD_GOOGLE_DOCS_API_KEY_READ_ONLY
KEYBOARD_GITHUB_TOKEN_FOR_API

​
Avoid these common mistakes

  • Generic names like KEY, SECRET, or TOKEN
  • Lowercase or mixed-case names
  • Ambiguous abbreviations
  • Storing secrets in code or configuration files
  • Using production keys in development environments

​
Step-by-step integration examples