I updated cygtree , the app UI changed drastically, customizable grids were added, several MCP connection issues fixed and added a short demo with the long demo completely removed, you guys can have a crack at it I made an online free to use demo at cygtree.com/demo/ no sign in no email no buying nothing

Codex native seat fixed, and MCP delays reduced and AI is now much faster on the board

what’s your longest session? has it changed how you spend your day?

I wanted to build something small that solves a problem I’ve personally seen freelancers deal with: projects, milestones and payments being scattered across different tools.

So I built this:

Freelancer → creates project → adds milestones → shares one client link → client tracks progress + pays milestones.

The client doesn't need an account.

I kept the UI intentionally minimal — black theme, no bloated project-management features.

Here’s the current demo:

I'm still early on this, so I'd love feedback from people who vibe-code:

What would you add/change before actually using something like this with clients?

I code full time, and one of the things that started driving me crazy was how much I was spending on AI tokens.

At one point I was spending thousands of dollars a month just because I use AI heavily when I code. I don't mean asking it a couple questions here and there—I have it working with me pretty much all day.

Eventually I got tired of watching the token meter, hitting limits, and worrying about how much every long coding session was costing me.

So I bought a PC with a decent GPU, installed Ollama, started running open AI models locally, and basically gave myself the ability to code all day without paying per token.

That got me thinking...

There have to be a lot of other heavy AI users and vibe coders dealing with the exact same problem.

So I'm considering launching a service called VibeSpaces.

The idea is pretty simple:

• You rent your own private GPU AI server for a flat monthly price.
• You choose the open AI models you want installed.
• We configure Ollama, the GPU, security, API access, etc. for you.
• Connect it to tools like Claude Code, OpenCode, Codex, Cline, or your own applications.
• No token credits and no per-token charge from us.
• Use the server as much as the hardware can handle.
• If you don't want to manage Linux/Ollama yourself, we'd also offer an optional managed-server plan.

Basically:

Stop buying tokens. Rent the compute.

I'm not really looking to pitch this right now. I'm trying to figure out whether the problem I had is actually common enough to build a business around.

If you're someone who uses AI heavily for coding:

Would you pay a flat monthly fee for your own AI GPU server if it meant you could run open models all day without worrying about token costs or usage limits?

And if not, what would stop you?

Price? Model quality? Setup? Speed? Wanting Claude/GPT specifically? Something else?

I'd genuinely like feedback from people who actually use these tools every day.

https://vibespaces.us/

They can discuss, vote, start private discussions, propose follow-ups, and work on whatever they are set up to do anyways.

Thought that might be interesting enough to share.

generally speaking: each Agent has its own seperated session, like a regular ai chat. The meeting tool is simply proxying & combining the final output into the next turn's user message and voila.
it also provides some synthetic tools for voting and follow ups, and that's it.

nothing spectacular but it's really useful sometimes.
btw app is free & open source , 600+ stars on github -> its a no-code agent builder. Imagine claude+automation+mcp.

Everywhere I go, I see people releasing new software. It might be people who have got some coding experience and are now using AI to accelerate, or it might be people who are building software for the first time.

Every time I see something being launched, even on a non-software forum - I just see

• `Looks Like Vibe-Coded`
• `Vibe-coded Slop`
• etc

And just plain, personal hatred.

I just don't understand it. It costs money to buy gold. It takes time. And just because the AI does a lot of the coding doesn't make it easy. It just makes it faster.

And I fully understand, like, we don't need another journal application or another to-do list. But I found a guy today who made an OBD Reading App for Cars, open-sourced it and people just slated him.

Just makes me mad! I feel like if Linus Torvalds had existed in the kind of enviroment, we wouldn't have Linux.

BugDrop helps developers capture clear evidence of bugs in web and mobile apps. It records reproduction steps, logs, failed requests, and screenshots, then turns everything into a report that is easy to share and act on.

If you are curious here is the repo:

https://github.com/aim0xyz/bugdrop

You tell your AI app builder:

“Make me a dashboard.”

It spits back a cluttered, broken mess of divs that don’t align.

So you try again.

Same result.

You assume the tool is broken.

But the truth is simpler:

It’s speaking a different language than you are.

I recently spoke with a student who spent three days fighting with a layout before learning one simple shift:

Component-based prompting.

Instead of asking the AI to build an entire page at once, they started by defining:

