Overcode: a calm signal for your workspace

A working developer maintains more than one repository, watches more than one pull request, and switches between branches, worktrees, and stashes during a normal day. The state is scattered: GitHub, GitLab, the local working tree, the watcher logs, the stash list. There is no single place to answer "what changed, and what needs my attention now." Overcode is a native desktop application that consolidates local Git state, GitHub, and GitLab into one operator workspace, and applies IBM watsonx.ai Granite to translate that state into actionable answers. Repositories are read directly from disk through simple-git in an isolated Electron utility process. Remote provider data is pulled per-account through user-scoped OAuth and cached locally. The data plane is local; there is no Overcode backend. Eleven AI features routed through a single callGranite entry point cover impact analysis on uncommitted diffs, conventional-commit drafting, repository onboarding briefs, plain-language stash labels, worktree vs base-branch comparison, code explanation at any reference, issue triage, daily standup rollups, and three pull-request reviews (full summary, hunk-level inline feedback, per-file deep dive). Each response is validated against a feature-specific JSON schema with one repair retry, then a local-data fallback so a parse error never reaches the panel. IBM Bob built the application. Every meaningful task, from IPC scaffolding and the activity feed to the AI panel, the GitHub and GitLab clients, the commit graph, and the eleven feature implementations, was produced in Bob IDE through the Plan to Code workflow. The bob_sessions folder in the repository contains the verbatim Bob task-history exports. Bob is the build-time partner. watsonx.ai Granite is the runtime intelligence inside the shipped app. The split is intentional and is the core of the submission story.