Alpha software. Expect bugs. noHuman Team runs AI workers on your own machine with real file, browser and desktop access — start on work you can afford to have go wrong, and leave the approval queue on. What is rough right now

Back to home

Troubleshooting

Start with the reported state, not a restart. Save the error text and check whether a command is still running before trying it again. A timeout can happen after files or an external service have already changed.

The desktop app will not open

  • Mac: use the current signed and notarized installer from Install. Choose Apple silicon (arm64) or Intel (x64) for your computer.
  • Windows: check Install for available downloads. An unsigned installer may trigger SmartScreen; verify the official download before proceeding.
  • Blank window: quit the app fully from its menu, then relaunch. Use Open Log Folder in the app menu to inspect startup errors if the window still fails.

An engine is missing

A “claude: command not found” or “opencode: command not found” message means the required engine was not found. Choose Help → Install Bot Engines in the desktop app. The installer shows its log and a manual command if installation fails.

Quit and relaunch after installation so the app can detect the new engine. The noHuman Terminal can check claude --version or opencode --version; do not paste credentials or an entire environment dump into a support report.

A member is not ready or will not answer

  1. Check the startup or readiness message. “Brain not ready” can mean the member has no usable account or model.
  2. Open App settings → AI accounts and reconnect the relevant subscription or API-key account.
  3. Open the member's AI model settings. Confirm the selected model and fallback are supported by that account and worker engine.
  4. Check Needs you and the conversation for a question, tool approval, or work-limit pause.
  5. Use the conversation's More → Activity & logs panel for the actual error. If a restart is needed, read its confirmation: active work can be interrupted.

Saved history and files remain after a restart, but unfinished work may need a handover. Inspect the last result before asking the member to repeat a command.

Provider sign-in, keys, and quotas

For expired subscription sign-in, reconnect in App settings → AI accounts and finish the provider's browser or device-code flow. For an API key, verify that it belongs to the selected provider, is still active, and has model access and billing enabled.

Use the account settings to replace an AI key, not a team integration variable. A service integration has its own credentials in Team settings → Integrations. Apply changes and check the reported result before revoking the old credential.

Rate-limit and quota reset times depend on the provider. Read its error and usage page, reduce simultaneous work, or select a supported connected model. Failover needs a configured, usable fallback; connecting another account alone does not guarantee that every failure can be recovered.

If a member is paused at a daily budget, review Work limits. These controls do not replace your provider's spending limits.

Browser or desktop controls fail

For Mac screen capture, grant Screen Recording to noHuman Team in System Settings → Privacy & Security. For clicks and typing, grant Accessibility to the app too. Grants to Terminal or node are not the same. Restart after changing permissions if needed.

Open Browser from the conversation toolbar. If its live view is blank, use Show window; a minimized Chrome window may stop drawing. Sign in through the real window when a passkey or password manager is required. See Desktop workers for control-sharing limits.

Windows desktop input is experimental. Stop the current action if clicks land in the wrong place, then describe the failure in your report. Desktop workers share your real screen, mouse, and keyboard.

Telegram or phone access is offline

For Telegram, check each bot token, the configured group ID, and your founder Telegram ID under Team settings → Telegram. A bot only accepts the configured group and founder's direct messages. Make sure the bot is not blocked and your computer is online.

For the companion, check the desktop's App settings → Mobile access pairing state and the phone's desktop-status indicator. Pairing QR codes and fallback codes expire after 10 minutes. The phone needs the paired computer online; it does not run the workers itself.

There are no push notifications or voice-message sending yet. A timed-out phone command may already have applied: refresh the state before resending. Read Mobile companion for pairing, approvals, and current availability.

Report a problem safely

Include what you were doing, the error text, what you already tried, your operating system, and the app version. Find version and update information in App settings → Updates or the app's About menu. The app menu's Open Log Folder gives access to startup logs; conversation diagnostics cover a specific member.

Logs and screenshots can contain conversation text, paths, account details, or service responses. Review and redact them before sharing. Do not include license keys, API keys, subscription tokens, pairing codes, or unreviewed environment dumps.