The Gram Code Editor - 2026-10-19


  1. mort

    16 Oct 2026 at 05:50: > Currently, it seems that Gram (probably because Zed did it) uses the `org.freedesktop.Flatpak` permission to allow itself to immediately exit the sandbox. So I'm trying to figure out how difficult it would be to remove that permission, and keep Gram within the Flatpak sandbox. I use the flatpak, but only because it's a nice distribution system that's less manual work to maintain than a tarball. I have no need for Gram to run in a sandbox and I don't see how it possibly could without breaking what I find useful. I use the integrated terminal a lot and want it to have the same access and the same view of the filesystem as any other terminal, and I need Gram to see system LSP servers. How compatible is this use case with sandboxing? ✎

  2. mort

    16 Oct 2026 at 05:50: > Currently, it seems that Gram (probably because Zed did it) uses the `org.freedesktop.Flatpak` permission to allow itself to immediately exit the sandbox. So I'm trying to figure out how difficult it would be to remove that permission, and keep Gram within the Flatpak sandbox. I use the flatpak, but only because it's a nice distribution system that's less manual work for me as a user to maintain/update than a tarball. I have no need for Gram to run in a sandbox and I don't see how it possibly could without breaking what I find useful. I use the integrated terminal a lot and need it to have the same access and the same view of the filesystem as any other terminal, and I need Gram to see system LSP servers. How compatible is this with sandboxing? ✏