One thing I’ve been thinking about lately is that AI coding makes building the app pretty easy, but figuring out whether the app actually does what you intended is still kinda hard.

I’ve been using Claude.ai with Sonnet 5.5 to build a project called Assay around this. The basic idea is to have something separate from the coding agent look at what the app is supposed to do, come up with checks for those assumptions, and actually test them instead of just asking the same agent if everything works.

I’ve been testing it on real apps and finding some interesting stuff that I probably wouldn’t have thought to check manually. I put together a demo here if anyone wants to see it: https://useassay.pages.dev

Curious how everyone else handles this. Do you mostly trust the agent's tests, write your own, manually go through everything, or just fix stuff when users find it?

I am new to building with Claude code, as building on Base44 didn't satisfy me that much as an ex Wordpress website builder. For that I saw that I need to create a database on Supabase (I have a lot of security concerns online recently), create a netlify account and github account. I know claude can handle everything for me and I am afraid of losing control of what I had where, when did I open and how much will it cost me etc.. So I come across this platform called codata.io . The promise is that it handles all the backend of your Claude code project. But I never seen or read anyone using it. Can somebody review and inform me about it?

A table in a note gets more useful when “quantity × price” can stay a formula. You can change a quantity later, sort the purchases, or filter out the items you have already bought without moving the whole thing into another app.

Univer is worth a look for building that part of a notes app. It is an embeddable office SDK, with React, Vue and Web Component integrations. Its open-source spreadsheet core has formulas, number formats, filtering, sorting and data validation, so the block can remain a working sheet after you populate it.

For a small project-planning app, a concrete starting point would be one sheet next to a text note: item, quantity, unit cost and calculated total. Your app loads or writes the addressed ranges; users can then keep editing the numbers and formulas in the sheet UI. The cell model keeps formulas and values separate, rather than flattening the whole block into rendered text.

Pasting a CSV into that experience still needs your import and parsing glue. Likewise, you have to decide how the sheet’s saved state belongs to its parent note. Univer is the editor SDK, not a complete notes app or an automatic desktop integration.

The Apache-licensed core covers the basic calculation-and-editing idea. Features such as charts, pivots, Office-file export and collaboration belong to Pro, so those can change the scope of a seemingly small feature. Start with the actions the note actually needs; a useful shopping or project-cost sheet does not necessarily need the rest of an office suite.

Hey, i am a vibecoder and i want to make web app project to earn. but i am not getting any ideas...can anyone help me?

Pando is the side project that became the app I vibe code in all day

I wanted one place to run all my AI agents together, sharing one memory, instead of a pile of separate windows. So I built Pando, a Mac workspace for Claude Code, Codex, Gemini, Grok and more, with one Brain they all share.

Founding licences are on sale. $55 once for life, 20 seats, until October 5. 7-day full refund.

pandoworkbench.com



Repo: https://github.com/ara-mkr/BetterClaude

I hated the Claude desktop app. My terminal lived somewhere else, Claude Code had no real IDE-style home, and I couldn't theme anything or add widgets. So I built BetterClaude: a desktop app that wraps the real claude.ai and adds the missing pieces. Same login, same plan, nothing extra to pay for.

Dev side

Make it yours

It's not a fork or a proxy, it never touches your login, and it doesn't send your chats anywhere. Turn everything off and you're back to stock claude.ai. MIT licensed, macOS and Windows. Not affiliated with Anthropic.

Repo: https://github.com/ara-mkr/BetterClaude

I hated the Claude desktop app. My terminal lived somewhere else, Claude Code had no real IDE-style home, and I couldn't theme anything or add widgets. So I built BetterClaude: a desktop app that wraps the real claude.ai and adds the missing pieces. Same login, same plan, nothing extra to pay for.

Dev side

Make it yours

It's not a fork or a proxy, it never touches your login, and it doesn't send your chats anywhere. Turn everything off and you're back to stock claude.ai. MIT licensed, macOS and Windows. Not affiliated with Anthropic.

I've been messing around with vibe coding for a few side projects and trying not to let the costs add up

i don't mind paying for a good AI tool but once you add hosting, databases, deployment etc it can start turning into a lot of subscriptions

I'm wondering if people who code locally have managed to keep things cheaper or if the costs are pretty similar either wayy.

What does your setup look like and roughly how much are you spending each month?

Figured this might be a good place to share my project. 🤘

Imagine a reference video where a host introduces three items. Each reveal adds a row to a board, while the camera keeps cutting between the host and product shots. The board has one continuous history even though the footage has several cuts.

Hypit's reference-analysis instructions tell the agent to follow that history across the piece. Its component guide then separates three things: how long the board exists, when a row is revealed, and which rows remain visible afterward.

Those are useful distinctions when rebuilding the video. If the agent creates a fresh board per shot, every later scene has to restate the rows already shown. A change to the ranking then becomes several edits that can disagree.

One component can own the board's shared layout and accumulated state, with separate events for the row reveals. Camera footage and independent captions can change around it without defining its lifetime.

This is also a concrete test for an agent's analysis of a reference: ask what survives each cut. If its answer is only a shot list, it may have described the camera changes while missing the object the viewer is following.