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

AI accounts and integration variables

Connect AI accounts once for this computer. Your teams can share those connections while each noHuman keeps its own model selection. Team integration secrets and environment variables have a separate settings page.

Connect an AI account

  1. Open App settings → AI accounts.
  2. Choose a supported subscription or API-key provider. Complete browser sign-in for Claude or ChatGPT, or enter the credential your provider requires.
  3. Check the connection status before choosing the account in a team's AI models settings or a noHuman's model picker.

The setup wizard supports Claude Pro/Max and ChatGPT Plus/Pro subscriptions, plus API keys for Anthropic, OpenAI, OpenRouter, Google Gemini, DeepSeek, Groq, Mistral and Moonshot. The full catalog contains 20 integrations across API-key and OAuth connections. A catalog entry does not guarantee that your account or installed engine can use a model.

Choose models without duplicating credentials

Use Team settings → AI models for the team's default account. In a conversation, select the model beside Send to choose that noHuman's model. Its AI model settings also let you choose a backup where supported.

A model change during work can interrupt a turn. Changing provider may restart the selected noHuman. Read the confirmation before applying a change; an account connection and a model selection are separate settings.

Manage team integration secrets

Open Team settings → Integrations for variables and integration secrets that belong to this team. Use the team-wide tab or a noHuman's tab for an override. AI-provider credentials belong in App settings → AI accounts.

noHuman Team v4.2.2Explore the interface

Environment variables

Give your team clear responsibilities and connected services. Changes here stay in this preview.

Values your team can use

Keep project variables together. Secret values stay hidden in everyday views.

PROJECT_NAMELaunch project
API_KEYSaved securely · Hidden
Read the variables guide
Project variables and hidden secret values stay separate from AI account credentials.
  1. Add or edit the variable, then save it.
  2. Review your changes before choosing Apply to noHumans. Saving and applying are separate actions.
  3. Expect running noHumans in this team to restart or have their work interrupted when you apply environment changes.

A per-noHuman value overrides the team value for that member. Keep secrets out of chat, shared documents and exported files. A masked value in the editor does not mean a tool cannot use it.

Rotate a credential

For an AI account, update or reconnect it in App settings → AI accounts, check its status, and test a small request. For a team integration secret, update it under Integrations and apply it after reviewing the interruption notice.

Revoke the old key in your provider's own dashboard after confirming the replacement works. Avoid deleting a working connection before you have the new credential.

Storage and access

Connected AI accounts are stored on this computer with owner-only file permissions and can be reused across teams. Each team runs its own local gateway.

For normal gateway-managed Claude and ChatGPT connections, noHumans use that team's stand-in credential. The gateway adds real authentication only when contacting allowed provider hosts. Prompts and selected content still go to the provider.

Native command-line sign-ins and fallback paths can store real credentials in worker files. Workers use your operating-system permissions; separate folders do not provide a filesystem sandbox. Keep secrets out of chats and shared files, since gateway authentication does not remove them.

A phone paired with the desktop does not receive AI-provider credentials. Team integration variables have their own scope and may be available to the tools you enable. Use the privacy policy to review external services, and Troubleshooting if a connection fails.