Operators
Report a problem
Two things live in the dashboard chrome for when something looks wrong: the report button in the top bar, and the platform status chip at the bottom of the sidebar.
Check status first
The chip in the sidebar footer shows Camper’s current platform state:
| Light | Meaning |
|---|---|
| Green | All systems operational |
| Amber | Degraded performance — Camper is up, something is slow or partial |
| Red | Service disruption — a major outage is in progress |
Select the chip to open the full status page with incident history and subscribe for updates.
If the light is amber or red, an incident is already open and you do not need to file a platform-wide report. If it is green and Camper is still misbehaving for you, that is worth reporting.
Send a report
Select the bug icon in the top bar, on any page.
- Pick a type — Bug, Idea, or Question.
- Describe what happened. On a bug, select Use the bug template to get the three lines that matter: what you did, what you expected, what happened instead.
- On a bug, say how much it is blocking you — Blocked, Working around it, or Minor. Triage weighs your answer; it does not override a real severity either way.
- Select Send report, or press <kbd>⌘</kbd><kbd>↵</kbd>. Sending runs a short proof-of-work check — no image puzzles.
Camper keeps what you typed if you close the dialog by accident: reopen it in the same browser tab and your draft is still there. A sent report shows a reference id — quote it if you follow up with support.
Reports are visible to operators in Activity for your workspace, so your team can see what has already been raised. The Camper team triages the report and, when it is a product bug or idea, tracks it as an internal engineering issue. Workspaces are rate-limited so a busy day of testing cannot flood the queue.
What gets attached
Open We attach your workspace, your email, and this page in the dialog to see the exact values before you send. Camper attaches:
- your description, your workspace, and your email address
- the dashboard page you were on
- your browser, operating system, window size, locale, and time zone
- any browser errors Camper recorded on your pages since you loaded the tab
Nothing else from the screen is captured — no screenshots, no form contents, no keystrokes, no network traffic. If a report needs a screenshot or a resource id, include it in the description.
Camper strips email addresses, ids, and anything that looks like a token or key from a report before it reaches triage or an engineering issue. That is a safety net, not a licence: do not put passwords, API tokens, or SCIM tokens in a report. Camper will never ask for a credential this way.
What happens next
Triage classifies the report, drafts a summary, steps, and expected-versus-actual, and — for ordinary bugs and ideas — opens an engineering issue that carries no reporter identity. Anything that looks like a security problem, or anything severe, waits for a person at Camper to read it first.