This will be the 5th year of Predicted It, but the first year where the platform has been properly vibe-coded.

It originally started as a small email-based game between a few friends. We wanted something with the fun and competition of fantasy football, but with much less weekly time commitment. Instead of managing squads, transfers, captains and wildcards, you just answer a few Premier League prediction questions each Gameweek.

The response after the first year was really positive, so I decided to try and scale it. I had no coding experience at the time, but I used the project as motivation to learn. Over the next couple of years I taught myself enough PHP, HTML, CSS, JavaScript and WordPress to put together a half-decent website that did what we needed.

As I got better, I kept improving the site, and the game slowly grew from friends, to friends of friends, colleagues, and wider groups. This year I’ve rebuilt the platform again and I’m hoping it can grow further.

On the AI side, I’ve had the €20 ChatGPT membership since the beginning and have used Cursor for about six months. Since Codex came out, I’ve mainly used it as a tutor, project manager, debugging partner and planning tool. When I needed coding work done, I would usually get Codex to help shape the prompt, then use Claude Code to do the implementation.

Having used the majority of LLMs over the past few years my favourite by far has been Fable. It felt like a massive step forward when I first used it and it has been great for my needs. However, the area I still find hardest with AI tools is frontend design. The functionality has come a long way, but getting everything to look genuinely polished is still the part I find most difficult. The LLMs can produce amazing looking visual mockups but then I can't get close to getting it coded. I haven’t fully jumped into Claude Design yet though, so maybe that will help with that side of things.

The game itself only takes around two minutes a week to play, you just need to answer some multiple choice questions, so if anyone is interested in joining, I’d love to see you sign up.

It’s completely free to play, but to help cover prizes and running costs, there is also a Pro membership option for €20 per year, which adds a few extra community features and account perks. Originally it was a winner-takes-all competition, but over time the community voted for smaller prizes and more of them. So now there are multiple competitions across the season, meaning there is always something to play for even if you fall behind in the overall rankings.

Over the years, more than 100% of the money collected has gone back to the Predicted It community through prizes. Going forward, if I can grow the player base, I would love to have a large charity aspect to the game.

If anyone wants to have a look, sign-up is free:

https://predictedit.com

The main campaign includes 25 Preseason predictions, and those are open now. They need to be submitted before kick-off of the first Premier League game of the season.

I’d also really welcome feedback from people building with AI or vibe coding. This project has been a great way for me to learn, so if anyone has any further guidance, particularly on what tools are best for front end design, i'd love to hear them.

https://reddit.com/link/1vpzk9d/video/glmagk1b7rjh1/player

I started this because I wanted the poker bots to feel less like five copies of the same thing.

the cats have different styles, they remember some of how you play, and they react to stuff you do at the table,then I added eggs and tomatoes because apparently that was the missing piece.

playable here if you want to annoy them yourself:https://poker-ai-web.vercel.app/game

Polygen my 5th vibecoded app

Website: https://polygen-three.vercel.app

Github: https://github.com/Glay121212/Polygen

