An experimental Nintendo 3DS emulator in JavaScript that runs in the browser (open source, GPL-3.0)

I'm building Pica3DS, an experimental 3DS emulator written from scratch in JavaScript. It has no build step and runs in the browser without an install. I used Claude Code for a good part of the development.

ARM and Thumb CPU with a JIT compiler
Software PICA200 GPU, plus a WebGL 2 renderer
Save states, save data, and rebindable controls

It's early and incomplete. Networking, camera, and stereoscopic 3D aren't implemented. The repo includes no game data, firmware, or keys. Users bring their own decrypted dumps.

Source and bug reports: https://github.com/khalzin0/Pica3DS
I'd appreciate feedback on the CPU compiler and the GPU renderer

A 9:16 version changes the space available for a presenter, title and captions. Those layout changes can use the performance already accepted for the 16:9 version.

Hypit records the canvas and component layout in the production source. The Run separately chooses the material used by this execution. Selecting the earlier media output retains that footage; selecting its completed SemanticTake also retains the preparation and word timing when the Script identities still fit.

The new source authors the vertical framing: the destination frame, fit, text placement and wrapping. Those choices describe how the existing material appears in the new canvas. The selected graph then builds and renders that composition around the retained output.

This gives the agent a precise revision task. Change the geometry for the vertical layout and keep the accepted performance selected in the Run. The new render uses the authored crop and arrangement, with the same chosen take underneath.

kimo is an open-source video editor with no GUI. Every feature is an MCP tool, and it ships as one small Rust binary. GPT-6.1 Sol on extra high made all of this video, card animation, colour and captions, purely through kimo tool calls.

What's new in v3:
- render_frame returns the frame inline as an image, so the model sees its own edits
- contact_sheet, describe_frame and audio_probe to check a timeline or find silence before cutting
- diff_frames and project_diff for before and after
- grouped, compact tools/list (16.5 KB down to 4.5 KB), search_tools and tool profiles so it only loads what it needs
- chunked export jobs you can start, poll, cancel and resume, with crash recovery
- batch calls with foreach, recipes, and text layout helpers (safe margins, constraint solver, lint_frame)
- golden render tests with bundled fonts, so output matches frame for frame across machines
- a plain CLI over the same core, plus a Python client

v3.0.0 is up!!

https://github.com/naman-sharma12345/kimo
https://getkimo.tech

If you hook it up to your agent, tell me which edit it couldn't do.

The next person editing a generated video needs the files that describe it and the material those files actually select.

Hypit's editable-project handoff includes the Author Sources, Recipes, Runs, assets, project components and dependency lockfiles. A Run can also select an accepted output from an earlier Build, so the Result repository is part of that handoff.

There is a specific reason to keep .hypit/results/ intact: a later Result can forward an output held by an earlier Build. The latest build directory can therefore depend on media stored elsewhere in that repository. Keeping the referenced Results preserves both the accepted material and the structured values used to continue the project.

Supplied local files need to travel with the project too, with their paths kept valid or rebased. The receiver prepares the Runtime and credential configuration needed for their next execution.

For a reference rebuild, this is what lets someone change the authored title, timing or layout and continue from the selected performance. The project handoff carries the choices that made the existing cut, including which result was accepted.

Hey everyone,

I currently run 6 micro SaaS that are actually live and generating a bit over $20,000 in recurring monthly revenue.

The wildest part? I barely wrote any code myself. I used AI to generate pretty much everything from the database structure to the frontend.

It definitely wasn’t magic from day one. I spent a lot of hours stuck on buggy code before I finally figured out a system that actually works:

- Keep the idea minimalist (a real MVP, nothing fancy)

- Guide the AI step by step instead of asking for everything at once

- Launch fast to get real users and feedback

Lately I’ve seen way too many non-technical founders quit at the first AI bug. It’s a shame because the technical barrier has basically disappeared.

AND PLEASE, STOP BUILDING ALONE IN YOUR BEDROOM

I’m starting a community.

Full transparency:

I’ll probably charge for the full program later. It makes sense with the specific workflows and copy-paste examples I’ll be sharing. But right now the main goal is just to build together. Working alone is the fastest way to give up.

If you want to join and build or market your own AI SaaS with us,

drop a comment or send me a DM and I’ll send you the link.

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.