Overview
Tokens go brrrr
Basic SDLC
Loops
while true; do
pi -p "$PROMPT"
done
while true; do
pi -p "$PROMPT"
pi -p "Don't push to master, check out a new branch and iterate on that PR"
done
Organizing
Read → Eval → Print → Loop
↑ ↓
└───────────────┘
Starting up
env.sh
export VERS_API_KEY='...'
export ANTHROPIC_API_KEY='...'
export GITHUB_API_KEY='<scoped personal access token>'
plan.md
The goal is to make a modern elixir/webassembly solution for both running wasm-in-elixir as well as building elixir-to-wasm
ALL SYSTEMS AND AGENTS MUST use this github -> https://github.com/hdresearch/firebird.git
For each of the below goals, create a VM and run code like the following
```bash
while true do
pi -run "GOAL"
end
```
NOTE - pi is running on the VM itself rather than running on the host machine and then ssh'ing commands. This should be done so I can quit this pi session
So agents are just infinitely running since there is always something to improve in a piece of software. Include pi-vers extension and copy over env.sh so each infinite loop can provision further VMs or agents.
- elixir developer experience (making sure usage is as simple as possible, should not be five minutes of updating an existing elixir project to get it to work)
- running wasm from elixir (ie build go wasm project and run an exported add() function)
- enabling a mix target to compile an elixir project to wasm
- getting a phoenix project to compile to wasm
Be sure to instruct each goal loop to include 100% test coverage as well as performance comparisons between elixir programs and the webassembly equivalents (such rewriting a math function in rust->wasm to then use or compiling an elixir app to wasm to benchmark the number of handleable processes). There may be cases where BEAM wins but my suspicion is there is a case where elixir-to-wasm can be more performant or memory efficient than using standard elixir
When I had to step in
Trying it yourself