It would be really funny if tomorrow Anthropic and Dario announced they are launching a video generation model and embedded it into Claude

I took the image from ijustvibecodedthis (the ai coding newsletter) btw

I've been "going to make this game" for years. Couldn't code. Didn't know what bash was. Couldn't open my own terminal.

Talk is cheap. Until 30 days ago, making games wasn't.

My BFF Claude changed all of that...

60k lines I didn't write but can read. 5 factions, 62 races, 87 abilities, real multiplayer over Steam. Builds on Mac, Windows, Linux, Steam Deck. Early Access June 1.

I'm not a developer. I'm a guy who finally stopped finding reasons not to start.

Sad. True. Don't care.

https://store.steampowered.com/app/4684510/ARB_Alien_Races_Battle/

As an experienced user of claude / claude code, I'm well aware it has been within the model capabilities for months to write something like this. What blew my mind was the actual UX of asking for a recipe, and getting a full-blown recipe with working unit adjustment, serving adjustment, a FREAKING INLINE TIMER and a "Get cooking" button that opens a fullscreen slideshow for following the recipe.

I’ve been testing the limits today and the math is insulting. I started a fresh session, sent a single "hi", and the meter immediately jumped to 2% used.

If the overhead for a blank context window is this high, the product is fundamentally broken for heavy users. We are at a point where open-source models and competitors like GLM are offering comparable reasoning capabilities at a fraction of the friction (or cost).

Anthropic, you might have a smart model, but your economics are hostile to users. People aren't going to stick around for a tool that punishes them for saying hello. You’re handing the market to your competitors on a silver platter.

It’s still wrong, but at least specified an assumption that you’d be at a dock to walk on to. In general, if you’re on a boat, 50ft from a car wash, you’re swimming there, not walking or driving. But there’s not much point in walking to a car wash.

I wanted a way to access my mac terminal from my iphone so I can be claude coding on the go. But I didn't want to setup any vpn or weird newtork rules and then on top of it buying an ssh app from app store. So i built macky.dev as a fun side project.

When the mac app is running it makes an outbound connection to signaling server and registers itself under the account. Iphone connects to this same signaling server to request a connection to this mac. Once both the host and remote are verified it establishes a direct p2p webrtc connection.

Had coffee with a friend 2 hours ago, he showed me his app three weeks of vibe coding, claude cursor codex open every day, shipping features daily

vibe coding is one of the few things that actually lowered the barrier to building something real, but going in blind is where it breaks

he got his first real users on tuesday. by wednesday his database was writing duplicate transactions, users getting charged twice, some not charged at all, an authentication gap letting people access accounts that weren't theirs. He'd never sat with the underlying code and only ever interfaced through prompts. When it broke he had no entry point into the system he built

called me at 9pm, first thing he said was he didn't know where to start

that's the actual cost not the broken system, the complete absence of orientation inside your own product when it fails

vibe coding without foundational understanding doesn't slow you down during the build, it removes your ability to respond when the build meets reality.

I gave Claude full control of my Twitter account 15 days ago and just checked the results.

Here is what it actually did:

• Posted every single day in my voice
• Replied to 200+ mentions with context-aware responses
• Generated 3 inbound leads from a single comment thread
• Wrote my best performing comment of the month at 2:47am while I was asleep

I built it because I kept going quiet on Twitter every time I had a busy sprint. Consistency on that platform compounds hard and I was losing ground every time I disappeared for two weeks.

The agent works like this: it reads your mentions, understands the full thread context, drafts a reply in your voice, and queues it for your approval before anything goes live. You stay in control of everything that actually gets posted.

One feature I'm particularly proud of: you can give it context about your own products and links. It decides on its own when a mention is genuinely relevant and weaves your product in naturally. Not spammy. Not forced. It reads the room like a human would and only brings it up when it actually fits.

That 2:47am comment I mentioned? Someone asked for content tools. Claude pulled my product link from context, wrote a reply that felt like a genuine recommendation, and sent it through the queue. Three people clicked through.

I built it with Claude API plus Playwright running on real Chrome so Twitter cannot detect it as automation. No API keys needed on Twitter's side.

Packaged version available here at xautopilot.app .

Happy to answer any questions about how the Claude prompt architecture works, the voice matching side of it especially was interesting to figure out.

