Done:
git subcommands not allowed?packages/spark-harness/extensions/git-tool.ts
update pi
update readme
TODO:
don't show full file diff in pi
when trying to open an url with an incompatible baxkend (or just no backend), print the entire html received. Should print a pretty message instead (and maybe write the html to some /tmp location).
replace nodejs by bun for bundling
inspiration from raindrop
- would help with other agent support
#29
local traces in the web browser without creating a braintrust account
- what should be the incentive to create a free account?
better looking clean up message? conflicts with raindrop-like onboarding I think
also distribute as npm pkg for people who have node installed, cleaner for them
- node version issues?
why the legacy deploy implementation?
on first run, launch the extraction async since the harness isn't needed until pi launches, then only block if pi needs to be launched before the harness is completely extracted
pi doesn't update llm api key given?
Done:
gitsubcommands not allowed?packages/spark-harness/extensions/git-tool.tsupdate pi
update readme
TODO:
don't show full file diff in pi
when trying to open an url with an incompatible baxkend (or just no backend), print the entire html received. Should print a pretty message instead (and maybe write the html to some
/tmplocation).replace nodejs by bun for bundling
inspiration from raindrop
#29
local traces in the web browser without creating a braintrust account
better looking clean up message? conflicts with raindrop-like onboarding I think
also distribute as npm pkg for people who have node installed, cleaner for them
why the legacy deploy implementation?
on first run, launch the extraction async since the harness isn't needed until pi launches, then only block if
pineeds to be launched before the harness is completely extractedpi doesn't update llm api key given?