DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a workflow in CI and parse its JSON event stream with Deer Workflow

Execute a saved workflow in a build pipeline and read a stable JSONL event stream.

Who it is forA DevOps or platform engineer who needs an agent-driven workflow to run on a server or in a CI job without an interactive terminal.

The problemAgent runs in a chat window cannot be scheduled, logged, or checked by automation.

The outcomeA non-interactive run that prints one JSON event per line, which a pipeline can capture, store, and act on.

What you need first

  • Bun installed (https://bun.sh)
  • Codex CLI installed and signed in, since Codex is the default Agent runtime
  • A terminal on macOS, Linux, or Windows with Bun support
  • Git, if you plan to clone the repository for examples or development

Steps

  1. Install Bun and the released CLI with bun install --global @deerwork-ai/deer-workflow.
  2. Commit your reviewed workflow.ts file to the repository that your pipeline uses.
  3. Add a pipeline step that runs deer-workflow run ./workflow.ts --input '<your JSON input>' --print. (inferred, check the README)
  4. Capture stdout and parse each line as a JSON event.
  5. Fail the job or alert the team based on the events that the run reports.

Prompt for your agent

Using the deer-workflow repository (deerwork-ai/deer-workflow), add a CI step that runs ./workflow.ts with the input <target input JSON> and the --print flag. Expected output: a captured JSONL event stream saved as an artifact. Verify that every stdout line parses as JSON before the job reports success.

Caveat. The README describes the JSONL stream as stable, but it does not show the event schema, so check the API Reference before writing parsers against specific event names.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page