wtf is critcache?

critcache is a command line tool that reviews the code in your project by sending files to AI models through a service called BTL Runtime, and then shows you, live in your terminal, how much of that review was served from cache and how much money that cache saved you. The core idea is that BTL Runtime already tracks whether each AI response came from a cache or was freshly generated, along with the cost and time saved, but those details are normally hidden in technical response headers most people never check. critcache pulls that information out and displays it plainly as the tool runs. When you point it at a repository, it picks out the most relevant source files, sends each one to an AI reviewer at the same time rather than one after another, and prints a line per file showing whether it was a cache hit or miss, how long it took, and how much was saved. It also writes a full written report to a markdown file. A separate compare command runs the same analysis twice back to back on the same files, so you can see the cache hit rate and total time improve between the first, cold pass and the second, warm pass. Other commands let you watch a project continuously and re-review files automatically each time you save, review only the files that changed compared to another branch or commit, review your current uncommitted changes, check which AI providers connected to BTL Runtime are healthy, and get a score on how well your own prompt setup is likely to benefit from caching. You can try it without any account by running it in a mock mode that simulates the whole process locally with fake cache behavior. For the full experience, you need a free API key from the BTL Runtime service. It requires Node.js version 18 or newer, and there are no license details included in what was shown.