Deploy to Castari

Workflow

Step 1: Check if the Castari CLI is installed

cast --version

npm install -g @castari/cli

cast --version

Step 2: Check authentication

cast whoami

cast login

cast whoami

Step 3: Check for castari.json

castari.json

ls castari.json

1. Detect the likely entrypoint by checking for these files in order:

   • src/index.ts

   • src/main.ts

   • index.ts

   • src/index.js

   • src/main.js

   • index.js

2. Ask the user for the agent name using AskUserQuestion. Suggest the current directory name as the default.
3. Generate

   castari.json

   with this structure:

{
  "name": "<agent-name>",
  "version": "0.1.0",
  "entrypoint": "<detected-entrypoint>",
  "runtime": "node"
}

Step 4: Deploy

cast deploy

Step 5: Verify deployment

• Agent name/slug
• Deployment status
• Sandbox ID (if returned)

Step 6: Offer to test

cast invoke <agent-slug> "<test-prompt>"

Error Handling

• npm not found: Ask the user to install Node.js (>= 18) first.
• Authentication failure: Suggest running

  cast login

  again or checking network connectivity.
• No entrypoint detected: Ask the user to specify their entrypoint file manually.
• Deploy failure: Show the full error output and suggest checking

  castari.json

  configuration or running

  cast agents list

  to verify the agent exists.

Notes

• The CLI requires Node.js >= 18.
• Authentication uses Clerk OAuth (browser-based).
• Deployments run in isolated cloud sandboxes.
• The

  castari.json

  file is the project manifest — it must be in the repo root.
• Common entrypoints:

  src/index.ts

  for TypeScript projects,

  index.js

  for JavaScript.