Leo di Donato, who helped create Falco, the cloud native runtime security, wrote a technical deep dive into how Claude Code bypassed it's own denylist and sandbox. And introduces Veto, a kernel-level enforcement engine built into the Ona platform.
47 karma · joined April 15, 2021
Leo di Donato, who helped create Falco, the cloud native runtime security, wrote a technical deep dive into how Claude Code bypassed it's own denylist and sandbox. And introduces Veto, a kernel-level enforcement engine built into the Ona platform.
I also share my own experience and what it costs to defend your identity, and what opens up when you stop defending.
Most identity transitions used to take decades. AI is compressing that timeline into months. It is removing the parts of the job that were never really about you. And the question of who you are without them shows up fast.
gitpod.io is an open-source developer platform that provisions and orchestrated developer environments in the cloud. We are backed by General Catalyst and more than 450,000 developers use the platform.
We are building both company and product in the public:
Our direction https://bit.ly/3wxA9Ep (2min read) Problem & Solution https://bit.ly/3kqbJI9 (10min) How we work https://bit.ly/3EgoZXE (10 min) Attributes & Values https://bit.ly/3om1ZQC (3min)
Essentially, we run nightly builds at OpenVSCode Server making it as upstream to VS Code as possible. In contrast to other forks the whole scope of the project is to add a minimal set of changes (specifics about what we added https://github.com/gitpod-io/openvscode-server/blob/main/doc...)
The architecture we use powers both Gitpod and GitHub Codespaces. Several of the devs and organisations that have asked for our implementation & now have adopted OpenVSCode Server referenced the following issue at Code-Server (https://github.com/cdr/code-server/issues/3835).
Essentially, we run nightly builds at OpenVSCode Server making it as upstream to VS Code as possible. In contrast to other forks the whole scope of the project is to add a minimal set of changes (specifics about what we added https://github.com/gitpod-io/openvscode-server/blob/main/doc...)
The architecture we use powers both Gitpod and GitHub Codespaces. Several of the devs and organisations that have asked for our implementation & now have adopted OpenVSCode Server referenced the following issue at Code-Server (https://github.com/cdr/code-server/issues/3835).
We are working actively with the team at Jetbrains to offer a great DevX integrating with their remote development implementation(https://youtrack.jetbrains.com/issue/IDEA-226455).
Gitpod is all about provisioning and orchestrating ephemeral developer environments (think about it as a resource efficient and powerful orchestration platform for your dev envs).An IDE is just one building block of a working cloud based developer environment, in addition to the operating system, databases, compilers and all the other tools you need to be productive. At Gitpod we want to support the IDE or editor you like best, and providing VS Code through the web browser is just one possibility. Alternatively, you can access your Gitpod workspaces through SSH, local VS Code and soon your favorite Jetbrains IDEs.
If you have a machine somewhere which you would like to access with VS Code through a browser, check out OpenVSCode Server. If you need control over your infrastructure and would like the orchestration capabilities that Gitpod offer you can self host Gitpod.