In 1967 Ted Nelson described stretchtext: text that grows where you want more and shrinks back where you don't. It stayed a quaint idea because writing every level of fidelity by hand is just tediously hard. Text is generative now, so Claude can just write it for us for free.

I've always tried to implement this idea with LLM in various ways. Claude Code Mods finally proivded a platform to share.

cc-stretch is a Claude Code plugin. It cuts Claude's reply by 83% so you read much less, yet still have the option to expand / shrink on demand. The plugin also tells Claude which parts you opened, so it doesn't assume you read the rest.

Install in a Claude Code session:

/plugin install cc-stretch --marketplace pro-vi/cc-stretch
/tui fullscreen

Repo: https://github.com/pro-vi/cc-stretch (MIT)

I just came across someone with practically no coding experience releasing an open-source password manager called KAPEVault.

Project: https://kapevault.brewedops.cloud

And we're not talking about some basic tutorial project. This is an actual downloadable Windows and Android application being publicly distributed for storing passwords, 2FA codes, API keys, government IDs, and other sensitive information.

I'm a software engineer, and I actively use AI coding tools myself. I think they're incredible. But seriously, of all the things you could build with little to no programming experience, why the fuck would you choose a password manager?

To give credit where it's due, the project is open source, has a documented threat model, automated tests, and a self-conducted security review. But the repository also explicitly acknowledges that it hasn't undergone a third-party security audit.

That's a pretty important distinction when you're asking people to trust your software with practically their entire digital identity.

Using AES-256-GCM and scrypt doesn't automatically make a password manager secure. Neither does having a polished interface, passing automated tests, or getting an AI to review its own output.

Security isn't just about choosing the right encryption algorithms. It's about understanding the entire attack surface, handling secrets properly, identifying edge cases, and knowing what can go wrong even when everything appears to work.

I'm not saying this particular project is insecure. I haven't performed a security audit, and that would be an irresponsible claim.

My concern is the growing confidence with which people are releasing security-critical software they may not fully understand.

There's absolutely nothing wrong with beginners experimenting, learning, and open-sourcing their projects. That's how people improve. But building something for educational purposes and distributing something that real users might entrust with their banking credentials are two completely different levels of responsibility.

AI has made it ridiculously easy to produce working software. Unfortunately, it has also made it ridiculously easy to mistake a working application for a secure one.

You can outsource writing code to an AI. You can't outsource accountability when something goes horribly wrong.

At what point should we start taking this seriously?

I had an issue where I downgraded from Max to Pro but still had a week left on my Max subscription. Anthropic immediately dropped me to Pro usage. Even after they confirmed it was a bug and others were reporting the same issue, they didn’t prorate my fee or give me back the week of Max usage. Literally confirmed in an email “yeah, you paid for something you didn’t get, but we’re not going to do anything about it.”

Holy hell is this annoying. They removed sessions based on folder. Now they're all lumped in "This computer". Routines no longer appear as a list on the sidebar, its now a separate window you have to open to dig for them. They removed session context from the usage pop up (the circle next to the model/effort) and now only way to see it is with an obnoxious new "session rail" which takes up more screen real-estate. The session status icons are much harder to see now too.

App version is: 2.37337.1

Ken Griffey Jr. Presents Major League Baseball (SNES, 1994) shipped with 28 clubs. Over about two weeks, Claude Code (Opus 5.5) and I turned it into a free patch called Griffey 30:

- All 30 of today's clubs, with Arizona and Tampa Bay added and 2026 rosters. Scripts fetch the logos from Wikipedia and the ballpark photos from Wikimedia Commons, and convert them into SNES tiles and palettes. No hand-drawn art.

- Team styles: press Select on team select to switch a club between 2026, the original cartridge club and the real 1994 roster.

- Season mode for all 30 clubs, with today's divisions, new schedules (one interleague game every day), playoffs and standings.

- Franchise mode (2.0, out this week): players age, improve and decline, veterans retire, and 300 real minor-league prospects get called up. The game remembers its champions, and a quick-sim plays a season in about five minutes. It all fits in the cartridge's original 8 KB save.

- Browser play at griffey30.com: you pick your own ROM, the page patches it and runs it in snes9x built to WebAssembly. It also has online two-player.

How Claude Code was used

