What the setup prompt installs

This page explains the tooling behind the Getting Started flow. The goal is to make the setup understandable without forcing novice users into a long manual install path.

Git

Git manages the project files. If Git is missing, the app-assisted setup should install it first. On native Windows, Claude Code also uses Git Bash when Git for Windows is installed.

Node.js and npm

Node.js runs the EAI CLI and npm installs it. The setup flow should use a stable current LTS release unless your environment already has a compatible version.

EnterpriseAI CLI

The EAI CLI is the command-line tool used to sign in, choose the right workspace, create a project, and interact with EnterpriseAI from your machine. It is not required to finish normal signup.

npm config set @eai-tools:registry https://eai-tools.github.io/eai/registry/ --location=user
npm install -g @eai-tools/cli

On Windows, avoid PowerShell `>>` redirection when editing `.npmrc` because it can write the file with the wrong encoding. npm global executables are linked into the active global prefix on Windows, so do not assume the command location is always `%AppData%\npm`.

npm config get prefix
npm prefix -g

Use those commands to confirm the active npm global prefix. The default is `%AppData%\npm`, but npm can be configured to use a different location. Whatever `npm prefix -g` returns is the exact directory that should be on the User PATH so `eai` and other npm-installed commands work.

After a User PATH or npm prefix change on Windows, close old terminals and open a new Command Prompt or PowerShell window before testing again. Microsoft documents that `setx` writes environment changes for future command windows only. If PowerShell blocks the script wrapper, verify `eai.cmd` or use CMD or Git Bash instead of weakening execution policy unless you explicitly approve that change.

If the shells still disagree about the roaming npm path or `eai` cannot be found even though PATH looks correct, a practical fallback is to move the npm global prefix to a simple stable path such as `C:\npm`, add that directory to the User PATH, reinstall the CLI, and verify again in fresh shells.

Gofer now arrives with eai init

For this onboarding path, users do not need a separate Gofer VSIX or extension install. The Gofer project files are expected to appear when `eai init` creates the project after the folder, project name, and active tenant are confirmed.

Public platform readiness checks

Use public EAI commands to check readiness before you build workflows into a vertical. These commands report whether the current tenant, plan, and runtime workflow binding are ready, need an upgrade, or need a platform operator.

eai doctor --check-updates
eai workflow readiness <workflow-key>
eai workflow status <workflow-key>
eai workflow request <workflow-key> --reason "Describe the app journey"
eai provision entra --rotate-secret

• `eai workflow readiness` checks tenant access, plan metadata, and optional workflow keys together.
• `eai workflow status` checks an executable runtime workflow binding for the active tenant.
• `eai workflow request` creates an operator-assisted request when a workflow is not bound yet.
• `eai provision entra --rotate-secret` rotates an existing app registration secret without creating a new app.
• If a command says an upgrade is required, use the account upgrade page rather than trying to bypass the plan limit.

Quick verification commands

git --version
node --version
npm --version
eai --version
eai whoami

What good looks like

• The machine can run Git, Node.js, npm, and EAI CLI without errors.
• The user can finish `eai login` successfully.
• The workspace created during signup can be selected when more than one workspace is available.
• A new project can be created with `eai init --skip-prompts` after the folder, project name, and active tenant are confirmed, and then opened in the chosen app.