Node privacy and troubleshooting

Use this guide to diagnose Node connection and media errors.

Check the connection in order

1. Confirm that mere.run Node displays online.
2. Confirm that AgentsMarkdown and the Node use the same mere.world account.
3. Open relay.mere.run and verify that the device is enabled and not draining.
4. In the Node app, open Models and select Scan.
5. Open Capabilities and verify that the required pack is ready.
6. Reopen or reload the AgentsMarkdown document.

This order separates sign-in, fleet policy, model inventory, and document UI problems.

Node is connected but a tool is missing

AgentsMarkdown reads the Node's advertised capabilities, not only its device status. A Node can be online and still lack image, speech, ASR, or OCR support.

Install the matching model or runtime pack, scan again, and check the capability list.

Installed models are not reported

Make sure the Node can find the same mere.run executable and model directory you use in the terminal. Start desktop apps from your user session, not with sudo.

On Linux, prefer the .deb package on Ubuntu or Debian because it integrates with the desktop environment and system executable paths.

A job stays queued

Queued work needs an eligible online Node. In the relay console, check:

• Whether a Node supports the job kind
• Whether the required model is installed
• Whether the Node is busy, disabled, or draining
• Whether another policy makes a different Node preferable

Live transcription does not start

Live ASR needs:

• Browser microphone permission
• A Node that advertises streaming ASR
• A ready Parakeet or Qwen ASR backend
• A stable relay WebSocket connection

Try batch transcription with the same audio source. If batch works, focus on browser permission and streaming capability.

Speech finishes but does not play

Check that the browser allows audio playback and that the document tab is not muted. Retry Listen after interacting with the page, because browsers can block playback before a user gesture.

Privacy boundary

The audio, image, or prompt must travel from the browser to the relay and then to your chosen Node so the job can run. Model inference happens on the Node. Results return through authorized relay and AgentsMarkdown routes.

Saved media URLs are separate access credentials. Anyone with an asset URL can retrieve the file without a document key or account session.

Revoking a share link or unpublishing a document does not revoke copied asset URLs. Deleting the document removes its stored assets.

Report a problem

Include the following information in a problem report:

• Node app version
• mere.run --version
• Operating system and architecture
• The capability name
• The visible error
• Whether the job appears in relay activity

Do not include share keys, account tokens, or private document contents in a public issue.