Vladislav Frigo

@AnthropicAI This is exactly the trust problem on the other side too — not just agent permissions, but whether the human deploying the agent actually understands what it built. Shipping with AI is solved. Owning what it shipped isn't. That's what codesip.dev is working on.

New on the Engineering Blog: The access and permissions we grant agents should evolve with their capabilities. In our own products, we set these parameters through sandboxing, which limits the scope of any potentially destructive actions. Read more: anthropic.com/engineering/ho…

@iamkarank5 codesip.dev — reads your entire codebase and explains it back to you. For the vibe coder who shipped with Cursor or Lovable and now can't fully explain what they built. Like a senior dev friend who already read everything.

Good Morning Devs 🌄 What projects you guys are working on

@sflorimm Understanding what you coded. Anyone can ship with AI now. The hard part is owning what you built well enough to explain it, maintain it, and fix it when users find the bug you didn't.

Developers, be honest What's harder than coding?

@Leohuynh57 No. Shame comes from not understanding what you shipped. The founder who built with AI and owns it — knows the tradeoffs, can explain the auth flow, spots the bug before users do — that's a real founder. The tool that built it doesn't matter. Ownership does.

Hey founders: Do you ever feel shameless calling yourself a founder when AI wrote most of your code?

@axeldelafosse @OpenAI @ycombinator Congrats! Curious how the Codex team thinks about the gap between shipping with AI and actually owning what you built. That's the problem I'm working on with codesip.dev — would love your perspective sometime.

Today is my first day at @OpenAI! I'm joining the Codex team. I'll be splitting my time between building the Codex app and working with developers/entrepreneurs to help them make the most of Codex. As a @YCombinator alum, I'm really looking forward to working with early-stage startups and couldn't be more energized about OpenAI's $2M investment in new YC startups. Despite OpenAI being the largest company I've been part of, it certainly feels like @sama, @gdb and the whole Codex team are in founder mode. I've never seen another startup move as fast as this team does. I'm truly honored to be joining such a brilliant team. As always, it's all about the people... so I'd like to thank @romainhuet, @dkundel, @coreyching, @ajambrosino, @embirico, @thsottiaux, and the rest of the Codex team for their trust. And thanks to @pankaj, @gilad, and @willhorn for believing in me, bringing me back to Silicon Valley after almost ten years, and giving me the opportunity to learn about AI.

@BrahimElghazi03 Honest answer: most builders I talk to don't use 10% of it. What actually gets used: one good model, one clear prompt, memory across sessions. The complexity is fun to build. But the tools winning right now are the boring ones that solve one real problem really well.

watching the ai agent ecosystem grow is wild agents that orchestrate other agents. skills managing prompts. models debating each other. are people actually using all this complexity or is it just fun to build?

@TTrimoreau Not replaced — but the gap is widening. The vibe coder who shipped with Cursor and understands what they built is pulling ahead. The one who shipped but can't explain it is falling behind. AI didn't replace anyone. It just made ownership of your code the new differentiator.

Has anyone actually been replaced by AI ?

@showupsanjeet Building codesip.dev — for the moment after you ship. Users show up. Someone asks "how does your auth work?" You hesitate. Codesip reads your codebase and explains it back. Like a senior dev friend who already read everything.

looking to connect people on X if you're into - building SaaS - vibe coding - AI tools - shipping in public - figuring it out as you go say Hi or drop what you're working on looking to follow active ones 👋

@ai_explorer25 @karpathy @bcherny @trq212 Great list. One more worth adding to the vibe coding layer — if you're shipping with Claude Code but can't fully explain what it built, that gap is exactly what codesip.dev is for. Not a lab account. But useful context for anyone in this thread building with AI.

best accounts to follow from each frontier lab to stay constantly up to date Anthropic @karpathy - must-follow account for AI; recently joined Anthropic @bcherny - Claude Code creator, always shares great tips @trq212 - also a Claude Code developer; writes amazing articles on CC OpenAI @polynoamial - works on reasoning research, shares a lot of technical details @gabriel1 - Sora developer, great career path @jxnlco - works on dev experience, shares a lot about Codex Google AI @OfficialLoganK - all the major Google Gemini and AI Studio updates @ammaar - product and design; shares great things about vibe-coding in Google AI Studio @fofrAI - cool use cases for generative models Cursor @leerob - the loudest voice behind Cursor updates @ericzakariasson - shares great insights on using Cursor @mntruell - Cursor’s CEO; major releases and usage updates xAI @milichab - recently joined xAI, shares updates on Grok @skcd42 - also covers major Grok releases

@YotamBlu @MartinPulitano Martin's friend is exactly who I'm building for. He shipped. Users might show up. And the moment something breaks or someone asks "how does this work?" — he has no idea where to look. That gap between shipping and owning is what codesip.dev is about.

@MartinPulitano that's the moment right there. someone with zero code background just shipped because the tooling finally got out of the way. claude + cursor made it possible to go from "i have an idea" to "it's live" in one session.

