@trq212 Yikes, how does this work on enterprise? We prohibit users filing bug reports due to the special data retention terms it uses. When this was manual with /feedback easy to stop people from doing, but if it’s a tool a user can just click through now that’s a huge issue for us.
@davep@FriesIlover49 Interesting that you factored it in to savings can you share any details on what’s included. For example if current context window is full 1 mil used; does that add weight to keeping model next turn vs. if a cache miss would only be 50k tokens?
@711_Joseph@optic0n@Audrey_Sage_@OpenRouter That’s not how it works with enterprise compliance and regulatory, especially with something as broad as an LLM gateway where literally all of your corporate data is going to end up in; it’s not just one sector of the data for a specific SaaS
@btsouth@brian_armstrong @conduitmcp Uh no, that has not been the case for over six months. That was how it worked in cursors v1 of their mcp client.
https://t.co/jM1URmf1gQ
Please stop sharing falsehoods and look at what the product landscape looks like today, not at the end of 2025.
@btsouth@brian_armstrong Claude desktop uses the same baseline harness as Claude code with the Claude agent sdk which just runs the Claude code binary. All of these known name harnesses have tool search built in now, it’s table stakes to even be a functional product after last several quarters.
@AmanAlam@raveeshbhalla@JPoehnelt@addyosmani The average person and developer also does not understand what a single sentence like not a funded project means and just assumes way too optimistically that has gone through legal and sec diligence just because a public repo is in a company’s org
@AmanAlam@raveeshbhalla@JPoehnelt@addyosmani I certainly agree and for me led to many questions on why don’t we allow using it referencing the tweets, but my point is if you are actually using this in any meaningful way for something as risky as this as a developer the bare minimum is to read the top level readme
@robwormald@raveeshbhalla@JPoehnelt@addyosmani So you better be sure what you’re putting out there without buy-in and sign offs does not have high security and legal risk, which this project pretty obviously did if you work on agents and enterprise mcp
@robwormald@raveeshbhalla@JPoehnelt@addyosmani Same with my career experience. The processes are not well defined, and you assume a bunch of risk as the employee that what you’re putting up isn’t going to be a problem internally if it gains traction because you aren’t going to get x-func resources to review your pet project
@robwormald@raveeshbhalla@JPoehnelt@addyosmani Maybe that’s the problem? Often employees in public GitHub orgs have access to put up whatever, even though expected to go through approvals channels. Did they go through security and legal approvals before putting it in the GitHub org and broadcasting it all over social media?
@raveeshbhalla@JPoehnelt@addyosmani You could have just looked at the top of the the readme and it said in big bold letters this is not a Google funded product and had no lisensing or liability terms
@JakeKAllDay@MetacriticCap Yes bedrock will get you desktop. They released desktop 3P through bedrock last week for highly regulated enterprises. Im evaluating moving mine to it right now, check the docs
@PatrickMoorhead Still missing docs, sheets, slides mcp’s on gcp for workspace. Drive today is a start but need those to really have great workspace coverage to get a lot of benefit
@tmfpretty @BoringBiz_ You think the federal government isn’t going to introduce payroll tax on agents based on % of consumption likely with a premium over the regular payroll tax once they start to see payroll tax revenues plummet if labor is displaced? Same thing happened with EV to cover road taxes