That's a nice idea but I hate how every instruction step in the README is just "Ask your agent to do it". Not only does it make it harder and more time-consuming to understand how the general system is implemented, but it also dumbs down users. Do you think people checking your repo wouldn't be able to copy/paste a few commands or find an equivalent on their system?
that's the neat part, there is no prescribed system or code. your agent decides the implementation which you control, the repo is mostly natural language (save for the presentational tui)
Comments
That's a nice idea but I hate how every instruction step in the README is just "Ask your agent to do it". Not only does it make it harder and more time-consuming to understand how the general system is implemented, but it also dumbs down users. Do you think people checking your repo wouldn't be able to copy/paste a few commands or find an equivalent on their system?
that's the neat part, there is no prescribed system or code. your agent decides the implementation which you control, the repo is mostly natural language (save for the presentational tui)
It would be neat if you can give a general idea what it tries - sets up a python web dashboard on this port and launchd to run off-hours etc.
https://imgflip.com/i/b0vp88
systemd service to write "opencode run --session <id> continue, make no mistakes"
...were you not prompting .e