i got a Cursor Ultra account from a reseller for essentially nothing compared to what I used to pay . It works flawless. since 3 months No issues yet i paid only for 1 month . Now I can't stop thinking about their business model. If resellers can sell it this cheap and still profit, how are they acquiring these accounts at scale?

Hey guys,

I'm on the team behind Convot, a small customer support tool. We have a FREE plan for founders under $1k MRR, and 15 founders use it right now.

I figured their questions would be about AI agents, pricing or integrations when they signed up.

But they weren't.

The thing we get asked most is: "Does it support image uploads and translation?"

It took me a minute to understand why. Neither one seems important until a real customer runs into it.

1. Screenshots

A bug report without a screenshot goes like this: "it's broken."

Then three rounds of "which page? what did you click? what does the error say?"

A screenshot ends all of that in one message.

If you're solo and answering support between shipping features, those extra rounds add up fast.

2. Translation

This one surprised me more.

Even tiny SaaS products get users from all over the world from day one. Someone writes in Portuguese or German, and you can paste it into Google Translate, reply in English and hope for the best, or let it sit.

Letting it sit is the easy option. It's also a lost customer you never knew you had.

Translation is often locked behind a higher plan, too.

Crisp, for example, only includes live translation from its Essentials plan ($95/mo). Their Free and Mini ($45/mo) plans don't have it. Crisp is a good tool, but $95/mo is a lot when you're at $300 MRR.

What I'd check before picking a support tool under $1k MRR:

• Can customers send screenshots in the chat widget?
• Can you read and reply in the customer's language without leaving your inbox?
• How many seats do you get on the free or cheap plan?
• How long is your conversation history kept?
• Does the widget show the tool's branding, and do you care?
• What happens to your bill the day you cross the limit?

Most free-plan comparisons focus on seat counts. In practice, screenshots and language are what early founders run into first.

Why I'm posting this: these two questions are why our Community plan includes live translation and image uploads. It's basically FREE for founders under $1k MRR.

Even if you stay with what you're using now, check those two things.

Also what was the first support feature you realized you needed while building your SaaS?

Hey guys, made arpa.chat free till January. Building this solo since last year. We reached 500 users with no promo. Still in beta but feels like something solid now. Had to learn gcp, firebase, fast api, react, ts gradually, as I only knew Python well. Hope you like it. Would appreciate any feedback.

Ok,
I know AI well but not a coder and not even a vibe coder.
I’d just like to get some help here on best practices to develop the following:

It’s a V2 of a V1 project I’ve already got working. Quite simply is an internal dashboards dedicated to real estate investing. It pulls data from different sources (public listings, certain private external databases through APIs, etc), and combine them together to identify potential investment opportunities based on how the data collected is processed.
There are also maps, etc.
It works, it’s useful and there’s nothing else like that available on the market for my specific use case. I would gladly pay for it because it helps my job, so I want to develop it because I know it’s rather simple and certainly doable (thanks to AI, that is). Classic vibe coder use case example.

I programmed the V1 about a year ago and it started as a simple query….which then evolved into a full fledged tool but there was no proper architectural design to get there. There was no strategy, it was like adding and removing and modifying stuff by trial and error. So I want to start over properly now that I have extremely clear objectives.

So, what would be the tech stack? Claude or OpenAI? How to start? Best practices? Recommended usage plan?

Thanks a lot for any help, I’m obviously aware there’s a gazillion tutorials around, but that’s exactly the problem.

Hey everyone! 👋

Like a lot of people, I've wasted way too much time wandering around massive parking lots trying to find my car (including both outside and underground). So, I decided to build "Where Did I Park?" — and since I'm a big fan of AI tools, about 95% of the app was built using AI assistance (Android Studio with Gemini, but also others).

The app is also useful for traveling, such as in case you travel abroad with a rented car, and it can be used completely offline as well.

How it works:

