jcutrell

If all I needed was common memory space I'd just use symlinks and cloud sync, Obsidian or whatever.

But the context shaping is what makes memory useful in the first place, so just doing one stop shop memory is IMO about as useful as plain old markdown...

How is this better than Claude Code's built in agent orchestrator? Do I need 100 agent types? How do I know the trained agents here are somehow better? Specialization doesn't equate to "better" in every case.

I want to see the light but at this point it feels like these kinds of projects need a better way to benchmark how they are improving on the available state of the art.

It feels like in 2018, a new browser state management tool emerging. Why does this exist?

I am working on building profiles for people I work with, and really my goal is to end at something like this for them.

People like to say no. (I'm not sure what this cognitive bias is, but anecdotally I agree.)

So, if you can frame your requests in a way that "no is permission", it will often get a red light a bit easier.

Example: replace "Is this a good idea?" with "is this a bad idea?"

Now, of course "not a bad idea" is not the same thing as "good idea", but it's a lot more likely. Even reading that, I imagine most people would respond more intuitively, because it helps us avoid a commitment we don't necessarily want to adopt.

Eventually they will capitalize more on the mesh density, rather than crushing the adoption now.