Skip to main content
Origin includes a built-in Send Feedback form that lets you send a bug report or feature request directly to the Origin team without leaving the platform. When you submit a report, Origin attaches the endpoint context you select and any files you upload, so the team has the information they need to reproduce the issue or scope the request — often without any follow-up.

​
Opening Send Feedback

Send Feedback is reached from your avatar, not from Admin or Endpoints — it’s personal to you, not tenant configuration. Click your avatar in the bottom-left corner of the console and select Send Feedback.

​
Filling out the report form

Complete as many fields as you can. The more context you provide, the faster the team can act on your report.
Even for a feature request, describe the workflow you were trying to complete in Description — it helps the team understand the use case and prioritize appropriately.

​
Adding context and attachments

The right-hand rail of the Send Feedback form contains two optional but highly recommended sections. Affected endpoint — Search for and attach a specific endpoint’s agent logs and telemetry to the report. Leave this blank for a general product or dashboard issue that isn’t tied to one machine. Attachments — Drag and drop files, or click Choose files to upload up to 10 attachments. Most file types are accepted; executables are blocked. Each file can be up to 250 MB. Screenshots of error states, exported logs, and diagnostic reports are all good candidates.

​
Submitting the report

Click Send Bug Report or Send Feature Request (the label tracks the Type you selected) to send the report to the Origin team. You do not need to follow up — the team will reach out if they need additional information.
For urgent production issues or situations where the built-in form is not accessible, contact Origin support directly. The support team can escalate and triage time-sensitive reports outside the normal queue.

​
What to include for faster resolution

The details below aren’t separate form fields — fold them into Description — but including them significantly reduces back-and-forth.
For agent-related issues, include the runtime logs from the affected endpoint.Windows
  1. Click the Origin icon in the system tray.
  2. Select Open Log Folder.
  3. The folder C:\ProgramData\Origin\Agent\Logs\ opens in Explorer. Zip the contents and attach them to your report.
macOS
  1. Click the Origin icon in the menu bar.
  2. Select Open Log Folder.
  3. The folder /Library/Origin/logs/ opens in Finder. Compress the folder and attach it to your report.
For console or platform issues that are not agent-related, include a screenshot of the affected view and your browser console output (open browser DevTools → Console tab, reproduce the issue, then copy the output).
Windows
  1. Click the Origin icon in the system tray to open the agent menu.
  2. The agent version is displayed at the bottom of the menu.
Alternatively, open Settings → Apps (Windows 11) or Control Panel → Programs and Features (Windows 10), and look for Origin Observability Agent in the list.macOS
  1. Click the Origin icon in the menu bar.
  2. The version string appears at the bottom of the dropdown menu.
Alternatively, run the following in Terminal:
Include the full version string (for example, 1.4.2) in your report.
If you are reporting a problem with the agent — such as missing AI events, a red or yellow tray icon, or an installation failure — attach the Diagnostic Report output to your ticket. To generate it: click the tray icon (Windows) or menu bar icon (macOS) → select Run Diagnostics. Copy or screenshot the full output, where every check should ideally read OK. Any failing line gives the team an immediate starting point.