# Reported issues for runx

Pod holds 15 of 15 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to [runx](/mcp/runx).

## Most discussed

### runx registry publish returns HTTP 500 (registry reads on the same host succeed)

`runx registry publish` against `https://api.runx.ai` returns HTTP 500 for us on every attempt. Reads against the same registry succeed, so this looks server-side rather than auth or connectivity.

### Command and result

```
$ runx --version
runx-cli 0.8.2

$ runx registry publish skills/x402-probe --registry https://api.runx.ai --json
{"error":{"code":"registry_error","message":"runx API registry publish returned HTTP 500: Internal Server Error"},"status":"failure"}
```

Tried twice, ten…

[Read the thread](https://github.com/runxhq/runx/issues/403) · 2026-08-11 · closed · external user · 11 comments

### runx login: connect.runx.ai/session returns 404 after GitHub OAuth; token never stored (CLI 0.6.13 & 0.6.14)

## Summary
`runx login --provider github` never completes: after the GitHub OAuth succeeds, the browser is redirected to **`https://connect.runx.ai/session`, which returns `404 Not Found`**, and the CLI never receives a token (`runx config list` stays empty, then the CLI eventually prints `public API login timed out before completion`).

## Environment
- runx CLI **0.6.14** (also reproduced on 0.6.13), macOS (aarch64).
- api.runx.ai is reachable (`curl -s https://api.runx.ai/` → 200; `POST…

[Read the thread](https://github.com/runxhq/runx/issues/207) · 2026-07-01 · closed · external user · 4 comments

### bug: hosted publish cannot resolve pinned official nested skill

### Summary

A valid graph package that composes the pinned first-party `data-store` skill passes local inspection and all harness cases, but hosted publication fails.

Public minimal reproduction: https://github.com/emilianochagoya/list-hygiene-judge-runx
Related integration PR: https://github.com/runxhq/runx/pull/398
CLI: `runx-cli 0.8.2`

### Reproduction

The graph uses the currently published first-party ref:

`registry:runx/data-store@sha-30c9df39e353`

Its public registry digest is…

[Read the thread](https://github.com/runxhq/runx/issues/401) · 2026-08-11 · closed · external user · 3 comments

### login --for publish returns 404 after GitHub OAuth, no publish token issued, publish always Unauthorized

## Problem
`runx login --provider github --for publish` opens the connect URL. After GitHub consent, the browser lands on a 404 page on connect.runx.ai. The CLI never receives a usable API token.

Subsequent `runx publish <receipt.json>` always fails with:
"runx-api publish returned error [api_error]: Unauthorized."

This affects both default and publish logins.

## Reproduction
1. runx login --provider github --for publish
2. Authenticate via GitHub
3. Browser shows 404
4. runx publish ... ->…

[Read the thread](https://github.com/runxhq/runx/issues/287) · 2026-07-12 · closed · outside contributor · 3 comments

### docs/getting-started.md quickstart claims an unverified local receipt

## Summary
`docs/getting-started.md` states the quickstart `runx skill ./examples/hello-world` run produces a receipt whose `runx.receipt_inspection.v1` projection shows "the receipt status, authority, decisions, acts, seal summary, and local issuer verification". Verified locally on main (2026-09-17) that the projection does **not** include a verification verdict, so the documented "expected verify verdict" is not actually produced.

## Reproduction
```bash
git clone --depth 1…

[Read the thread](https://github.com/runxhq/runx/issues/491) · 2026-09-17 · open · external user · 2 comments

### `runx new` scaffold next steps fail on fresh install without receipt signer

## Summary

On a fresh npm installation, the exact `next_steps` emitted by `runx new` fail at the first command because no receipt signer is configured. This conflicts with the scaffold source comment that the generated skill "runs and harnesses immediately."

Project: https://github.com/runxhq/runx ? docs: https://runx.ai

## Environment

- runx: `runx-cli 0.6.15`
- install: `npm install -g @runxhq/cli`
- OS: Microsoft Windows 11 ??? ??? (10.0.26200, AMD64)
- shell: Windows PowerShell…

[Read the thread](https://github.com/runxhq/runx/issues/220) · 2026-07-03 · closed · external user · 2 comments

### connect.runx.ai OAuth login broken: POST /session returns 404

## Bug: runx login --provider github --for publish fails with 404

### Summary

The `runx login --provider github --for publish` OAuth flow is broken. After clicking "Connect" on the runx Connect page, GitHub's login form is rendered — but the form action is rewritten from `github.com/session` to `connect.runx.ai/session`, which returns **404 Not Found**.

### Steps to reproduce

1. Run `npx runx login --provider github --for publish`
2. Open the generated `connect.runx.ai` URL in a browser
3.…

[Read the thread](https://github.com/runxhq/runx/issues/215) · 2026-07-02 · closed · external user · 2 comments

### Hosted login provider unavailable — runx login fails with login_provider_unavailable

## Summary
`runx login --provider google --for publish --json` fails immediately with:

```
{
  "error": {
    "code": "login_failed",
    "message": "runx-api login returned error [login_provider_unavailable]: Hosted login provider is unavailable. Try again later."
  },
  "status": "failure"
}
```

Same behavior with `--provider github`: CLI prints the OAuth URL, polls indefinitely ("Waiting for public API login..."), never receives a callback.

## Reproduction
```
runx --version…

[Read the thread](https://github.com/runxhq/runx/issues/89) · 2026-06-20 · closed · outside contributor · 2 comments

## Most recent

### Windows: cli-tool skills abort with node exit 134 (CSPRNG assertion) — child spawned with empty environment; README quickstart fails on 0.9.1

## Summary

On Windows, every `cli-tool` skill run aborts during child-process startup with `exit_code 134` (`Assertion failed: ncrypto::CSPRNG(nullptr, 0)` inside `node.exe`). The documented README quickstart fails on a clean Windows 11 install. The receipt still seals correctly (`disposition: failed`, `reason_code: process_failed`), so governance works — but no Windows user can seal a *successful* first receipt from the five-minute path.

This is **not** #444 (verbatim `\\?\` cwd). That fix…

[Read the thread](https://github.com/runxhq/runx/issues/504) · 2026-09-18 · open · external user · 1 comment

### catalog: two first-party skills cannot be installed on runx-cli 0.9.1 (steps.3.mutation unsupported; declared module missing)

## Summary

Two published catalog skills cannot be installed/run with `runx-cli 0.9.1`. In both cases the **catalog advertises them as runnable**, and `runx registry read` reports `trust: first_party`.

## A. `runx/sourcey` — manifest uses a field the CLI rejects

```
$ runx skill inspect runx/sourcey@sha-60f1861aafe3 --registry https://api.runx.ai
runx: X.yaml: steps.3.mutation is not supported; approval and authority are owned by the invoked capability

$ runx add…

[Read the thread](https://github.com/runxhq/runx/issues/488) · 2026-09-16 · open · external user · 0 comments

### cli-tool runner: wasm instantiation fails with 'Out of memory' inside the governed sandbox (works outside it)

## What we hit

A governed run of a local `cli-tool` runner fails inside runx's execution sandbox with a **WebAssembly out-of-memory** error, while the *exact same command* succeeds when run directly in the same shell on the same host.

```
closure.disposition: failed
closure.reason_code: process_failed
error.exit_code:    1
error.message:      failed to asynchronously prepare wasm: RangeError:
                    WebAssembly.instantiate(): Out of memory: Cannot allocate Wasm memory for new…

[Read the thread](https://github.com/runxhq/runx/issues/487) · 2026-09-16 · open · external user · 0 comments

### Docs/CLI drift: canonical SKILL.md quickstart uses commands that do not exist in runx-cli 0.9.0

**ENV**
- CLI: `runx-cli 0.9.0` (installed 2026-09-12 via `npm install -g @runxhq/cli`, also reproduced notes below on Ubuntu 24.04 / Node 22)
- Trigger doc: https://runx.ai/SKILL.md (canonical, "the agent-facing quickstart")

**WHAT THE DOC SAYS**

Under "How to use":
1. `runx x search <query>`
2. `runx x install <owner>/<name>`
3. `runx run <skill> --input ...`
4. `runx receipts tail`

**WHAT THE CLI ACTUALLY DOES**

```text
$ runx x search evolve --json
runx: unknown command x

$ runx run…

[Read the thread](https://github.com/runxhq/runx/issues/461) · 2026-09-12 · closed · external user · 1 comment

### docs: reference.md documents `runx export-receipts --trainable`, a command that does not exist

## Environment

- `runx --version`: `runx-cli 0.8.2`
- Windows 11 (10.0.26200), PowerShell 7
- Source checked against `c9f8b25b`

## What is broken

`docs/reference.md` has a section "Trainable Exports" (line 717) that tells the reader to run `runx export-receipts --trainable`. There is no such command. It is not in the 0.8.2 CLI, and it is not in the repo source at HEAD.

The section says trainable export is "a TypeScript-maintained projection command", suggesting it lives in the npm package.…

[Read the thread](https://github.com/runxhq/runx/issues/448) · 2026-09-07 · closed · external user · 0 comments

### Windows: cli-tool runner spawned with extended-length \?\ cwd aborts node (quickstart hello-world fails, exit 134)

## Summary

On Windows, the README quickstart (`runx skill ./examples/hello-world -i message="hello, runx" --json`) fails every time. The `cli-tool` runner is spawned with an **extended-length (`\?\...`) working directory**, and `node.exe` aborts during process initialization before `run.mjs` ever executes.

The receipt is still sealed correctly (`disposition: failed`, `reason_code: process_failed`), so governance behaves — but no one on Windows can seal a *successful* first receipt from the…

[Read the thread](https://github.com/runxhq/runx/issues/444) · 2026-08-31 · closed · external user · 0 comments

### Docs: receipt output examples do not match CLI 0.8.2

## Documentation locations

- The root quickstart says the skill `--json` output includes a
  `runx.receipt.v1` document:
  https://github.com/runxhq/runx/blob/26db2258812bb8c94d3d77f1b57e810c0b76fd42/README.md#L91-L92
- The getting-started guide says default `history --json` shows a
  `runx.receipt.v1` stamped by a local issuer:
  https://github.com/runxhq/runx/blob/26db2258812bb8c94d3d77f1b57e810c0b76fd42/docs/getting-started.md#L45-L55

## Observed behavior

I reproduced the checked-in…

[Read the thread](https://github.com/runxhq/runx/issues/443) · 2026-08-31 · closed · external user · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/runxhq/runx/issues).