The Gram Code Editor - 2026-06-02

is there anyway i can support the development of gram? i use it daily and i want to see the project succeed more. i tried looking around the docs for a donate or something similar.

Hi, and thank you :) No, not right now. At least right now it’s mostly just me, and I have full time commitments so I can’t promise much when it comes to gram. We do have a corporate sponsor of sorts, meaning me and my company which is providing CI runner and web hosting. But time is the biggest limitation right now.

krig, I now have issue triaging permission but I'm not sure what I shall do when someone opens a feature request ticket. Can we add a dedicated label before closing, maybe? On top of that, I think that a "zed-port" label when there is a linked zed commit could be useful too. Do you still believe that a dedicated empty repo for feature requests is the way to go? If you create it, I could try contributing an issue template where we make it clear that feature requests are out of scope, and point to the other repo for them? These are just ideas, I don't mean to be pushy or anything, let me know what you think when/if you feel like it. ;)

@nicoco I think a feature request label makes perfect sense, lets go for that. I can make one and add a note to the wiki

oh, and I’ll add a zed-port label

hello! i had heard of zed before but saw its completely AI-centric so I didn't try it. only a couple days ago I discovered gram and i've been trying to use it for my projects. really glad to see all AI stuff removed (and also the overall focus of the project)!!

anyways, i've been trying to understand a bit the structure of the all the code (and un-rust my rust knowledge :P), but... is it me, or are there crates and random structures that are not being used anywhere?

There may absolutely be! I have been removing stuff bit by bit but there’s bound to be a lot left to remove.

okay okay, so it's probably because of those were used by the removed AI features and stuff, right?

and yeah poking around in gram is how I am improving my rust skills too. I’m would say though that it’s clear that a lot of it is vibe-coded or at least hustle-coded. Meaning there’s duplicated functionality and general code expansion everywhere.

yeah probably!

more specifically, i just noticed a crate that's only used to download and run node for the remote functionality (VSCode style i guess), quite cursed if you ask me...

anyways, for now I'm missing support for the makefile syntax, and I wanted to give a try to adding support for it

i saw a zig extension exists, but maybe it makes sense to include it by default, what do you think?

yeah sounds good. My longer term plan is to drop support for zed extensions entirely and add a scripting language for extensions instead. Wasm adds like 50MB to the executable and makes tree-sitter support more complicated…

oh god i didn't notice it, so the extensions are compiled to wasm...

yeah