
Your code can pass its tests and still become harder to change. Dependencies spread across modules, circular imports creep in, and a simple feature starts touching parts of the application it shouldn’t. ArchPulse makes those relationships visible—and gives developers a way to act on them. At its heart is an interactive dependency graph that gives developers and IBM Bob a shared view of the codebase. It reveals how files and modules connect, highlights architectural violations, and helps both the developer and Bob understand why a problem exists. That shared picture makes it easier to discuss a repair and understand its impact. Built as a local MCP add-on for IBM Bob, ArchPulse combines dependency analysis with AI-assisted refactoring. It groups connected issues into focused repair cases, giving Bob relevant context to investigate and propose a change the developer can review and approve. The repair then has to stand up to verification. ArchPulse runs configured tests and typechecks, rescans the architecture, and checks that the selected violations are resolved without introducing new ones. Before-and-after graphs and recorded results show what changed and whether the checks passed. Designed for JavaScript and TypeScript projects, including monorepos, ArchPulse helps teams tackle architectural debt with a clearer understanding of their code and evidence behind each repair. Understand the dependency. Repair with evidence.
27 Sep 2026