Set up the organization, trusted device, system agent model, worker API key, and worker connection for a Nenjo workspace.

Onboarding prepares your browser and organization for a usable Nenjo workspace. It is not just a checklist of settings; it establishes the trust boundary that lets Nenjo protect encrypted content and safely connect a worker.

Open the login page to start onboarding.

When onboarding opens, Nenjo first checks your account state. If this account already belongs to a secured workspace, the page switches into restore mode so the current browser can be approved or restored with a recovery phrase. If this is a fresh workspace, the five-step onboarding flow begins.

1. Create Org

The first step names the organization that will own shared resources and worker access.

In the product, this step updates the current organization name. That organization becomes the shared boundary for agents, routines, projects, workers, API keys, trusted devices, and encrypted organization content.

2. Secure

The Secure step makes the current browser a trusted device for your workspace. This lets Nenjo protect encrypted workspace content while still allowing this browser to work with it.

Nenjo also creates a recovery phrase during this step. You must copy it, confirm that you backed it up, and type two requested words from the phrase before continuing.

The recovery phrase is the way back into encrypted workspace content if you use a new browser or lose access to trusted devices. Store it somewhere safe and do not paste it into chat, project context, or Library documents.

3. Create Agent

The Create Agent step chooses the provider and model that will power the default system agent.

You select:

Provider
Model name
Agent/model display name
Temperature

Behind the scenes, Nenjo creates a model record and assigns it to the system agent. This is what gives Nenji a model to use when you first enter chat.

You can skip this step and continue to the dashboard, but Nenji will not be fully ready until a usable model is configured.

4. API Key

The API Key step automatically creates a Worker Key for connecting the local worker to the platform.

The raw key is shown once. You must copy it before continuing. After you continue, the raw key is cleared from the page state and session storage.

This key is used by the worker command in the next step. It is not a manual scope-selection step in the onboarding UI.

5. Connect

The Connect step gives you a command snippet for installing the Nenjo CLI, setting provider credentials, setting the generated NENJO_API_KEY, and starting the worker:

curl -fsSL https://nenjo.ai/install | bash

export PROVIDER_API_KEY=your-key-here
export NENJO_API_KEY=nen_sk_************

nenjo run

The provider environment variable depends on the model provider you selected in the Create Agent step, such as ANTHROPIC_API_KEY, OPENAI_API_KEY, or GOOGLE_API_KEY.

While the worker connects, the page polls for worker enrollment. If the worker needs approval, the trusted browser signs the worker enrollment and wraps the account and organization content keys for the worker. Once the worker is connected, onboarding can open your first Nenji chat.

You can skip worker connection and enter chat, but Nenji will only be able to run worker-backed tasks after a worker is connected.

Restore Mode

If your account already has an existing secured workspace and this browser does not have local trusted-device access, onboarding switches into restore mode.

Restore mode lets you:

Approve this browser from another trusted device
Restore this browser with the saved recovery phrase
Start a new organization if trusted devices and recovery material are unavailable

This protects encrypted workspace content while still giving you a recovery path for a new browser.

Next Step

Once onboarding is complete, use Bootstrap to prompt Nenji for your first project, agents, routines, and Library knowledge.

Onboarding