BobOps is an autonomous AI engineering organization that detects production incidents, performs root-cause analysis (RCA), proposes and validates fixes (security & QA), and opens production-ready pull requests on GitHub for human review.
⚠️ Important: BobOps uses shell-based automation and requires proper credentials. Do not run on untrusted systems.
ℹ️ Design goals: Low-code / No-code operation and a chatting-less system — actions are invoked via shell/modes, not by interactive chat.
- Real-time log monitoring and incident detection
- Automated root-cause analysis and contextual mapping to repository files
- Automated fix generation, validation (QA & security), and PR creation
- Non-interactive "Team of Bobs" modes for reproducible automation
- Web UI for incident visibility and manual escalation
- Prerequisites
- Python 3.8+ and
pip - PowerShell on Windows (recommended)
- Bob shell integration (follow IBM Bob installation instructions)
- Git and GitHub credentials configured for the environment
- Git Token for automatic PR creation
- Python 3.8+ and
- Install Python dependencies
pip install -r requirements.txt- Install or place Bob modes
- Copy your
.bobfile(s) (custom modes) into your user profile directory as described by Bob.
- Copy your
- Start the UI server
# Windows
uvicorn app:app
# Linux / macOS
uvicorn app:app- Open the UI: http://localhost:8001
- Connect a repository — enter the full repository URL or owner/repo name.
- Start monitoring — the "Team of Bobs" will begin watching logs in real time.
- Reproduce or wait for an error — incidents will appear in the UI.
- Inspect an incident and click to invoke Bob (choose a mode/role).
- Bob will attempt an automated fix, run validations, and open a PR when ready.
- Review and merge the PR after human validation.
- A lightweight monitor watches runtime logs and surfaces incidents to the UI.
- Each incident is enriched with file / stack trace mapping to the repository.
- The selected Bob role runs non-interactive shell sequences to generate and test patches.
- If tests and checks pass, a Git branch and PR are created automatically.
- app.py — main web server and UI entrypoint
- monitor_pool.py — monitor orchestration
- monitor_worker.py — per-repo monitoring worker
- sockethandler.py — socket comms for UI updates
- workflow.py — fix workflow orchestration
- agents/ — role-specific automation scripts (e.g.,
developer_bob.py,qa_bob.py) - requirements.txt — Python dependencies
Below are quick view of the system.
| Landing page | Connect a Repository |
|---|---|
![]() |
![]() |
| Existing Repositories | Incident Tracking & Monitoring |
|---|---|
![]() |
![]() |
⚠️ Warning: BobOps runs shell commands and performs automated changes. Always:
- Use a dedicated machine or container with restricted credentials.
- Ensure GitHub tokens are scoped minimally and stored securely.
- Review PRs before merging — automated fixes may need human judgement.
- If Bob shell commands fail on Windows, run PowerShell as Administrator and follow IBM Bob's installation notes.
- If the UI doesn't start, check process logs in the console where
app.pywas started.
- Add or improve
agents/role scripts to extend automation. - Open issues or PRs with reproducible examples.
- Run tests (if present) and follow repo coding style.
See LICENSE.






