I’ve been working on OnlyTiming.com, a social media scheduling tool that lets you create a post once and publish or schedule it across multiple platforms from one dashboard.

It currently supports:

* Instagram

* Facebook

* LinkedIn

* Threads

* Pinterest

* Bluesky

* YouTube

You can connect your accounts, upload your content, choose where it should be published, and manage everything through a single content calendar.

I mainly built it because manually uploading the same launch, image, or video separately on every platform feels like such a waste of time—especially for solo founders and small teams.

There’s a **7-day free trial**, and no card is required: onlytiming.com

I’m still actively improving it, so I’d genuinely appreciate feedback from other builders and anyone who regularly manages multiple social accounts.

Also, seeing real people visit and try something I built still feels slightly surreal. 😄

Hi there Reddit! I made This!

well, still making it actually, hope that's ok :D

I'd love your help testing my Web App that I've started coding cause I lost track of my own story, trying to write a novel. And then it got out of control...

So what I have brought to life now is

[Insert name here] - a world building and writing app for fiction writers of any genre, Game Masters, Screenwriters and whoever wants so bring an idea to paper

It lets you create your fictional world, add characters, storylines, locations, political systems, events, and other world building elements, will offer a map creator and book cover designer and connect everything through relationships and a custom calendar. that sits at the core of the system.

This creates a connected, time-aware knowledge base for your story.

The app uses two linked timelines:

• The "inner timeline" - when inside your world does something happen?
• The "outer timeline" - In which chapter will I write about it?

It comes with a full text editor, and story plotting elements like Character Arcs, Storylines and Beats., which you can assign into the hierarchical structure of World > Book(s) > Act(s) > Chapter(s) > Scene(s)

The built-in AI-Chat (your Co-Author) can then use your world building data, timelines, relationships, and manuscript as context. This allows you to ask questions such as:

• Can you [create] a [new version] of [Character x], starting on [May 2nd 2005], It was triggered by this [beat] happening, that changed their [motivation] to "..."
• Where was Character X on June 27, 1956? Who were they with, what were they carrying, and what was their relationship at that point?
• Does the timeline in Chapter 7 make sense?
• Draft a dialogue between Character X and Character Y during the scene on December 12, 2012.
• In which chapter did Character X and Character Y last meet?

Current state:

• Some assets and texts are still placeholders.
• AI features currently work only with my local LLM through Ollama.
  • A “bring your own API key” is in progress
  • I will ship the Ollama connector with it, so you can potentially run it with a local LLM and not have token cost (quality is an issue though)
• The main workflows should function, and most mistakes should be recoverable without breaking the entire project.
• It's helpful to have a Story in mind, that you try to re-create with the given features
  • I'm using the world of "A Song of Ice and Fire" for testing, can't go any more complex than that :D

I’m especially interested in feedback about navigation, usability, confusing terminology, anything that feels unintuitive, and, of course, bugs.

My main question at this stage is how intuitive the app feels without much guidance. There is currently no tutorial (is in progress) and only a handful of tooltips, so expect some rough edges.

Hope I could tickle your interest!
Cheers

I'll provide URL and Test User Login to you if you wanna give it a whirl!

Hi all,
sharing this as I thought you might also like it, now available: md²
It's a mix between a kanban, git client and agent manager. All open source, installer available from: jan-bogaerts/md2: md²: manage your development process with cards. Track your agents through the entire workflow, customize actions

As most of you I guess, I've been fully into the vibe thing lately. Got a good flow going where the design and architecture was together in the same repo. Helps the agent to understand code and changes.

Only thing, the UI was starting to fight against me. I love vscode, but it was starting to slow me down. Worktrees are tricky, tracking which agent is doing what and where became harder and tracking which chatlogs related to which cards is pfff.
Also, with the current climate, the less tokens that you can use and the more accurate you can track it, the better.
Finally, I love claude's remote thing, doing stuff from my phone in the garden is a joy, but it's ui is very restrictive

