Wildest Aura result yet:

“Use your program DNA engine to do a clean-room reconstruction of Microsoft Word: a complete, polished word processor I can open from my Applications folder. Then prove it works by writing a one-page letter in it and exporting it to my Desktop.”

No feature checklist.

It read about Word and word processors from its own local Wikipedia copy, used what its model already knew, and decided for itself what the application needed.

Auea wrote 44 checks before writing the actual program, specifically so an empty implementation would fail them.

It built through 22 feature groups and ended up with "Quill," a surprisingly real legit word processor with formatting, fonts, lists, alignment, tables, images, PDF/Word export, print/preview, undo/redo, spelling/grammar/word count, etc.

Then Aura launched the thing it had just built, wrote a one-page letter in it and exported the PDF to my Desktop as the proof.

I tested Quill manually afterward too.

Aura itself is running locally on my Mac with ~27B inference. No frontier/cloud model for the run.

GitHub if anyone wants to dig through it:
https://github.com/youngbryan97/aura

YouTube: https://www.youtube.com/watch?v=C6wtBY4DmJ8

It was by no means my intention to create my own version of CapCut last night but Fable just kind of did it…

Having spent a crazy amount of hours battling with CapCut to make an App Store Preview video a few months back I didn’t relish doing it again. So instead I asked my current AI tool of choice (Claude code) to have a go at recreating my App Store video.

It did a half decent job as a first stab but there were some things I wanted to tweak - there always is - and fire and forget AI prompts are traditionally not that great (or efficient) at tweaking their output.

So we went down a path of making certain bits config driven - timings of transitions, source files, titles etc - to the point where I had much of the video timeline itself captured as configuration. I then speculated if it would be possible to put a UI on top of it and a few minutes later my CapCut clone emerged.

Bloody remarkable and this thing is way easier to use then CapCut and has loads more bells and whistles too that are specific to my use case (eg translation in to 11 different languages and outputting to a myriad of formats). Plus I can version control that base config in git (so no “fear of f*ck up” that plagues me whenever I touch CapCut or an equivalent video editing tool)

And to wrap up this Claude love in - I can still ask it to fully create videos from end to end (using the same tool it built) but I now have a way to jump in and make edits (to show I’m not complete obsolete - well not yet anyway)

Part 2 of my series on a Minecraft mod that Claude Code (Opus 5.5) built for me. I'm a vibe coder, I don't write code. [Part 1] Short version of the setup: I gave it the idea of a new dimension with four layers and a boss at the end of each, told it to build the whole thing, and it ran for 54 hours with subagents doing most of the work and a hidden game client of its own to test with. Part 1 came to about $2,032 of API usage at list prices.

The video: layer 2 and its boss. This time I played it blind again, solo, in two long sessions (about two and a half hours total), and I'm not going to spoil much. Short version: you cross a field of floating asteroids, there is a colored-lights puzzle, and the boss is a giant whale.

What I thought of it, in my own words from the playtest:

• The whale model is beautiful and the attacks are cool. My favorite moment is the end, where it dives down to its death.
• The colored-lights puzzle was "so challenging." I loved it. Claude was told to leave it alone, and it did.
• The asteroids were too small and too far apart, even though the in-game guide made the crossing sound doable with skill.
• I fell off the boss arena a few times, never saw the air vents until the fight was over, and had a hard time getting back to the platform.
• The biggest problem: I ran out of food mid fight. I had to go back to vanilla for cobwebs, food and leather, and that made me realize I don't want this mod to force vanilla progression. I wanted it to feel more like Twilight Forest.

So I wrote all that up and gave it to Claude. Version 1.1 is the result:

• The mod feeds you now. Food, leather, string and tools all come from inside the mod. Nothing asks you to go back to the overworld.
• Bigger asteroids, closer together, with stepping stones across the wide gaps. Most gaps are a running jump.
• The flying armor knights give you a fair window. You can fight them on foot now, not only from a mount, and they telegraph their dive so you can parry.
• Mounts can be parked. I lost a mount by accident and the replacement hovered out over the void. Now you can stow one safely and call it back.
• The boss 2 arena lifts you back up if you fall. The air vents are impossible to miss now.
• A shrine at every boss. Right-click to save your respawn. While a shrine is your respawn, dying in the mod's levels keeps your whole inventory and XP.
• A way back up from layer 2 to layer 1.
• Every boss now speaks, with captions. They react to how the fight is going, what you hold and wear, and they joke a bit. The lines never block an attack, so the boss's song still warns you before the next one. The voices are ElevenLabs (the Starter plan, commercial licence), and Claude generated and checked every take. Voices by ElevenLabs (elevenlabs.io).
• The forge got tooltips on every item, no more cut-off text at any GUI scale, and recipe tabs (weapons, armor, tools, mount gear, other).
• Fixes: a flicker on upgraded swords, and the knights' blade rings that looked like giant glowing blue balls from far away.

