Skip to main content
If you can’t find a solution here, use the Feedback button at the bottom of the kipmox panel to contact support.

​
Installation & sign-in

The extension may not have activated yet. kipmox activates when a supported file type is opened.
  1. Open any .cls, .trigger, .js, or .html file
  2. Save the file once to trigger activation
  3. If the icon still doesn’t appear, run Developer: Reload Window from the Command Palette
kipmox prompts you to sign in with a magic link to keep using the Free plan. If it doesn’t appear:
  1. Run Developer: Reload Window from the Command Palette
  2. Make the request again — the prompt should appear
  1. Run Developer: Reload Window from the Command Palette
  2. If the issue persists, try signing out and signing back in from the kipmox panel

​
Deployment

The deploy option only appears for supported file types. Make sure the file you are right-clicking is a .cls, .trigger, .js, or .html file.If the option still doesn’t appear:
  1. Save the file once to trigger kipmox activation
  2. Run Developer: Reload Window from the Command Palette and try again
Make sure you are deploying to the correct org. Check your active Salesforce CLI default org:
  1. Look at the org name in the VS Code status bar at the bottom of the screen
  2. Click it to change to a different org if needed
kipmox always deploys to whichever org is set as your Salesforce CLI default.
Your Salesforce CLI org session may have expired. Re-authenticate:
  1. Click the org name in the VS Code status bar
  2. Select Authorize an Org and follow the login flow
  3. Try deploying again
LWC components deploy as a full bundle — all files in the component folder are deployed together. If another file in the bundle has an error, the deploy will fail even if you only changed one file.Check the Deploy Errors panel for the specific file and line causing the failure — it may not be the file you edited.
kipmox requires the Salesforce CLI to be installed and available in your terminal PATH.
  1. Run sf --version in your terminal to verify it is installed
  2. If not installed, download it from developer.salesforce.com/tools/salesforcecli
  3. After installing, run Developer: Reload Window in VS Code and try again

​
Deploy Errors panel

kipmox only monitors deploys triggered via kipmox: Deploy to Org. If you used the Salesforce CLI directly or an SFDX command, kipmox will not detect the errors.Always use kipmox: Deploy to Org from the right-click menu or Command Palette to get automatic error detection.
Check the following:
  1. Make sure you haven’t hit your Free-plan limit — see Plans & Limits
  2. Check your internet connection — Explain requires an active connection in online mode
  3. On Pro, switch to Offline Mode to keep working locally with no network round-trip
Bulk Analyze & Generate Fixes — fixing every deployment error at once — is a Pro feature. On the Free plan, work through errors one at a time with Explain.Upgrade to Pro → kipmox.com
  1. Click Undo Fix in the notification that appeared after applying, or use Cmd+Z / Ctrl+Z to revert
  2. Review the Confidence and Risk ratings before re-applying
  3. For Low Confidence fixes, consider applying the change manually using the explanation as a guide
  4. Use the chat input at the bottom of the panel to ask kipmox for more context or an alternative approach
Some errors are layered — fixing one can reveal another underneath. Run kipmox: Deploy to Org again. kipmox will open the panel with the next set of errors and repeat the fix cycle.
  1. Check your internet connection
  2. Check you haven’t hit your Free-plan limit — see Plans & Limits
  3. Run Developer: Reload Window from the Command Palette and try again

​
Code Analysis

Explain & Fix All Warnings is a Pro feature and is not shown to Free plan users. On the Free plan, use the kipmox: 💡 Explain & Fix CodeLens link above each individual flagged line.Upgrade to Pro → kipmox.com
One-click Apply Fix and bulk Fix All are Pro features. On the Free plan, kipmox shows the full explanation and the fixed code — copy it and apply it to your file manually. This is the same for warnings and deployment errors.Upgrade to Pro → kipmox.com
After applying a fix, kipmox saves and re-analyses the file automatically and updates the warnings. If a warning persists, the fix may not have fully resolved the issue — click kipmox: 💡 Explain & Fix again for further analysis.
Start with 🔴 Critical issues — these are the most likely to cause deployment failures or governor limit errors. Address 🟡 Warning issues next, then 🔵 Info items at your own pace.See the Code Analysis Rules page for a full explanation of each rule.

​
AI requests & plan

The Free plan includes 15 fixes and 2 documents every 4 hours; each resets 4 hours after you reach it. You can still deploy, view warnings, and navigate normally while you wait.Upgrade to Pro → kipmox.com
The kipmox panel header shows how many Free requests you have left, updating after each AI action. The Free plan includes 15 fixes and 2 documents every 4 hours, counted separately. See Plans & Limits.
  1. Run Developer: Reload Window from the Command Palette
  2. If it still shows Free, sign out and sign back in from the kipmox panel
  3. If the issue persists, use the Feedback button in the panel to contact support

​
Performance & connectivity

Response time depends on your internet connection and current AI service load. If responses are consistently slow:
  1. Check your internet connection
  2. Try again in a moment — response times vary with model load
  3. Consider switching to Offline Mode for faster local responses (Pro only)
The Offline indicator in the panel header means kipmox cannot reach the AI service.
  1. Check your internet connection
  2. If you are on a corporate network, check whether outbound HTTPS traffic is restricted
  3. If you have Offline Mode set up (Pro), switch to it with kipmox: Toggle Online / Offline Mode
kipmox requires outbound HTTPS access to function in online mode. If your network restricts outbound traffic, contact your IT team to whitelist the kipmox backend.Alternatively, set up Offline Mode (Pro) to run kipmox fully locally with no outbound connections required.
kipmox analyses a file when you save it. If VS Code feels slower on large files:
  1. Run Developer: Reload Window to clear any stale processes
  2. If the issue persists, use the Feedback button in the panel to report it with details of the file size and type

Plans & Limits

Understand request limits and what Pro unlocks

Privacy & FAQ

How kipmox handles your code and data