GitHub Actions for oddyssey, Observability-Driven Development for coding agents: they bring the ODD loop into your workflows. A setup action installs a coding CLI and the oddyssey package on the runner; an action per oddyssey capability then runs it there and turns the answer into outputs a workflow can gate on.
| Action | What it does |
|---|---|
setup-copilot |
Installs the GitHub Copilot CLI (pinned, checksum-verified) and the oddyssey package on the runner, the model (default gpt-5.6-luna) and the package version (default latest; a tag or a commit SHA) as its only inputs. |
setup-opencode |
Installs opencode (pinned, checksum-verified) and the oddyssey package on the runner, an OpenAI-compatible endpoint as its provider (default OpenRouter, the key as a secret input), the same model and package version inputs. |
setup-claude |
Installs Claude Code (pinned, checksum-verified) and the oddyssey package on the runner, an Anthropic API key or a Claude OAuth token as its credential (one of the two, as a secret input), the same model and package version inputs. |
odd-status |
Runs the packaged /odd-status through the CLI a setup action installed and turns the verdict the package computes (ok, warning, error, the next actions) into outputs; fail-on makes it a gate; the Copilot run takes the workflow's token itself (token overrides it), the Claude Code run the credential its setup kept. |
One setup action per CLI. Each CLI installs, authenticates, takes its
model and loads the package differently, so a setup-<cli> action owns
one CLI end to end. There is never one action with a cli input whose
other inputs mean something else per value. Every setup action exports
ODDYSSEY_CLI and ODDYSSEY_MODEL to the later steps, which is how an
action that runs a prompt knows which CLI to launch and how.
- uses: using-system/oddyssey-actions/<action>@v1Pin the floating major tag (v1, moved on every release of that
major), an exact release tag (v1.0.0), or a commit SHA. Each action's
README states its inputs, its outputs, how the launch step
authenticates and one complete example workflow.
Each release of the actions names the oddyssey version it needs at
minimum, in ODDYSSEY_MINIMUM_VERSION: a
setup action installs that version in place of an older tag and says
so; latest and a commit SHA resolve as given.
A release is a tag vX.Y.Z pushed to this repository: the release
workflow creates the GitHub release from the merged PR titles and moves
the vX tag to it. Versions follow
Conventional Commits on the PR
titles (feat: a minor, fix: a patch).
CONTRIBUTING.md is the workflow, AGENTS.md the conventions a coding agent reads, and the Code of Conduct applies. Security reports go through private reporting, never a public issue (SECURITY.md).
MIT.