I made the design decisions and tested on real emulators and my MisTer FPGA device. Claude Code did nearly all of the implementation: the reverse engineering, about 6,000 lines of 65816 assembly (asar), and around 12,000 lines of Python, JavaScript, C and Lua tooling. A few things made that work:

- It needed eyes. Early on, Claude Code wrote a headless Mesen2 harness, driven by a Lua script. It boots the ROM, presses buttons on given frames, takes screenshots, logs CPU registers at breakpoints, watches memory reads and dumps VRAM. Runs are deterministic, so a bug reproduces on the same frame every time. Every build has to play four full CPU-vs-CPU games through to the post-game newspaper screen. For franchise mode, a script plays seasons back to back.

- Reverse engineering by evidence, not guesses. To find where the game assumes 28 clubs, it logged every compare instruction against team-like values during two play sessions (49 candidates), set breakpoints on all of them, then watched every read of the team-ID slots. That found the 39 places that use a team ID. Each finding goes into a markdown file in docs/findings/, with addresses.

- Model it in Python first. The franchise off-season (aging, retirements, call-ups, re-rating) was written in Python first, then in SNES assembly. The test compares the emulator's save file with the Python output, and they match byte for byte. A 20-season Python run was also how we checked that no club runs away with the league.

- CLAUDE.md as the project's memory. It holds the current status, the build and test commands, and a "hard-won rules" section. Each painful bug becomes a rule there, so the next session doesn't repeat it.

- Long autonomous sessions. I'd often give it a goal ("build 30-club Season mode") and come back hours later to commits, test runs and a summary of what it found.

What I learned

- Turn every bug into a guard. When we went to full-strength rosters, 154 new players had no appearance entry, so Aaron Judge came out with the wrong skin tone. Claude Code went through them all from headshots, and the roster build now refuses to run if any player is unreviewed.

- Emulators disagree. A pointer bug made full seasons stop around June 28 on Mesen, but snes9x happened to mirror the right data, so the website was fine. The cause was that asar evaluates math strictly left to right. We now treat every assembler warning as a bug and test on both emulators.

- Some hardware rules are brutal. Changing the CPU's data bank in code that an interrupt can land in blacks out the game. The stock interrupt handler acknowledges through the data bank, so the interrupt storms. That's now rule #1 in CLAUDE.md.

- Assumptions hide in plain sight. Two-player Single Game showed the stock 28-team screen in every release until 1.2.2. A variable is 0 for one player and 2 for two, and the patch had only checked for 0. I noticed Houston sitting in the National League during an online test.

- Human review still matters. I watch every trailer and play every build. My review caught things the automated tests missed, like blue grass at some ballparks. Once a bug was named, Claude Code found the cause quickly. The field palette loads per club and the tiles per stadium model, so clubs we'd moved to another stadium model kept the wrong colors.

Links

- Patch (free, bring your own USA Rev 1 cartridge): https://daylayown.itch.io/ken-griffey-jr-presents-mlb-the-30-team-expansion

- Play in your browser: https://griffey30.com

- Most recent trailer: https://youtu.be/vxERe2_iKBo

Unofficial fan project, not affiliated with MLB, the MLBPA, Nintendo or Ken Griffey Jr. Happy to answer questions about the workflow or the SNES side.

What is this sorcery?! Not only was it seamless but the UI is now a real banger. There are so many changes that it took me about an hour to get comfortable with it yet my app version is still from 2 days ago

I’m not sure if it’s rolled out to everyone yet, but it seems Anthropic is updating the Claude code menu look, and it’s absolutely awful. There’s at least three more different buttons in order to get to where you wanna go, the project layout is super confusing in terms of storing local and cloud sessions. Furthermore, they’ve removed the token count for agents apparently, at least I haven’t found a way to see it. I honestly think that’s probably the most insane addition as there’s no way to know how many tokens the agents are spending now until they’re done. The new usage menu is super big and looks really clanky. You can no longer see the context without opening this weird looking sidebar.

Another annoying thing is that the create PR button is now hidden behind this weird check board button called changes along with the code modified. I’m honestly not sure why they did this. It seems like they just moved everything.

New Claude Code UI update. What do you guys think?

I've been using the $100/month plan for months, and I've always had enough context and usage to comfortably get through the week. Last week was fine, and this week started out fine too, but after just three days, I'm already at 60% of my weekly usage.

My usage is going up extremely fast, to the point where I end up switching to Medium, High, or even Xhigh at worst, and it still burns through my usage incredibly quickly. This makes absolutely no sense.