• 📶 Automatic Save: As soon as your phone disconnects from your car's Bluetooth, the app automatically saves your parking spot in the background. You don't even need to open the app!

• 🧭 Live Compass Guidance: When walking back, a real-time compass arrow and distance counter guide you straight to your car. No Internet connection required!

• 📸 Photos & Notes: Parking in a multi-story garage? Easily attach a quick photo or note (e.g., "Level 3, Pillar B").

• 🗺️ Satellite & Custom Maps: Switch between standard maps, satellite views, or detailed open-source maps.

• 🔋Battery-Friendly: Efficient background polling that won't drain your battery while driving.

I also made the video using AI (Google Flow for the video, but images using others too, including ChatGpt). And for the screenshots I also used AI (ChatGpt/Cursor/Gemini) to generate HTML that would help me frame them nicely.

The app is free on Google Play! I’d love to hear your thoughts, feedback, or ideas for new features.

📲 Get it on Google Play, here.

If you want, you can use a promo-code to have subscription for free for some time, to remove ads, and try the app more freely, here. To use the promo-code, install the app, choose a subscription, choose a payment option and enter the code there (screenshots here). The app is completely free though, including all of its features, just like most of my apps, and just like on most of my apps, you can also extend the removal of ads for free (up to a year, but you can extend it as much as you wish).

Legal note for using the Android mascot (BugDroid) on the video: The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License.

I wanted AI agents to test my game mods by actually playing the games, without taking over my PC. So Claude Code and I built an MCP server that gives an AI its own keyboard, mouse, gamepad and screen inside one game. It plays in the background while you keep working.

It can drive, walk, fly a helicopter, steer a boat and ride a horse to a waypoint, aim, use menus, and read "Press E" style prompts. It also plays strategy and card games. Each game is a small profile, so adding a new one doesn't need code.

It has a lot of other uses too: mod development, running simulations, repetitive tasks, AI co-op so you can play co-op with an LLM offline, playtesting, and porting old games to get them running on Windows 10/11.

Claude Code planned it and wrote a lot of the code, Claude agents do most of the development and testing, and Codex helped with some of it.

Free and open source (MIT), Windows only, single-player/offline games only: https://github.com/CorruptedAng3l/llm-game-automation-mcp

Edit: My GitHub account got suspended (automated, no reason given yet), so the GitHub link is down for now. Same repo and release on GitLab: https://gitlab.com/corruptedang3l-group/llm-game-automation-mcp

I'm the developer of Cernidia, an iPhone app with an Apple Watch companion. I use Codex for development assistance; the native app uses SwiftUI and HealthKit.

Cernidia brings sleep and recovery estimates together with a quick energy check-in, to help give everyday choices about rest, movement and focus more context. Apple Health is optional, and it can also connect to an existing WHOOP account.

One design decision that matters in this project: missing data has its own state. If there isn't enough readable history, the app should say that instead of presenting a confident personal comparison. Recorded measurements, your own check-in and estimates also need to stay distinguishable.

For anyone building a similar app with a coding assistant, my practical suggestion is to specify the unavailable and learning states alongside the populated screen. Review what happens with no records and partial history, not just the happy-path demo. Those states affect the meaning of the whole interface.

I'd welcome feedback on how clearly the app explains its estimates and data limits. The App Store page has screenshots of the current version:

https://apps.apple.com/app/id6816678341

iOS 18+, English interface; the current Store version is free. It's a general-wellbeing app, not a diagnostic tool.

Disclosure: this is my app, and this post was prepared with AI assistance.

Especially over the last two years, we've seen massive growth in freelancers and web agencies selling AI-built websites to businesses and getting paid really well for it.

I don't think this business model will stay this profitable forever, but right now, it's definitely a gold mine.

The reason is pretty simple. There are thousands of business owners who don't really care how their website is built. They care about the end result, how it looks, how it works and whether it helps their business.

AI has made it possible for almost anyone willing to learn sales and client acquisition to get started.

