Help & support
Most questions are answered in this documentation. Use search first, then troubleshooting, then escalate to the right contact based on whether your issue is org-scoped or platform-wide.
Search the docs
Press ⌘K (or Ctrl K) and search for what you're trying to do. The docs cover installation, cloud agents, integrations, API routes, and operator procedures.
Popular starting points:
First-run setup for new users.
Remote agent runs and automations.
Ports, sign-in, integrations, and network issues.
Agents API and platform API routes.
Production URLs
When reporting issues, include which surface you were using:
Local development quick reference
If you are debugging locally, confirm the relevant dev server is running before escalating:
Full commands and env requirements are in Troubleshooting.
Self-service checklist
Before opening a support ticket, work through this list:
Search the docs
Press ⌘K and try alternate keywords (for example, "402" for budget errors, "webhook" for GitHub automations).
Check troubleshooting
Match your symptom to Troubleshooting — especially ports, Supabase env vars, and integration status.
Confirm integration status
Only GitHub is fully connectable today. Slack and Linear show in the UI but cannot be connected yet.
Gather context
Collect org ID, run ID, timestamp, and the exact error message or HTTP status code.
Who to contact
Organization questions
Contact your organization admin for:
- Members, roles, and invitations
- Model access and Model control policies
- Budget policies and spend questions
- Repository allowlists and GitHub app access
- Team structure and project settings
Org admins manage these in the dashboard. They cannot change contract-level entitlement — that requires a platform operator.
4RGE support
Email support@4rge.ai for:
- Product bugs and unexpected behavior
- Sign-in issues after troubleshooting auth and deeplinks
- Cloud agent failures that aren't environment or budget related
- Desktop app crashes and update problems
- Security concerns — include "SECURITY" in the subject line for priority routing
For cloud agent issues, include the run ID and organization ID. Operators can correlate these with audit events and the operations summary API.
Information to include in support requests
Copy this template into your email:
Organization ID:
User email:
Issue summary:
Steps to reproduce:
Expected behavior:
Actual behavior:
Run ID / automation ID (if applicable):
Error message or HTTP status:
Environment: [desktop / cloud / CLI / local dev]
Network: [direct / VPN / corporate proxy]
Timestamp (with timezone):Operator and admin resources
Platform operators and org admins have additional documentation:
Response expectations
4RGE support cannot change org membership or budget policies on your behalf — those requests must go through your organization admin.
Still need help?
- Troubleshooting — common fixes for local setup, sign-in, integrations, and ports.
- Help & support — you are here.
- support@4rge.ai — when self-service and your org admin can't resolve the issue.