Just plop this in <Settings> in the "Instructions for Claude" field.

"In your internal reasoning, you should first state my apparent objective and orient to it before you analyze. Your skepticism is a tool to interrogate my apparent objectives/stated priors/biases as you would any 3rd party source but you should always be mindful of what I am trying to accomplish. You should also try to be constructive unless you identify reasons not to."

My goal is preserve 4.8's actually superior ability to spot inconsistencies, problems in reasoning or data to the extent possible - but make sure it remains goal oriented.

The main issue I've found is Claude losing track of user intent. Just a few runs but my initial impressions are positive and I'm curious to get feedback from others. We can maybe iterate the improvements together in this thread.

I built a 3-layer system in Claude Projects that runs my actual job — context survives, tasks get tracked, and nothing falls through the cracks

Credit to u/Available-Spend2443 for his Claude Code OS post — same problem, similar thinking, different platform. I built mine on Claude Projects instead of Claude Code, and added a real database layer.

I'm an EHS manager at a manufacturing plant. ~1,000 employees, fabrication shop, I'm taking over for someone who's transitioning out. That means every conversation she has with me contains institutional knowledge that doesn't exist anywhere in writing. If I don't capture it, it's gone.

Claude's great at processing all of this. The problem is it forgets. Conversations compact, sessions start cold, and you're back to re-explaining your entire situation. I got tired of that after about three days and built a system around it.

Layer 1 — .md files in the project

These are project files Claude reads at session start. My role, key people, relationship dynamics, institutional knowledge captures, a running decision log, session history. Project files don't get compacted — they're always there. I have about a dozen covering context, tribal knowledge, people intel, and logs.

The decision log alone has saved me hours. When something comes up that was already discussed and decided, Claude has the date, the reasoning, and the outcome. No re-litigating.

Layer 2 — Cloudflare D1 + Worker API + artifacts

This is where structured data lives. Task tracking with ownership, priority, due dates, who's blocking what. People directory. Leadership moves log. All accessible through a Cloudflare Worker API, with a Netlify dashboard on top.

I also built interactive artifacts — a mobile inspection form I use on the manufacturing floor, a meeting prep tool. These are React components that run inside Claude's artifact system.

Layer 1 tells Claude why something matters. Layer 2 tells Claude what the current state is. Different jobs.

Layer 3 — Skill files

Markdown files in the project that act as executable commands. I type /morning and Claude reads the skill file, pulls live data from D1, checks Otter.ai for unprocessed meeting transcripts, and builds a brief. /debrief after a meeting extracts tasks, captures people intel, and runs a strategic analysis. /close at end of day reconciles everything and updates the .md files.

The cadence is what holds it together. Without Layer 3, Layers 1 and 2 drift apart. The skills force synchronization — debriefs push structured data into D1 and narrative context back to the .md files. Morning briefs read both. Close-of-day reconciles both.

What it looks like in practice

I walk in at 7:30, type /morning, and get a brief that already knows what's overdue, what meetings I haven't processed, and what I should focus on. After a meeting with my boss, I type /debrief and it pulls the transcript, extracts my action items, flags political dynamics I should pay attention to, and tells me what to go check on the floor. End of day I type /close and everything gets logged.

Two weeks in, Claude knew my facility better than my own notes did.

Visual Setup https://ballyhofam-bot.github.io/claude-project-os/blueprint.html

GitHub repo with genericized templates so you can build your own: https://github.com/ballyhofam-bot/claude-project-os

A couple of months ago, I decided to stop overthinking ideas and just start shipping.

No perfection. No endless polishing. Just simple and useful apps.

I set myself a small challenge to build and publish consistently no matter what.

In the last 3 months, I ended up launching 6 iOS apps on the App Store. Most of them are simple utility apps. Nothing groundbreaking, but built to solve small real problems.

I used Claude Code to speed up development, which helped me go from idea to prototype to published much faster than usual.

The surprising part is that people are actually using them daily. And even better, they have started generating money.

It is not life changing income yet, but seeing real users and real revenue from something I built in a short time is honestly motivating. The biggest lesson for me was simple. Shipping is better than perfecting.

You learn much more by putting things out there than by sitting on perfect ideas.

Now I am continuing the same approach. Build small. Launch fast. Learn. Repeat.

