Complete your first EAI setup

Use this page after signup and the Getting Started prompt have run. Signup creates your workspace and admin access; this checklist confirms your computer is ready to use that workspace for real EAI work.

What signup already prepared

• Your EAI workspace was created from the plan and details you chose.
• You were added as the workspace admin.
• Your region, starter settings, storage, and baseline resources were prepared automatically.
• Your workspace admin area is ready at /platform without a separate CLI provisioning step.

Step 1: Confirm the basics are ready

• Your chosen app account is signed in and working.
• The app you chose is installed or already open.
• Git, Node.js, npm, and EAI CLI were installed or confirmed.
• You can run version checks without errors.

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

Step 2: Sign in to EAI

If the app did not complete sign-in for you, do it now. Use the same account you used during signup.

eai login
eai whoami

Step 3: Choose the right tenant if needed

Some users only have one workspace. Others can access more than one. If you can see multiple workspaces, select the one you just created before you create or edit your first project.

eai tenant list --format json
eai tenant select <tenant-slug>
eai whoami

Step 4: Create your first project

Before the app runs `eai init`, confirm that the current folder is the right place for the project, choose the project name you want, and make sure the active tenant is the workspace you intend to use. This setup path expects Gofer files to arrive as part of `eai init`, so you do not need a separate Gofer extension install.

eai whoami
eai tenant list --format json
eai tenant select <tenant-slug>   # only if needed
eai init <your-project-name> --skip-prompts --tenant <active-tenant-id>

• A new project folder appears.
• The project name was confirmed instead of assumed.
• The active tenant was checked before the project was created.
• The folder contains the EAI and Gofer starter files.
• Your chosen app can open the folder and work inside it.

Step 5: Check AI workflow readiness

If your vertical uses AI chat or workflow-backed automation, check the public workflow key before you rely on it. A status of `available` means the runtime workflow is ready. A status of `operator_required` means the platform team must bind the workflow before chat calls will work.

eai workflow readiness <workflow-key>
eai workflow status <workflow-key>
eai workflow request <workflow-key> --reason "First app setup"

These commands use the public platform API and intentionally avoid showing private platform internals. They give you the next action without asking you to guess from failed chat requests.

Step 6: Start your first guided session

Once the project exists, open that folder in your chosen app and start the first Gofer stage.

/0_business_scenario

Describe the business problem, who it is for, and what outcome matters most. Keep the explanation simple and concrete.

If you already had the tools installed

• It is fine to skip the install step on the Getting Started page.
• You still need to confirm the versions and sign in successfully.
• If `eai init` did not create the expected files, rerun the setup with the app or open the tooling page linked below.
• Do not use CLI provisioning to finish normal signup. Those commands are for development, operator, recovery, or backfill workflows.