if i use claude or codex, i constantly am screen capping to show bad padding / alignment / whatever. is there a defacto way to let claude or codex tool call to see the browser or render a page for themselves?

I am a product designer, not a coder, and so "lowcode" code editors leave me lost. It simply takes too long to ask Claude to step-by-step me through anything I want to do.
I have projects in the works in Lovable.dev and Medo.dev, Anything and Dazl - but yet to get things to work after migrating them to Vercel breakl out of the co-branding that these app-builders like to sneak in (notice the rainbow you see here and there on Lovable-built sites, even whn they use their own domain...?)
Gemini's suggestions:
AI code generation is prone to the "90% Problem," where the final 10% of polish requires significant manual intervention.  

• Bolt.new: Users report that while blazing fast (app skeleton in 20s), it often "shits the bed" when projects get complex, leading to massive token consumption to fix errors .

• Lovable: Praised for UI aesthetics, but its 7-message memory limit leads to "recency bias," causing the AI to get "drunk" on different approaches during long debugging sessions .

• Tempo Labs: While it provides excellent planning features (PRDs and diagrams), some users have reported that its export to GitHub is unreliable, providing only "fragments of code" rather than a full app .

• Blink.new: Emerging as a smoother alternative for full-stack builds, handling authentication and backend integrations with fewer breaks than Bolt .

Strategic Implementation Path

1. Selection (Phase 1): Use Dyad.sh or Anything if you want the most stable backend/auth foundation .

2. Generation (Phase 2): Build your MVP on the Pro tier for 1 month (~$19-$25). Use Discussion Mode to plan changes without burning credits .

3. Sync & Export (Phase 3): Sync your project to a private GitHub repository immediately .

4. Deployment (Phase 4): Connect the repo to Cloudflare Pages for free, unlimited bandwidth or Coolify on a $5 VPS for total control .

5. Refinement (Phase 5): Use Cursor (locally) for further edits. It provides a full IDE environment with better project context for $20/month, allowing you to maintain your "clean codebase" without builder overhead .
   I then asked, about a cheap solution starting with Baidu's Medo.dev - because Medo gives us many credits to start, 100 more/day free, 20 more for 20 clicks on other's projects... So you can build a lot, download, but then have to sort out login and other backend problems. Possible, but takes some doing.
   Gemini's response:

   1. In Supabase Dashboard: Go to Authentication > URL Configuration. Change the "Site URL" from http://localhost:3000 to your actual production domain (e.g., https://your-app.com).

   2. In Vercel Dashboard: Go to Settings > Environment Variables. Add a new variable called NEXT_PUBLIC_APP_URL and set its value to your domain. This tells the backend where to send users when they click the email link.

   3. In Cursor: If the error persists, open your project in Cursor and ask the AI: "Search for all instances of 'localhost:3000' in the authentication logic and replace them with the environment variable for the site URL.".
      But what about you? What is your process if you are no-code building and shipping?

Proximity Lock System ranked #4 Product of the Day on Nov 15, really grateful for the support and feedback.

Building this CLI reinforced how much people still value simple, reliable tools that quietly do one thing well.

This was the second launch of Proximity Lock, and I m continuing to iterate based on real usage feedback.

The idea is simple: pick a vibe upload a selfie get a consistent pack of share-worthy pics in minutes.

Works great for: profile pics, dating apps, UGC, new year / glow up content, and just having fun.

There s a Free plan, so you can try it instantly.

MUJO Photoshoot is also part of MUJO an AI Visual Studio, where we re building more mini-apps for social + ecommerce.

1. Recently, several small bloggers have talked about ProblemHunt: a few from the USA, a few from Spain, and one from France. And we noticed an obvious thing: traffic from these countries, although not much, has started to grow.

2. But the most important thing is that people from these countries have started sharing problems more actively. For example, in the last month alone, France has already submitted 4 problems, three of which were published yesterday and today.

Most AI apps eventually hit the same wall. They forget users unless you build a ton of infrastructure first. This means every AI dev eventually will end up building this infra to provide the best user experience needs for their agent and app.

What rolling your own really means:

• Vector DBs + embeddings + tuning

• Extracting memories from conversations (and resolving conflicts)

• Designing user profile schemas and keeping them in sync

• Managing long chat history + summarization pipelines

• Juggling different formats across OpenAI, Claude, etc.

• Hosting, scaling, backups, monitoring

Hey folks,
Hope everyone had a good relaxing Happy New Years!

Here's what we're shipped recently:

• Support for select/radio/checkbox fields (more betterments coming soon!)

• Alternate fill modes that trigger superfill.ai autofill directly from form fields & context menu without the need to open extension UI.

The github repo can be found here: https://github.com/basejump-ai/b...

A little more history on what led us to this point. We started working on Basejump in 2023 and always had the goal to eventually open source. It took us almost 3 years, but we're really happy with what we're giving to the community.

