Finish your first EAI session

This page keeps the old route alive, but it now focuses on the first safe session rather than asking novice users to deploy immediately.

Step 1: Confirm who you are

eai whoami

Make sure the account shown is the one you intended to use for this workspace.

Step 2: Confirm or change the active tenant

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

Only move forward when the active workspace is the one created during signup. This prevents starting the first project in the wrong place.

Step 3: Create or reopen the first project

Before you run `eai init`, confirm that the current folder is the right place for the project, choose the project name you actually want, and make sure the active tenant is correct. Then run `eai init` non-interactively with the confirmed tenant.

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>

• If the project already exists, reopen it in your chosen app.
• If the project is new, check that the starter files and Gofer files are present.
• Do not let the app assume a project name or quietly use the wrong tenant.

Step 4: Confirm runtime workflow readiness

Verticals that include AI chat need a real runtime workflow binding. Shared workflow metadata is not enough by itself. Check the workflow key before you build user-facing chat or automation screens around it.

eai workflow readiness <workflow-key>
eai workflow status <workflow-key>
eai workflow request <workflow-key> --reason "First guided session"

Step 5: Start the first guided stage

/0_business_scenario

Describe the business problem clearly and simply. Explain what is slow, manual, or confusing today and what outcome you want instead.

When to think about deployment

Deployment is a later step. For a novice first session, the real finish line is a signed-in machine, the new workspace, a working project, and the first Gofer stage underway.