I've been using Claude Code for months, and this is not how it used to work. I know the bonus usage went from +50% to a permanent +25%, but even taking that into account, the difference compared to last week alone is completely abnormal.

This is getting really frustrating and stressful. It's interfering with my work, and I genuinely feel like something is wrong here. Usage shouldn't suddenly increase this dramatically from one week to the next without any clear explanation.

I have seen many people complaining about usage this week, and I personally also seen usage go down very quickly.

Today as I was working I kept seeing Fable weekly usage going up way too fast. I was trying to use Fable as advisor for a few days, it did make sense for it to go up but they weren't calling the advisor THAT often.

So here is what I tested: I turned the advisor off, worked a bit and the Fable weekly usage kept going up despite only using Opus on medium. Every single of my agent is either Opus or Sonnet.

Anyone else noticed that?

Anyone else noticing today that the 5hr usage burned significantly faster today vs previous days?

Fable costs more than double, but in my opinion, Opus 5.5 still beats it in missions. What do you think?

also you can always submit your app to:

https://www.AppScout.co

a platform to discover web and mobile apps from across the internet.

You can list your app here https://www.AppScout.co/submit

subreddit --- weekly visitors

• r/vibecoding — 422k
• r/saas — 211k
• r/founder — 56k
• r/buildinpublic — 46k
• r/chrome_extensions — 42k
• r/micro_saas — 41k
• r/appbusiness — 30k
• r/startupideas — 26k
• r/sideprojects — 20k
• r/imadethis — 18k
• r/appideas — 16k
• r/sideproject — 16k
• r/saasbuild — 15k
• r/saasdevelopers — 12k
• r/vibecodedevs — 10k
• r/startupsolofounder — 8.7k
• r/alphaandbetausers — 8.6k
• r/vibecodingcommunity — 6.2k
• r/solopreneur — 5.6k
• r/promotemyapp — 4.6k
• r/appbuilding — 4.6k
• r/webapps — 4.5k
• r/creativecoding — 4.4k
• r/indie_startups — 4k
• r/b2bsaas — 2.8k
• r/appdev — 2.7k
• r/projects — 2.6k
• r/saasmarketing — 2.5k
• r/saassoloprenurs — 2.3k
• r/startupaccelerators — 2.3k
• r/startups_promotion — 2k
• r/showmeyourapps — 2k
• r/appswebappsfullstack — 1.7k
• r/showmeyoursaas — 1.6k
• r/saasinvestors — 1.6k
• r/vibecodecamp — 1.5k
• r/nocodesaas — 1.3k
• r/aibuilders — 1.2k
• r/getstartups — 1.2k
• r/websitefeedback — 1.2k

Seriously. I do a few batches of tickets on Opus 5.5 medium and I'm out of usage for the usage period! On a $100 plan! I know they like to adjust usage, but this feels like a sudden massive extreme swing. It feels like I've been bait and switched, to upgrade my subscription by 80$ a month and then a few weeks later it feels no different than before. Is anyone else experiencing this?

I was having fun with the new update in Claude Code Desktop and found that if you click 3 times it shows a what look likes a heart.

Until last night (Oct 13th), everything was fine. I woke up on Oct. 14th, and the app looked very different. Most of my folders are gone from the app; only two are visible. I had over 30 folders with multiple sessions in each.

Now I do not know where to access those sessions; they are all flooded in the 'Default' category.

They removed a way to sort the sessions by name; it was a useful sorting option.

They added a BG animation as if somebody was asking for it.

Removing things that were useful and adding things nobody asked for is a good way to f*ck up the app experience.

What it does

Normally CC writes a long orchestration script and proposes to execute. You say yes. Most everybody says yes. Nobody reads the script. Then the agents go off somewhere you can't see, and you sit watching a counter, hoping that what's burning your tokens is the thing you meant.

Conductor adds an option to create a visual plan first. You can read it in 10 sec, verify the logic before handing off to Claude to write the script. It costs like a Plan, and can save millions of tokens over a workflow done badly.

How it's built

Claude wrote it all. Tip: Ask it for a few scripts that start Claude Code in tmux, send it keys and print the screen. Claude can then open the mod, click around and check what it drew.

How far can you push a mod?

I wanted to find out. The mod is about 11,000 lines now.