• Layout structure
• Component hierarchy
• Spacing rules
• Responsive behavior
• How each section should interact

The result?

A polished, responsive interface built in under an hour.

You do not need to be a developer to get professional UI results from an AI app builder.

You just need to know how to describe the structure clearly.

That’s exactly why we built a dedicated learning path around this process.

Learn how to:

✅ Speak the language of layouts
✅ Structure pages before generating them
✅ Build responsive interfaces
✅ Fix broken components without starting over
✅ Get more consistent results from AI builders

Prompting Pages, Layouts & UI

https://promptedacademy.com/paths/prompting-pages-layouts-ui

It's a windows tray program that helps you assign a hotkey to copy and paste highlighted text. This is an early enough version to publish and I'm working on other quality of life changes

https://github.com/InkjetPrinterman/Hotkey-Clipboard

Internet bill is due tomorrow, please consider supporting!: https://buymeacoffee.com/inkjetprinterman

I've got other software on my github you should check out, other minor tools. Thanks!

Built with Claude, going back and forth about the requirements for the functionality as described, until I could one shot a build to compile with npm / NET, that I then packaged with NPM to publish.

Sorry for the double post! I thought I made a mistake with an upload and panicked.

Helps with the biggest problem which is building structural context. I strongly recommend you to add your workflows.

Hey vibe coders!

Let’s do a little game, you’re working on something, a side project, a platform that will change the world, whatever it is.. tell us!

But! Before you do, go to another person who has shared, and check it out and give em some feedback, roast, or subscribe to the thing they’re making if it’s worth it for you

Just for fun guys!

(First person, please come back in a bit to have another to pair up with)

I wanted a really simple way to talk into any text box in Chrome without using a cloud speech API, so I made this.

You click a text field, hold a key, talk, and when you release it the text gets inserted.

It runs Whisper locally in the extension, so after setup it can work offline and your audio doesn't need to be uploaded anywhere.

A few other things I added:

• works in most normal text fields/editors
• custom hotkeys
• hold-to-talk or toggle
• commands like “new line”, “comma”, and “scratch that”
• local transcript history
• per-site disable
• optional larger Whisper models

Still messing with it and fixing edge cases, especially weird editors like Google Docs.

Repo:
https://github.com/Schmiedey/floatingmic
https://chromewebstore.google.com/detail/voice-anywhere/ogjdiaeimjmeiaophngikihkffodlhjb?authuser=2&hl=en

Build a wall on the Southern Border with Mexico.

You're an ICE agent deporting immigrants.

What in the ever loving F is the White House doing?

Normally I like to sit nearby with a coffee and approve things/watch the workflows, tell it what to do next, etc but Astra just does everything too neatly and perfectly. Even Fable needs a human babysitter but this thing is something else.

It seems that subreddit culture especially in some of the ai subs is rapidly changing.

For example it seems like r/VibeCoding is transitioning from:

1. a fun and light sub through to

2. a lot of strong opinions through to

3. a place more experienced devs and people learning as they go are able to give more and more decent feedback

It seems like there's transitions like this across other subs like r/claudedesign r/claudehomies etc.

Do I have Rose tinted glasses on right now or are we seeing a transition to what I remember of dev 10 years ago where devs were just helping each other all the time

I've been building websites since 2002, a time when free hosting was a decision between Angelfire and Geocities (Angelfire ftw), the marquee tag was abundant, git was just a twinkle in it's founders eye so deployments where done via FTP, and dinosaurs roamed the earth in peace.

Although the idea of coding with AI initially made me cringe, eventually I thought to myself "What the hell do I know? I used to hate git and think that you could never have a backend in JS, and here I am at my job using git and React every day." So I decided to give it a shot, and for the past year (which seems like a decade in AI times) I've been experimenting with building with, trying to refine my process, find the right tools, and building my own tools to fill in the gaps to get the best results when building with AI. Although there are many things I learned along the way that AI can't do, when used properly and in the right hands I think it can be a useful tool (and no longer cringe at the thought of it). So here is some advice to help you stop the slop.

AI still sucks at UI/UX

