---
title: "Get help"
description: "How to reach Judgment support, and what to put in a bug report."
sidebar:
  label: "Get help"
seo:
  title: "Get help | Judgment Docs"
  description: "How to reach Judgment support, and what to put in a bug report."
---

Email [support@judgmentlabs.ai](mailto:support@judgmentlabs.ai). The **Support** menu in the app (open your user menu) has **Report a Bug**, **Request a Feature** and **Contact Us**, which open an email to the same address with the subject filled in.

If something looks down, check [status.judgmentlabs.ai](https://status.judgmentlabs.ai) first. The user menu shows the same status badge.

## What to include in a bug report

- Your organization ID and the project name.
- A link to the trace, Issue, judge or test run you're looking at (open it and copy the URL from your browser).
- What you expected and what happened, with the steps to reproduce.
- For tracing problems: the SDK and version (judgeval 1.3.3+ for Python, 1.3.4+ for TypeScript), the integration you use, and any warning the SDK logged at startup.
- For API errors: the endpoint and the status code.

Never paste an API key into an email or a chat. If you think one leaked, rotate it under **Personal API Keys** or, for an ingest API key, **Ingest API Keys** in Settings.

## Ask from your coding agent

With the Judgment MCP server connected, your coding agent can search these docs while it works. [Connect your coding agent](/documentation/connect/connect-your-coding-agent) sets it up.

For questions about your own data, such as why a trace failed, ask the [Judgment Agent](/documentation/agents/judgment-agent) in the app.