lizziepika

thank you, Alex!

Karthik's comments have been getting blocked. I don't agree with the screen recording because an agent session isn't just a reply of keystrokes. A session contains not just what happened, but why: the intent and reasoning from the prompts, the dead-ends, what was attempted but not shipped, and "why did we do it this way." That shouldn't disappear when a session ends.

Similarly, human review doesn't matter because humans type the code, it matters because someone still ahs to decide if something is right and if not, own the consequences.

And starting fresh with agents is pricey. Continuous memory is helpful so you can see why the last change was made, burning fewer tokens and not repeating mistakes so you don't need to relearn the codebase from scratch each time

Concretely, our CLI is OS (MIT), and we're working toward open-sourcing the storage backend EntireDB so you can self-host it on your own infra or run a variant of it. That your sessions, prompts, and review history live in your repo, not locked in our platform, means you can always walk.

Agents are such an amazing building tool, similar to how compilers and high-level languages were. It superchargers builders and that's why so much code is now being written (not always by humans.) The bottleneck was never typing, but to me, it's deciding what to build, verifying it's right, and keeping it all coherent, which is what we're rebuilding the forge around.

Agree on creating channels where people share innovation and news and what they’re building! Others will share it more people share

What do you think of the women in tech movement, and other diversity initiatives?