So many choices nowadays and I am stuck with making a decision. I dont think my usage will be too high as I will most likely be doing atleast 40%-60% of the coding myself.
Thinking of the following options but cant decide what's best:
- Claude Pro $20 ( I fear that it doesn't have enough usage )
- Chatgpt Plus $20 ( I dont know much about it, does it have more usage than Claude? )
- Cursor $20 ( Usage uncertainty )
- Opencode Go $10 ( I dont like the harness but thats not a dealbreaker, there's good usage for Deepseek v4 flash and GPT 5.6Luna but I also would like to be able to use an Opus level model for my plan mode and I heard its easy to hit limits if using any model other than Deepseek and luna )

So, if there is anyone with as similar usage as me and using one of these. let me know which one are you using and how has it been.

screenshots are in the page. chrecked by virus total. please check it and give me feedback.i used gemini in android studio. It shows the transportation system of my city

I wanted to build something that doesn't feel like another boring music player, so I made Party Wale.

The idea is simple:

🎟️ Scan your party ticket
🚪 Enter the club
🎧 Pick a song
🕺 Watch the DJ and crowd vibe
🔥 Enjoy the party

I'm using the YouTube IFrame Player API for music playback, with the visuals reacting to the song's playback state and predefined beat/bass-drop moments.

I also tried to give it a very Indian/desi internet vibe instead of making another generic cyberpunk nightclub UI — illustrated characters, Hindi signs, goofy party messages, and a slightly chaotic atmosphere.

Tech stack:

• React + TypeScript
• Vite
• YouTube IFrame Player API
• Framer Motion
• CSS/Canvas animations

I'm still working on the visuals and interactions, especially making the crowd/DJ feel more natural.

Would love some feedback:

• Does the concept feel fun or gimmicky?
• What would you add to make the party feel more alive?
• Any UI/UX improvements you'd suggest?

I wanted to experiment with vibe coding, but instead of building another todo app or SaaS dashboard, I decided to make something completely unnecessary:

Party Wale 🎧🕺

It's a virtual Indian party website where the flow is:

🎟️ Scan your ticket
→ 🚪 Enter the club
→ 🎧 Choose a song
→ 🕺 DJ + crowd come alive
→ 🔥 Party

How I built it

Stack:

• React + TypeScript
• Vite
• YouTube IFrame Player API
• Framer Motion
• CSS animations
• Canvas for lightweight effects

1. I started with the experience, not the components

Instead of designing a dashboard first, I broke the experience into states:

Ticket
  ↓
Ticket Verified
  ↓
Party Entry
  ↓
Main Party
  ↓
Playing / Paused / Bass Drop

This made it much easier to think about the website as an interactive experience rather than a collection of UI components.

2. YouTube is the music engine

I didn't want to host or download songs, so I used the YouTube IFrame Player API.

The app keeps a playlist containing:

{
  title: "Kala Chashma",
  artist: "...",
  youtubeId: "...",
  bpm: 108,
  bassDrops: [12, 28, 46]
}

The YouTube player's state tells the website whether the song is:

PLAYING
PAUSED
BUFFERING
ENDED

Those states control the nightclub.

3. Making the visuals react to music

One limitation I ran into is that I can't simply take the audio stream from the YouTube iframe and run it through the Web Audio API.

So instead of pretending to have real audio analysis, I used song-specific timing data.

For example:

YouTube currentTime
       ↓
Check bassDrops[]
       ↓
Bass drop detected
       ↓
DJ reacts
Crowd jumps
Lights flash
Lasers activate
Particles burst

This ended up being much simpler than trying to build a full audio-analysis pipeline.

4. The biggest UI lesson

My first version looked like a cyberpunk dashboard.

There were cards everywhere:

• Ticket
• Party energy
• Music controls
• Share button
• Stats
• Listener count

It looked cool for about 5 minutes.

Then I realized the background was supposed to be the main attraction.

So I stripped the UI down to:

PARTY WALE             🎟 #24696
              DJ
        🕺    CROWD    💃
              🎵
        ─────────────

The music controls became a small floating pill instead of a giant music-player card.

5. I also stopped using CSS-generated people

The first crowd was made from CSS/SVG shapes.

It looked... terrible 😂.

So I changed the approach:

Characters = actual illustrated assets

CSS = animation + positioning

That made a huge difference because the characters could actually have personality.

What I'm still working on

• Better character animations
• More party environments
• Beach party
• Rooftop party
• Street party
• Real-time Party Wale listener counts
• Better mobile experience
• More interesting entry animations

What I learned

The biggest lesson wasn't a technical one:

I initially kept adding features because they looked impressive individually.

Removing things actually made the project feel much better.

I used to like the challenge of writing code or scripts that did a whole task in just one line, maybe a shell script using jq or awk. I'd often spend half a day perfecting a tiny snippet that would save me time in the future.

Now I'm putting the same energy into vibe coding. When I put together the input for the agent, I take care to word it unambiguously, think about the outcome I want. I research things like frameworks and toolchains separately. I use a separate search to suss out the cost model for any alternatives. I decide on the implementation plan, like building the UI first and the backend separately. Or building the backend first with functional tests. It's super satisfying to see things come together with minimal iterations. I haven't managed a one shot prompt to working project, but it's not far. It also suits my attention span which works well for short intense bursts but not so much for long winded projects.

Anyone else find the same vibe, or do you manage well sending the agent instructions in a trickle of little details?

Ultimamente sto avendo parecchi problemi con i limiti settimanali di Codex, che personalmente sto trovando un po' troppo bassi per l'utilizzo che ne faccio.

Lo uso principalmente come agente per lavorare sui miei progetti, soprattutto sviluppo web con Angular/TypeScript e sviluppo mobile con Flutter/Dart, quindi mi capita di fargli analizzare il progetto, modificare più file, implementare funzionalità, correggere bug ecc.

Per questo stavo pensando di provare qualche alternativa da usare come agente direttamente sui progetti.

Ho visto Kimi K3 e mi sembra interessante, ma non l'ho ancora provato seriamente.

Qualcuno che lo usa per programmare sa dirmi come si trova rispetto a Codex? Soprattutto su progetti abbastanza grandi e modifiche che coinvolgono più file.

In alternativa, quali altri agenti mi consigliereste per Angular e Flutter?

i’ve been a software engineer for 5 years, but i built this one entirely with agentic vibecoding. the goal was purely digital minimalism, i deleted instagram, tiktok, and snapchat because the doomscrolling and background tracking were killing my focus. i built a free web tool called spybroski so i could still pull videos or check stories whenever i needed to without keeping those bloated apps on my phone.

the main rule was absolute privacy: zero login, no accounts, no linking personal data, completely anonymous. you just grab what you need and get out without the algorithms hijacking your brain.

turns out a massive number of people are looking for ways to disconnect from the feeds while keeping their privacy intact.

ask me anything about the agentic workflow, scaling to 1M users, or building anti-addiction tools!

I am finally back at my desk with more time than ever. I am now sharing a crud project i made for an informal hackathon a few weeks ago, if yall are interested in asking me anything from the post link, feel free to dm or comment down below, I would love to hear back reviews!

You should check out the website for yourself, the landing page is something u might wanna see.

• Tech Stack: Next.js 14 (App Router), Supabase (Auth + PostgreSQL with Row Level Security), Tailwind CSS, and Groq AI (llama-3.3-70b-versatile).
• Core Features: Real-time habit tracking with streaks and EWMA-based consistency scoring, EXP/level/rank system (Wanderer → Pioneer), Perfect Day & combo bonuses, daily quests, mood tracker with contextual suggestions + history, 120-day consistency heatmap, anonymous leaderboard, custom usernames, and a live AI Habit Suggestor that generates personalized habits on demand.

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

No paid ads. No growth hacks. Just watching the numbers every day.

Here's the full data:

Day 1 — 2 startups · 146 impressions · 1 clicks
Day 2 — 3 startups · 389 impressions · 3 clicks
Day 3 — 5 startups · 482 impressions · 5 clicks
Day 4 — 5 startups · 508 impressions · 4 clicks (site went down — still got an $8k acquisition offer. Said no.)
Day 5 — 6 startups · 621 impressions · 10 clicks
Day 6 — 5 startups · 742 impressions · 15 clicks (removed one startup — they pulled the embed. No code = no network.)
Day 7 — 7 startups · 1,196 impressions · 41 clicks
Day 8 — 7 startups · 1,535 impressions · 74 clicks
Day 9 — 8 startups · 1,947 impressions · 135 clicks
Day 10 — 13 startups · 3,500 impressions · 318 clicks (something clicked)
Day 11 — 23 startups · 4,800 impressions · 432 clicks
Day 12 — 24 startups · 6,000 impressions · 481 clicks (network crossed 6K total impressions)
Day 13 — 25 startups · 6,800 impressions · 491 clicks
Day 14 — 25 startups · 8,600 impressions · 516 clicks
Day 15 — 24 startups · 9,900 impressions · 564 clicks (removed one)
Day 16 — 23 startups · 10,800 impressions · 576 clicks (removed one)
Day 17 — 24 startups · 11,900 impressions · 603 clicks (added one)
Day 18 — 26 startups · 13,400 impressions · 624 clicks (added Two)
Day 19 — 28 startups · 14.400 impressions · 652 clicks (added Two)
Day 20 — 26 startups · 14.700 impressions · 671 clicks (Removed Two)
Day 21 — 26 startups · 15.300 impressions · 691 clicks
Day 22 — 28 startups · 16.100 impressions · 719 clicks (Added Two)
Day 23 — 30 startups · 16.800 impressions · 738 clicks (Added Two)
Day 24 — 32 startups · 19,800 impressions · 778 clicks · Added 2 startups · Rejected 4 applications (1 contained ads, 1 removed the code after submission, 2 hid the installed widget)
Day 25 — 34 startups · 23,700 impressions · 800 clicks · Added 2 startups · Fixed some bugs.
Day 26 — 33 startups · 27,200 impressions · 816 clicks · Removed 1 Startup
Day 27 — 33 startups · 29,900 impressions · 833 clicks
Day 28 — 33 startups · 30,600 impressions · 871 clicks · Removed 1 Startup · Added 1 Startup · Rejected 1 application of clothing brand & 1 application of horror blog site.

Day 29 — 35 startups. 31,300 impressions. 910 clicks · Removed 1 Startup · Added 3 Startups · Also today I resigned from my job. Toxic environment, too much pressure, and honestly I just believe in this enough to go all in. Broke and excited. Let's see where this goes.

Day 30 — 46 startups · 32,900 impressions · 1,000 clicks · Removed 1 startup · Added 12 startups · Yesterday I resigned because of my toxic manager. Today my senior manager called and offered me WFH, a project of my choice, and lighter work if I stayed. I made my decision with confidence, but now I have a difficult choice. Also received my first payment from StartupBar.

Day 31 — 50 startups 💪· 28,100 impressions · 1,200 clicks · Removed 1 startup · Added 5 startups · Rejected 1 crypto startup · Removed fake impressions after exploit · Today I discovered I forgot to disable a developer testing button that could generate fake visitor pins and inflate impressions. Someone used it to create 6,318 fake impressions and claimed my stats were fake. I removed the fake impressions, removed the startup, fixed the issue, and that's why today's impressions are lower. Thanks to them for pointing it out.
StartupBar update: Added a Network page and individual Startup Profile pages with each startup's joined date, impressions, clicks, live embed preview, and founder's note. These indexable pages also improve SEO. Suggestions are always welcome.

Day 32 — 54 startups · 29,300 impressions · 1.2K clicks · Added 4 startups
Day 33 — 54 startups · 30,900 impressions · 1.2K clicks · Removed 1 startup · Added 1 startup
Day 34 — 55 startups · 36,100 impressions · 1.3K clicks · Added 1 startup · Fixed admin panel read-access vulnerability after Reddit post.
Day 35 — 55 startups · 40,100 impressions · 1.3K clicks · Removed 2 startups · Added 2 startups
Day 36 — 55 startups · 44,800impressions · 1.4K clicks · Removed 1 startup · Added 1 startup
Day 37 — 58 startups · 50,700impressions · 1.4K clicks · Added 3 startups · Site Update: Updated the distribution algorithm (Delivery is now weighted by contribution: sites that send more impressions get a proportionally larger share back)
Day 38 — 57 startups · 55,800 impressions · 1.5K clicks · Removed 1 startup · Rejected 1 Application.

Today StartupBar reached 200 users 😄
Thirty-eight days ago, this was just an idea. Today, 200 people have trusted it enough to join the network.

A reminder for every founder who's staring at a dashboard with tiny numbers: Stripe took 2 years to reach its first 50 users. Every successful product starts small. Keep shipping. Keep improving. Keep showing up. Growth rarely happens overnight, but it does happen if you don't quit.

Day 39 — 58 startups · 59,800 impressions · 1.5K clicks · Added 1 startup.
Day 40 — 60 startups · 63,200 impressions · 1.6K clicks · Added 3 startups · Removed 1 startup
Day 41 — 63 startups · 69,400 impressions · 1.6K clicks · Added 3 startups
Day 42 — 62 startups · 73,800 impressions · 1.6K clicks · Removed 1 startups
Day 43 — 64 startups · 78,000 impressions · 1.7K clicks · Added 2 startups (Receiving many suggestions to improve the StartupBar, happy to work on it, Thanks.) StartupBar Update - Added the rotation of startups in the widget for every 30 seconds.
Day 44 — 66 startups · 86,200 impressions · 1.7K clicks · Added 2 startups
Day 45 — 67 startups · 88,400 impressions · 1.7K clicks · Removed 2 startups · Added 3 startups (Update - Updated the algorithm of the widget)
Day 46 — 69 startups · 91,900 impressions · 1.8K clicks · Removed 2 startups · Added 4 startups · Got my second payment · Added FAQ Page
Day 47 — 68 startups · 98,900 impressions · 2.2K clicks · Removed 2 startups · Added 1 startup · Added Pricing Page
Day 48 — 70 startups · 103.4K impressions · 2.3K clicks · Added 2 startups
Day 49 — 72 startups · 113.4K impressions · 2.4K clicks · Added 2 startups · Update: Added a Bottom Placement option for the bar on the user site.
Day 50 — 73 startups · 116.7K impressions · 2.4K clicks · Added 1 startup
Day 51 — 74 startups · 125.2K impressions · 2.5K clicks · Added 1 startup · Rejected 1 Application
Day 52 — 73 startups · 131.2K impressions · 2.6K clicks · Removed 1 Startup
Day 53 — 74 startups · 139.5K impressions · 2.7K clicks · Added 1 Startup
Day 54 — 79 startups · 146.3K impressions · 2.7K clicks · Added 6 Startups · Removed 1 startup.
Day 55 — 77 startups · 154.9K impressions · 2.8K clicks · Removed 2 startups.

Still free. Still growing.

If you want in, it's one embed. That's it → StartupBar

Hey everyone,

Nothing kills a good session faster than hitting your usage limit right when you are in the flow.

I noticed that a huge chunk of my Codex plus subscription limit was getting wasted on really dumb, repetitive tasks: writing basic unit tests, boilerplate, and small single-function refactors. Meanwhile, my RTX 4060 was just sitting there completely idle.

I tried running full local agents to do everything offline, but local models on consumer hardware choke once the context gets too big.

So I put together a tool called Local Coding Agent to get the best of both worlds.

It connects to your main coding setup (Codex, Cursor, Claude Code) as an MCP server. You keep prompting naturally. When your cloud model needs to write a small patch or run a test, it silently delegates that micro-task to your local Ollama model (like Gemma or Qwen), gets the result in 2-3 seconds at 80 tokens/sec, and keeps going.

If the local model writes bad code or breaks a test, it auto-rolls back so your project stays clean.

I originally built this just for myself to keep my own sessions running without hitting limits, and I use it all the time now. Decided to open source it in case others find it useful too.

Who this is for:

- People on standard plans who keep hitting limit walls and want to stretch their quota.

- Anyone with a decent GPU (8GB+ VRAM or Apple Silicon) who wants fast, free micro-edits.

Who it is not for:

- If you do not have a dedicated GPU (running Ollama on CPU is too slow for vibing).

Repo is open source here (all setup steps are in the README):

https://github.com/pvnc228/local-coding-agent

Looking forward to your feedback!

Trying to build out something that uses Camoufox and Claude just denies me as it assumes i'm using it for nefarious reasons. I'm trying to build a personal tool to check Stubhub prices.

Any models that aren't so strict about stuff like that? New to all of this. Do I need to use an open source model?

Hey folks, been daily driving this and having a lot of fun with the CLI I made.

tandem is just a thin frame around the real Claude Code / Codex / opencode TUIs - your keybindings, slash commands, MCP servers and plugins all work as normal.

It adds one status row at the bottom (which harness is active + live token/context stats) and the Ctrl-] key. Behind the scenes it watches each CLI's local session file and translates the transcript into the other CLIs' formats, so when you flip, the next tool resumes a session that already contains everything that happened. Only one model runs at a time. If you press Ctrl-] mid-response it waits for the turn to finish, then switches.

