Skip to main content
Support
LoginGet Started
EnterpriseAI

Quick Links

  • Home
  • DAISY Assist
  • DAISY Assess
  • Blog

Contact

  • Level 12, 50 Carrington St
  • Sydney, NSW 2000
  • Australia

Business numbers

  • ABN: 71677246409
  • ACN: 677246409
  • DUNS: 893114053

Legal

  • Terms of Use
  • Privacy Policy
  • Scam Warning

© 2026 by Enterprise AI Pty Ltd

EAI CLI

Documentation

EAI Platform

  • EAI Platform Docs

Getting Started

  • What EnterpriseAI Is
  • Complete Your First EAI Setup
  • EAI Platform - Run
  • EAI Platform - Manage
  • Getting Started

Builders

  • What the Setup Prompt Installs
  • EAI Gofer
  • Start Your First EAI Session
  • EAI CLI

EAI CLI

Simple commands that connect your app to the EAI backend with Enterprise governance, ready to run.

Setup, environment, and type commands

eai init [name]

Create an EAI-ready app project from the approved starting template, including the standard structure, configuration hooks, and EAI Gofer files the team uses to shape the work.

eai dev

Start the app locally so the team can build and test changes, while keeping the same platform assumptions the app will rely on later.

eai login

Sign in so commands run against the right EAI account, making sure workspace, tenant, and platform access are tied to the correct person.

eai logout

Sign out and clear saved access from the machine, which is useful when switching accounts or finishing work on a shared device.

eai whoami

Show which user, workspace, tenant, and profile are currently active, so the team can confirm commands will affect the right environment.

eai update

Check for CLI updates and move to the latest approved version, keeping builders on the current platform tooling without rewriting their app.

eai env pull

Bring platform settings into the local app, so it has the right URLs, IDs, and workspace configuration to connect cleanly.

eai env list

Show the environment settings available to the project, helping builders understand what configuration the app is currently using.

eai env push

Send approved local environment settings back to the platform, keeping shared configuration aligned when a team intentionally changes it.

eai types validate

Check local data definitions before they are published, catching mistakes in the business data model before they affect the platform.

eai types seed

Publish approved data definitions to the platform, making the app resource model available for APIs, forms, workflows, and AI features.

eai types diff

Compare local data definitions with what is already published, so teams can review model changes before they are applied.

eai types pull

Download published data definitions into the project, helping a builder start from the latest approved platform model instead of stale local files.

eai types define

Start the guided path for defining the app data model, turning the business objects the app needs into platform-ready resource definitions.

Resource and file commands

eai resources schema

Show the business data model for the active workspace, giving builders a clear view of the resources the app can read, write, and connect to.

eai resources sync-schema

Refresh local schema information from the platform, keeping the app aligned with the latest approved resource definitions.

eai resources list <type>

List business records for one resource type, helping teams inspect the real data the app will display or act on.

eai resources get <type> <id>

Open one business record by type and ID, useful when checking a specific customer, case, document, or workflow item.

eai resources create <type>

Create a business record from approved input, so test data or operational records can be added through the same resource layer the app uses.

eai resources update <type> <id>

Update an existing business record safely, using the platform resource model instead of changing data through a one-off script.

eai resources delete <type> <id>

Delete a business record when authorised, making removal explicit and tied to the same access controls as the rest of the app.

eai resources query

Find records using filters across the resource layer, which helps teams check whether the app can retrieve the right business information.

eai resources search <query>

Search business records with a simple query, making it easier to explore data without knowing every technical field name.

eai resources aggregate <type>

Summarise records for reporting or checks, giving the team quick counts and grouped views without building a dashboard first.

eai resources batch-create <type>

Create many records in one controlled operation, useful for loading sample data, onboarding records, or prepared business content.

eai resources batch-update <type>

Update many records in one controlled operation, helping teams apply approved changes consistently across a set of business records.

eai resources batch-delete <type>

Delete many records in one controlled operation, with the action kept visible and governed instead of hidden in manual cleanup.

eai resources storage status

Check storage health for resource data, confirming the backing storage is available before teams rely on it for app workflows.

eai resources storage doctor

Diagnose storage setup issues for resources, giving builders a clearer path to fix data access or file-storage problems.

eai resources file upload <type> <id> <property> <path>

