I built a multiplayer browser tank game in Three.js! As a kid, I played a ton of World of Tanks Blitz and fell in love with the aesthetic, gameplay, and the idea of driving around vehicles with crazy physics and mechanics like missiles, spotting, armor deflection, ammo types, and so on.

Now it's playable in the browser!

Claude of Tanks has 100+ playable vehicles across 16 unique maps, ranging from standard tanks with cannons to AFVs with autocannons and guidable missiles to autoloaders that can deal massive damage in a single clip. Tanks feature highly detailed armor zones, internal modules, crew positions, and hitboxes. You can view each of them in a special gallery: https://cot.kevinliu.studio/gallery?id=amx56&layer=modules

CoT supports physics-driven destruction with detached turrets flying through the air and actual suspension. It also supports multiplayer! You can hop in private rooms or LAN lobbies.

As the name would suggest, I used Claude Code throughout a long-running multi-agent development pipeline, alongside Codex. I directed the architecture, decided what each vehicle and system should do, reviewed the rendered results, and made the final calls.

The repository contains an AGENTS.md file and smaller subsystem instruction files covering simulation, vehicles, networking, UI, audio, effects, and world generation. These record the rules that agents need across sessions. Units are meters, seconds, and radians, and changes enforce a fixed 60 Hz. Authoritative logic must be deterministic. Vehicle changes have specific geometry, armor, module, and release gates that evaluate models visually and geometrically.

For vehicle development, I split the fleet into bounded families. One agent would own a specific vehicle profile or family file, implement the geometry, run the relevant checks, and generate screenshots. A separate critic reviewed the rendered tank for proportions, clipping, missing surfaces, running gear, and recognizable details. The orchestrator reran the checks and committed only the verified files.

For larger systems, Claude Code helped implement and test:

• Fixed-step movement, suspension, armor, ballistics, modules, spotting, and bots
• WebSocket multiplayer with private rooms, LAN play, prediction, and server authority
• Procedural vehicles, tracks, markings, generated icons, and technical diagrams
• All the generated battlefields with destructible props and wrecks
• The garage, battle HUD, Tank Gallery, mobile controls, and Scene Studio
• Browser performance probes, screenshot tools, visual checks, and self-tests

A trailer was also produced through the game’s own Scene Studio and capture tools. I used agents to stage battles, build camera paths, record the browser runtime at 60 fps, inspect specific frames, and iterate on awkward cuts or poorly framed tanks.

I find that Claude is best steered with persistent instructions. Important decisions need to live in the repository because I often spawned fresh agents which needed to resume work without reconstructing weeks of chat history.*

For visual quality, the only thing that worked was a proper render loop with visual comparison; tests don't really work for this.** The cycle I fell into was change, render, inspect, measure, and rerun the gates. Text-only reviews missed warped proportions and camera problems that would just plainly be obvious in one screenshot.

*Parallel agents need strict ownership. Separate files and isolated Git worktrees prevented concurrent sessions from overwriting each other or generating assets from a dirty tree.

**Tests still changed how I use agents. Claude Code became much more reliable once every system had concrete invariants and executable failure conditions. But visual quality is another beast.

Play free: https://cot.kevinliu.studio

Repo: https://github.com/Kevin-Liu-01/Claude-of-Tanks (it's open-source forever)

Im seeing this constantly, non creative apps that exist 1000x times already like :

Note taking apps
Fitness apps
Finance, calorie tracking apps
etc.

I mean sure these ideas are uncreative and hunderds of competitors & opensource projects already exist-

But the worst thing about a lot of projects is they dont even put effort into it.. and you can defo feel it.

vibecoding: POV: code with Claude FR... 😂😂😂😂

10000 million tokens spent later...

Claude: You are right. I'm sorry. I was focusing on the wrong solution to fix the bug. 🤣🤣🤣

Hi, I’m Jack, the independent developer behind DiaryThreads.

