GitHub
Repos, issues and releases via the GitHub API on your token. Connected with your own key — encrypted, server-side only, never exposed to the browser.
What you can build
Prompts like these, typed into opix, produce working GitHub features.
Connect it in three steps
Create the key
Generate an API key in your GitHub account — the link below takes you to the exact page.
Paste it in opix
Open your project → Connectors, paste the key. It's stored encrypted and injected server-side; even you only see the last four characters afterwards.
Prompt what you want
Describe the feature in chat — opix writes the GitHub code with honest fallbacks built in.
Keys & setup
| Environment variable | Required |
|---|---|
| GITHUB_TOKEN | Yes |
Create a fine-grained personal access token under GitHub → Settings → Developer settings → Fine-grained tokens, scoped to just the repos and permissions your app needs (e.g. Issues read/write). Public read-only features work without a token at a low rate limit.
Honest by default
Apps built with opix never pretend. Without a token, public read features still work (rate-limited, cached); write features show a connect note and their routes return 503.
Build with GitHub today
Describe the app, connect your key, ship it.
GitHub is a trademark of its respective owner, used for identification purposes only. opix is not affiliated with or endorsed by GitHub.