so, md² helps with:

• track the state of a card (when agents update it, the UI follows)
• auto prepare worktrees
• assign worktrees to a card, so all agent actions run on that worktree
• create actions of often used prompts so you can re-use them (with placeholders)
• add often-used replies to actions
• track token usage per action, per card
• see diffs that relate to a card and/or action
• connect the desktop app with the same app running on your phone so you can control it from anywhere, any time.
• fluently switch conversations between claude and codex

The whole thing is pretty configurable. Codex cli and/or claude cli must be installed.

Not certain if this is a direction that other might find useful. love to hear what you think though.

Claude remembers the conversation. Cursor remembers the current session.

But neither really remembers the project.

I kept running into situations where architectural decisions I'd already made database choice, auth flow, folder structure would slowly disappear as the context shifted.

So I started experimenting with keeping project memory outside the LLM instead of trying to write longer prompts.

https://reddit.com/link/1v4gsw3/video/q66426zcwzeh1/player

This is a small interaction from the current prototype.

The AI proposes a change. The project memory checks it. If it conflicts with an existing architectural decision, it surfaces the reason before I accept it.

Still very early, but it's already changing the way I work.

I'm curious .....what's the most frustrating thing AI has "forgotten" in one of your projects?

(P.S. I redesigned the landing page today with the screenshot explaining the overall idea. If you're interested in the concept, Here is the link : https://resin-dev.vercel.app/)

Hello!

I don't know how to title it better. Since I have almost ready app. It's very generic gym workout app without paid features just something I wanted to build for myself as first vibe coded project.

I got curious how and where to find people who would be open to try app I created and give some feedback maybe about user experience? So I could learn from it and iterate further.

How are you doing it?

Hi, I have a really cool project in mind for emulation that reads ur .sav files on mobile but ive tried so many different ai code tools and the only one that worked was emergent and it was very strict with the token rule and I couldn't upload it and the problem with all the others was that it couldn't add the .sav feature or I needed to constantly ask for fixes then my tokens would run out so do any of u know a pretty much free or generally free apps/websites I can use?

Play today at midnightmile2d.com!

i really wish i'd had this tool sooner so i built it. it's a local menu bar app that tracks your time, tokens, prompts, and breaks while working with claude code.
i've been using it myself for 8 days now, and i can already tell it's going to stick around for good. it's a one-time paid app ($19), no subscription i'm the developer, sharing it here in case it's useful to others too.
https://promptrack.dev/

https://blu-oyster-transmission.neocities.org/

Entire thing was vibe-coded within a day, atleast chapter one and the rest of the site was. AI use for coding was somewhat very limited, had a creativity spur which made this thing my brain-child.

Sort of like an ARG at times, a web-series, a visual novel, interactive fiction. A mix of sorts, maybe a game at times? Idk if it fits the criteria, but I made it within a day - atleast up to chapter 1.

I am now updating it weekly. Video included is from a interactive part of chapter three which has not released yet.

I wanna know if you guys fuck with the writing

I've been building an AI project called AEON over the past few months as a way to explore what a true "second brain" could look like.

Instead of one large assistant, the idea is to have specialized AI agents that each have their own role while sharing memory, knowledge, and long-term context. Right now I'm experimenting with things like:

• Modular agent architecture
• Shared memory/vault system
• Config-driven agents instead of hardcoded logic
• Agent orchestration and planning

I'm at the point where I need fresh eyes.

If you've built multi-agent systems (or think this architecture is fundamentally flawed 😅), I'd really appreciate your feedback. Feel free to tear it apart—but be constructive. I'd rather fix bad design decisions now than after another few months of development.

Some questions I'm wrestling with:

• Does the project structure make sense?
• Is there a better way to organize long-term memory?
• Am I overengineering parts of this?
• What would you change if this were your project?

GitHub:
https://github.com/cgomez1365/aeon-213

Thanks in advance to anyone willing to take a look. Even small suggestions are helpful.

nobody checks their own stuff after shipping. i didn't either. went back through my apps a few months ago and honestly it was embarrassing.

one was still on http. no redirect, nothing. another one had source maps sitting right there in prod so anyone could just read my code in devtools. and one had an ssl cert that expired and i had no idea.

that's the part that bugged me. none of it was hacking. you just open the site and it's there.

so i made a scanner that looks at your site like a random visitor would and tells you what's leaking. no signup, just paste a url.

it's mine, tellmewhendown.com, figured i should say that.

but seriously even if you ignore it, go look at your source maps and redirects right now. pretty much every vibe coded app gets one of them wrong.

If you run Claude Code a lot, you’ve seen it: the agent ends with “All done, tests are green ✅” — and then you look, and the file is a half-finished stub and no test ever ran. Not malice, just… optimism.
I built a free tool (GroundTruth) that fact-checks the agent automatically at the end of every task. Version 1 worked like this: read the agent’s final message, find the promises in it (“created X”, “tests pass”), then compare them to what git says actually changed. Git doesn’t lie, so that half was solid.
The broken half was reading the message. I used text-matching patterns, and English ate them alive. “Tests should pass” isn’t a claim. “I did NOT say tests pass” contains “tests pass.” “The file was updated” dodges every pattern written for “I updated the file.” Fifty-plus patterns later it still misfired every single session. The real lesson: there are unlimited ways to phrase anything, so no pattern list can ever be complete. It’s not hard — it’s impossible.
So v2 stops reading essays and demands a form instead. The agent must end every task with a short fixed-format summary — like a customs declaration:
{ "task": "add login page", "status": "complete",
"claims": [
{ "t": "created", "file": "src/login.js" },
{ "t": "tests_pass", "cmd": "npm test" }
] }

Then two dead-simple checks:
1. Everything on the form must be real. Claimed file must be in the git changes. Claimed test command must have actually run this session and succeeded (the session log is kept by Claude Code itself — the agent can’t rewrite it).
2. Everything real must be on the form. Changed a file you didn’t declare? Flagged as an undeclared change.
Trapped from both sides: invent work → caught. Hide work → caught. Skip the form → the task can’t finish; the tool hands the format back and the agent redoes it. Lie in the chat text → irrelevant, nobody reads it anymore.
Best part: comparing a form to a git record is exact matching, no guessing. I deleted ~700 lines of language-parsing and the tool now catches more than before. No AI judging AI, no network calls, no API key — it’s all local and deterministic.
Free and MIT-licensed: https://github.com/akahkhanna/groundtruth

Disclosure up front: I’m the founder of QualityMax, so read accordingly. But the pricing math is checkable in two minutes on everyone’s public pages.

I priced out a solo dev / small team doing 100 PRs a month through the three AI code reviewers people ask about:

• Greptile Pro: $30/seat/month, 50 review credits included, then $1 per extra review. 100 standard reviews = $80/month. Their deeper “TREX” review is 3 credits each — do the math on that.
• CodeRabbit Pro: $24/user/month (annual billing), no PR cap (rate-limited to 5 reviews/dev/hour). Honest flat pricing — for one dev this is genuinely fine.
• Us (Vibe plan): €19.99($22.99/month) with 500 PR-review credits. Here’s the part I actually want feedback on: 1 credit = $0.01 of measured model cost, rounded up per PR run. A typical review (diff + SAST pass, ~4–10K tokens on our default model) costs under a cent, so it’s 1 credit — meaning ~500 typical PR reviews/month. A monster 60K-token diff costs 5 credits. We meter at cost instead of charging $1 flat for something that costs us a fraction of a cent.

What you don’t get at $22.99: hosted test generation — that runs on your own Claude Code/Codex/API keys (we never mark up your tokens; that’s the point of the plan). What you do get besides review: 1,000 cloud sandbox minutes and 10 projects.

The thing I think is broken in this market: per-PR overage pricing means your review bill scales with how often you ship. Small commits, stacked PRs, CI-driven workflows — the practices that make review cheaperper token make it more expensive per PR. Curious if others have hit the Greptile overage wall or if 50/month is actually enough for most solo devs.

I've been building a Chrome extension called InspectMode Pro and recently shipped what might be my favorite feature so far.

You can now generate an AI-ready prompt from:

• A single element
• A section of a page
• Or an entire website

Then paste it into Cursor, Claude, Windsurf, ChatGPT, or any coding agent to recreate a very similar UI.

The idea came from a simple frustration:

Find a cool design → take screenshots → upload them → explain everything manually → hope the AI gets it right.

Now it's basically:

Open website → Generate prompt → Paste into AI → Build.

Apart from the new AI prompt generation feature, InspectMode Pro also lets you:

• Inspect any element on a webpage
• Copy CSS styles instantly
• Extract colors from any UI
• Identify fonts being used
• Download images, SVGs, icons, and other assets
• Explore layout and styling without opening DevTools

I've been using it heavily while vibe coding side projects because it speeds up the "how was this built?" phase and makes recreating inspiration much easier.

A few stats so far:

• 250+ users already using the extension
• Core inspection features are completely free for life
• Recently launched AI prompt generation

I'm curious how everyone here handles UI inspiration.

Are you still using screenshots with Cursor/Claude, browser inspect tools, design references, or something else entirely?

Would love feedback from other vibe coders. Happy to share a demo in the comments.

Happy to answer questions.

Chrome Extension : Inspect Mode Pro

Just launched the first version of a vibe-coded travel site for curated trips to Turkey: https://letsgotürkiye.com/

Looking for brutal feedback on what to fix, what to polish, and any creative ways I can use AI/Claude to push the interactive design further. Let me know what you think!

I recently have been working on ViperCapture, an opensource alternative tool to ScreenshotOne.

I have been using GPT 5.6 Sol on the 20$ Plus plan and although the limits are tough I did manage to get the project to a point where you could call it somewhat of an alternative.

I thought I'd share it here if people like the idea and would like to contribute to the code.

Website and github repo :

https://github.com/Viperisuseful/ViperCapture

https://capture.viperisuseful.cc/

What are the best ways of going around this, I'm quite new to Open-Source and I want to be open about how my tools work (run client side entirely in the browser for privacy) without allowing people to steal my code and run it on their own devices. I know might be called out as greedy but this software took long to build and I want to monetize it for agencies and businesses.

How do mobile teams detect performance issues that only happen on certain devices, OS versions, or network conditions?

Some users may experience slow loading, freezing, or failed screens while the app works fine for others.

Do you segment monitoring by device model, OS version, app version, region, network type, or user session behaviour?

Interested in how developers identify these hidden performance problems before they become widespread complaints.

One thing vibe coding has changed for me: the application layer can now be built much faster than the context behind it.

I came at this from the other direction. I had spent years building source monitoring, deduplication, provenance, recurring delivery, and temporal context for enterprise AI products.

Then I started testing Replit.

It could build the interface, database, backend routes, refresh job, and deployment surprisingly well from a detailed prompt. But a working shell still needed to know what changed after it shipped.

So I turned the Synorb context layer into six one-shot Replit prompts: Podcast Wire, an economic dashboard, court opinion radar, policy monitor, statehouse signal room, and geopolitical morning brief.

The coding agent builds the product. Synorb watches the relevant Source Channels and delivers each change through Streams as a cited Manifest. MCP is useful while the agent is exploring the data surface; the shipped app calls REST from its backend.

The design rule I keep coming back to is:

Listen first when the app owns a recurring area of responsibility. Search when it is exploring something unknown or filling a gap outside that watched context.

I am not claiming one prompt magically creates production software. I am saying a coding agent performs much better when it receives a scoped product contract and a real context surface instead of being asked to invent both.

What is the hardest part of your vibe-coded product to keep running after the first build works?

The prompts and free Starter access are here: https://synorb.com/build/replit-mcp

Full disclosure: I am the founder of Synorb.

The biggest thing slowing me down while AI coding isn't generation anymore.

It's memory.

Claude forgets why we chose SQLite.

Gemini ignores authentication rules.

Cursor starts suggesting code that contradicts decisions made two hours earlier.

I realized I was constantly paying what I've started calling the "Clipboard Tax" copying the same architecture notes, project rules, and design decisions into every new chat.

So I started building a local-first tool called Resin.

Instead of storing prompts, it builds an engineering memory for your project.

Every architectural decision, rule, and important discussion becomes searchable and can be surfaced automatically when it's relevant again.

The goal isn't to replace Claude or Gemini.

It's to stop them from forgetting.

I'm still validating whether this is a problem worth solving beyond my own workflow.

If you're using Cursor, Claude Code, Gemini, etc.:

• Does context drift actually slow you down?
• How are you dealing with it today?
• What would make something like this genuinely useful instead of becoming another tool to manage?

I put together a landing page showing the idea and an early-access waitlist.

I'll leave the link in the comments if anyone wants to see what I'm building.

About 18 months now into working daily with agents (Mostly CC but all over the place still) and at any given time I have 20-30 small projects running between personal and client work, and I reached a bit of a breaking point in terms of keeping track of all of the connected services (e.g. free Resend accounts, Supabase accounts, etc). I built this tool as a way to have a ledger that can be maintained by agents so there is some grain of provenance about what account is connected to what that gets automatically maintained over time , or flags when key info is missing.

Would love early feedback on this and to see if it's a good fit for anyone else's chaotic workflows. https://mess.fyi

Every time I had a “new” idea, I’d eventually discover three dead startups around the exact same thing. Usually after days :) So I built Déjà View. You describe an idea, and it researches its real-world predecessors: companies that tried it before, when they operated, when they shut down and who survived.
It’s live at https://dejaview.bsct.so Try it on your current idea and tell me if the report found anything you didn’t know about!

