I do a lot of experiments, and I know I should share them more. My latest one is a small CLI tool for scheduling agent runs with GitHub Actions.

It’s writing GitHub Actions config for you, and leveraging your existing OpenCode config. It’s simple but enables a lot:

  • You could push target test trees only, and trigger an agent that diffs between target and actual and then implements.
  • You could run a test review and improvement agent every hour, in a busy trunk-based codebase.
  • You could implement really sloppily, and trigger an agent that examines your implementation for intention, writes tests to formalise that, then uses them as the basis for test-driven reimplementation of your code.
    All of this just by writing some OpenCode agent (one .MD file) and running Tender CLI.

I’m not using it – for now I’m still an ADDD (Agentic Dictator Driven Development) practitioner. I also never liked automatic commits, but maybe Tender is me starting to let go of that.

If you want to play with it and use NPM, you can run it at repo root with npx @susu-eng/tender.

You can also ask your coding agent to explore the CLI and take care of it for you. Just tell it to run npx @susu-eng/tender --help. This was my first agent-first UI, and it was fun watching Claude figure out how to operate it (trial, error, actually reading instructions, success).

This was only an experiment, implemented 100% by Codex – please use it carefully.