V1.2.3-experimental (haha, 1-2-3…) | you can freely access JAE by sending a DM through the Hack Club workspace to the agent, or by joining the #-jae channel! <3

After a lot of trial and error, I’m proud to say that Jae now has ONE tool that hasn’t been released yet, called the run_command tool.

On the running of this tool, an Alpine Linux container will be spun up for Jae to experiment inside! The packages I included in the Dockerfile (or image) for Jae to use are Rust / Cargo / Rustup, Python 3 and NodeJS.

Docker Compose manages the behind-the-scenes for the Jae Execution Server and Docker-Socket-Proxy (thanks, Tecnativa :D) and if you were to run the bot on a different machine from the execution server, you can use the handy environment variables declared in the bot EXECUTION_SERVER=<IP>:<PORT> and EXECUTION_SERVER_TOKEN=.... Of course I had to include a token, otherwise it just wouldn’t be that secure.

A next bit to this might be persistence for a single conversation thread, or setting resource limits so the bot doesn’t accidentally run a crypto miner. And, then even allowing Jae to interact with programs could be a great addition.

Update is live on Slack, but of course I will be monitoring + Jae will be a little hesitant to run commands.

Thanks for reading!

README | Commit History