iSolveAI

An AI-assisted Chrome extension for turning technical error messages into clear explanations and practical troubleshooting steps.

Overview

iSolveAI is a Chrome extension built to help IT support technicians troubleshoot unfamiliar errors faster. A user can enter or select an error message, send it for AI analysis, and receive a concise explanation together with step-by-step troubleshooting guidance.

The project combines a browser extension UI with a Node.js backend and an AI provider, while keeping API credentials out of the extension code.

Features

• Analyze errors from Windows, macOS, Linux, and web applications
• Generate plain-language explanations and troubleshooting steps
• Analyze selected text through the browser context menu
• Keyboard-first workflow: Enter to analyze, Shift+Enter for a new line
• Copy generated analysis to the clipboard
• Scrollable result card for longer responses
• Support for a backend AI fallback
• Clean, lightweight Chrome extension popup

How It Works

Error message / selected text
            │
            ▼
     Chrome Extension
            │
            ▼
       AI analysis
      ┌─────┴─────┐
      ▼           ▼
 Built-in AI   Node.js backend
                  │
                  ▼
             AI provider
            │
            ▼
 Explanation + troubleshooting steps

Tech Stack

Layer	Technologies
Extension	Chrome Extension APIs, HTML, CSS, JavaScript
Backend	Node.js
AI	Google Gemini / OpenAI-compatible backend integration
Configuration	Environment variables

Project Structure

iSolveAI/
├── backend/          # Node.js AI backend
├── popup.html        # Extension popup
├── popup.js          # Extension logic
├── popup.css         # Popup styling
├── manifest.json     # Chrome extension manifest
└── README.md

Getting Started

1. Clone the repository

git clone https://github.com/Luke-Manyamazi/iSolveAI.git
cd iSolveAI

2. Load the extension

1. Open Chrome and visit chrome://extensions/.
2. Enable Developer mode.
3. Select Load unpacked.
4. Choose the repository directory.

3. Configure the backend

cd backend
npm install

Create a local .env file containing the AI provider credentials expected by the backend. Never commit API keys or other secrets to Git.

Start the backend using the repository's Node.js entry point, then ensure the extension is configured to call the correct local API endpoint.

Engineering Highlights

• Designed around a real IT-support workflow rather than a generic AI chatbot
• Browser context-menu integration for faster troubleshooting
• Separation between extension UI and server-side AI credentials
• Fallback architecture for different AI execution environments
• Practical focus on reducing time spent searching documentation and forums

Roadmap

• Dark mode
• Error categorization by operating system and application type
• Caching and rate limiting for repeated analyses
• Additional AI model providers
• Hosted backend deployment
• Improved diagnostics and troubleshooting history

Security Note

API keys and secrets should only exist in local environment variables or the hosting provider's secret store. Do not place provider credentials in popup.js, manifest.json, committed .env files, or documentation.

License

MIT License.

Author

Luke Manyamazi