Support
Reach the team, browse common troubleshooting paths, and jump to the public docs without entering the dashboard.
Public support
Use this page when you need product guidance, setup help, or a direct contact path without entering the dashboard. If you are already signed in and need workspace-specific help, use the protected support page in the app sidebar.
Open workspace supportBest for private questions, access issues, and anything that needs longer-form follow-up.
acm@uta.eduDiscord
Best for quick questions, implementation discussion, and community help in the ACM at UTA Discord.
#siloGitHub issues
Best for reproducible bugs, feature requests, and tracking known issues in public.
Open an issueDocumentation
Public setup guides, API reference, evaluation details, and operational troubleshooting.
View public docsCommon public topics
Getting started
- Install the CLInpm install -g silo-drift-cli
- Scaffold a reposilo setup
- First syncsilo sync --base origin/main --head HEAD
Troubleshooting
- 401 on syncCreate a fresh API key
- Empty dashboardCheck frontend-to-backend proxy config
- No drift runBootstrap happens first; drift starts on later versions
Tips
- Use silo doctorValidates URL and auth
- Pin CLI versionKeep CI reproducible
- Gate qualityUse silo gate after runs complete
Public FAQ
- How do I reset my API key?
- Open API Keys in the dashboard, revoke the old key, and create a new one. Update your local env vars and CI secrets afterwards.
- Does Silo work with private repositories?
- Yes. The CLI and GitHub Actions workflow run from your repo and call your deployed Silo API. Your repository does not need to be public.
- What models does Silo support?
- Silo uses OpenAI models by default and supports optional Ollama-backed flows in parts of the system.
- Where are results stored?
- Runs, prompts, and support tables are stored in Supabase/Postgres and surfaced in the dashboard and API.