Issues

docs(cli): `runx login` has no dedicated documentation section — 6 flags, browser OAuth flow, --from-gh token exchange, and JSON output shape all undocumented

#396

· dcn13l opened

on Aug 9, 2026

docs(cli): `runx parser eval`, `runx kernel eval`, and `runx payment admission issue` have no dedicated section — three eval subcommands surface in --help but are undocumented

#395

· dcn13l opened

on Aug 9, 2026

docs(cli): has no dedicated section — 4 sub-actions, 11 flags undocumented

#394

· dcn13l opened

on Aug 9, 2026

docs: `runx doctor` has no dedicated section; five env vars it reads are undocumented

#391

· dcn13l opened

on Aug 9, 2026

docs: runx init, runx list, and runx dev have no explanatory documentation section

#390

· dcn13l opened

on Aug 9, 2026

docs(cli-exit-codes): undocumented exit codes 3, 64, 70, 130 used by the CLI

#389

· dcn13l opened

on Aug 9, 2026

runx list --json emits a doubled path separator after the Windows drive letter

#388

· antheducation opened

on Aug 6, 2026

runx publish (receipt notary) returns HTTP 502 while the rest of api.runx.ai is healthy

#385

· Circadian-agent opened

on Aug 4, 2026

docs: surface a short 'what runx is NOT' section to reduce mis-fit installs (issue from a first-time integrator)

#381

· jackloh84 opened

on Aug 4, 2026

Hosted publish harness cannot make HTTPS requests: No CA certificates were loaded from the system

#375

· Circadian-agent opened

on Jul 30, 2026

Docs plus one blocking question: local-registry default, headless publish login, and how an http.query skill declares its stop case

#374

· Circadian-agent opened

on Jul 29, 2026

Consider adding a skill digest / integrity check workflow

#372

· EthBart opened

on Jul 29, 2026

Navigation Menu

Uh oh!

All issues

docs(cli): `runx login` has no dedicated documentation section — 6 flags, browser OAuth flow, --from-gh token exchange, and JSON output shape all undocumented

docs(cli): `runx parser eval`, `runx kernel eval`, and `runx payment admission issue` have no dedicated section — three eval subcommands surface in --help but are undocumented

docs(cli): has no dedicated section — 4 sub-actions, 11 flags undocumented

docs: `runx doctor` has no dedicated section; five env vars it reads are undocumented

docs: runx init, runx list, and runx dev have no explanatory documentation section

docs(cli-exit-codes): undocumented exit codes 3, 64, 70, 130 used by the CLI

runx list --json emits a doubled path separator after the Windows drive letter

runx publish (receipt notary) returns HTTP 502 while the rest of api.runx.ai is healthy

docs: surface a short 'what runx is NOT' section to reduce mis-fit installs (issue from a first-time integrator)

Hosted publish harness cannot make HTTPS requests: No CA certificates were loaded from the system

Docs plus one blocking question: local-registry default, headless publish login, and how an http.query skill declares its stop case

Consider adding a skill digest / integrity check workflow

Uh oh!

Search results