Jev as the cheap decision layer in a local Claude Code second brain
A local Claude Code setup with persistent memory, browser control and automation routes tiny forks like which file or retry-or-stop to Jev, which returns a choice with a probability in 70-500ms.
It is becoming f*cking dangerous: when Anthropic disclosed this, they didn't even realize they were opening a Pandora's box 1. Create a folder named SECOND BRAIN on your PC 2. Launch Claude Code inside this folder and install GWS CLI (to gain access to your Gmail, Calendar, and Drive) 3. Create a subfolder named MEMORY inside the main folder 4. Place a CLAUDE.md file in the main folder and add a rule to save all key details to the MEMORY folder 5. Install Graphify from GitHub to link your notes and build a knowledge graph 6. Install Playwright so Claude can control a web browser 7. Set up skills to merge everything into an automation executable with a single command The whole setup process takes around 10 minutes now the part nobody wires up. every one of those steps has the same slow spot: a tiny fork that doesn't need a thinker. which file. which tool. retry or stop. keep this chunk or drop it. that's where Jev fits. it can't write a word. it returns the choice with a probability in 70 to 500 milliseconds, at $0.042 per million input tokens, output free. that's thousands of decisions for the cost of one LLM call. > let Claude think. > let Jev decide what deserves Claude. > let code do the actual work. what you end up with: the full Anthropic stack running on your own machine - persistent memory, a swarm that explores in parallel, a real browser, your mail and drive, and Jev making the thousands of tiny calls in between the step-by-step setup is in the article below. save this before your next session.
This post quotes another post: x.com/beaver_0x/status/2105662726655590821