Skip to main content

v2.26.0

Release notes for orun v2.26.0.

Highlights​

  • The MCP server never fails the handshake. orun mcp serve now always answers initialize — a missing login, an unset backend URL, or a resolution error degrades to a served connection instead of a silent exit. A new always-present connection_info tool reports auth state, backend URL, and which planes mounted (with reasons and the exact fix command), so an agent can always orient. Absent and expired credentials now behave the same: mounted-but-degraded, with per-call errors that carry run \orun auth login``.
  • orun mcp doctor. A pre-flight for agent integration: binary path and version with a PATH-mismatch warning (catches a stale orun on PATH that lacks mcp serve — the most common "Failed to connect"), auth source and session expiry, the workspace resolution chain, per-plane backend probes (a 404 on a platform route is called out as "not an Orun Cloud API endpoint"), and the exact absolute-path claude mcp add orun -- <path> mcp serve registration line.
  • Resources & prompts. The unified server now serves all three MCP surfaces: two resource templates — catalog://{workspace}/{entityKey} (service overview as markdown) and runs://{workspace}/{project}/{runId} (run summary with the plan-DAG job table) — and four packaged prompts (investigate_failed_run, access_review, usage_review, service_snapshot), identical to the hosted remote server and pinned to the same vendored contract. Capabilities are advertised only when the backing plane is mounted.
  • Truthful tool metadata. Every tool — work and platform — now carries complete readOnlyHint/destructiveHint/idempotentHint annotations on the wire, so strict clients stop over-prompting on work-plane reads. Tool counts in help text derive from the live roster and can no longer drift.
  • Actionable errors. A platform tool hitting not_found against a non-Orun-Cloud backend URL now says so (instead of a bare NOT_FOUND), and 401s include the login hint. --verbose on serve prints a startup summary of what mounted and why.

New: never stranded​

orun mcp doctor        # pre-flight: binary, auth, workspace, backends, registration line
orun mcp serve --verbose
✓ binary       /usr/local/bin/orun (v2.26.0) has `mcp serve`
✓ auth         session (expires in 12m; refresh available)
✓ workspace    ws_8D3ZJQM2 (from repo link)
✓ platform API ok
✓ work API     ok

register this binary with your MCP client (absolute path — never plain `orun`):
  claude mcp add orun -- /usr/local/bin/orun mcp serve

Even with no login at all, orun mcp serve completes the MCP handshake and serves connection_info, which tells the agent exactly what to run next.

Compatibility​

  • The default tools/list roster grows by one (connection_info, always present). resources and prompts capabilities appear on initialize when the platform plane is mounted; clients that ignore them are unaffected.
  • Work-plane tools now carry wire annotations; clients that key confirmation UX off readOnlyHint will prompt less for work reads. The six work mutators advertise idempotentHint: false (they carry no idempotency key) — retry deliberately.
  • No tool names, schemas, or routes changed.