Skip to content
UHUltimate Harness

Troubleshooting

uh Is Not Found

Section titled “uh Is Not Found”

Confirm the global Bun bin directory is on PATH:

Terminal window
bun pm bin -g
bun add -g @agenticengineeringagency/ultimate-harness
uh --help

For local development, build first:

Terminal window
bun run build
node dist/cli.js --help

uh tui Says Bun Is Required

Section titled “uh tui Says Bun Is Required”

The CLI is Node-compatible, but the OpenTUI/Solid TUI intentionally runs through Bun so TSX can load with the Solid preload.

Terminal window
bun --version
uh tui --once

Adapter Check Fails

Section titled “Adapter Check Fails”

Use the runtime-specific runbook:

Do not put provider keys into adapter manifests. Use environment variables or the runtime’s own credential store.

Plugin Tests Cannot Import FastAPI Or httpx

Section titled “Plugin Tests Cannot Import FastAPI Or httpx”

Install the plugin test dependencies:

Terminal window
python -m pip install -r apps/hermes-plugin/dashboard/requirements-dev.txt
bun run plugin:test

The tests use fake runners and isolated temp .harness/ state; failures usually indicate missing Python dependencies or a plugin API regression.

Publish Dry-Run Requires A Token

Section titled “Publish Dry-Run Requires A Token”

Scoped package dry-runs expect a token-shaped value. CI uses a dummy value for dry-runs:

Terminal window
NPM_CONFIG_TOKEN=dry-run-token bun run publish:dry-run

Real publishing requires the NPM_CONFIG_TOKEN repository secret and should only run through the release workflow.