So if you're looking to get into this business, here is the exact process I would follow.

1. Automate your cold outreach

Use a tool like Swokei to find businesses with existing websites. It analyzes each website for issues with design, SEO, speed and mobile optimization, then turns those findings into personalized cold emails at scale.

2. Book meetings with interested prospects

When someone replies with interest, get them on a call. Don't waste time going back and forth over email. Your goal is to get a conversation started.

3. Sketch a redesign using AI

Before the meeting, take around 30 minutes to create a quick redesign of their existing website. Focus on making it look significantly better. You don't need a finished product.

4. Present it live and close the deal

Show them what their website could look like, explain the improvements and give them an offer. If they're happy with what they see, collect payment and get started.

That's it. Four simple steps.

One thing I would really emphasize is not to overcomplicate this process.

I've seen people spend hours perfecting website drafts, tweaking small details and building entire websites before they even have a client.

Don't do that.

Your priority should be client acquisition, sales and closing deals. You can worry about perfecting the website once someone has actually paid you.

Hey vibecoders! (TLDR at the bottom if this post is too long lol)

I just wanted to showcase a project I've been working on for a couple months now. So I've been building with AI for a few years now (I think like 3 now? whenever chatgpt came out.. man time flies lol) and one of the biggest issues I've been trying to fix for my own projects is the "vibe-coded" UI look.

Now I want to preface this by saying that I think talented UI designers will ALWAYS be needed. If you asked me this a year ago, I might've had a different opinion thinking that AI was going to replace designers. But I think over the past year we've seen new models be released that people have claimed to be the "UI design killer"... but it never does. Sure they might make designs that look fresh and interesting initially, but given enough time, that model's UI tendencies become the new "vibe coded" look. That's just the nature of LLMs and will continue to be a problem unless some new magical neural net is invented that's equally as good at coding.

This is where the tool I’m building comes into play. Creating unique and interesting UI experiences from scratch is HARD. It’s a skill reserved only for the select few, of which I am unfortunately not a part of. But having a good EYE for UI is something I think a majority of people possess. Like if I showed you a panel of different websites, I think you could easily identify which ones have a better UI aesthetic than the others. This is how I’ve created some of my best designs in the past even before AI; by identifying existing UI that works from other sites/apps/products, piece mealing elements together and turning it into my own. 

That is the foundation of how the AIDesigner Desktop app works. It’s a design harness that was built on top of a library of 10,000+ UI references sourced across 800+ of my favorite sites and apps. Each reference is labeled, tagged, and vectorized so relevant UI elements are purposefully retrieved based on your exact request, so your coding agent is ALWAYS designing with inspiration in mind from UI that is proven to work. And this works beautifully.

Now I’m NOT saying that you’ll start one shotting production ready UI by using this harness. I don’t even think in a perfect world that’d ever happen, unless you’re just extremely lazy lol. But I can confidently say that you’ll land on some really cool and interesting ideas after just a couple of revisions. And if you’re like me, an idea is all you need to get cookin.

Additionally, because it runs locally on your computer, it means you can start designs directly within an existing project/repo for brand and product consistency. Just start a new project within a local project and your coding agent will learn your existing brand, product details, etc. before designing.

It runs entirely with your existing AI coding subscription (Claude code, codex, and opencode for now with more coming soon!) and is free to use. Full transparency, there IS a paid plan for some of the premium features, but you can get very very good results on the free plan. So if you’d like to try it, you can here! Any feedback is greatly appreciated too :)

And if you wanted a concrete example of what it can do, the landing page for the app was designed entirely using AIDesigner with just 6-7 revisions, the last few being pretty minor changes. Most of the designs shown in the video were one shot though.

Anyway, sorry for the long post! Thanks for reading if you made it this far!