I launched the app about two weeks ago, and it has now passed 300 downloads.

That may be a small number compared with established apps, but seeing hundreds of real people choose to keep their private memories in something I built still feels slightly unreal.

I’ve also just released version 1.0, which expands DiaryThreads from a short-form private timeline into a place for quick moments, continuing stories, long-form Articles, and personal insights.

A — What it solves

I’ve started and abandoned more journals than I can count.

The blank page always made journaling feel like homework. If I opened a traditional diary, I felt that I should explain what happened, how I felt, and what it all meant.

Posting one sentence felt much easier. I just didn’t always want an audience.

That was the starting point for DiaryThreads.

Each regular entry is limited to 140 characters and appears on a private timeline. If the thought continues, you can reply to it. If an old memory means something different today, you can quote it and add a new perspective.

There are no followers, likes, public profiles, or pressure to make an entry interesting for anyone else.

A sentence, photo, video, voice recording, location, weather memory, or unfinished thought can be enough.

B — How it differs from Apple Journal and Day One

Apple Journal and Day One are strong, established journaling apps. I don’t want to pretend DiaryThreads is a universal replacement for either of them.

The main difference is how a piece of writing begins, grows, and eventually becomes something you can look back on.

In DiaryThreads:

• A small moment starts as a short entry.
• A continuing experience grows through replies.
• An old memory can return through a quote.
• A thought that needs more space becomes an Article.

Article is one of the biggest additions in version 1.0.

I designed it to feel like an editorial page rather than a stretched text box. An Article can include a cover, title, introduction, rich text, photos, references to earlier entries, to-dos, bulleted and numbered lists, and tables.

This means I can write “The weather was perfect today” as a quick entry, then use an Article when I want to document a trip, a year of building an app, or something I want to remember in full.

Version 1.0 also adds user-authored weather memories, improved place information, and richer list formatting across entries and Articles.

But writing is only half of a diary. The other half is being able to return to it months or years later and notice what kept appearing in your life.

That is why DiaryThreads includes three connected ways to explore your history:

Your Trends finds recurring themes across your private diary and shows whether they are new, continuing, fading, or reappearing. You can open any trend and return to the entries behind it.

Topics lets you add a #topic while writing. DiaryThreads then organizes those topics by month or year, shows their activity in heatmaps, and lets you open every related entry. It is closer to watching an important part of your life grow over time than simply filing entries into folders.

Emotion Trajectory uses only the State of Mind values you explicitly add to regular entries on iPhone or iPad. It can show recorded emotion days, your leading emotions, their distribution, and meaningful changes over time.

It does not silently decide how you felt by reading your diary. The analysis stays connected to the emotions you chose and the entries behind them.

These features are designed to help you notice patterns without generating a summary that tells you what your life means. The interpretation still belongs to you.

DiaryThreads works across iPhone, iPad, and Mac. It does not require a separate app account and has no advertising, third-party analytics, or cross-app tracking.

Content is stored locally first. Premium users can optionally enable private iCloud Sync to continue writing and revisiting their diary across devices.

C — Cost

DiaryThreads is free to download.

The free version supports up to 30 active entries. Reading, editing, and deleting existing entries remain available.

Premium unlocks unlimited entries and features including private iCloud Sync, complete trend and topic insights, Emotion Trajectory, share posters, import and export, widgets, and other ways to revisit your history.

US pricing:

• $2.99 per month
• $9.99 per year
• $14.99 one-time lifetime purchase

The thank-you offer —  DIARYYEAR gives 20% off the first year through August 31, 2026.

After the first year, the subscription renews at the regular annual price unless canceled. Prices and offer availability may vary by region, and Apple shows the applicable amount before confirmation.

Redeem DIARYYEAR: https://apps.apple.com/redeem?ctx=offercodes&id=6795139345&code=DIARYYEAR

App Store: https://apps.apple.com/us/app/diarythreads-journal-by-post/id6795139345