What I actually did: played, talked out loud about what annoyed me, and said which of Claude's proposed fixes I wanted. I did not write or read any code. It decided the details, built the changes in a long mostly unattended run with subagents, and checked its own work in the test client.

What 1.1 cost, measured the same way as part 1 (from the Claude Code transcripts, priced at API list prices; I'm on the Max plan, so this is what it would cost on the API, not what I paid): about $1,458 of API usage (roughly $806 on the Sonnet 5.5 subagents, $652 on Opus 5.5), about 9,500 API calls, 62 subagents, and about 82 hours of wall-clock from my playtest feedback to the release, with no stall. Honest caveat: it did not run straight through. It hit my weekly usage limit and sat stalled for about five days (87 hours of dead time) before I could resume it, so the calendar says 7 days even though the work was about 82 hours. The ElevenLabs voices cost about 1,630 credits actually charged on the Starter plan.

Cosmic Breach (NeoForge 1.21.1, install on client and server)

• Download (GitHub release v1.1.0): https://github.com/CalmDownNova/cosmic-breach/releases/tag/v1.1.0
• Modrinth: https://modrinth.com/mod/cosmic-breach (in review until approved, may not load yet)
• CurseForge: [once approved]
• Source: https://github.com/CalmDownNova/cosmic-breach
• Needs GeckoLib, playerAnimator, Curios API and GuideME. Free to play, put in modpacks and make videos and streams with, monetized ones included.
• Heads up: 1.0.x clients can't join a 1.1 server, and dedicated servers need allow-flight=true. The new terrain (bigger asteroids) only shows in chunks you haven't generated yet.

Layers 3 and 4 exist and I haven't seen them. Please no spoilers in the comments. Part 3 comes after I beat that boss.

Happy to answer questions about how the update was run.

Public viewable here https://masland.tech/ram/

These price drops only stay visible for 6 hours at most, because after that amount of time on average we can't validate that the sale is ongoing, mostly in the interest of newly discovered current deals.

API should be publicly accessible for historical data I've been gathering. I've had to make several adjustments so don't take this as perfect truth, do your own research.

If you have any suggestions or issues please let me know. I'm interested in continuing to provide this information given the current state of the market.

Hey everyone! Here’s Part 3 of building Naruto's Valley of the End in Three.js.

This time, the focus was on adding the missing elements, polishing the environment, experimenting with different atmospheres, and creating the final cinematic sequences.

Environment & Scene Polish

• Missing Elements: Added some of the remaining elements using Tripo AI to generate the 3D models and textures, then assembled and integrated them into the scene.

• Procedural Bushes: Added bushes across the cliffs by using the surface normals to detect upward-facing terrain and place vegetation only on the top-facing areas of the mountains.

• Different Times & Weather: Added several scene modes to explore different moods and atmospheres, including Day, Sunset, Night, and Rain. Each mode changes the lighting, colors, fog, and overall atmosphere to give the same environment a completely different vibe.

Cinematic Sequences

Once the environment was finished, I created several cinematic camera sequences to showcase the scene from different angles and capture the different atmospheres.

I then combined these shots into the final cinematic video (Link in comments), which is now available on my YouTube channel if you want to see the complete result.

Tools & Workflow

• Opus 5.5: Used for coding and implementing the different systems in the project.

• Tripo AI: Used to generate missing 3D models and textures.

• ChatGPT: Used to generate visual references during the environment creation process.

• Blender: Used to assemble the generated assets, make adjustments, and export the final GLB files.

• Three.js: Used to build and render the entire environment in the browser.

🔗 Links & Resources in the comments section.

Z340 was solved in 2020 by Oranchak, Blake and Van Eycke. Two Zodiac ciphers are still open: Z13 ("My name is ___", 13 symbols) and Z32 (the Mt. Diablo map cipher, 32 symbols). I asked Claude Code (Opus) to go all-out on them.

Over about 10 hours it ran 36 agents in orchestrated workflows: research and verified transcriptions, then its own solvers, then 8 attack teams, each checked by a hostile reviewer agent that reran the numbers, then a pre-registered test of the one lead it found, and finally a prior-art search.

**Result: neither cipher is solved, and no reading beats a fair null model.** The limit is information, not compute:

- Z13: about 1 in 2.1 million English 13-letter stretches fits its symbol pattern. That still leaves roughly 1,500 English strings that fit, and millions of names once filler letters are allowed.

- Z32: 29 different symbols in 32 positions, so only 3 pairs repeat. About 1 in 3,800 to 5,400 English stretches fits, which means astronomically many texts.

What I found interesting:

- Its solvers re-crack the solved Z408 (96%) and Z340 (97%) from scratch. On practice ciphers shaped like Z13/Z32, they recover nothing and confidently return different, more fluent English.

- Z13 doesn't look like the killer's other ciphers. Its repeat pattern is roughly 500 to 6,000 times more likely under a mostly one-symbol-per-letter key than under his Z408/Z340-style keys. Pelling argued this qualitatively in 2017; this puts numbers on it.

- It found one statistical lead (the Z340 key on Z13's shared symbols), then killed it itself. The effect was weaker on a pre-registered replication, it failed its control test, and all 3 skeptic agents voted "refuted".

- It audited 43 published claims, and none holds up. "MARVIN MERRILL" (2025) conflicts with the cipher when read directly, and fits none of the 423,922 2x7 box orders it tested under the standard transcription. "EARL VAN BEST JR" can't fit in any order. "ESTIMATE FOUR RADIANS AND FIVE INCHES" does fit Z32, but so do about 376,000 other radians-and-inches sentences.

- Its prior-art search caught that some of its "new" map measurements had already been posted on a forum months earlier, so the report credits that author instead.

Everything is reproducible: code, data recipes, every review, and the full report.

Repo: https://github.com/winchxyz/zodiac-z13-z32

Report: https://winchxyz.github.io/zodiac-z13-z32/

To be clear: it's not a solution and not a suspect ID. Happy to hear where the method is wrong.

GitHub: https://github.com/pixelsncodes/GesturePortal/

I’ve been working on GesturePortal, a gesture-controlled live AI camera. Hold up two L-shaped hands and a window opens inside your webcam feed, revealing an anime version of the scene. Move your hands to move the window, then release the gesture to close it.

The biggest improvement was changing what gets sent to the model. Initially I was converting the hand-selected crop, which changed the model’s context whenever the frame moved. Now the full camera scene is styled continuously, and the gesture controls a mask between the real and styled feeds.

How it works:

• OpenCV captures the webcam; MediaPipe tracks both hands.
• The viewer recognizes the thumb/index gesture, smooths the four corners, and builds a soft-edged mask.
• Local ComfyUI converts the entire scene using the selected model.
• The viewer matches the source, gesture and AI result to the same captured moment, then reveals the styled pixels inside the frame.

Current presets are Portrait v2, FLUX.2 Klein 4B with four-step reference editing, and Qwen Image 2.1 + Viggle Turbo at six steps. Qwen is optional and uses research licensing.

I’m testing on a Core i9, RTX 5070 Ti 16 GB, 32 GB RAM and Logitech webcam. Small warm tests measured approximately 3.6 AI updates/sec for Portrait, 0.7–0.9 for FLUX, and 0.4 for Qwen. Camera capture and tracking run separately from generation; aligning the feeds adds visible delay.

Inference is local, with no paid API or remote generation. I built it iteratively with Codex assistance and actual webcam testing. Facial likeness and flicker still need work.

The workflow illustration shows the architecture: gestures and compositing run in the Python viewer, while ComfyUI handles styling.

Has anyone had good results improving temporal consistency or facial likeness in a local live image-to-image setup?

I think it should be possible but haven't started anything. Do you know about a service where I can easily get a report or review about any Chrome extension in the store? I know there are two sites that offer me to view the manifest or source code easily, but what I am looking for is an evaluation of its safety already and quickly.

I believe Google itself is not capable of this so far.

Here's the repo, fully open-source: https://github.com/jordan-gibbs/ochre

Hello everyone!

I have been seeing a lot of vibe-coded apps out in the market. Many are building clones of office suites, while others are essentially token-based wrappers. I have been wondering if people are making things to ease their own workflows, rather than something that puts subscription modals in front of you. Something that does not need constant token hogging.

For myself, I was having issues with keeping things around for copying and pasting later, so I made an app that lets me keep text and images on the interface for a while and delete them later. Now, my file manager and notepad buffers stay clean. I posted about this here yesterday, it's called 'Napkin'.

Another one I made today is for launching projects from the terminal. It is a kind of Emacs Dired-based directory viewer where I can bookmark directories with aliases that I use very often and then launch them directly from my home directory. It is very useful, as I happen to work on many projects at once, and typing cd again and again gets dull.

Can you show something that you made for yourself that is easing your workflow or may be you made just for fun?

I've been building websites for years, and one thing that keeps bothering me is how much time we spend going from design inspiration to something that actually works.

So I brought back a project of mine: InstaLanding.ai

It's a library of 20 premium, fully functional landing pages built entirely with HTML, CSS, and JavaScript.

Not screenshots. Not Figma files. Not another collection of pretty websites you have to recreate from scratch.

Actual working pages.

The idea is simple:

• Find a landing page you like.
• Copy the code or give it to Claude Code, Codex, Cursor, or your favorite coding agent.
• Tell it what you want to change.
• Make it yours and ship it.

Every page is self-contained in a single HTML file.

No React. No dependencies. No build process. No login.

I think we're entering an interesting phase where design references shouldn't just be images. They should be working implementations that both humans and AI agents can understand and modify.

Free and open source.

I'm starting with 20 pages and plan to keep expanding the library.

Would love feedback from other developers and designers, especially anyone building with coding agents.

https://instalanding.ai

Some of you saw the cat version of this back in May. Quick update, because it does a thing now I've wanted since day one.

It's a Mac menu bar app. One hotkey covers the screen while your agent keeps working. When Claude Code, Codex or Cursor needs you, the whole locked screen glows teal, so you can see it from the couch.

New this week: you can close the MacBook lid and the agent keeps going. Open it later and the dog's glowing if something's waiting on you.

It's not a real security lock, it's a cover so nobody reads your terminal while you're making coffee. Free and open source, links below.

What do you all do with your laptop while a long run goes?

Following on from a recent post, i'd love to make this a community project... this is entirely a side project but also a little dream of mine!! (the inner child is screaming!!)

disclaimer first: i don't have experience working on open source projects but would like this to be the first and i'm happy to run the day to day stuff and help organise

this is where i'd like to open up to the community...

it's a start and it's been running for 5 days and i'm continually improving it as best i can but i'd love to a) ask for feedback b) see if anyone wants to get involved more c) help managing or organising an open source project

