Settings
Bring-your-own-key LLM providers — stored locally, encrypted at rest. No trackers, no telemetry.
AI change scope
MYTHIC's AI assist is bounded: one-click repair may patch deployment metadata or minimal application source files that caused the failed build, but it must not touch host-level Docker/Traefik configuration without an explicit operator action.
- build command, start command, app port
- runtime environment suggestions
- Dockerfile fallback hints for the deployed repo
- minimal source patches for build-blocking app errors
- host Docker socket, Traefik, DNS provider tokens
- broad refactors unrelated to the failed build
- secrets, API keys, or database contents
Multideploy · GitHub access
Multideploy only ever lists and deploys repos you own — enforced by GitHub's own affiliation=owner filter, re-checked server-side on every stack you create, never a repo picked from someone else's account. A fine-grained personal access token with read-only Contents and Metadata permission is enough — it is stored encrypted the same way as your LLM keys and only ever sent to api.github.com.
Where to get an LLM API key
Reference only — MYTHIC never auto-registers you anywhere. Pick one, get a key, paste it above.