noHuman Team 4.3: setup with no terminal and overnight recovery

You can set up noHuman Team on a Mac or a Windows PC without opening a terminal. The setup wizard installs the AI software your team needs, and you sign in to Claude or ChatGPT once for the whole computer. After a long night, the app restarts its own background service if that service stops answering.

Available in noHuman Team 4.3.0 and later on Mac and Windows. noHuman Team 4.4, out now for Mac with Windows to follow, adds the 7-day trial to the wizard's License step.

Install noHuman Team or read the 4.4.0 release notes. The 4.4 overview covers the rest of what changed since 4.0.

Do I need a terminal to set up noHuman Team?

No. Since 4.1.3 the app opens the setup wizard on first launch, and since 4.1.4 the wizard installs missing AI software inside the app. You pick the team's folder in Finder on a Mac or in Explorer on Windows, and the wizard has no commands for you to paste.

The wizard has eight steps: Team name, Workspace, License, Provider, Template, Telegram, Group and Launch. You can skip the two Telegram steps. Choose folder shows the full path, and canceling the chooser keeps your earlier pick. If Claude Code or OpenCode is missing, Install and continue installs it and shows progress, with Try again after a failed download. Later, Help → Prepare AI Software runs the same installer.

You can stop halfway. An unfinished team shows Set up team in the sidebar, and the app keeps its name and folder through a restart. If the wizard cannot load your saved settings or the templates, it offers Try again and keeps an unreadable settings file intact.

Setup ends on a checklist where you confirm each noHuman's model. Until 4.1.6 fixed it, the app returned you to the first step after Launch team, and you chose everything again.

In noHuman Team 4.4, the License step offers the monthly plan's 7-day trial above the key field. The setup wizard guide covers each step.

Do I sign in to Claude or ChatGPT for each noHuman?

No. Since 4.3.0 you connect a Claude or ChatGPT subscription once per computer, in the wizard or in App settings → AI accounts. All teams on that computer share it. The app deletes the old per-noHuman sign-in files the next time a noHuman starts.

The connect dialog installs or updates Claude Code before a Claude sign-in. Cancel stops the sign-in on the computer as well as in the dialog, and a sign-in you walk away from closes after 10 minutes. Once the account connects, the dialog tells you which noHumans the app restarted: "Restarted CEO and Developer to use this account."

The wizard takes a Claude Pro or Max plan, a ChatGPT Plus or Pro plan, or an API key for Anthropic, OpenAI, OpenRouter, Gemini, DeepSeek, Groq, Mistral or Moonshot. The FAQ explains whether you need an API key and lists the supported providers.

Which model does a new ChatGPT team start on?

gpt-5.6-sol, since 4.1.6. Once the team is up, setup sends the first noHuman one short check message. If your ChatGPT plan refuses the model, setup moves the team to the next model on its list.

Before 4.1.6, new teams started on gpt-5.5, and many ChatGPT plans answered "not supported when using Codex with a ChatGPT account". Setup switches models on that kind of refusal alone: a timeout or a quota message leaves the model as it is. You can change any noHuman's model on the checklist after setup, or later in its settings.

Will the team still answer after my computer sleeps overnight?

Yes, from 4.3.0. The app's background service checks itself every 30 seconds. If three checks in a row get no answer, about a minute and a half, the service quits, and the app starts a fresh one and brings back the team that was running.

On 20 October, after about 12 hours overnight, the service's worker threads stopped taking work, with 3,932 name lookups and 462 file operations stuck in the queue. The app's pages still loaded, but messages to noHumans failed with "chat-stream connect failed: fetch failed", and the phone companion kept trying to connect. I shipped the self-check in 4.2.1 that morning; Windows users got it in 4.2.2.

On 21 October the check caught the same jam, but the stuck service hung while quitting, so the app did not restart it. 4.3.0 makes the service end itself at once, so the restart goes through. 4.2.1 also removed a second cause of "fetch failed": the app reaches its noHumans by address instead of by name.

Does quitting the app stop everything?

Yes. Since 4.2.1 the background service stops with the app, even after a crash or a force quit. Every 5 seconds it checks that the app which started it still runs, and once the app is gone, it stops the team and exits. Before, a service left behind by a crash could keep running for days.

Windows needed one more fix, because it has no polite stop signal. Earlier Windows builds killed the service without asking: the team skipped its normal shutdown, and each noHuman's browser lost its last 30 seconds or so of sign-ins. From 4.3.0, quitting on Windows asks the team to stop first.

Why did the first message after launch take minutes?

The team gateway counted idle connections as requests in progress, and 4.2.0 fixed it. A starting teammate's open connections had filled the team's 10 slots, so its first real request waited in the queue. Now a connection gives its slot back once its response has been quiet for 2 seconds.

On 19 October, each Claude teammate's first turn after a launch took 3 to 5 minutes. At start-up, Claude Code opens about 10 connections at once and keeps them open, enough to fill the slots by itself.

The same release stopped two teams running at once from mixing their tools, which could send one team's questions and reports to the other. While a noHuman starts on your message, the chat shows "Starting on it…" with a timer after 15 seconds.

Where do I find the log when something goes wrong?

Choose Help → Open Log Folder. Since 4.3.0 the app keeps one log file per day next to your teams, starts each line with its time, and deletes files older than 14 days.

Each file carries its date in the name, such as app-2026-10-25.log. A day's log starts a second file after 20 MB, and the app removes the oldest files once all logs together pass 500 MB. Before 4.3.0, an app opened from Finder kept no record of its background service's output.

A slow or busy noHuman's conversation shows "Loading this conversation…" with Try again instead of looking empty, a change from 4.2.1. The troubleshooting guide lists what to check before you restart anything.

Which computers can run noHuman Team?

macOS on Apple silicon or Intel, or Windows 10/11 with PowerShell 5.1 or later. Windows desktop click and type is experimental. Cardamon signs the Mac installers, and Apple notarizes them. For a team of four noHumans, 16 GB of memory is comfortable.

noHuman Team 4.4 is out for Mac now, and its Windows build follows. In the meantime, Windows users can install 4.3.0 from the release archive. The FAQ lists the system requirements.

Do updates keep my team?

Yes. Your teams, settings, conversations, files and Memory live outside the app, so a new version keeps them. The app stops a running team before an in-app update installs, so finish or pause work first.

Choose Check for Updates… in the noHuman Team menu on a Mac or the Help menu on Windows, or open App settings → Updates. On a Mac, 4.1.5 added a note that installing takes a few minutes and that the app will reopen, plus a manual download when the app cannot replace itself. The same release made the installers smaller, and 4.1.6 cut about 100 MB from the Windows installer. The FAQ explains how updates work.

Quick answers

Do I need Telegram to finish setup?

No. You can skip the Telegram and Group steps and talk to your team in the app.

Does the 7-day trial start inside the app?

No. In noHuman Team 4.4, Start trial on the License step opens the pricing page in your browser. After checkout, you enter your email and the key you received in the wizard.

Does switching a paused noHuman to another model end a usage-limit wait?

In noHuman Team 4.4, yes. The pause ends when you switch, and the messages it queued go out. If the new model has reached its limit too, the noHuman waits for that provider's reset time. Token use per task covers usage limits in more depth.

For what runs on your computer and what goes to your AI provider, read How to run AI agents locally.

Install noHuman Team and set up your first team without a terminal. The monthly subscription starts with a 7-day trial; payment details are required at checkout. Your AI provider charges separately.