nibab
Joined 10 years ago
Joined 10 years ago
at the same time, context poisoning is a real cognitive problem for humans too and I can't tell you the number of times I've seen irrelevant details become a drag on execution. my fear is that having too much context will only cause bikeshedding and a revisiting of prior decisions.
frankly, our organizational structures were already pretty good at creating mechanisms for eliciting the right implicit context at large scales. it is possible that we're just going to come up with the same mechanisms from first principles...
its interesting to see how "lock-in" is the main pitch here. all things considered, i don't think "lock-in" is relevant at all unless the activity performed with the tool is highly strategic to the company.
you could argue that some orgs may not want openai/anthropic to have their sensitive data leave the parameter, but im also here to tell you that even the most privacy sensitive companies in the world probably resolve this by having a proxy in between the users and the LLM APIs from the labs.
so where does this leave you ? cost savings from OSS? maybe, but its hard to imagine that we are in the phase of the adoption cycle where companies have become as acutely aware of costs as you think they are.
my 2c - focus on the integrations and see which one gets most traction. that will be your value capture mechanism long-term.
looks great btw. congrats