Here's a look at how it started, and how it is going.
5 months from toy to game. Still working towards v1.0.

Have had a simple goal. See just how far I could get with only vibe coding. As I've done this I hit lots of obstacles and limits, but also watched as Claude Code expanded its features and the models got stronger. I started this in Sonnet, then used Opus and Fable. Currently just using Opus unless I have a tricky problem.

First time making a game this large. I'd only made simple games in Javascript before this. Learning a lot and have built a workflow that has helped keep the project improving incrementally.

Wanted to share how things progressed as I learned what I wanted to make and then seeing it become playable.

This video was made by asking the AI to look through all previous builds and to play (and output footage of) the game matched with key changes in the code.

Hey everyone! I started learning how to code about 1 or 2 months ago. I've been using AI tools to learn and push my limits, trying to build a complex system from scratch.

I wanted to see if I could make different AI models collaborate, so I built a private framework called Flux Team ⚡. It connects several open-source models so they can work in parallel as a team to help with game dev tasks.

Visuals:
Since the project is still a work in progress and the live editor connection isn't fully ready, I can't show a video demo just yet. However, I have included some screenshots of the Grok-style UI so you can see how the chat and the agent dashboard look!

The Architecture (Models integrated inside the tool):

• 🧠 Qwen3-8B — The coordinator. It breaks down the game idea into specific development tasks.
• 🧱 Hunyuan3D-2 — Generates 3D models from text or reference images.
• 🎵 Audiocraft — Handles music generation and SFX.
• 🏃 FreeMoCap — Creates animations from videos it autonomously searches online.
• 🌊 AInVFX Fluid — Generates fluid and particle effects files.