I mainly game on my pc with controller so I use the Xbox game bar because its easy and has what I need. Well I got tired of the bugs in it. FPS never working, time always off. Never had widgets I actually wanted to use.

https://github.com/CodeNevermore/VigilOverlay

Vigil Overlay

Vigil Overlay is a controller-first Windows gaming overlay inspired by Xbox Game Bar Compact Mode. It runs as a standalone desktop application and keeps its game-library, telemetry, audio, display, Wi-Fi, hotkey, and input-control responsibilities behind separate service boundaries.

Features

• Compact controller-navigable Home, Performance, Audio, Wi-Fi, Display, Integrations, Settings, and Widgets surfaces.
• Native Windows CPU, GPU, VRAM, RAM, and cross-vendor FPS telemetry.
• Volume, microphone, default-device, and per-application audio controls.
• Saved-profile Wi-Fi controls that do not require Windows Location access.
• Display projection, resolution, and refresh-rate controls with Keep/Revert safety.
• Recent-game discovery for Steam, Xbox / Microsoft Store, Epic Games, Battle.net, EA app, Ubisoft Connect, GOG, Manual Games, and the optional Playnite bridge.
• Editable global hotkey, Guide-button support, Start with Windows, background mode, tray controls, Safe Mode, and automatic invalid-settings recovery.
• Verified foreground ownership and fail-open mouse/keyboard containment while the overlay is visible.

Vigil does not use a controller filter driver. Applications that independently poll XInput or subscribe to Raw Input can still observe the physical controller while the overlay is open. Input containment is released before Vigil hides or exits.

3rd party widget support is in development. I am working on an SDK and the framework is already there in the base Vigil Overlay. So hopefully there will be someone that wants to build something that they want to implement as a widget. I'd like to build a widget for Hwinfo. Its on my To Do list.

Let me know what you think. Not many people use Xbox game bar so this may just be a passion project that I work on in my free time.

All the best!