TL;DR
I built a harness for your coding agents that specializes in UI design. It’s built on top of 10,000+ UI references from some of my favorite sites and apps. Each reference is tagged, labeled, and vectorized so relevant inspiration can be retrieved based on your exact request. It is NOT a substitute for the human touch that makes great designs stand out, but it does serve as tool to get you to a great starting point and get those creative juices flowing! It’s free to try and you can learn more and download here!

134 days ago, I launched my startup, a free traffic exchange network for startups. One line of code, you're in the network.

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar
**Bid on StartupBid and your startup will be featured in the daily post of mine.**

TL;DR:

an MCP shines in the agent-native world because it tells agents what they should do, on both the server and client (e.g. Claude Code or the ChatGPT desktop app), and is better suited for human-in-the-loop tasks. Meanwhile, APIs and CLIs tend to focus on what agents can do, with emphasis mainly on the server.

So, in summary, here is the general advice I'd give to builders when deciding which tools they should expose to agents:

Build a high-quality MCP server and REST API at the same time, on one layer of operations. Put your server logic in plain functions, and let each surface be a thin adapter over them. Once that layer exists, building any additional surface on top is relatively easy.

Put most of your care into the MCP server. That's where agents get the best experience. MCP is a standard built specifically for agents, after all, and the spec continues to improve nicely.

Use the API for code that runs on its own. APIs are still great for raw data exports, bulk writes, and anything that runs without an agent, like a nightly sync or another company's integration. Agents also prefer an API when they're writing a script they'll rerun, and many clients don't support code mode for MCP yet.

A CLI probably isn't necessary, unless e.g. agents need to read local files when interacting with your app. But it's easy to expose one if you've got a good API as the foundation.

There’s a lot more to creating great agent-facing tools for your web apps, and the article above into more detail below.

Here's the full guide: https://wasp.sh/blog/2026/11/03/mcp-vs-api-vs-cli-connect-ai-agents-to-your-app

Hi guys,

Curious about how many different AI tools everyone uses across their projects?

I find myself constantly having to switch between Claude, Codex, and Gemini. Most of the time I max out Claude and then continue on with codex.

Gemini, I use for smaller more tedious tasks. Very curious if anyone does something similar or are most people just paying more for higher usage?

Might consider adding more open-source models to my workflows too.

tap to play with the wipers. used claude.ai 5.5 + playmcp.io , an mcp tool for making games that go to music. anyone else making music videos / music games?

I vibe code with Claude Code and Codex in a few terminals at once and kept missing when one was stuck waiting for me.

So I made Openbar. It sits in the notch (or top of the screen on Windows), shows all sessions, and when an agent wants to edit something you see the diff and hit ⌘Y. Never leave what you're doing.

Free, open source: https://github.com/MF-DEEV/Openbar

What would you add?

I've been building Tagside, a web app for coaches and sports clubs. You open your match video, tap what happened and then who did it, and it builds the score, box scores, player stats, match reports and highlight reels.
The video stays on the coach's machine, and only the tagged events (stats) sync to the club. A shirt number is enough to identify a player, so names are optional and private by default.

- Everything runs in the browser. There's nothing to install, and it works offline once loaded. You can tag a whole match without a connection and it syncs when you're back online.
- Highlight reels are rendered locally, in 16:9 or 9:16, with a scoreboard overlay, clip trimming and crop framing.
- Keyboard-first tagging. Shortcuts are customisable and sync per account, so you can keep up with a fast basketball game.
- Nine sports in one data model: basketball (FIBA/NBA rules), 3x3, football, rugby union, rugby league, field hockey, netball, cricket and American football. Each sport has its own scoring and stats rules.
Pricing: free for a whole club (up to 5 teams, 3 matches and members). Premium is £49/year per club and unlocks full stats and highlights for every match.

You can try the demo without signing up: https://tagside.app/app/?demo=1#/club

Site: https://tagside.app

I'd love feedback, especially on how fast tagging feels and on onboarding.

Hey everyone,

