evansjp

Nothing prunes it, atm. Currently I'm not sure if it's valuable that it does? 97KB is ~25k tokens. `grepathy context <file>` filters by the decision's Touches: list - a typical file pulls 3KB, not 97. But, I'm open to hearing a case on pruning!

For comparison the whole git log body on that branch is 3KB; the pack holds 33x the reasoning.

these are great suggestions! terrific recs - thanks. I think you're right to lean into OC and Hermes

whatever your CLI currently uses. so if you use subscription, it'll use that. vice-versa for API.

hey that's awesome! yeah the eval showed first pass was only ~65% real decisions. The fix that stuck was an entry has to name a real file it touches or it gets dropped. A code decision names code.

I agree agents don't always self-talk decisions, that's why we distill the whole transcript after the fact instead of asking them to log anything. Your baselining idea is good!

lol yes, agents ran the mechanics. I set the bars before any run and audited the keys. And the "why" behind the project is literally in the repo's .ai/why/ where you grep it if you would like.

thank you so much! started with a Claude Code adapter, but you think Codex would be a good next one?

CTO responded well to it - frankly because we're all using some coding agent and it's just the natural process of code review for them to sniff things out. No mention of it in any PR summary - CTO found it in the migration that would mutate the User record to accept `null` email.

Some of you are wayy too bored at work - some of these are too realistic

You're absolutely right, I'll get an update out here to lift the country restriction.

Very cool, but shouldn't be on Show HN yet until people can actually use it.

That's actually a super good idea for a metric I didn't think about tracking and I love that you commented that.

What was the time for the event that didn't show up in the calendar? Was it something till midnight?