Code-Boy

Code Boy solves a problem almost every developer knows: after a break, a context switch, or returning the next day, the code is still there—but the mental context is gone. Developers have to reconstruct what they were doing from open tabs, terminal history, Git changes, failed tests, diagnostics, TODOs, and memory. This wastes time and makes it easy to miss unresolved work. Our solution is Code Boy, a working VS Code extension with ContextBack, a local developer memory layer that continuously reconstructs the state of a project. ContextBack records lightweight development signals such as edited files, Git activity, diagnostics, test results, terminal command metadata, TODOs, and session history. When the developer returns, it shows a “What I did yesterday” recap, files to revisit, open threads, test state, and a suggested next step. Code Boy turns this technical state into an ambient visual companion. It reacts to real project health: it becomes concerned when there are failing tests or diagnostics, reflects active coding and focus, and celebrates only when a known blocker is actually resolved. A commit by itself is never treated as proof of a fix. IBM Bob is integrated into the deeper analysis workflow. Developers can opt in to send bounded, filtered code samples to Bob for focused reviews. When a blocker needs deeper investigation, Code Boy prepares a human-reviewed prompt containing the relevant context for Bob IDE. Bob can then inspect the repository, investigate the issue, and help with the fix. We also used Bob IDE directly during development for tasks such as identifying missing test coverage and performing a full-project review, with task session consumption evidence committed in the repository. The main target users are software developers, students, solo builders, and teams that frequently switch between projects or return to unfinished work. Interaction happens directly inside VS Code, without forcing developers into a separate dashboard or replacing their normal workflow. What makes Code Boy unique is the combination of developer memory, project-health awareness, and an expressive companion. It does not try to be another generic coding chatbot. Instead, it remembers what happened, makes unfinished work visible, and gives IBM Bob better context when deeper reasoning is needed. Privacy and control are central to the design. ContextBack stores its session history locally. Bob reviews are opt-in, API keys are stored in VS Code SecretStorage, sensitive files and common secret patterns are filtered, and only bounded samples are sent. The result is a practical workflow for reducing context-recovery time, surfacing blockers earlier, and helping developers continue work with less friction.