← Back
Complete

Context Cabinet

A macOS desktop app that finds and manages every Claude Code configuration file. Fifteen scattered config files, one place to deal with them.

Context Cabinet app icon

A tool for the tools

Claude Code uses ~15 scattered config files across global and per-project directories. Most developers don't know they exist. Context Cabinet finds them all and makes them manageable.

Context Cabinet dashboard showing sidebar navigation, stats cards, and quick actions

The Dashboard — stats, quick actions, and every config file type in the sidebar

The Story

Somewhere around my fifth Claude Code project, I noticed a pattern: I kept losing track of my own configuration. Claude Code has something like fifteen config files — CLAUDE.md, settings.json, keybindings, rules, skills, hooks, agents — scattered across your home directory and every project folder. I'd set something up, forget about it, set up something slightly different somewhere else, and wonder why nothing worked the way I expected.

To put it in terms I understand: it was like running a law practice where every case file is in a different building and none of them are labeled.

Context Cabinet is the filing system. A native macOS app that finds every Claude Code config file on your machine, shows you what each one does, lets you edit them with proper syntax highlighting, and lays out the scope hierarchy so you can see what's overriding what.

What It Does

Auto-Discovery

Scans global (~/.claude/) and per-project (.claude/) directories to find every config file automatically.

Smart Editor

CodeMirror 6 with syntax highlighting, info popovers explaining each file's purpose, and template-based creation.

Health Check

Project scanner with scoring that tells you what's configured, what's missing, and what you might want to add.

Scope Hierarchy

Tree view showing how global vs. project settings interact and which ones take precedence.

Command Palette

Cmd+K fuzzy search to jump to any file or action instantly. Two display themes (dark + warm taupe).

File Watching

Detects external changes to config files and updates the UI automatically. Edit anywhere, see it everywhere.

Files managed:

Built with Claude

Yes, I used Claude Code to build a tool for managing Claude Code. I'm aware.

This was the project that dragged me furthest from anything I'd done before. Electron, React, TypeScript, Zustand, CodeMirror, Framer Motion, Radix UI — six months earlier I could not have told you what any of those words meant, and I include "React" in that statement. Now there's a desktop app on my dock that uses all of them.

The interesting wrinkle was the audience. Everything else I've built is for my family or for fun. This is a developer tool — for people who actually know what they're doing. I had to think through UX conventions I use every day but had never implemented: command palettes, keyboard shortcuts, file watchers, tree views. It's one thing to use Cmd+K. It's another thing entirely to build Cmd+K.

I also learned more about Electron's architecture than I ever planned to. Main process, renderer process, IPC bridges, sandboxing. Claude was patient. I was not.