42 points lizziepika 1 hour ago 24 comments
rkarthik1993 1 hour ago | parent
Rather than write an essay about why we built this, I’d rather just answer whatever you’re skeptical about. Happy to get into the actual mechanics: how sessions get attached to commits (it’s git refs, not a side db), what the 89x push number does and doesn’t mean, where the context/token savings fall apart, who can read whose session transcripts, how you’d migrate off if you hated it, whatever.
The one thing I’ll say up front: The bet is that once agents write most of the code, the PR stops being the right unit of review, because the diff is cheap and the “why” vanishes when the session ends. Everything else follows from that.
Ask away, I’ll be in the thread for a while.
argee 1 hour ago | parent
Also, if your business has agents writing most of the code, why would your business care about human reviews at all? In for a penny, in for a pound, after all. Wouldn't you be better off looping your agents into your support tickets and autofixing bugs? In that scenario, isn't it more confusing for an agent to deal with sessions + code rather than start fresh with the code?
solyin 1 hour ago | parent
argee 16 minutes ago | parent
If you are arguing effort versus value, let me escalate: I don't think even the call leader of an Amazon sev one would be interested in seeing such screen recordings, when all of Amazon.com is down, and when workable solutions would be worth putting Herculean effort behind.
I want to know where the value comes from, then, just because it got easier to query such data doesn't in itself make it valuable. You would be better served by having Opus look over your code after Sonnet made mistakes, rather than having Opus first digest whatever (potentially poisonous slop) Sonnet cooked up before looking at the code.
0gs 1 hour ago | parent
is the carrot JUST the time savings for large dev orgs?
Haimantika 54 minutes ago | parent
You can read more about session storage on our docs here: https://docs.entire.com/guides/checkpoints/checkpoint-storag...
conartist6 1 hour ago | parent
This isn't a belief. What do you actually believe about the future of software?
Let me put it this way. The premise of agents is that some combination of programming languages and programming tools suck so incredibly much that humans don't want to use them.
You're effectively betting that this problem can never be fixed. AI is a layer of kludges on top of the problem of bad programming tools. Haven't you ultimately made a rather cynical bet?
lizziepika 47 minutes ago | parent
salt-licker 1 hour ago | parent
This feels insincere coming from a venture-backed software startup. Do you have a unique ownership structure, or a particular emphasis on open-source or self-hosting?
abhisinghs 46 minutes ago | parent
Haimantika 1 hour ago | parent
stryan 1 hour ago | parent
philipwhiuk 1 hour ago | parent
hedgehog 1 hour ago | parent
Haimantika 1 hour ago | parent
Haimantika 1 hour ago | parent
For Trails: There’s agent sessions, gates, agents(evals basically) and checks - so it gives you all the information you need to review better (compared to the diffs for example).
Here’s our docs link too: https://docs.entire.com/guides/trails/overview
Here if you have additional questions!
stryan 2 minutes ago | parent
1. The "What are trails" section does not actually tell me what trails are; it tells me it brings agents and devs together, and that branches are involved somehow through "changes", but it doesn't actually tell me what they are
2. I am never going to willingly watch a Youtube video embeded in docs. I'm barely going to watch a video in a docs page at all. I'm here to learn how to use something, not see a sponsored ad for NordVPN.
3. The marketing blurb, the top half of the docs, and the bottom half ("Enable Trails" onwards) all feel like their describing different things. The marketing blurb describes a total reinvention/view of the PR layout where instead of seeing diffs you see different bars that you can balance by telling the bots to keep reviewing/changing. The top half of the docs sounds like some sort of spec description system and absolutely reeks of LLM speak.
4. The rest of the docs make more sense: Under the web UI tab for "Create a Trail" I finally see what a Trail looks like (a simplified Jira ticket or GH issue) and I start actually understanding that this is an elaborate "built for AI" version of stacked PRs, CI checks, and project management.
5. The Agents and Gates subdocs are where content starts getting interesting and the documentation quality is a lot better. I am actually getting interested in this product.
I still don't fully understand what and why I would want Trails, but I suspect I'm not the target audience. There's bits of it that certainly look interesting but having to swap all my infra over to Entire is a hard sell.
shepherdjerred 1 hour ago | parent
I would happily try this out if it were going to be free for the next 1-2 years, or if I knew that the upcoming bill would be reasonable
Haimantika 1 hour ago | parent
TLDR: You only get charged for Agents. We also give you a $100 signup credit.
bestcodes 26 minutes ago | parent