Skip to main content

v2.93.0

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

This release is orun-cloud's saas-skill-driven-agents SD1: the Orunbase skills become the one library of how agents work, and the runtime stops handing every agent every playbook.

A box loads the skills meant for it​

orun agent serve and orun agent run used to write the whole skill registry into the harness's .claude/skills/, whatever the session's job. A skill's appliesTo frontmatter, which every default carries, was read nowhere. Now a session of agent type T loads:

  • every skill whose appliesTo names T;
  • orunbase, whatever its appliesTo — the entry point that routes to every other playbook by name;
  • every skill that declares no appliesTo (an org's own skill written before audiences existed).

A session with no agent type still loads everything. The pins recorded for the PR manifest (.orun/agent-mcp/skills.json) name exactly the skills that were loaded, and the log line says how many of how many: orun agent: 6 of 11 skill(s) materialized into … for implementer.

appliesTo speaks a closed vocabulary, agent.AgentTypeNames: work-agent, implementer, bootstrapper, initiative-owner, orchestrator and reviewer. A test fails when a shipped persona is not one of them; orun-cloud pins the same list for the skills it ships.

The skills stay out of git​

The skills land in the checkout, and nothing kept them out of it: a session's git add -A committed the playbooks into the repository it was working on. Before it writes, the runtime now adds the skills directory to the repository's local .git/info/exclude (/.claude/skills/, relative to the work tree's root), once. It is never committed, and it does not untrack a .claude/skills/ a repository already tracks. Outside a git checkout, or without git on PATH, nothing happens.

One software-factory​

The software-factory skill lived twice: in this repository's skills/ and in the Orunbase registry, and the two had drifted. The copy here is gone. SOFTWAREFACTORY.md installs it with orun skills pull --client <client> (or from the mirror at https://orunbase.com/skills/), and the README links the mirror.

The personas route to the skills​

  • implementer keeps its tool lanes. Its "Orunbase tools" section, which restated the tool map and put designs in docs/design/, is now "Your playbooks": start with orunbase; task-branch-pr for the change, milestone-loop for the loop, design-authoring with software-factory's templates for a design (the epic's doc set under specs/epics/<slug>/), mcp-tools for which tool answers what. Who decides comes from the kickoff, else orunbase's defaults.
  • orchestrator keeps its tool lanes. Its 780-line operating loop over /ai/context/* and spec directories that no longer exist is replaced by a persona that names its skills: planning, initiative-lifecycle, design-authoring, milestone-loop, task-branch-pr, mcp-tools.