We just shipped multi-provider support in @Mnexium AI so you can change LLMs without resetting conversations, user context or memories.

The problem

When teams switch providers, they usually lose everything:

Hi folks,

I ve been spending a lot of time on Discord and Reddit helping people who are trying to add AI chat to their no/low-code apps.

What keeps coming up is that the setup is way more fragile than it looks.

It s usually not the model itself it s everything around it:
conversation state, memory, retries, edge cases.
Vibe-coding works for demos, but once people try to ship something real, things start breaking.

I have been cranking out apps for the past few years and loving it.  Then one morning a week or 2 ago I got a little ambitious and decided to build a desktop email client because outlook was so-so and superhuman was ridiculously expensive.  

Is this a big mistake?   Am I wasting my time ?

Hey makers!
I've been deep in prompt engineering lately while building an AI tool, and I'm genuinely curious about how others approach this.
A few questions:
1. Do you save your best prompts somewhere? Notion, text files, dedicated app, or just copy-paste from chat history?
2. How do you iterate? Do you have a systematic approach or just tweak until it works?
3. Different prompts for different models? Or do you use the same prompt for ChatGPT, Claude, Gemini?
4. Text vs image prompts do you treat them completely differently?
I've noticed I was doing the same optimizations over and over (adding role, being more specific, structuring output format), which made me wonder if everyone has their own "prompt formula."
Would love to hear your workflows!

I m noticing something weird happening in solo dev land.

We used to compete on:

• remembering docs

• knowing frameworks

• being a better coder

Now it feels like the real edge is:

AI and no-code tools are evolving insanely fast right now. Every few weeks there s a new tool that changes how quickly you can go from idea to product.

I ve been experimenting a lot with different vibe coding platforms lately, trying to find the right balance between speed, control, and flexibility. What s surprised me most is how far you can go today without a traditional engineering setup.

For context, I recently built @Sendrise , an all-in-one cold email outreach platform, using a no-code + AI stack. I used @Lovable for building the product flows and UI, combined with AI tools for writing, automation, and logic. What started as an MVP quickly turned into a fully working product with lead management, campaigns, CRM, and analytics.

AI dev tools are moving stupid fast. Every few weeks, there s a new must-use. Some stick. Most don t.

Some vibe coders are developing full products with @ChatGPT by OpenAI+ @Replit. Others swear by @Cursor + @Claude by Anthropic . A few are mixing @Lovable , @v0 by Vercel , and @bolt.new . New and shipping way faster than expected.

I ve been refining my own vibe stack lately.
Building with @Google Antigravity at the core. It keeps the flow clean when things get messy.

Share your current Vibe Stack:

I'm Kevin, founder of EnginifyAI. Over the last 12 months I've been working on a prompt engineering tool. I started off using Bolt but quickly I found myself unable to completely use it effectively. I then tried Cursor and was using it early on but maybe I had the wrong settings as I found myself using all my credits in 2 days. So, I switched to Windsurf, and to my surprise credits were a bit more manageable and it took about 2 weeks before my credits were consumed. Keep in mind that I am new to coding so I spent a lot of time asking questions in Windsurf instead of using my paid subscription to Anthropic.
I'm coding using React/Typescript and Supabase. I have learned that coding is a lot of work, a lot of fine-tuning, and a lot of testing and fixing. The one thing I haven't quite figured out completely is how to fix migrations. Early on I was running SQL scripts directly in Supabase without migration scripts because I found it to be faster. But now Windsurf uses very old migration script references and I find myself fixing the same issues because of an old migration script reference. Any idea how to fix this?
I assume that vibecoding is an experience everyone can enjoy but comes with frustrations about asking the right questions, or being very specific about my requests. I am using Claude Sonnet 4, 4.5 and 4.5 thinking. Are these the best coding ai models for Typescript?

For me, productivity means getting (more) results faster in less time. My goals for 2026 are closely linked to the fact that I want to learn a lot of things, which will require a lot of concentration.

Therefore, I think that a large part of what I want to gain will be ensured by:

As one year comes to an end and a new one begins, I find myself pausing to reflect. If you had the chance to say something to your future self to the version of you in 2025 and 2026, what would it be?

Looking back, I want to thank myself for how much I pushed through this past year:

• For finding a job I genuinely value, even after going through a long period of stress and fear of unemployment

• For speaking up and sharing my own perspectives at work

• For choosing action over just talking

• For walking away from toxic and unnecessary work relationships

• For daring to learn new things outside my original field of study

• For letting go of some comforts and entertainment to focus more on my health

Senior Reviews: Architecture Help or 'Premium Nagging'?

Yesterday, I wrote about the "Friday Merge" ghost story the pain of waiting days just to get code shipped.
(Thanks for the great discussion on that)

The feature you ve been asking for is officially live

Record with Professional AI Voices

You can now transform your screen recordings into studio-quality demos using professional AI voices.

Just record your screen and let AI handle the voiceover with clean, natural, and professional every time.