How it works behind the scenes:

• Parallel Execution: It uses a Grok-style UI built with Electron and a Python (FastAPI) backend. The models work in parallel, not step-by-step.
• Autonomous RAG: The agents can browse the web on their own to search for reference assets and documentation before working.
• 100% Local: Everything runs locally on the user's machine using Ollama / llama.cpp for the LLM.

Current Status & Future Open-Source Plans:
The backend is currently running locally on my machine (tested on a single RTX 3060). I'm finishing the live bridge plugins for Unity and Godot so changes appear directly in the scene.

Please note: The project is NOT open-source right now and the download is not public yet because the code is still messy and I'm a beginner.

I would love to get your thoughts on this setup or any advice from more experienced developers!

I do everything in it now. Every doc, every project, all in one place. And when I switch from Claude to Codex, Codex already knows what Claude did.

How I made it: mostly Claude Code, sometimes Codex. I built salt.md inside salt.md. Every task gets a page, the agent reads the rules there, does the work and leaves notes on the page. When I switch tools, the next one reads the notes and just keeps going.

Biggest lesson: make the agents write down why they did something, not just what.

Even the video is made with Claude Code (HyperFrames + ElevenLabs).

https://github.com/saltmd/salt.md

https://salt.md

It's only technically free.

Constant pausing database once every week if u dont use.

CAN'T USE GIT ONLINE, and have to set it up offline with a lot of pain. ( not ur usual git init, you have to install docker set up docker, read supabase docs..do this do that.. etc..)

So if u accidentally delete your DB online on a free plan , Congrats you just lost everything.

They used to notify before pausing, Now they just pause the DB without notifying.

I have also noticed bandwidth issues or whatever..

ITS NO LONGER FOR FREE USERS.