Every couple of weeks, someone reaches out to tell me how much they love Dotenvx, followed by: “How have I never heard of this? Is it new?” Meanwhile, tens of thousands (maybe hundreds of thousands) of developers are quietly using it every week. Dotenvx has never been the hot thing on tech Twitter. It's grown the old-fashioned way: developers (and now agents) discovering it, using it, and sharing it with other developers. There's something pretty special about that.

It is tough these days to build secure software - especially if you are under a major attack like OpenCode. So I feel for them and they build great product. But this is another example of why you should use a model like Dotenvx or SOPS. Split your secrets cryptographically so that an attacker has to attack both the providers secret store (in this case that is what was attacked) AND the encrypted secret in your code (which was not attacked or even reachable here). This is why we wrote our whitepaper. Meanwhile, every other provider retweeting OpenCode and saying 'use our secrets store' is repeating the same systematic problem - centralizing your secrets to their secrets store yet again. Dotenvx or solutions like SOPS are the only way to solve this for your organization. xitter.cf/opencode/status/211151…

Making french fries

Quality of life improvement for Dotenvx.

very lucky to get to wake up each day and work on dotenv.

so bad to be in the middle in these kind of times. either log off or never log out. either embrace agentic or build human only. either raise massive or don't raise at all. these are not the middling times.

The @anomalyco emerging exhibit A on this. It was never about the software.

Insane. Thanks everyone. New tooling on the way expressly for your agents.

good music you find meaning in maybe in the near future, good software, you'll find meaning in. maybe i'm being too sentimental. but maybe that will be the future. i mean music has been basically free to make since the 50s now and software is just getting started.

When radio was born and classic music was broken, music changed - it became songs about love and lost love. Sometimes I wonder these days if software will follow the same path. Less about technical feat, more about emotional reach.

Enjoy what you create. Make some people happy. Let the rest take care of itself.

These are the times you look back and say... wow, those were the good times. Most of us are working harder than ever. Days feel like weeks. Ups and downs. More productive than ever yet somehow still feels like not enough. The whole market changing, the whole engineering discipline changing, new winners, new losers. It's a historical time right now, and we're lucky to be riding it. Grab the bar, white knuckle it, and see you all at the end!

Well needed break, from competing with all my secrets-solutions frenemies, to competing against my oldest frenemy. The wall.

Dotenvx, over 1,000 PRs.

We all have our fates. Dotenv is mine. Will never stop.

I'm still surprised none of the harnesses have attempted top tabs like chrome. I'd prefer it. opt + cmd + left/right so fast for switching. and shift + cmd + left/right for terminal. it is so ingrained in how i work and then i'm slowed down in the codex and others. someone tell a friend at openai, xai, or anthropic.

It's the fastest change to dotenv in a decade. require('dotenv').config({ fast: true })

Faster than Node's native parseEnv? No, way. Yes. Yes, way. Dotenv's fast mode now beats Node's native parser on Node 22 and 24 across Linux and Windows in our benchmarks. Five months ago, the wildest PR ever landed in dotenv. Most contributions are small parser changes, type fixes, or feature proposals. This was a new parser, claiming 2x speedup. Some guy from Sweden, @pelaseyed. A character scanning approach. Pretty sick, tbh. So what did I do? What any maintainer does for a package depended on by tens of millions. I sat on it. lol. But we also got in touch. He and his cofounder run @superagent_ai, securing PRs. They generously offered to secure Dotenvx's, and today they do that for all kinds of open source projects—even Firecrawl. Back to Dotenv. The parser was contributed as a full replacement. That's too risky, so we put it behind a fast flag. On September 17th, five months after that initial PR, we released it. It's fast. With dotenv 18 or later: require('dotenv').config({ fast: true }) Or from the CLI: npx dotenv run --fast -- node index.js The community has already found edge cases, and we've patched them. That's exactly why we made it opt-in. Node's native parser still wins in some configurations. Full benchmark breakdown in the post below. Maintaining dotenv means maintaining the past while still moving .env forward. This parser is a small piece of that. Huge thank you to @pelaseyed and @superagent_ai for bringing it to the dotenv community. dotenvx.com/blog/2026/09/28/…

Been 6 days since my last video demo of a new dotenvx feature. Some cool stuff in the pipeline for our users. Will reveal soon.