Troubleshooting & FAQ
Common questions and sticking points across the Control Panel and the IDE.
Overview
Most of what looks like a bug in Creytix is actually a tier badge or a deliberate gate doing its job. This page collects the cross-cutting questions that don't belong to any one department — for a specific department's own gotchas, check its troubleshooting page (linked from its overview).
Common issues
"A page says Building or Preview — is that broken?"
No. Building means active development with an honest-scope section telling you what's not there yet; Preview means early access with roadmap framing. Neither is a GA claim, and neither is a bug — check the changelog for what recently moved between tiers.
"The workspace picker asked me to choose — did I lose access to something?"
No. If more than one workspace candidate is available and you haven't explicitly picked one yet, the IDE opens a picker on first load rather than guessing. Pick one; you can switch anytime from the 📁 chip in the header.
"An AI model in the IDE won't respond."
Check the Models tab: a BYOK model needs its provider key added to the Secrets vault first (it shows "needs a key" rather than failing silently), and a local Creytix model needs the Creytix Model Server running — check npm run creytix:models:status.
"The desktop app won't open — macOS says it can't verify the developer."
Expected on today's build — it's unsigned. Right-click the app → Open the first time, or clear the quarantine flag (xattr -dr com.apple.quarantine). See Install the desktop app.
"I can't type into the vault paste field."
That's intentional — the field only accepts a paste, never typing, so a secret's value never lands in visible page state. See Vault & secrets.
"The IDE terminal hangs or shows a blank screen for some commands."
The terminal is a command-runner, not a full PTY yet — interactive full-screen programs (vim, htop, less) aren't supported. Run those in a real terminal outside the IDE for now.
"I can't self-serve a permission or role change for my team."
Fine-grained, per-feature roles are still being built out — today's model leans on workspace-level isolation. Raise specific access-control needs with your Creytix contact rather than assuming a role model exists that isn't documented. See Workspace, tenants & RBAC.
"Something Inspector/Prompt Guard/Design Labs flagged wasn't fixed automatically."
None of these tools auto-fix by design — they detect and report so a human makes the call. See each department's own troubleshooting page for specifics.
Limits & honest scope
This page covers cross-cutting issues only. It will not always have your exact answer — when it doesn't, the relevant department's own overview and troubleshooting pages are the next stop.