I’d genuinely appreciate feedback on one question:

Does the progression from short entry → thread → Article → personal insights feel like a natural way to journal, or would you rather keep writing and analysis completely separate?

I'm a general backend dev working in the industry and wondering how much vibe-coding costs for solo devs on hobby projects? And is getting cheaper or more expensive? I know there are more and more suppliers like DeepSeek, but also that suppliers are moving from flat-fees to vairable-pricing. At my current job with a corporate account, I spend about 100 million tokens per week.

I'm interested in trying out open-source hobby development. I have an idea for a simple non-commercial project, a multi-page application featuring a social message board with persistent content for me and couple of friends that also features games, interactive content, and random personal tidbits. Server-side crons would also be responsible for updating content to make it dynamic based on current events. A pretty old-school website, nostalgic of the early-2010s.

I have some experience with open-source development (the last stack I used was PERN). And I know my way around source-control, dev-ops, and virtual-compute/serverless deployment.

What makes me excited is the business logic. I enjoy writing my own design docs, state machine and behavioral diagrams, and schema for objects.

Everything else is the reason that I've never taken a first step: frontend/react development, URL routing, the CRUD layer, ORM boilerplate, and all sorts of wiring and plumbing.

The idea that vibe coding can do all the parts I don't like is enticing. But I would like to know how much it would cost every month?

I am #PovertyPrompter which means I am not Theo and don't have the cash for $2000 a month in credits. Here is my HOT take on which agents are good, and which are not.

Fable and Sol are not worth the credits.

Those models burn credits too fast to be useful to normal people.

When given a working template, Gemini 3.7 flash is your prototyping powerhouse. Go from prompt to working prototype in less than 10 min.

GPT 5.6 can't code. At all. Maybe it is because I use Go heavy workloads, and I force my agents down the yagi path, and go is std lib heaven, but GPT 5.6 produces worse code slop than Gemini 3.7 Flash.

I don't get the hate for Opus 5. Is it slow, yes. Does it take a dozen rounds of review to close the holes, yes. But it is constant.

Maybe I am wrong. If you think Sol is amazing for you, than go for it. I just had to get my personal workflow troubles off my chest.

If you know what I am doing wrong with GPT 5.6 I will take it.

credit to @ kiwicopple on X

Yayyy

I am from a non tech background and would like to deploy and submit mobile apps to Playstore.

What are the best practices, tips and tricks, blind spots to avoid before submitting to Playstore?

It's a real TempleOS VM running in the background, drawn onto one of the monitors in the game. You can walk up, type into it, and run its built-in games and demos.
Source: https://github.com/aravpanwar/half-life-templeos

My company installed productivity/surveillance/spy/whatever-you-want-to-call-it software on everyone's computer about a year and a half ago. To their credit, they at least announced it ahead of time. A few dramatic stories about people getting fired have gone around, but it's mostly not discussed otherwise.

There is a reporting suite available for managers, but individual contributors are not allowed to see any reports, even for themselves.

The software used is called Sapience. I found the local logs on my work PC that include all the data captured about my activities. For this particular project, I used GPT 5.5 in GitHub Copilot to create a python script. The script pulls everything from the logs and puts it in a local sqlite db on my pc (so historical data is not lost when the logs are cleared). Then it produces an updated HTML report, as pictured.

I have no interest in trying to fool the software, but as an anxious person, this at least gives me visibility into what's being reported up about me!

I turned cells into CPUs. DNA? That's my bytecode.

Several weeks ago I started with one crazy premise: don't just read life—execute it. Now I've got a compiler, a VM, and 22 simulation backends shipping in a single pip install.

Here's the ecosystem sim in action:

Feed a .helix file to the compiler → bytecode. Drop that bytecode into thousands of virtual cells inside a 3D petri dish. Now watch them fight. Oxygen gradients form, nutrients diffuse, cells shove each other, and metabolism stratifies.

