Help & support
Help & support is your guide when the docs alone are not enough. It explains where to look first, who can actually change things (you, your organization admin, or X4RGE), and what to send so your question gets answered quickly—not lost in a generic ticket.
Most answers are already here: use search, then Troubleshooting for common fixes. Use this page when you need a person—for access, policy, billing context, or a product bug after you tried the steps.
What this page is for
If something is broken or blocked right now, open Troubleshooting and match your symptom first. Come back here when you know you need a human.
Find answers fast
Press ⌘K (Mac) or Ctrl K (Windows) anywhere in the docs and search for what you're trying to do — install, cloud agents, GitHub, budgets, sign-in, and more.
Popular starting points:
First-run setup for new users.
Remote runs and automations.
Sign-in, integrations, and common errors.
Members, models, usage, and settings for admins.
In practice
Match your situation to the right starting point. Many rows point to docs; others mean asking someone on your team or at X4RGE.
How help works
Follow this order so you do not wait on the wrong team.
Search the docs
Press ⌘K or Ctrl K. Try alternate words — "budget" for spend limits, "GitHub" for repos.
Try troubleshooting
Match your symptom on Troubleshooting. Fix one thing at a time.
Choose who to contact
Access and policy → org admin. Product bug after steps → X4RGE support. See Who to contact.
Send complete context
Use the What to include checklist — especially run ID for cloud agents.
GitHub is fully connectable. Slack and Linear may appear in the UI before connect is finished — see those pages for workarounds, not support for "why won't it connect."
Who to contact
Different problems need different owners. Sending the request to the right place is usually faster than emailing everyone.
Organization admin
Ask your admin for:
- Members, roles, and invitations
- Model control and which models you can use
- Usage and budget policies
- GitHub app access and repository allowlists
- Teams, projects, and org Settings
Admins work in the dashboard. They cannot change plan-level entitlement — that comes from your commercial agreement.
X4RGE support
Email support@x4rge.ai for:
- Product bugs and unexpected behavior
- Sign-in issues after you tried Troubleshooting
- Cloud agent failures that aren't fixed by environment or budget settings
- Desktop app crashes or update problems
- Security concerns — put SECURITY in the subject line for priority handling
Support cannot change org membership or budgets for you — those requests go through your organization admin.
What to include
A short, complete message helps support or your admin reproduce the issue on the first reply. Copy this mental checklist before you send email or Slack.
Always helpful:
- Organization name (and org ID if your admin shared it)
- Your email and which product you use — desktop, cloud, CLI, or dashboard
- What you expected vs what happened
- Steps to reproduce (short numbered list)
- Screenshot or exact error text if you have it
- When it happened (date and timezone)
For cloud agent issues, also include:
- Run ID from the Agents workspace
- Automation name if the run came from a schedule
Open the run in the Agents workspace and copy the run ID before emailing support or your admin.
Response expectations
These are typical timelines — your org admin may respond faster or on their own schedule.
Still need help?
You searched, tried Troubleshooting, and contacted the right person with the details above. If the issue remains:
- Org admin — membership, models, budgets, GitHub access on your org.
- support@x4rge.ai — product bugs, sign-in after troubleshooting, security (SECURITY in the subject line).
Keep the same context in follow-ups so nothing gets re-asked from scratch.