CodeVerse: Watch IBM Bob Debug Your System

PROBLEM When production breaks, the hardest part isn't writing the fix. It's finding where to look. An on-call engineer gets a vague ticket ("payment failed at checkout"), a wall of logs and a codebase spread across many services. Red herrings in the logs pull attention the wrong way, and root-causing means opening file after file to rebuild a mental model that static docs and diagrams never provide. When AI assistants help, their answers arrive as text that engineers must re-verify line by line, because an AI can sound confident and still be wrong. SOLUTION CodeVerse is a visual incident-debugging platform powered by IBM Bob. It turns a repository into a living 3D city: services become districts, files become towers, API routes become gateways, the database becomes a glowing core, and real calls flow as light between them. Then you watch Bob investigate an incident inside that city. Every file Bob reads lights up as Bob's probe arrives, subagents split off in their own colours, Bob's reasoning plays as captions, red herrings are ruled out, and the failing request animates until it fractures at the exact failure point. Each citation opens the exact line of code. Bob's fix appears as a diff, and when the tests pass, the broken path heals to green. TRUST, BUILT IN CodeVerse separates what is proven from what is reasoned. A deterministic static analyzer builds the city; Bob supplies the understanding. A Grounding Score checks every file, line, symbol and call path Bob cites against the real code, and anything that doesn't exist appears as a flickering "phantom". USERS AND INTERACTION On-call and backend engineers, tech leads reviewing incidents, and developers new to a codebase. On the web, they follow three chapters: explore the system, watch Bob investigate, see it fixed. Inside Bob IDE, developers run the same investigation with one slash command: /codeverse-investigate. The public site replays real recorded Bob sessions, so anyone can explore it safely with no credentials involved. DEMO Our sample checkout system contains a real seeded bug: a customer profile never initialised after SSO sign-in, causing a null reference in payment, plus three red herrings in realistic logs and an incident ticket. Bob read the ticket and logs, traced the failure with subagents, ruled out the red herrings and fixed it with a one-line change. Tests went from 6/7 to 7/7. [Bob's real investigation time and number of files opened.] WHAT MAKES IT UNIQUE Most AI tools show the output. CodeVerse shows the reasoning, spatially, and verifies it. Debugging shifts from reading dozens of files to watching a grounded, replayable investigation, and every replay can be shared as a link so a whole team understands an incident in minutes.