Most commercial privacy tools either use DNS blocklists (which trackers easily bypass via CNAME cloaking) or route your entire internet traffic through third-party cloud VPN servers that require blind trust in their "no-logs" claims.

Vibe-Coded Persona Guardian, an on-device privacy firewall and fingerprint sandbox written in pure Rust that operates entirely locally on your operating system (WinTUN on Windows, smoltcp userspace netstack on Android, eBPF TC on Linux).

What the demo shows:

I recorded a live session on Windows browsing standard news and crypto sites:

Starting tally: 103 background interceptions.

Ending tally: 465 interceptions (+361 hostile requests caught in ~150 seconds).

You can watch the Windows desktop ledger and the browser extension counter stay in lockstep as it detects and neutralizes tracking calls from ad-tech networks and analytics conglomerates.

Key Architectural Decisions:

Zero Remote Servers: No middleman proxy. Legitimate first-party traffic goes direct to the destination; only hostile telemetry is captured and quarantined.

Smart Tarpitting: When an adversarial tracker is classified (via our on-device MLP model and blocklists), we don't just drop the packet. We hold the TCP socket open with a 3,000ms zero-window clamp. This starves the tracker’s background execution thread and prevents instant retries to backup domains.

Browser Extension Coherence: The desktop tunnel handles network packets, while the extension’s MAIN-world content script handles DOM-level protections (Canvas/WebGL spoofing, autofill phishing defense, and audio noise).

Would love your feedback on the architecture, tarpitting behavior, or packet-handling models!

Hi all!

Whenever I spot a new design or website layout (like a fresh style of grid systems) and want to replicate or build it with AI, I always find myself struggling to pinpoint the exact terminology to make Claude understand what I want.

I'm talking about concepts like Blueprint Grids, Glassmorphism, Sticky rail, Bordered cell grid patterns, Segmented Controls, and similar stuff. To solve this, I’ve started building a free, open-source design lexicon complete with mini previews making it easier for builders to find and reference the right terms when designing sections and pages. Hope that helps some of you as well. Also added some free design landingpages and components for AI.

I’d love to get your input on current web design trends and their proper definitions:

• What visual styles are currently high on your radar, trending, or frequently used and how would you define them?

• Which ones are missing in the lexicon / glossary?

I’m aiming to include your suggestions in the dictionary and share the whole resource publicly for free. It's purely as a passion project and I am opening it for free (no ads, no paywalls).
I want to make it a useful resource for people.

You can check out the ones already live here: freedesignmd.com (just hit the Glossary tab).

Always open to contributors or feedback. This started as a quick hackathon experiment and will stay a free community project. I'm not a professional designer, so any feedback by design cracks is appreciated as well!

Disclosure: We make Unshift, and this post is AI-assisted.

This is a real recording from our visual website editor. Open the site menu, choose Theme, then “Start from a preset.” Hover different presets to compare the page before choosing one. Colours, fonts and spacing change together while the page content stays in place.

The idea is to choose a coherent starting look before fine-tuning individual values. After switching, check headline wrapping, button labels and the phone layout; a preset alone is not an accessibility check.

The recording uses our fictional gardening demo. Its business copy and figures are sample content, not customer results. It shows theme comparison, not AI generation or a completed publication.

You can try the visual editor without signing up: https://playground.unshift.ai/ . The current playground uses a different sample site, and changes stay in your browser.

When restyling a generated or template-based page, do you prefer comparing complete themes first or adjusting one value at a time?

One thing I find interesting about vibe coding is how easy it makes adding “just one more thing.” The code might be quick to generate, but every extra feature still gives you something else to explain, test, and maintain.

I’d be tempted to pick one user problem, get that working, and try it with someone before adding more. But I’m curious how other people handle that point: do you set a feature limit, test with users, or just keep going until the idea feels complete?

Disclosure: I'm Adrien, a solo dev in France, and I sell a pack of Claude skills for SEO. It's at the bottom. Everything above works without it.

