Manage encrypted secrets that are passed to your sessions as environment variables.
Synopsis
catty secrets <command> [arguments]
Commands
| Command | Description |
|---|
add <name> | Add a secret interactively |
set <name> <value> | Set a secret (non-interactive) |
list | List configured secret names |
remove <name> | Remove a secret |
test <name> | Test a secret (e.g., verify GitHub token) |
catty secrets add
Add a secret with hidden input.
catty secrets add MY_SECRET
For GitHub, use the special guided setup:
See GitHub Integration for details.
catty secrets set
Set a secret non-interactively (useful for scripts).
catty secrets set MY_SECRET my-value
The value may appear in your shell history. For sensitive secrets, use catty secrets add instead.
catty secrets list
Show configured secret names (not values).
$ catty secrets list
Configured secrets:
• GITHUB_TOKEN
• GH_TOKEN
• MY_API_KEY
catty secrets remove
Delete a secret.
catty secrets remove MY_SECRET
catty secrets test
Verify a secret works. Currently supports github:
$ catty secrets test github
Testing GitHub token...
✓ Token valid (user: yourname)
How Secrets Work
- Secrets are encrypted and stored locally at
~/.catty/secrets.json
- When you run
catty new, secrets are decrypted and sent to the API
- The session receives them as environment variables
- Secrets are never stored on Catty servers
See Also