The first 626 Labs Day
Today is 6/26/26, the first 626 Day since 626 Labs existed. The whole surface is shipped and live in one window: 14 Claude Code plugins and 6 Microsoft Store apps, one new and two with major updates this week.
This is it.
Today is 6/26/26. The first 26th day of June since 626 Labs has had a name to put on it. 626 Labs is named for the home frequency, so 6/26 was always going to be the day. The Lab just needed to actually exist. The whole surface is shipped and live, all of it, in one window: 14 Claude Code plugins and 6 Microsoft Store apps, one new and two with major updates this week.
So I'm planting the flag. 6/26 is 626 Day, starting now.
The state of the surface
The plugins are the spine of the studio. Fourteen of them, the Vibe family, all built on the same idea: an agent that reads the code before it touches it. Cartographer plots an idea into a shipped app. Iterate ships the next feature off real signal. Keystone bootstraps a repo's ground rules. Doc, Test, and Sec guard documentation, coverage, and the security posture. Taker, Walk, and Wrap handle capture, discovery, and the clean handoff at the end of a session. Insights pulls cross-machine recall out of the session logs. Thesis Engine and Thesis scaffold long-form research with rendered output. Prompt audits the LLM prompt sites in an app. And Lingual, the 14th, shipped today: internationalization retrofits that are codemod-safe, validated by localizing most of Celestia3 before I'd call it done.
The native apps are the other half. Six on the Microsoft Store now: Sanduhr für Claude, RBX15 Shirt & Pants Maker, Right Click PNG, SnapSnip, RORORO, and the sixth, 626 Mod Launcher, just live. Different audiences, different stacks, one studio behind all of them.
Three I want to put in front of you
Not a list. Three releases this week that earned the headline.
626 Mod Launcher is the sixth Store app, out this week. It's a mod toggler for PC games, Bethesda, Unreal, FromSoft, BepInEx, Stardew, built on one rule I refuse to break: disabling a mod never deletes anything. It moves the files instead, so every toggle is reversible and every change is atomic. Either it happened or it didn't; there's no half-applied state to recover from. The Store build ships with a sealed core, so the safety guarantee isn't a setting you can talk yourself out of.
RORORO v1.7.1 is the Roblox multi-launcher, and v1.7 is where it grew up from v1.4. Multi-instance recovery now means it can stop every instance at once and reload on error instead of leaving you to clean up a wedged fleet by hand. The plugin host got hardened: installs are https-only, and every capability a plugin wants is a consent prompt, not a default-yes. And every release auto-publishes a signed roblox-compat feed, so the compatibility data is something you can verify, not something you have to trust.
Sanduhr v3.1 is the Claude-usage widget, and v3.1 is an honest rebuild of the widget itself, not a feature-invention pass. Compact mode collapses the readout to whatever tier is burning hardest right now. The bottom icon strip got consolidated into a single hover-lift row with a theme flyout instead of a scatter of controls. The taskbar button tracks pin state, the close button is a native rounded control, and the sparkline is range-normalized so the shape actually means something across different load levels. Nothing here is invented. It's the same widget, rebuilt to feel like one.
Why mark it
Six native apps and a fourteen-plugin family is a lot of surface for one person. I'm not saying that to flex, I'm saying it because the work tends to disappear the moment it ships. You close the PR, the next thing is already open, and the thing you just finished becomes invisible by Tuesday. A studio that never stops to count loses the plot of its own scale. If I was trying to flex I would say before last July, I hadn't looked at code seriously since the late 80s and the Microsoft Store apps were half single-day build-to-store stories.
626 Day is the stop. It is close enough to the anniversary of me dabbling in building that it can mark a reminder of why 626 Labs exists. Not a roadmap, not a pitch. A checkpoint. Are we still building something different, are we still doing it with our style and are we proud of what we have made? The surface is shipped, it's live, and on 6/26 that's allowed to be the whole point.
Next year there'll be more, but 6/26 was never about the count. It's the day to ask whether the work is still different, still ours, still worth being proud of. That's the tradition: every June 26th, answer that honestly and mark the day it's named for. This is the first one. It won't be the last.
Imagine Something Else.
— Este