Skip to main content

v2.94.0

Binaries and the merged-pull-request list are on the GitHub releases page.

This release is part of orun-cloud's saas-skill-driven-agents SD4: every output names the skill revisions that produced it.

The manifest line, in the harness's environment​

A pull request's manifest block (<!-- orun:manifest … -->) names the task, the session and the skill revisions the work was done under. orun pr open and the pr_open tool write it from the pins the session recorded (.orun/agent-mcp/skills.json). A session that opens its pull request with gh — every orun.work session — could not: the pins sit beside the MCP config, outside its checkout, and its manifest named the task alone.

orun agent serve now renders the same block orun pr open would, from the session's task (--task / ORUN_TASK_KEY), its id and the pins of the skills it just loaded, and hands it to the harness as ORUN_MANIFEST. A pull request body that ends with $ORUN_MANIFEST carries the full manifest:

gh pr create --head orun/APP-3-booking --title "APP-3: Booking" \
  --body "Visitors can book a class.

Orun-Task: APP-3

${ORUN_MANIFEST:-<!-- orun:manifest {\"version\":1,\"task\":\"APP-3\"\} -->}"

The fallback after :- keeps the command working under an older orun, which sets no ORUN_MANIFEST (its closing brace is escaped, \}, so it does not end the expansion early). A session with no task gets no line; a session whose registry read failed gets a manifest with no pins.