I talked about the soft launch of Tight Code during Brandon Hancock’s developer call last night. Tight Code reviews your code every time you run git push. It works directly with Claude Code, so there’s no new editor or workflow to learn. Here’s what happens:​ 1. You push your code normally. 2. Tight Code scans the changes for secrets and redacts anything sensitive. 3. Multiple AI reviewers check security, code quality, performance, documentation, and release readiness. 4. One verdict and a clear list of findings appear in the dashboard. 5. Claude Code helps you work through each finding—but you approve every decision. It can run quietly in the background or stop a push when it finds something critical. If an AI provider is unavailable, it fails open so your work isn’t trapped. What makes it different:​ - It reviews at push time, not only when you open a pull request. - It uses Anthropic and OpenAI models for independent perspectives. - Secrets are removed before any AI model sees the code. - Your source code is never stored in the dashboard. - It remembers why you dismissed something as a false positive, so the same bad recommendation doesn’t keep returning. - It works with the Claude Code and Codex subscriptions you already have. So far, Tight Code has run 1,176 real reviews across 19 repositories, raised 2,157 findings, and caught 96 critical issues. About 92% of its findings were fixed, while only 8% were judged to be noise. The stack, for anyone interested:​ - A local Homebrew-installed Git hook and CLI - Claude Code with optional OpenAI Codex reviewers - A Next.js and TypeScript dashboard hosted on Vercel - Supabase for review history and reporting - Stripe for subscriptions - No source code or unredacted secrets stored in the cloud See the video, sign up, and install it:​ https://tightcode.dev Tight Code is normally $39/month. Brandon’s community can use code BRANDON20 to take $20 off each of the first three months, making it $19/month for those three months.

🦸🏻THIS IS A BRANDON WEEK, Come say hi!!!🦸🏻 Two fresh model drops, a token-budget experiment that built a whole site in ~3,000 tokens, and Patrick's Codex plan somehow dead by noon — last week was a lot. If you missed it, the "tokens per task completed" metric alone is worth the catch-up. 📞 HOW THE CALLS WORK The calls can run 2+ hours. We want to make sure we're respecting everyone's time. Especially those of you who actually show up. Here's the structure: 👉 Reply to this post with your questions before the call 👉 If you submit a question and you're on the call, you go first 👉 We work through questions in the order they came in 👉 Then we open it up for everyone else If you can't make the call but want your question answered, drop it in the comments. We'll get to it. But priority goes to people who are there. The goal is simple: if you're taking the time to show up, you shouldn't have to wait behind questions from people who aren't even on the call. Plenty of threads still open from last week: Ty's head-to-head test of T3 Code vs. his CMUX setup, Daniel's weekend experiment with Honcho.ai, and Patrick's deep dive into JEV as a decision-making router. If you've been trying any of these yourself — or want to know how they turned out — bring your questions. 🔗 ZOOM LINK (save this) https://us06web.zoom.us/j/81995207847?pwd=Xe6u6LmIQOmCP5VTnOwWYjDBfZNKGB.1 📅 WHEN Tuesday September 29th at 6PM ET Looking forward to seeing you on the call!