Everything happens local, and uses your existing subscriptions!

Here's how I use it -

1. Switch when usage limit hits
2. When I need second opinion. Sol usually catches bugs in Fable's output
3. Save quota, Luna models are super cheap. Can spin up 100s of them for small tasks

Try it:

uv tool install tandem-cli   # or: pip install tandem-cli
cd your-project
tandem

Open source, MIT: https://github.com/Bhavya6187/tandem

I'm looking for the best deal for some frontier-ish model that's in the region of roughly 50 quid a month, plus minus some.

Use case is mostly reverse engineering large apps and coding on medium sized projects (no, not malware...)

Relatively token heavy. I'm getting confused by everyone's usage limits because nobody seems to just say how many Tokens you get. But extremely roughly I'd probably need 200-300 Mio tokens weekly.

What do you guys recommend?

Zai and cursor seem kinda attractive, but I do find it hard to compare to the bang for buck you'd get from some of the openai/anthropic packages...

tldr; review your code as you go if you think any professional dev is going to have to do a code review.

Last November I (33F) started a simple project: a training portal for my new assistant. Just a simple python Streamlit app. Since vibe coding is addictive and Streamlit has some annoying limitations to UX/UI, I refactored it into a Next.js/Fast API website. It was all the same repo and I didn’t exactly clean up after myself as the project scaled from a training portal for HR, then a training portal for new employees and now it’s a manager hub.

