Bob's CLI

The "sovereign by design" framing is appealing, and credit where it's due, I checked the npm package and it's MIT with a public repo, so the code is actually auditable. For a tool that reads all my files and profiles how I work, that's exactly the right answer to "why should I trust it," and it's worth shouting louder than you do.One thing I'd still love clarified: you mention "Built with Firebase," which is Google infrastructure, while also promising nothing leaves my machine. So where does the "behavioral DNA profiling" actually live, local on disk, or synced anywhere? Spelling out exactly what touches the cloud (auth? telemetry? nothing?) vs. what stays local would make the sovereignty pitch land even harder. Not a gotcha, the open code already won me over, just closing the last gap :)

You say updates ship daily. For users who intentionally keep everything local and don't update constantly, how do you avoid version drift between what you're demonstrating and what they're actually running?

Running local models is nice but keeping everything on my own machines is the part that caught my attention

The local first approach is what caught my eye. Feels like a very diff tradeoff compared to cloud based coding agents.

Keeping everything local is honestly the most interesting part for me. A lot of people love AI tools still hesitate to give them full access to their codebase.

@kemone_phillips @amanda_phillips6 Local-first is a strong direction for coding tools. The more an AI assistant learns from your workflow, the more important it becomes that developers understand what context is being used and can keep control of the environment.

Nice angle. For a local-first coding CLI, the thing I’d want to see is how it handles the boring failure cases: failed tests, half-applied edits, and leaving a diff that is easy to review or roll back.

Local-first for a coding CLI is a genuinely interesting architectural choice. Keeping code context local avoids round-trip latency and the data-residency concern that blocks enterprise adoption of cloud-based tools. What's powering the 'adapts to you' part? Is it RAG over the local codebase, fine-tuning on usage patterns, or closer to behavioral prompting based on past interactions?

This looks promising, especially for builders who prefer keeping everything local. I'd love to know what the recommended hardware setup is for running this effectively. Congrats on the launch!

Local-first with auto-detected local models is a great angle, especially the no-API-bill part. Curious about the day-to-day feel: on a normal laptop with a local model, is it fast enough to keep in the loop while coding, or more of a background reviewer?

Congrats on the launch! The idea of an AI partner that remembers project context and works around a developer's limited time is really compelling.

Hey Everyone 👋 Kemone here, founder of Bob's Workshop.I built Bob's CLI because I was tired of a lie this industry keeps selling: that you need to quit your job, raise capital, and go all-in to build something real. That's gatekeeping dressed up as hustle culture. The truth? You can keep your day job, pay your bills, and still ship production-grade software — if your tools respect your time.The Reality for Most Builders:You're a developer with a 9-5. You have a side project — maybe a SaaS, maybe an app, maybe something that could change your life. But you only get 45 minutes on the train. An hour before bed. A lunch break at your desk. And every time you sit down, you waste half that time just remembering where you left off.What Bob's CLI Actually Solves:Bob is a senior AI engineering partner that lives permanently in your terminal. He remembers your entire project architecture. He remembers your last conversation. He remembers YOUR patterns — how you think, how you decide, how you build. So when you open that terminal at 6am before work, there's zero ramp-up time. You're immediately productive.But here's where it gets real — SovereignLink. Start bob serve on your desktop before you leave the house. Now your home machine is a personal AI cloud. On the bus? Send commands from your phone through the web app. At a coffee shop with a Chromebook? bob remote chat "add the payment webhook". Your desktop at home receives it, reads your actual files, generates the fix, writes it to disk. You come home and the feature is waiting for you.No dropout required. No VC required. No risk required.Just a developer with a vision, a terminal, and a tool that refuses to waste their time.What Makes This Different From Every Other AI Tool:Runs on YOUR hardware — zero API costs on the free tierYour code NEVER leaves your machine unless you chooseAuto-detects your local model — type bob chat "hello" and it just worksBehavioral DNA profiling — Bob adapts to your style over timeConversation forking — explore ideas without losing your threadAutonomous code review — Bob finds bugs while you sleepOne command to push: bob push "shipped it" — stage, commit, push, doneWho This Is For:The developer who drives for DoorDash but has an app idea. The teacher coding between classes. The parent building after bedtime. The full-time employee who's also a full-time dreamer. You don't need to bet your livelihood to build something incredible. You just need a tool that multiplies the limited time you have.Install it:Bashpnpm add -g @bobsworkshop/cli
Your AI. Your hardware. Your schedule. Your future.I'm in the comments all day — tell me about the project you're building in the margins of your life. I guarantee Bob can help you ship it faster. 🌱