TL;DR Install Entire right now.
"Drift"
You want to launch a product. You go to your favorite agentic coding harness. You tell it, "Build me a $100m MRR. Make no mistakes".
You watch words scroll past. Salivating at the idea of the wealth that's coming your way.
"Shimmying..."
"Whirring..."
"Cranking..."
"Getting sturdy..." (this doesn't exist but it should).
It's done! Finally, you're set up for a successful business.
You open the app, you create an account to test. You start clicking through. Things don't look that great, but you figured at least the product works, right? You click through the core features. You realize it's actually not working at all. It just LOOKS like it works. You were vibe coding, but your LLM was happy path coding. Does this sound familiar? This is what I like to think of as Prompt Drift.
Maybe not exactly like this. But some version of it, every single day.
Exploring Backwards
How do you measure your prompt engineering? Most people are making changes as they go, hoping things will get better. But how would you even know if they did? When things aren't going your way, you're left to wonder:
- What was my intention? Did I properly convey that to the LLM? How did the LLM interpret what I wanted?
- Did the LLM properly reflect what I was trying to do?
- If you came back to this codebase 3 months later, would you be able to explain why it was built this way?
These questions would straight up go unanswered. At best, you probably documented things somewhere, built your own system to track your history. But for the most part, when you look at that code, none of that context exists. Or rather, it does exist — it just didn't have a place to live.
Entire Solves This
Entire is a CLI tool that captures your entire agent session and associates it with the code that was written. Every time you commit, it quietly attaches the full conversation that produced that code to the commit itself. Not only would you have git history, you'd have prompt history too. Entire calls these snapshots Checkpoints.
Setup is easy — run their install steps, enable it with the CLI, and it attaches to your IDE's hooks. After that you never have to think about it again. Because of this smooth onboarding, and the fact that it's free, I genuinely believe you should have Entire set up on all your projects. This is one of those things you're gonna wish you had months down the line when you're putting out LLM-generated fires.
I've been using Entire extensively for the past two weeks and I realized there's a new lane for developer tooling. There is so much tooling that reads code — linters, review tools, docs generation. All of it depends on some kind of output. Entire brings a whole new layer to the picture that hasn't been this thoroughly captured before. We can now build developer tools that read intent as the resource. That context that once felt ephemeral is going to exist within your .entire folder.
Intent as a Resource
Every code review tool today (BugBot, CodeRabbit, Greptile etc) can only make a guess at intent. They read your diffs, your commits, your code structure, and they infer what you were trying to do. That's the best they can do, because the actual intent was never captured anywhere.
With Entire, that changes. The prompt history is right there. So I built a code review tool that reads it. I'm naming it Nimbus.
Nimbus pulls your Entire session context — what you asked for, what constraints you gave, what decisions were made — and uses it alongside the diff. The result is a review that can answer a question no other tool can: does this code actually reflect what you were trying to build?
It's early and there's a lot more to explore here. I'll write a full post about it soon. In the meantime it's open source: github.com/dayhaysoos/nimbus
If you want to try it on your own repo, reach out — I can set you up with an API token while I iterate on it.
The Ecosystem Is Just Getting Started
I highly recommend checking out Entire. It takes no time to install, it's free, and you're gonna appreciate yourself later for doing it. Join the Entire Discord — the community is just starting to form and it's worth being early.
Think about the bottlenecks you've been facing in this agentic coding era. I'm willing to bet some of them could have been resolved if you'd had a way to go back to the intent.
Entire introduces a shift. We've been building tools that read machine-made artifacts as the resource. Imagine what we could do now that we can capture human intent. We can solve for the drift that happens between what you meant and what you got.
Top comments (0)