How to Get All IDE Configs When Installing BMAD Method

Tisone Kironget — Fri, 20 Mar 2026 04:28:41 +0000

If you have tried installing the latest version of BMAD Method recently, you may have noticed
that the installer no longer includes Kilo Code and other popular IDEs during setup. Older
versions supported a full list — the newer versions have trimmed this down significantly.

This matters because BMAD generates IDE-specific configuration files during installation. If
your IDE is not in the installer's list, those files do not get created, and you have to set
them up manually.

Here is a simple workaround that takes less than two minutes.

The Problem

The latest BMAD installer no longer includes Kilo Code and other popular IDEs in the
selection step. If you rely on any of these, you will not get the configuration files
generated automatically.

Version 6.0.1 still includes the full list:

│  Selected tools:
│    • Kilo Code
│    • Windsurf
│    • GitHub Copilot

The Workaround

Install the older version first to generate all the IDE config files, then upgrade BMAD to
the latest version. The IDE files created during the initial install stay in your project
even after the upgrade.

Step 1 — Install the older version

npm install bmad-method@6.0.1

Step 2 — Run the installer

npx bmad-method install

Work through the setup prompts. When you reach the IDE selection step, select all the IDEs
you need. BMAD will generate the corresponding configuration files in your project.

Step 3 — Upgrade BMAD

Once the install is complete, upgrade to the latest version:

npm install bmad-method@latest

Your IDE configuration files from step 2 remain in the project untouched. BMAD core gets
updated. You get the best of both.

Why This Works

BMAD generates IDE config files during installation and writes them to your project directory.
The upgrade process updates the BMAD core package but does not overwrite or delete existing
project files. So the IDE configs persist across upgrades.

Found this useful? The BMAD community is active on
GitHub and
Discord.

Scrapamoja: A Python Web Scraping Framework

Tisone Kironget — Sat, 14 Mar 2026 20:21:57 +0000

I've been building Scrapamoja — a Python scraping framework built on one idea: you shouldn't need a different tool for every site you scrape.

🔗 GitHub: https://github.com/TisoneK/scrapamoja

What is Scrapamoja?

Scrapamoja blends the English word Scrape with the Swahili word Pamoja — meaning together. Scrape together. One scraper, many sites. One framework, many contributors.

It's also a quiet nod to Moja, Swahili for one — the idea that you shouldn't need a different tool for every site you want to scrape. One framework should be enough, and it should be good enough that anyone can extend it.

That philosophy shapes everything about how Scrapamoja is built. It's not a scraper — it's the infrastructure that makes scrapers reliable: handling anti-bot measures, selector drift, network failures, and browser resource leaks so you don't have to. New sites can be added by anyone, existing ones improved by the community, and the whole thing grows stronger the more people contribute to it.

Scrape together. Build together.

Core Framework Capabilities

🎯 Intelligent Selector Engine

The selector engine is the heart of Scrapamoja. Instead of brittle single-selector lookups, it uses a multi-strategy approach — CSS, XPath, and text-based selectors can all be defined for the same element. Each strategy is weighted, and the engine picks the best match with a confidence score. When a selector fails, it falls back gracefully rather than crashing. Selectors are defined in YAML, not hardcoded, making them easy to maintain without touching Python.

Site → Sport → Status → Context → Element

🛡️ Resilience System

Built around the assumption that things will go wrong. Automatic retries with exponential backoff, failure classification (network vs. selector vs. parse errors), checkpoint-based recovery so long scrapes can resume, and a coordinator that ensures graceful shutdown even mid-scrape.

🕵️ Stealth & Anti-Detection

A dedicated stealth module handles fingerprint randomization, human-like behavior simulation, consent popup handling, and proxy rotation. Sites that actively fight scrapers are manageable targets.

🔍 Snapshot Debugging

When a scrape fails, Scrapamoja captures a full snapshot: the page HTML, a screenshot, structured logs, and selector resolution traces — all correlated by session ID. Debugging a failure means looking at exactly what the browser saw, not guessing.

📊 Telemetry & Observability

Structured JSON logging with correlation IDs, built-in metrics collection (execution time, success rates, selector confidence distributions), and alerting hooks. Production scrapers need production-grade monitoring.

🌐 Browser Lifecycle Management

Browser and page pooling, session state persistence, tab management, resource monitoring (memory, CPU), and corruption detection. Long-running scrapers won't leak memory or leave orphaned browser processes.

🔀 Hybrid Extraction Modes

Scrapamoja chooses the optimal extraction method based on each target site's architecture:

Mode	Description	Use Case
DOM Mode (default)	Navigate with browser, extract from HTML	Sites requiring full rendering
Direct API Mode	Skip browser, call APIs directly	Open APIs, millisecond latency
Network Interception	Capture API responses during browser session	Sites requiring browser initialization
Hybrid Mode	Browser once to harvest session, then direct HTTP	Sites requiring authenticated sessions

If you're building on top of the web, I'd love to hear what you're scraping.

👉 https://github.com/TisoneK/scrapamoja

DEV Community: Tisone Kironget