I went a completely different route when implementing zeptoforth (https://github.com/tabemann/zeptoforth) -- I went right for implementing a fully-featured system rather than focusing on minimalism, and came out with something that I am extremely comfortable writing non-trivial code with rather than a toy that shows how small of an implementation I can make without regard to being a practical tool. And yes, zeptoforth is very big as Forths (especially microcontroller Forths) go -- because the goal is to make something that can be used to program real systems out of the box with minimal effort on the user's part.
How about a ZeptoFORTH-MCP bridge (to implement services in ZeptoFORTH that can be called by local or remote agents) and an official way of programmatically configuring and interacting with an LLM, like on a Jetson, from ZeptoFORTH?
I have not had any feedback from Chuck, but from looking at Chuck's work I think he wouldn't consider zeptoforth to be all that Forthy.
As for a zeptoforth-MCP bridge, well, I am not really a fan of LLM's. At work we have GitHub Copilot, and I find its autocomplete to be more of a nuisance than anything, as I never like its suggestions and find the fact that it suggests anything, which I then have to reject, as largely something that interferes with my flow.
