Does this primiarly work with Claude for now given MCP?

Good question -- the MCP naming is a little misleading... while Anthropic designed MCP to work in Claude, it's actually an open standard and also is implemented in Sourcegraph Cody, Cursor, Cline, Goose by Blocks, and many other client contexts.

mcp.run Tasks are an MCP client as well, in that they can call tools just like Claude would if provided MCP servers.

I’ve seen so many deals get hung up on the smallest legal issues. One time a company spent 6 months just negotiating the NDA before could even get to a POC that the champion kept pushing and wanting to do!

I think what’s cool about CommonPaper is not just having the negotiations scoped to smaller areas but also the affect on the sales cycle. If can trim months off a deal process, that can help save a startup in terms of resources spent and dollars coming in earlier.

That's a good point, and the magnitude of the impact of speeding up sales cycles can be really surprising if you haven't done the math. We wrote a blog post about this last year with a model in Google Sheets that you can customize for your business, but the TLDR was that while holding everything else constant, moving the sales cycle from 4 month to 3 increases ARR by 46%. That's with the same starting capital.

Full blog post and math here: https://commonpaper.com/blog/impact-of-accelerating-sales-cy...

I think what’s interesting is while UDF has existed for some time. It anecdotally has seemed to be increasing in pace in announcements recently driven by wasm. For all the benefits explained in the post leading to a great end user experience, I would expect it’s something all the database providers to roll out as tablestakes in the future.

There's a company that does this already! The visualization of code and diagrams helps different times of learners I think. Which also is beneficial for knowledge transfer since everyone learns different, some better from pictures vs some better from drilling down deeper. I also think you systems thinkers having a good architecture diagrams that can be visualized in different ways can lead to insights that otherwise are hidden. https://www.codesee.io/

I was going to mention that code visualization is increasingly becoming an important topic to new and expert engineers and coders. And I did come across CodeSee.io that looks to be leading the charge for that. Excited to see the developments in code visualization and the visuals themselves.

The automated checks on authentication and keys is a very nice feature! Bringing security into the gateway directly rather than an add-on feature

Yes, it is refreshing to see security as a first-class citizen, instead of an afterthought or add-on like it is on so many other products these days. Do other gateways do this too?

Very cool use case for CRDTs! I've seen a bunch of different use cases from other products like https://liveblocks.io/ and https://electric-sql.com/. It's interesting how CRDTs are now taking hold so much for all these collaborative syncing scenarios. Wonder what's driving the proliferation now given they've been around for awhile?

I've been interested in them since the early days of Atom, but it's just taken a while for me to develop as an engineer and build a system around the theory that puts them to practical use.

They gave no information on what was hacked. Although they're saying no passwords were compromised because of their encryption and architecture.

For a layperson, what's the best tips for what to do. Are passwords in Lastpass still safe or should we change all the passwords? Or simply change the master? Or should we migrate to something else?

I've thought about migrating before but frankly any password manager will have breaches...

The checksum validation was something I hadn't come across before. Interesting way to minimize the load on the API key store.

Yeah, some folks might consider going further and use hashes that salted or one-way encrypted via key so that nobody else can recreate the checksum. Some performance tradeoffs but can prevent some other vectors like cache-filling etc.

Much more of a focus on security and infrastructure than other EL tools. Like these security policies for example - https://www.cloudquery.io/docs/core-concepts/policies

I wonder if having some sort of dependency scanner giving more upfront visibility would help clear things up. Then you'd be able to get a sense of what the composition of issues might look like. Seems like there's so many scanners out there that something must solve this.