CLI Problems

Overview

The Asiyst CLI (asiyst) interacts with the Asiyst Cloud Gateway to validate integrations, sync knowledge sources, and deploy assistant settings.

Command Not Found: asiyst

Symptom

bash: asiyst: command not found

Resolution

1. Ensure npm global bin directory is in your PATH:

      export PATH="$(npm config get prefix)/bin:$PATH"

1. Or invoke via npx without global install:

      npx @asiyst/cli status
   
      npx @asiyst/cli sync

Authentication & Session Expiry

Symptom: HTTP 401 Unauthorized during CLI commands

1. Re-authenticate via the browser OAuth flow:

      asiyst login

1. If working in a headless environment (e.g., Docker container, remote SSH), pass your API token directly:

      export ASIYST_API_TOKEN="sk_live_your_management_token"
   
      asiyst status

Validation & Schema Errors

Symptom: asiyst validate fails with invalid configuration

Run with verbose output to pinpoint the exact schema discrepancy:

asiyst validate --verbose

Common causes:

• asiyst.config.json has invalid JSON syntax or unmatched quotes.

• The specified projectId does not exist in the active organization.

• Specified model names in the config do not match supported providers.

Automated CI/CD Pipeline Failures

In GitHub Actions, ensure you provide both the project ID and secret API token:

- name: Verify Asiyst Config
  run: npx @asiyst/cli validate --project ${{ secrets.ASIYST_PROJECT_ID }}
  env:
    ASIYST_API_TOKEN: ${{ secrets.ASIYST_API_TOKEN }}