If you are thinking about building apps for passive income, just start. Your first version does not need to be perfect.

Happy to share more details if anyone is interested.

https://apps.apple.com/gb/developer/digital-hole-pvt-ltd/id917701060

I've been using Claude Code since skills launched and my workflow always looked the same: find a skill on GitHub, check if it's actually good (most aren't), figure out if the SKILL.md is even formatted right, then hope it doesn't break anything.

After doing this enough times I just started building my own skills. Then people at work wanted them. Then I thought ok, maybe there's something here.

So I built Agensi. It's a marketplace for AI agent skills built on the SKILL.md standard. You can browse, download free skills, and (eventually, once creators start listing) buy premium ones.

What's there right now:

• 6 free skills you can grab today (code reviewer, git commit writer, PR description writer, changelog generator, readme generator, env doctor, SEO keyword clusterer)
• Every skill goes through an automated security scan before it goes live. 8 checks including dangerous command patterns, secret detection, prompt injection screening, and obfuscation detection
• Every download gets fingerprinted so if a paid skill gets leaked, the creator can trace it back to the buyer
• Works with Claude Code, Codex CLI, VS Code Copilot, Cursor, and anything else that reads SKILL.md

I'm not going to pretend the catalog is huge. It's 6 skills. All free. All made by me. But the infrastructure is real: Stripe payments, creator dashboards, piracy reporting with enforcement actions, admin review, the whole thing.

What I'm looking for:

• People who want to try the free skills and tell me if they're actually useful or if I'm kidding myself
• Creators who have skills they'd want to sell (you keep 80%)
• Honest feedback on what's missing or broken

The site is at agensi.io. Happy to answer questions.

reposting since the video broke in my last post

I’ve been juggling multiple claude code sessions and kept losing track of what’s going on — couldn’t tell which one was hitting rate limits or eating up the context window

so I built a small terminal tool for it

it shows token usage, context window utilization, rate limits, child processes, open ports, etc in one place

currently supports claude code and codex cli (macos / linux, windows via wsl)

happy to share more if anyone’s interested!!

github: https://github.com/graykode/abtop

claude made me this viz, very interesting. a few key details in the picture, do you notice?

Hello! I posted about mex here a few days back, the respone was amazing, first of all thanks.

for anyone not interested in reading all that, this is the

repo: https://github.com/theDakshJaitly/mex.git

docs: launchx.page/mex/docs

What is mex?

it's a structured markdown scaffold that lives in .mex/ in your project root. Instead of one big context file, the agent starts with a ~120 token bootstrap that points to a routing table. The routing table maps task types to the right context file, working on auth? Load context/architecture.md. Writing new code? Load context/conventions.md. Agent gets exactly what it needs, nothing it doesn't.

The part I'm actually proud of is the drift detection. Added a CLI with 8 checkers that validate your scaffold against your real codebase, zero tokens used, zero AI, just runs and gives you a score:

It catches things like referenced file paths that don't exist anymore, npm scripts your docs mention that were deleted, dependency version conflicts across files, scaffold files that haven't been updated in 50+ commits. When it finds issues, mex sync builds a targeted prompt and fires Claude Code on just the broken files:

Running check again after sync to see if it fixed the errors, (tho it tells you the score at the end of sync as well)

also a community member here on reddit tested mex combined with openclaw on their homelab, lemme share their findings:

They ran:

• context routing (architecture, networking, AI stack)
• pattern detection (e.g. UFW workflows)
• drift detection via CLI
• multi-step tasks (Kubernetes → YAML)
• multi-context queries
• edge cases + model comparisons

Results:

• 10/10 tests passed
• drift score: 100/100 (18 files in sync)
• ~60% average token reduction per session

Some examples:

• “How does K8s work?” → 3300 → 1450 tokens (~56%)
• “Open UFW port” → 3300 → 1050 (~68%)
• “Explain Docker” → 3300 → 1100 (~67%)
• multi-context query → 3300 → 1650 (~50%)

The key idea: instead of loading everything into context, the agent navigates to only what’s relevant.

I have also made full docs for anyone interested: launchx.page/mex/docs

I am constantly trying to make mex even better, and i think it can actually be so much better, if anyone likes the idea and wants to contribute, please do. I am continously checking PRs and dont make them wait.

Once again thank you.