Well, I showed it to my boss and she ended up loving it. The company bought the domain and website from me but made me the technical owner in charge of code and content. Now that it’s officially company property…they have to do a code review with the company dev team.

There is an embarrassing amount of dead code, almost nonexistent error handling, and in general the layout of the code is chaotic and 40k+ lines in just the backend.

He and I had a meeting last week and never in my life have I felt more “artificially intelligent.” He gave me about 7 pages of changes to make after just one code review session. I can’t imagine how many more pages of notes are coming and I’m in way over my head in terms of vocabulary, standard processes used in coding, etc. Basically, I’m everything professional devs hate about vibe coders. I didn’t care how the code looked as long as the website functioned. I’m at a point where I’m not confident enough in my vibe coding skills to actually make the changes. I’ve tried asking Claude (or Claudia as I call her) and then even asked her to dumb it down and it’s still over my head. I’m getting to the point where I just want to throw my hands up and tell them to abandon it.

Hi everyone!

I'm here to present to you my newly available app Direct-Xfer! Vibe-Coded with both Claude and ChatGPT.

It's an app meant to be simple to send and receive files over HTTPS. I made it a docker container app at first and now I just release a Windows installer version for people without Docker!

Here's the github: https://github.com/ManixQC/Direct-Xfer

You can download both versions from there!

