Add support for IBM Bob IDE and CLI tools#540
Conversation
|
Thanks for adding IBM Bob support. Main has no Bob integration, so this is useful and not superseded, but the current head cannot merge safely. Bob Shell's documented global MCP path is ~/.bob/mcp_settings.json, not ~/.bob/mcp-config.json, so this branch writes to a file Bob Shell will not read. Please use the current “Bob Shell” name, align STDIO output with IBM's command-based schema rather than adding type: "stdio", and make Bob IDE auto-detection conditional so --platform all does not create .bob/mcp.json in every repository. Add tests for both exact paths, preservation of existing servers, idempotence, CLI choices, and all-platform detection, then rebase on current main and run the full CI matrix. The current head has only GitGuardian coverage. |
Reconcile PR #540 on current main with documented Bob Shell and Bob IDE paths, command-based STDIO entries, conditional detection, lifecycle tests, and symmetric uninstall coverage. Co-authored-by: mohan-kumar-m2 <243704502+mohan-kumar-m2@users.noreply.github.com>
|
Maintainer follow-up: the IBM Bob integration from this reconciliation has been reverted from The code now lives in draft PR #656, which is explicitly blocked on real-client discovery, tool invocation, reinstall, and uninstall checks in both Bob applications. |
IBM Bob is a AI-Powered Development Partner which assists developer across Software Development lifecycle right from feature planning to pr review, Having Bob support in code-review-graph enables thousands of developers using Bob across the globe to leverage code-review-graph to use AI efficiently