Mathieu

hey @conductor_build, would it be possible to detect the state of agents using big terminal mode? i'd love to see in the sidebar if claude cli is still working

@grok @IroncladDev @grok seems like v4 is not always random enough. when would one use v6?

It depends on your use case. For most new projects (esp. DB primary keys), **UUIDv7** is the best in 2026: time-sortable + solid randomness, great perf, no fragmentation. **v4** is still fine for pure random needs like tokens or APIs where order/privacy matters most. v6 is decent but v7 is preferred over it. What's the context?

that's why there's UUIDv6

Imagine the amount of unnecessary panic because of todays Tanstack hack. npm decided to set all versions matching '>= 0' as hacked leading everyone everywhere to get a positive on running npm audit. I spent hours rotating production secrets and notifying customers on a secondary secure laptop while it turns out I wasn't impacted at all.

you need to be delusionally optimistic negative thinking poisons your brain and leads to congitive decline whereas positive thinking, and gaslighting yourself into thinking everything is amazing, ACTUALLY makes your life amazing too. you must be a silly goose

@MarcJBrooker i guess v7 makes it way less likely?

This is such a great example of theory vs practice. In theory, UUIDv4 collisions don't happen (generating one million per second, probability of seeing one collision in a year is ~10^-8). But they have been observed to happen in practice, especially in distributed systems. Why?

@buildwithparas @rawkode npm = github

@rawkode npm could just check the sha actually belongs to that repo before pulling, this isnt only github's problem

For fuck sake. When are GitHub going to stop linking fork commits to the upstream repository? dependencies: { "@tanstack/setup": "github:tanstack/router#79ac49ee” } Commit 79ac doesn't exist in the repo and npm pulls it in as if it does. This has been abused for over a decade

AI slop is good, actually. Slop is what enables fast parallel experimentation. The etiquette and skill is understanding the boundaries of where slop exists and the extent to which it should be cleaned up and how. A few examples: I’m working on the internals of some system right now. The API and GUI of this thing is fully zero shame slop. It’s horrible. But it lets me focus on the core quality while shipping a usable piece of alpha quality software to testers (transparent about the slop frontend). Similarly, this system has plugins. We sent agents in Ralph loops overnight to generate dozens of plugins. The plugins are slop. The quality is bad. The plugin API/SDK is absolutely not done. But we can test a full GUI with a full plugin ecosystem. When we change the API, we can regenerate them all. The cost of change is just tokens, the velocity is incomparable to before. I built Terraform. We tested and shipped TF 0.1 with about 3 very weak providers. Because we ran out of time. Building was slow. And when we changed our SDK the cost was immense. Totally different today, 10 years later. Today, I would’ve slop generated 100 providers (again, with transparency and cleanup later, but just to prove it out). As an anti example, I would not PR this (without prior warning) to another project. I would not throw this onto customers without full review or transparency (as I’m already doing). I would not accept first pass slop. It’s almost never right. Slop is a tool. And like anything else it’s not blanket bad or good. The context is everything.

trying @t3dotcodes after using @conductor_build for a long time (in ai terms). i like it a lot. being able to run it on my homelab, connect from laptop or mobile and just letting it run regardless of disconnecting. no more "shit, i have to leave, but my agent is still running"

i'd actually may use claude code in the @ClaudeDevs desktop app if i could just use --dangerously-skip-permissions there as well. now it's just annoying to use.

we need @better_auth, but for @EffectTS_. passing a session down the request handler as service which you can yield* where needed would be so nice. immediately visible which endpoints need auth

@mattyp btw, any chance you guys are taking on testers for conductor mobile/remote? 👀

@m9tdev it does

caffeinate -i

@mattyp til! awesome to have it in conductor now as well then

can’t wait for mobile remote @conductor_build

@levelsio i had hvac in my previous rental in rotterdam. it’s really an awesome system. also means less dust in your whole house because a lot is filtered out!

So a few things: only until recently European homes didn't have AC installed, not just no HVAC, barely any AC at all Even now it's very low, about 20% of European homes have AC Our house has AC in every room though, but just to cool, they do nothing for air treatment like removing CO2, setting humidity right, getting in fresh air, etc But no HVAC, no air tubes, no central air, etc, I haven't see any European house that has that, best we have is an air vent in bathrooms that goes to the roof to get humidity out a bit Of course Europeans just open the window, which is great, I live near the ocean, but at night there's noise sadly, barking dogs, garbage trucks at 6am, it goes through ear plugs, I'm not complaining but an HVAC system would fix the CO2 and get fresh air in without the noise And sure in office buildings in Europe but not homes, we don't have air treatment like HVAC, no ducts, nothing!

@garybernhardt i can see it work if you put a lot of effort into setting it up, but this process is going to cost you a lot of tokens because of the mistakes you will make before getting it right

i’ve tried paperclip, which worked pretty well. i was through my claude code max 20x subscription usage very quickly tho (before they nerfed usage). still needed quite some steering and created a lot of stuff i didn’t actually want. in the end i continued the project with just claude code in conductor for more control, lower costs and higher quality

Are there any actual success stories for "software factories" like gastown? Anything I can see running, and preferably see code?

why is it a requirement to have @Cloudflare manage my domain/dns for using the email service? i have a domain that i can't transfer, but would really like to build something with cloudflare workers, durable objects and email. will this be supported in the future?

@thdxr you can have all my code as long as i can opt out for my hermes/openclaw instance

opencode go is currently zero data retention however we can increase limits and make it all more sustainable if we collect data to train future open source models you can opt out of this - is that something you'd be ok with?