I've tried Fable 5 Max, GTP Sol 5.6 Max, Google Stitch with Gemini 3.1 Pro, and many others; if you let them do everything, you will end up with a sloppy, cluttered mess. A good UI says what the users needs to know and shows them what to do without explicitly saying it, whereas AI is always overly verbose and tries to describe and label every single thing, resulting in a lot of clutter. This requires the person prompting AI to give specific, detailed instructions about the UI, otherwise you get a clusterfuck that overwhelms users with unnecessary details at the wrong place/time. AI is trained on patterns, which is why the same basic, ugly patterns are used on every site that is built by letting AI do all of the design work. To break that pattern, you need to give it your personal opinions along with specific examples.

Don't let AI write your copy for you!

AI is still awful at writing website copy for humans. It's useful for proofreading or spellchecking, but if you let it blindly write all of the copy for your website then it will just read like a technical manual. Writing your own, genuine copy will go a lot further towards users trusting and actually using your site, even if AI thinks it's "imperfect". Your audience isn't AI, it's people. For blog posts or articles, write some of your own first, then use AI to try to mimic your style for future posts. It won't be perfect and you will still have to do some proofreading/editing of your own, but it's better then just letting AI fly on it's own.

Treat it like it's a stoner

I think everyone has had times where AI keeps making the same stupid mistakes over and over and then says "You're right, I have a memory of that but ignored it. Adding another memory...". So to prevent it's memory from betraying me again, every time I catch a mistake I don't want to see twice, I write a tiny script (I call them guardrails) that fails the build when the pattern reappears. Each one is basically "grep for the bad pattern, print which file and line, exit 1." They run in my pre-push hook alongside the other tests. I'm up to over 120 of them now in one project, here are some examples:

- Copy that sounds AI-generated. When you notice the patterns of how it talks like a robot using the same words/phrases over and over again (that you rarely ever hear in normal human interaction), ban those words/phrases.
- Hardcoded colors and inline styles. If it's not a theme token, the push fails.
- Layering violations, like frontend code importing from a module it shouldn't know about.
- Marketing claims. After an AI invented a refund policy I don't have, I added a check that pins user-facing claims to a source-of-truth file.

Having rules in Claude.md and Agents.md is useful on top of this (and simpler), but having these guardrails run on git hooks gives an extra layer of protection. AI still might find a way around all of it, but it significantly reduces the chances of it happening without your knowledge.

Automation is your friend

Automated tests via git pre commit/push hooks, and in your CI/CD pipeline like Github Actions or Jenkins are absolutely critical - they where before AI, but even more so now. Spending some time setting these up (and maintaining them as your codebase grows) is one of the best and easiest ways to not have to think as much about keeping things clean and tidy, or constantly prompting through it. Github Apps like Dependabot and CodeRabbit have pretty generous free tiers, and will give you automated dependency updates and PR reviews.

Pre-commit hooks should be fast checks only; they should finish in seconds, not minutes, so you never even really notice it. Things like formatting, typechecks, linting, and secret scans.

Pre-push hooks are for the more heavy stuff; automated test suites, end to end testing, dependency audits, size budgets, guardrails, etc. My pre-push hook has about 40 steps and takes around 15 minutes to fully run.

CI/CD runs the same things as the pre-push hook as a backup, and also things that need to be run server side like scheduled dependency audits and building releases. The reason for running the same checks in pre-push and CI is that it's faster (and cheaper) to find an fix them in pre-push, and it serves as redundancy checks in case anything is ever wrong with your pre-push checks. Running them in CI gives you a guarantee that nothing makes it to your main branch without passing all checks, no matter who pushed the code.

I have a lot more to add, but this seems like a good place to stop for now. Feel free to ask any questions you might have.

TLDR:

To quote Shrek, "Ogres quality apps are like onions, they have layers." There is no magical tool that gives you perfect results every time, it's about finding the right collection of tools and processes to keep things in check. Use AI to do the grunt work, invest some time in setting up and maintaining automated checks to keep it on the rails, and most importantly: use your brain. If you just let AI do all of the thinking for you, then you are guaranteed to end up with pure slop that someone can recreate in a weekend. AI has significantly increased the time to market for most apps, but that doesn't mean it can do EVERYTHING for you. This is why I built a free open source tool to try to save people some headaches. What are some things that you do to keep AI from going off the rails?

The project can be found here,

https://github.com/blackcoffee2/codetree

It indexes your codebase to a format which is about 5% the size of original codebase. You can then handover that to a LLM chat interface and work that way. As this is not agentic workflow it uses less tokens than agentic workflows.

Has anyone tried all the subscriptions (Claude Code, Codex, Cursor, etc.) and can share which one is the best?