On this page
01Step by step
- Run the command line setup script in your project root to install the package, configure your application entry point, and automatically set up the Model Context Protocol connection for your AI editors.Screen: Terminal
- Alternatively, install the package manually via npm if you prefer not to use the automated command line tool.Screen: Terminal
- Import the SDK into your application entry point and initialize it with your project API key and configuration settings before any other code runs.Screen: Code Editor
- Manually capture handled exceptions by passing the error object and optional context details to the capture error function.Screen: Code Editor
- Associate user identities with subsequent event tracking by calling the identify user function after a user successfully authenticates.Screen: Code Editor
- Ask your connected AI assistant about open production issues to verify that the SDK and Model Context Protocol server are communicating properly.Screen: AI Chat
02Questions
How far back can I view event history on the Pro plan?
The Pro plan retains event data for up to 90 days.
Source: prodfixai.comWhat security risks does ProdFix check during code deployments?
It checks runtime deploys for leaked secrets, Content Security Policy issues, and vulnerable dependencies.
Source: prodfixai.comHow does the performance monitoring module detect site regressions?
It monitors Core Web Vitals across real user visits and alerts you if a deploy decreases speed.
Source: prodfixai.comHow long is event data retained on the Free plan?
Data captured on the Free plan is retained for 14 days.
Source: prodfixai.comCan I use ProdFix with the Zed editor?
Yes. ProdFix connects to Zed via its MCP server.
Source: prodfixai.comCan I test the security scanner without creating an account?
Yes. You can run the free security scan without registering for an account.
Source: prodfixai.com