Remedy Your users do not just create tickets. They can start the repair process.
A small in-app Remedy Pill turns a visible problem into a structured engineering incident without executing raw user instructions.
Report the defect where it happens
A user, tester or support colleague opens Remedy Reporter inside the affected web or mobile screen. They explain what they expected, what happened and any relevant steps while the context is still fresh.
Evidence, subject to configuration and privacy controls
A report may include a description, screenshot, route or screen, application version, build, recent bounded events, relevant errors, device or runtime information and other diagnostic context. The project controls what can be collected.
- Description and optional screenshot
- Route, screen, version and build
- Bounded recent events and relevant errors
- Device and runtime context permitted by policy
Free text is not a coding command
Remedy sanitises and structures the report before diagnosis. User-provided text does not pass directly into a coding agent as executable instruction. The resulting incident combines the observation with authorised evidence and project policy.
Frequently asked questions
Is Remedy Reporter a website bug reporting widget?
Yes, the Reporter/Pill is the embedded human-facing entry point, designed for web and mobile applications.
Can it capture screenshots?
Screenshot evidence can be supported subject to product configuration, consent, privacy controls and the application environment.
From bug report to verified fix.
See how Remedy connects evidence, diagnosis, repair, deterministic checks and production verification.
Explore the complete workflow →