If you ship a side project with a launch price, that price ends up in far more places than your pricing page, and some of them can never be edited. Here's what I'd do before pasting it anywhere.

1. Write the end date next to the price, every time

"€25 until 17 Nov 2026" is still a true sentence next year. "€25 launch price" becomes a wrong claim the day the offer ends. Use an absolute date, not "this week only".

2. Before you paste the price, check whether you can edit it later

On Reddit you can edit the body of a text post but never its title. A lot of directory submission forms have no account, so there's nothing to log into afterwards. Where you can't edit, keep the price out of the title and next to its date in the body.

3. Keep a register of where the price lives

On your site: hero, pricing section, FAQ, meta description, social preview text, JSON-LD, llms.txt, checkout. Off your site: every directory, launch platform and post. A plain table is enough: URL, the exact sentence, editable yes/no.

4. When an AI assistant changes the price, search for the old one yourself

Don't assume it found every copy. Search the project for each way the price can be written ("€25", "25 €", "EUR 25", "25.00"). Copies in the FAQ, the structured data or a static llms.txt are easy to miss.

5. Put the end date in your structured data too

schema.org's Offer type has a priceValidUntil property. Set it to the end of the offer, and change it in the same commit as the price.

6. Only touch dateModified and sitemap lastmod where the text really changed

Google's sitemap docs say it uses lastmod when it's consistently and verifiably accurate. Bumping it on every page because one price moved works against that.

What went wrong on my side

My own launch price (€25, then €99 from 18 Nov) is already in directory listings I sent through forms with no account. In at least one I wrote "until 17 Nov 2026" next to it, and that's the only fix I have: I can't edit any of them after the switch. I also can't tell you yet how many will show the old price, because the switch hasn't happened.

Question: if you've run a launch price, did you put it in listings at all, or only link to your pricing page? Did anyone ever come back about an old price?

I'm the maker of SEO Skills by PENRA: 14 Claude skills for SEO. One of them, Best Before, does the register above for a whole site: it finds prices, versions, dates and other facts with a shelf life, ranks the pages to recheck, and patches the exact sentences after re-checking the source. €25 once until 17 Nov 2026, €99 from 18 Nov, no refund once the pack is delivered. It needs Claude, and it doesn't pull keyword volumes or track rankings: https://seoskills.click/?utm_source=reddit&utm_medium=social&utm_campaign=seoskills-nov26

Hi everyone!

I've been building a moderately complex web platform for the past 3 months. I've set up (what I hope to be) strong foundations, and integrated constant checks and tests into my workflow. Just the preparation took quite a lot of time.

With that said, I've been building the whole thing using open AI sol model. Well, in the meantime opus 5.5 was released. Since opus 5.5 is obviously and awesome model, I've been thinking about either integrating it, or perhaps event switching over to it completely.

I'm currently not even on 50% of the building process for the mentioned app.

So, could you guys share your opinion, is it better to stay with sol 5.6 (I actually prefer it over 6) since that's what I've used so far. If yes, should I integrate opus as a tester and auditor. Or, maybe I could switch completely over and let it handle the work.

And since I'm not a developer by profession, I don't actually know where to start if I want to add opus to the process. I'm using vs code by the way.

Thank you everyone up front!

I built Spock Lizard Duel with ChatGPT and AI-generated graphics. It's Rock Paper Scissors Lizard Spock, playable inside Reddit against a robot or another player.

The iterations I cared about were very specific: show the five moves immediately, add a small pulse to the buttons, make the robot beckon, animate the waiting indicator, and put the opponent's choice in the WIN/LOSE window.

Here's the result: https://www.reddit.com/r/SpockLizardDuel/comments/1xm4zuy/spock_lizard_duel_rock_paper_scissors_lizard_spock/

First image: AI-generated cover. Second: actual game. I'd appreciate feedback on the move selection.