DEV Community

WangChunyang
WangChunyang

Posted on

Publish an agent run as a playable Story from GitHub Actions

Agent runs are usually reviewed as raw logs after the fact. That works for debugging, but it is weak for demos, release notes, and evaluation reviews: the useful part is the sequence of conflict, decision, action, evidence, and result.

SunfishLoop now has a GitHub Marketplace Action for this workflow: it converts Codex, Claude Code, OpenClaw, JSONL, and plain LOG traces into a sanitized, playable Run Story. It is designed for CI runs where you want a public artifact without copying secrets or private chain-of-thought into a post.

A concrete example of the output shape is this public Story: https://sunfishloop.com/stories/story_flagship_wrong_door_v1?ref=devto-20260731

The important difference from a normal log viewer is the audience. A maintainer can open a Story and see what happened, why the run changed direction, what evidence was available, and what result was produced. That is more useful than asking someone to read a long job log or trust a one-line summary.

Typical uses:

  • attach a Story to a release note when an agent generated or verified part of the change
  • make an eval failure easier to inspect without exposing raw traces
  • turn a Claude Code, Codex, or OpenClaw run into a shareable artifact for reviewers
  • keep a public, sanitized record of autonomous workflow behavior

The Action supports GitHub OIDC so a workflow can publish without storing a long-lived SunfishLoop API key. Raw traces should still be treated carefully: publish only summarized decisions, visible actions, non-sensitive evidence, and final outcomes. Do not publish credentials, internal logs, private chain-of-thought, customer data, or anything your repository would not normally expose.

CTA: install the GitHub Action and publish one sanitized run from a real agent workflow: https://github.com/marketplace/actions/publish-agent-story

If you maintain an agent framework, eval harness, or autonomous workflow project and want a minimal opt-in workflow, I can prepare a small PR that only adds the Story publishing step behind a manual or CI trigger.

Top comments (0)