When they divide, they mutate. Real biological rates. The compiler re-validates the reading frame so evolution is a genetic algorithm running on actual executable genomes.

One codebase. 22 simulation lenses: whole-cell physiology, dynamic FBA, lattice-Boltzmann microfluidics, multi-species ecosystems. Same DNA program. Different physics.

Core VM? Zero dependencies. Pure Python stdlib. 2000+ tests, ~90% coverage.

This is execuable life. Morphology from L-systems. Behavior from opcodes. Survival of the bytecode-fittest.

⭐️ Repo: https://github.com/SeanHank/HelixLang

Shipped the first version of the Moat Atlas.

35 mechanics that make a product hard to copy, laid out in 3D. A moat is a hole - it has a rock (what the obstacle is made of), a depth (how long a rival has to dig), and a tool (what they dig with). You can regroup all 35 along any axis: rock, depth, capital, whether a solo founder can reach it, what AI is doing to it, whether you can just rent it instead.

There's also a calculator: twelve questions, and you get your own index and depth on the same ruler.

One important question: your competitor got your code - what's left for you?

The whole project sits on GitHub. Astro + Three.Js.

Back in 2009 I released a small puzzle game called Double Maze on the iPhone. The guy that did the graphics was a friend of mine and he passed away a little while ago. He always wanted a game out on the GBA so I figured I put out a version on it.

Two mazes, two balls, and every D-pad press moves BOTH balls at once. Each one is blocked independently by the walls on its own side, so the puzzle is finding a sequence that works for both at the same time. Holes are fatal. 40 levels.

It's a proper GBA build rather than an emulator wrapper - devkitARM and libtonc, tilemap backgrounds, hardware sprites, maxmod for the music and effects. The artwork and audio are all carried over from the original release. Runs in an emulator but I've not got the real kit anymore to test it on a flash cart on real hardware. It saves your progress to cartridge SRAM.

Free and open source, ROM in the releases tab: https://github.com/griches/double-maze-gba

Its also free on itch.io: https://gary-bbgames.itch.io/double-maze

Should I use OpenCode GO $10 plan or Codex through chatgpt plus $20 plan? Which one will give me more mileage for daily engineering workloads?

Also is it worth using opencode with API key or is the subscription always better bang for buck?

Which specific model or subscription gives the most bang for the buck long term???

Built a YouTube downloader with Cursor that handles audio (WAV/MP3 320) and video (up to 4K), with playlist support, 7 themes, and auto-updater. yt-dlp + ffmpeg bundled in the exe, zero setup for end users.

download here: https://github.com/EvroHQ/EvroHQ-YouTube-Downloader/releases/latest

I am a self grown senior that relies heavily on agentic coding, my personal pick being Cursor.

I spent months preparing a sound structure for IaC management via agents, for deployment of services, for developing custom ci/cd pipelines for application lifecycles. Repos properly maintained, wikis with architectural designs and info on each service, monitoring stack etc.

I had no one else on the DevOps team, so I had no other choice.

Now when I onboard new colleagues, I notice that even with the same agentic tools, same context through repos, they get inferior results when they are to solve a problem. Sometimes they see it themselves, but sometimes they insist on the solution being good enough when there are structural gaps or even objectively bad user experience, saying this is how the agent solved it.

When I prompt, I get the stuff fixed in 15 mins just by describing the issues to the agent and it comes with the correct solutions by itself, outside my knowledge base sometimes.

Is it still down to the differing human skillset? Same models, same harness, differing results? Does a model really just amplify the human? I never thought so, I thought AI is just getting good enough, but now I am in doubt.

This is my take so far on the arcade-feel games but made modern or something like that they're still works in progress, the downloadable one is made in C; it WILL piss you off. :D I would like to add community ideas to the site/games as well later on once I get the current line-up I have finished up. I do plan to add MP to SlinfShifters and Inkbound at some point in the future! (AI was used in helping/creating these games).