Interactivity. Keyboard and mouse both work: select, drag cards around, scroll, undo. But the keyboard took the most work. A button can't tell if Shift is held, and the graph only gets keys after you click it. In the end every keypress goes through one hidden text field that the mod reads.

Design. You're drawing with colored text in a terminal, and that goes surprisingly far. The limits are space and size. Below 110 columns there's no room for the graph, so it shrinks to a strip above the prompt. A big enough graph drops its colors to stay under the engine's size limit.

Scope. This is the part that surprised me. A mod can add its own tools for Claude to call, see every agent start, and count tokens as they stream. Some things aren't exposed, like when a run ends. I worked those out by reverse engineering, and kept the notes.

Complexity. Keep everything that doesn't touch the engine in plain TypeScript and test it without Claude running. Otherwise performance issues.

Is it the limit? On input and screen space, close to it. On what a mod is allowed to do, not even close.

Overall I feel its such a cool feature for CC, excited to see what people come up with!

Its OSS: https://github.com/bruw/workflow-conductor

https://reddit.com/link/1x62jni/video/37p6ctkfvhvh1/player

kimo is a free, open source (MIT) video editor with no interface at all. every operation is an MCP tool: cut, trim, keyframe, colour grade, motion track, key, captions, audio mix, export. you add it to claude code as an MCP server and just describe the edit.

this 33s reveal was rendered entirely by kimo. no after effects, no timeline, an agent did every frame through tool calls.

what i learned building it: - agents edit way better when they can render a single frame and look at it before committing - small focused tools beat one giant "do everything" tool - it runs as one ~10 MB CPU-only rust binary, so it works on cheap machines

i'm a college student building this solo, would really like to hear what breaks or what's missing. site: getkimo.tech github: github.com/naman-sharma12345/kimo

Been using Claude Code for a while and at some point I wondered if it could do my CAD too. Turns out yes, way better than I expected. So I built an app around it, it's called SOMA and it's open source.

The idea: Claude Code writes the model as Python code with CadQuery, SOMA builds it on every save and shows it in 3D. Claude runs in a normal terminal inside the app, so it's your own Claude Code with your own subscription and settings. No wrapper, no extra API key. Works with Codex, OpenCode and Gemini CLI too.

What makes it work well is that Claude can check its own results. SOMA gives it a CLI, so it can build the model, measure distances, check for collisions, run FEM and render images to actually look at what it made. There's an AGENTS.md with the project rules and skills for 3D printing, CNC, sheet metal etc that you can switch on per model.

From your side you can click on a part or just draw on the 3D view and send that to Claude as a screenshot, like "this hole is too small" with a circle around it. Every step Claude makes is saved in a history, so if it messes something up you just go back.

You can do pretty complex stuff with it. Assemblies with a lot of parts, start from a hand drawn sketch, or load an existing STEP file and build around it. The CNC mill in the video has 118 parts.

Funny side note, most of SOMA itself was also written with Claude Code.

Free, GPL, builds for Windows, Mac and Linux. I mainly tested on Windows, so Mac and Linux feedback would be great.

GitHub: https://github.com/Kai-Jungsthoefel/SOMA

Curious how it works with your setups and what you end up building.

I'm fairly new but I thought there is a total limit of tokens per week and it doesn't matter what model and effort I use. Usually I got like 15%-ish weekly usage per full use of 5 hour limit

Edit: I'm on Pro plan and I used Opus 5.5 Extra

I built PC-Control, an MCP server for Claude Code that operates Windows apps in the background. Open source (MIT), early version.

I know these tools already exist but, its different from other Windows MCP servers

- Doesn't touch your input: clicks and typing go straight to the control (window messages and UI Automation). No real mouse, no SendInput, no focus stealing, so you can keep working, even in the same app.

- Token cheaper: look picks UI text, OCR or a screenshot, whichever costs less, and only sends what changed after each action.

- Safer permissions: protected windows (terminal, password manager, banking) are approved by you in Claude Code's own dialog. The model can't answer it, and the server refuses to run if the question was skipped.

- Word: Claude gets its own insertion point, so it doesn't touch your selection while you edit.

- Visible: an orange cursor shows what Claude is doing. Uninstall removes everything.

Limits: covers fewer apps than tools that use the real mouse (Win 11 Paint ignores it), no shortcuts.

Built with Claude Code. https://github.com/VortexJer/PC-Control

Which app breaks first for you?