Reporting a bug needs an account. A guest has no Report a bug control and the request is
refused, so sign in first.
Before you file
Two minutes of checking often saves the round trip.1
Check whether Cortex is down
If everything is failing at once rather than one action, look at
System status or status.cortex.foundation
before writing anything. A maintenance window shows its own screen, titled Cortex is taking a
short break, with a Time remaining countdown.
2
Read the message you were given
Most failures carry a short heading and a stable code. Not included in your plan, You have
used this plan limit and Please sign in again are expected answers, not bugs.
Troubleshooting lists what each message means, and the
problem catalog has a page per code.
3
Copy the reference id
When a failure was on Cortex’s side, the card shows a reference id and asks you to quote it.
Paste it into your report; it is the fastest way for the team to find your request.
Open the dialog
There are three entry points, and they all open the same Report a bug dialog:
The first two are permanent. The banner is dismissible, and dismissing it does not take the other
two away.
Fill in the report
The dialog opens with a single line of intent, “Tell us what went wrong. We read every report”, and three fields.1
Title
A short summary, up to 200 characters. One sentence naming the thing that broke beats a
paragraph.
2
What happened
Up to 8,000 characters for the steps you took, what you expected, and what you saw instead. The
field’s own prompt asks for exactly those three. Add the reference id here if you have one.
3
Where it happened
Pick a surface: Not sure, Cortex Chat, Cortex Code or Cortex Bot. Not sure
is a real answer, so use it rather than guessing.
4
Send report
Choose Send report. On success the dialog shows Report sent with “Thank you. We will
look at this”, and a Done button. Cancel closes without sending.
Screenshots
Screenshots are optional and usually worth adding. You can drop files onto the dialog, paste them from the clipboard, or use Add screenshots. Each thumbnail has a remove control if you change your mind.
A file in another format is refused with “Screenshots must be PNG, JPEG or WebP”, and an oversized
one with “Each screenshot can be at most 4 MB”. Shrink or re-save the image and try again.
What is sent
Your report carries the title, the description, the surface you picked if you picked one, your screenshots, and the page you were on, which Cortex attaches for you. That is all. Reports stay inside Cortex and reach the team, the title and description are encrypted at rest, and nothing is forwarded to a public tracker. Cortex does not publish a mailbox for bug reports. The dialog is the channel, which is also why a guest cannot file one: a report needs an account to come back to.When a report will not send
Reports that belong somewhere else
A mistake on this site
Documentation lives in its own public repository. A page that is wrong, stale or missing belongs
there rather than in the product dialog.
A security weakness
A suspected vulnerability is not a bug report. Cortex Bounty has its own intake and its own
scoring.
Related
- Troubleshooting for what a message in the product means.
- Problem catalog for the code on a failure card.
- System status for outages and maintenance windows.
- Frequently asked questions for the short answers.
- File a report for security findings.