Attach a file to a business record, so documents, evidence, images, or supporting files sit with the resource they belong to.

eai resources file get <type> <id> <property>

Download or inspect a file attached to a business record, helping the team confirm the right document is connected to the right item.

eai resources file delete <type> <id> <property>

Remove a file attached to a business record, keeping document cleanup tied to the resource model and permissions.

eai resources doctor

Diagnose resource API and schema issues, helping builders understand why data is not appearing or behaving as expected.

Tenant, vertical, and user commands

eai tenant list

List the company workspaces available to the signed-in user, so the team can see which customers, departments, or environments they can work with.

eai tenant select [tenant]

Choose the company workspace the CLI should use, making sure later commands affect the intended tenant and not another customer or test area.

eai tenant info <id>

Show details for one company workspace, including the information needed to confirm it is the correct tenant before making changes.

eai tenant create

Create a company workspace and make sure it can be used, giving a new customer, department, or child organisation a governed place to run apps.

eai tenant delete <id>

Delete a company workspace when authorised, keeping high-impact tenant cleanup explicit and restricted to the right users.

eai tenant storage list

List storage configurations for a company workspace, showing where that tenant stores resource data and supporting files.

eai tenant storage verify

Check that workspace storage is ready to use, so teams know data and file operations will work before a product goes live.

eai vertical list

List vertical app instances for the active workspace, helping teams see which apps or product areas already exist for that tenant.

eai vertical create <name>

Create a vertical app instance in the workspace, giving a new product or business process its own platform-backed app context.

eai vertical select <key>

Choose which vertical app instance to work on, so later commands connect to the right app rather than another product in the workspace.

eai vertical provision <key>

Prepare platform pieces for a vertical app instance, wiring the app to the services and configuration it needs to run.

eai provision entra

Create or confirm the sign-in registration for the app, so users can access it through the approved identity setup.

eai provision entra --rotate-secret

Rotate the sign-in secret and update the app settings, helping teams refresh credentials without manually rewiring the app.

eai provision storage

Prepare storage needed by the app, making sure resource data and files have a platform-managed place to live.

eai user invite --email <email>

Invite a user into the active workspace, giving the right person access to the tenant without changing permissions by hand.

eai user provision-me

Set up the signed-in user for the active workspace, useful during first-time setup when your own account needs tenant access.

AI, verification, and release commands

eai workflow readiness [keys...]

Check workspace access and workflow readiness together, showing whether the AI or automation paths the app needs are ready to use.

eai workflow status <key>

Show whether an AI workflow is connected and ready, so teams can see if a specific capability is live, blocked, or waiting for setup.

eai workflow request <key>

Request help for a workflow that is not ready yet, creating a clear handoff when an operator or platform admin needs to unblock it.

eai chat send <message>

Send one message through the connected AI workflow, useful for testing whether an assistant or RAG flow answers as expected.

eai chat stream <message>

Stream an AI response as it is generated, making it easier to test conversational experiences that respond in real time.

eai docs upload <file>

Upload a document for AI or document workflows, placing the file into the platform path used for classification, validation, or search.

eai docs classify <file>

Classify a document through the platform, helping teams check whether the AI understands the document type and business context.

eai docs index <documentId>

Index a document so AI search and chat can use it, making uploaded content available to RAG and knowledge workflows.

eai verify

Run platform connectivity and readiness checks, giving builders a quick view of whether the app can reach the services it depends on.

eai verify storage

Check storage connectivity and configuration, confirming the app can use the data and file stores behind the tenant.

eai verify calls

Audit CLI platform API calls and contracts, helping teams spot mismatches between the CLI, the app, and the backend APIs.

eai doctor

Run broader diagnostics with suggested fixes, giving builders a practical checklist when setup or platform connectivity is not working.

eai deploy setup

Prepare deployment workflow files and settings, so the app has the release path it needs before anyone tries to ship it.

eai deploy trigger

Start the deployment workflow, moving an approved app build into the release process without leaving the CLI.

eai deploy status

Check deployment progress and result, so the team can see whether a release is still running, has passed, or needs attention.

eai gofer refresh

Refresh Gofer-managed project files safely, updating the guided process assets while protecting the team’s existing work.

eai template check

Check whether the app has drifted from the approved template, giving the team a clear view of differences before they decide what to update.

←
Previous
Start Your First EAI Session