Mi amigo estudia finanzas. Nunca escribió una línea de código. Anoche, entre tres partidos de FIFA, puso una app en producción. Me escribió de la nada: "leí sobre Claude. Quiero hacerle una app de finanzas a mi familia." Le dije "venite, es fácil". Pensó que le mentía. Vino esa misma noche. Arrancó descolocado. En vez de escribir, grabé nuestra charla con Wispr Flow mientras me contaba qué quería. Me trató de quemado por hablarle a la compu. Diez minutos después le hablaba él. Abrimos Claude Opus 4.7 y le pusimos un sonido para que avisara cada vez que terminaba una tarea. Arrancábamos algo, metíamos un partido, volvíamos y ya estaba hecho. Lo que más le sorprendió: casi no tuvimos que corregirle nada. Opus 4.7 entendía lo que mi amigo quería incluso cuando lo explicaba en idioma "finanzas", no en código. El stack entero: Wispr Flow para hablar. Claude Opus 4.7 para construir. GitHub para versionar. Vercel para publicar. Una noche. Jugando al FIFA. Su amigo programador de toda la vida. Claude. Él no lo podía procesar. Pero estaba contento. Él no sabe programar. No importó. La barrera para construir ya no es saber código. Es animarse a empezar.

@amanhostednft Appreciate it 🙏 What's your stack — did you ship with Lovable or something else?

@FrigoVladislav Thank you

I want to connect with more founders builders vibe coders AI enthusiasts web designers freelancers growth operators startup employees If you’re one of them, drop what you're working on and let’s connect

@lawrence_king1 100% agree — Lovable is the fastest path from idea to something real. The gap I'm seeing is what comes after: when users show up and something breaks, most vibe coders don't know where to look. That's the problem codesip.dev is solving.

You can do both actually depending on where the code is hosted. You could use lovable to generate the UI and push the code to git so you could fix and even play with the code. You should understand Lovable exists for guys like us who can’t code but need to validate ideas fast without the financial burden of hiring a dev.

I have built tons of working apps with Lovable.dev and its absolutely the best thing to happen to me. You don't need to code to build apps anymore. Focus that energy and resources on selling and validating your idea in the market. Sign up on lovable with this code link and get 10 FREE credits to build your dream app for free. lovable.dev/invite/Y49U3SE

@harshitduggal5 "'Production tells the truth' — exactly this. Most vibe coders find out the hard way. Building codesip.dev to catch this before users do — scans your repo and explains what's actually exposed, in plain English."

The demo runs. Production tells the truth. Vibe-coded apps don’t die from bad UI. They die from one breach, one surprise refactor bill, one broken auth flow, or one churn spike when real users hit it. One Lovable app leaked 1.5M API keys. Escape tech found 2,000+ critical vulnerabilities across 5,600 AI-generated apps. If you shipped with Cursor, Claude Code, Codex, Lovable, Bolt, or Replit: DM me “cleanup” + your app URL. I’ll do a brutal 60-minute teardown and show you exactly what’s exposed, what breaks first, and what it costs to fix.

@YotamBlu @MartinPulitano "'I still had to make a thousand decisions about what matters' — exactly. The hard part isn't shipping anymore, it's understanding what you shipped well enough to maintain it. That's what I'm building codesip.dev for."

@_williambowen "Love the concept — AI parsing handwritten workout notes is clever. Quick question: if something broke in the Lovable app tomorrow, would you know where to look in the code?"

How I track my workouts. 1. Write workout notes 2. Ai parses notes and tracks over time. 3. Chat with my workouts using ai, has complete context on my training history and patterns. Built to reward consistency. Built on lovable.

@nickf_ai @Lovable "The jump from 'I don't code' to Claude Code is wild — most people go the other way. Curious: now that you've shipped with Lovable, do you actually understand what's inside the app or mostly trust that it works?"

I skipped the no-code phase and went straight from “I don’t code” to Claude Code/Codex. So yeah, I’ve been judging tools like Lovable from afar. Tried @Lovable today. Built an ebook reading app with stats and gamification. I get it now.

@harshitduggal5 "This is exactly what codesip.dev scans for automatically — exposed secrets, missing RLS, open endpoints. Built it because vibe coders shouldn't need a security expert to find out their app is leaking data."

Your app probably has the same problem. Not maybe. Probably. If you built with Cursor, Lovable, Bolt, Replit, or anything similar, reply with what you used. I’ll tell you the most likely thing that’s exposed.

This wasn’t some weird edge case. Escape.tech scanned 5,600 vibe-coded apps already in production. They found: 2,000 critical vulnerabilities 400 exposed API keys and secrets 175 apps leaking PII, including medical and payment data Live products. Real users.

@denis_kasala @rauchg "Nice stack — Cursor + Supabase is a solid combo. Quick question: when something breaks in production on schoolconnectafrica, do you know where to look in the code or do you rely on Cursor to debug it?"

@rauchg SaaS school management system schoolconnectafrica.co.za built with Cursor, deployed on vercel with supabase

Show me the thing you’ve built with AI you’re most proud of. Reply with a working product URL and what model / agent you primarily used.