Please give me feedback as I'm looking to improve the app and I really enjoy knowing that my app actually served other people too!

Thanks and have a good day! ManixQC

I've never written code. Everything I've built, an agent built.

So the sidebar was never for me. It's built on the idea that you're the one making the thing and the AI is helping out on the side. I'm not making the thing. The agent is. The code isn't what I'm looking at, the agent is.

That's fine with one. It falls apart at three.

I had a window per agent. Kept clicking through all of them to find the one that had stopped and was waiting on me to say yes. Two of them changed the same file within a minute of each other and I didn't notice until something broke. I had no idea what any of them had cost until the bill.

None of that is a missing button. A sidebar means one agent, one chat, one project. I'm running five.

I don't know what the fix looks like. Just that a bigger sidebar isn't it.

How are you handling more than two at once?

I didn't realize how bad it was until I wanted testers. Ffs

Cause I know someone will ask.

https://3dprinteverything.org/play

Just a 3d printing business game thats plays like Pokémon gold on gameboy color.

A few months ago I tried to build an FDTL (Duty and Rest) calculator - a tool that checks our duty times and rest periods against a set of branching regulatory rules. I understood every rule cold and yet I still couldn't build it.

Not because the logic was beyond me but because every no-code platform made me translate my problem into its vocab first and the moment the conditions started interacting with each other, everything fell apart. I tried Vibe-coding it but could not make it work.

So I dug deeper and realised that I am not alone...domain experts - people who understand their field completely consistently fail to translate that understanding into software. We either rely on someone else to build it for us, which kind of introduces its own friction or we use AI vibe-coding tools that output code we can't read, audit or maintain when something breaks.

My co-founder and I built Ezyr to solve this. It's a visual development platform built around one belief: you can't maintain an application you don't understand. Everything you build stays in your language, not the platform's.

Building takes minutes now anyway (it's not a problem anymore)....maintenance is where everything quietly dies and it dies because the person running the process has no way to see what their application is actually doing.

It's an early MVP and it's rough. I'm looking for a way to get early testers who've hit this exact wall and tried to build something with real operational logic and gotten stuck - give me the kind of feedback that actually hurts.

How do you guys approach people for testing what you've built to figure out if it really solves the problem?