responseiq 2.14.0

AI-Powered Infrastructure Copilot: The Self-Healing SRE.

ResponseIQ

"Don't just debug. Fix."

ResponseIQ is an AI-Native Self-Healing Infrastructure Copilot. Unlike traditional parsers that match regex strings, ResponseIQ reads your application logs, loads your actual source code into an LLM context, and generates surgical, context-aware remediation patches for incidents.

---

📸 See It In Action

Above: ResponseIQ scanning a crash log, reading the service.py file mentioned in the stack trace, and proposing a specific code patch.

---

✨ Key Features

• 🧠 AI-Native Analysis: Uses Generic AI reasoning instead of fragile regex parsing rules.
• 👁️ Context-Aware: Reads the local source files referenced in logs to understand why the crash happened.
• ⚡ Self-Healing: Can generate Pull Requests or apply patches directly (CLI mode).
• 🛡️ Battle-Tested: Includes "Sandbox Mode" to safely test remediation logic.

---

🚀 Quick Start (CLI Tool)

For developers who want to fix bugs in their local environment or CI pipeline.

1. Install

pip install responseiq

2. Configure an LLM

Choose one option:

Option A: Ollama (free, fully local — recommended)

# Install Ollama: https://ollama.com
ollama serve &
ollama pull llama3.2

# Add to .env in your project root:
echo "LLM_BASE_URL=http://localhost:11434/v1" >> .env
echo "LLM_ANALYSIS_MODEL=llama3.2" >> .env

Option B: OpenAI

echo "OPENAI_API_KEY=sk-..." >> .env

Option C: No config (rule-engine fallback) Works out of the box with no API key — uses a local heuristic parser.

3. Scan Your Logs

# Single file (JSON or .log or .txt)
responseiq --mode scan --target ./logs/error.log

# Whole directory
responseiq --mode scan --target ./var/log/app/

Example output:

------------------------------------------------------------
  ResponseIQ Scan Report
  Target : logs/error.log
  Status : SUCCESS
------------------------------------------------------------
  Scanned  : 1 message(s)
  Incidents: 1 found
------------------------------------------------------------
  1. [CRITICAL] Out of Memory Error
     Source     : ai
     Description: The system is experiencing a critical error due to an out of
                  memory condition caused by a resource leak or excessive allocation.
------------------------------------------------------------
  Tip: run with --mode fix to apply safe remediations.
------------------------------------------------------------

4. Shadow Mode (zero-risk demo)

Analyse all incidents and get a projected MTTR savings report — nothing is changed:

responseiq --mode shadow --target ./logs/ --shadow-report

---

🏢 Platform Server (Self-Hosted)

For Platform Engineers who want a centralized incident response API (webhooks for Datadog, PagerDuty, Sentry etc.).

Prerequisites

• Docker & Docker Compose
• LLM configured via .env (Ollama or OpenAI — see Quick Start above)

Running with Docker

# 1. Start the API and Database
docker-compose up -d

# 2. The API is now available at http://localhost:8000
curl http://localhost:8000/health

Development Setup (Local)

We use UV for lightning-fast dependency management.

# Install dependencies
uv sync

# Run the API server with hot-reload
uv run uvicorn src.app:app --reload

---

🧪 Development & Contributing

Workflow

1. Linting: make lint
2. Testing: make test
3. Format: make format

Project Structure

• src/cli.py: Entry point for the CLI tool.
• src/app.py: Entry point for the API Server.
• src/services/remediation_service.py: The core "Brain" that interfaces with the LLM.

License

MIT

---

⚠️ Disclaimer & Liability

This tool uses Generative AI to suggest infrastructure and code fixes. By using ResponseIQ, you acknowledge that:

1. AI Can Hallucinate: The suggestions provided may be syntactically correct but functionally wrong or insecure.
2. Human Review is Mandatory: You must strictly review all Pull Requests or patches generated by this tool before deploying them.
3. No Warranty: As per the MIT License, the authors assume no liability for system outages, data loss, or security vulnerabilities resulting from the use of this software.

For security reporting instructions, please see SECURITY.md.