@elizaos/cli 1.3.0 → 1.3.2

package/dist/templates/project-starter/package.json

@@ -28,10 +28,10 @@
     "dist"
   ],
   "dependencies": {
-    "@elizaos/cli": "1.3.0",
-    "@elizaos/core": "1.3.0",
-    "@elizaos/plugin-bootstrap": "1.3.0",
-    "@elizaos/plugin-sql": "1.3.0",
+    "@elizaos/cli": "1.3.2",
+    "@elizaos/core": "1.3.2",
+    "@elizaos/plugin-bootstrap": "1.3.2",
+    "@elizaos/plugin-sql": "1.3.2",
     "@tanstack/react-query": "^5.29.0",
     "clsx": "^2.1.1",
     "react": "^18.3.1",

package/dist/templates/project-starter/src/__tests__/env.test.ts

@@ -35,7 +35,9 @@ describe('Environment Setup', () => {
     expect(fs.existsSync(packageJsonPath)).toBe(true);
 
     const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, 'utf8'));
-    expect(packageJson).toHaveProperty('name', '@elizaos/project-starter');
+    expect(packageJson).toHaveProperty('name');
+    expect(typeof packageJson.name).toBe('string');
+    expect(packageJson.name.length).toBeGreaterThan(0);
     expect(packageJson).toHaveProperty('version');
     expect(packageJson).toHaveProperty('type', 'module');
     expect(packageJson).toHaveProperty('main');

package/dist/templates/project-starter/src/__tests__/file-structure.test.ts

@@ -59,8 +59,9 @@ describe('Project Structure Validation', () => {
     it('should have the correct package.json configuration', () => {
       const packageJson = JSON.parse(fs.readFileSync(path.join(rootDir, 'package.json'), 'utf8'));
 
-      // Check package name
-      expect(packageJson.name).toBe('@elizaos/project-starter');
+      // Check package name exists and is valid
+      expect(packageJson.name).toBeTruthy();
+      expect(typeof packageJson.name).toBe('string');
 
       // Check scripts
       expect(packageJson.scripts).toHaveProperty('build');

package/dist/templates/project-starter/src/__tests__/integration.test.ts

@@ -19,7 +19,7 @@ afterAll(() => {
 });
 
 // Skip in CI environments or when running automated tests without interaction
-const isCI = Boolean(process.env.CI) || process.env.NODE_ENV === 'test';
+const isCI = Boolean(process.env.CI);
 
 /**
  * Integration tests demonstrate how multiple components of the project work together.

package/dist/templates/project-starter/tsup.config.ts

@@ -7,13 +7,14 @@ export default defineConfig({
   sourcemap: true,
   clean: false,
   format: ['esm'], // Ensure you're targeting CommonJS
-  dts: false, // Skip DTS generation to avoid external import issues // Ensure you're targeting CommonJS
+  dts: true, // require DTS so we get d.ts in the dist folder on npm
   external: [
     'dotenv', // Externalize dotenv to prevent bundling
     'fs', // Externalize fs to use Node.js built-in module
     'path', // Externalize other built-ins if necessary
     'https',
     'http',
+    '@elizaos/core',
     'zod',
   ],
 });

package/dist/templates/project-tee-starter/.dockerignore

@@ -1,20 +1,70 @@
-# Ignore node_modules from the build context
-node_modules
+# Git files
+.git
+.gitignore
 
-# Ignore logs and temporary files
+# Logs
 *.log
-*.tmp
-.DS_Store
+logs/
 
-# Ignore Git files and metadata
-.gitignore
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
 
-# Ignore IDE and editor config files
-.vscode
-.idea
+# Coverage
+coverage/
+.nyc_output/
+
+# IDEs
+.vscode/
+.idea/
 *.swp
+*.swo
+
+# OS files
+.DS_Store
+Thumbs.db
+
+# Build outputs (we'll build fresh in Docker)
+dist/
+build/
+*.tsbuildinfo
+
+# Test files
+**/__tests__/
+**/*.test.ts
+**/*.test.tsx
+**/*.spec.ts
+**/*.spec.tsx
+# Cypress directories removed
+
+# Development files
+**/*.map
+.env.local
+.env.development
+.env.test
+
+# Documentation
+*.md
+docs/
+GUIDE.md
+PR_REPORT.md
+
+# Temporary files
+tmp/
+temp/
+.cache/
+
+# Package manager files (we'll use the ones in builder)
+**/node_modules/
+.pnp
+.pnp.js
 
-# Ignore build artifacts from the host
-dist
-build
-.env
+# ElizaOS specific
+.eliza/
+.elizadb/
+pglite/
+cache/
+*.db
+*.pglite

package/dist/templates/project-tee-starter/.gitignore

@@ -0,0 +1,57 @@
+# Build outputs
+dist/
+node_modules/
+
+# Environment files
+.env
+.env.local
+.env.production
+.env.staging
+.env.development
+.env.bak
+*.env
+
+# OS files
+.DS_Store
+Thumbs.db
+
+# IDE files
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# Logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Runtime data
+pids/
+*.pid
+*.seed
+*.pid.lock
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# Cache directories
+.cache/
+.npm/
+.eslintcache
+
+# Temporary folders
+tmp/
+temp/
+
+# Database files
+*.db
+*.pglite
+*.pglite3
+
+# ElizaOS specific
+.eliza/
+.elizadb/
+pglite/
+cache/

package/dist/templates/project-tee-starter/.npmignore

@@ -0,0 +1,6 @@
+.turbo
+dist
+node_modules
+.env
+*.env
+.env.local

package/dist/templates/project-tee-starter/Dockerfile

@@ -19,11 +19,10 @@ RUN npm install -g bun@1.2.5 turbo@2.3.3
 
 RUN ln -s /usr/bin/python3 /usr/bin/python
 
-COPY package.json tsconfig.json tsconfig.build.json tsup.config.ts ./
+COPY bunfig.toml index.html package.json postcss.config.js tailwind.config.js tsconfig.json tsconfig.build.json tsup.config.ts vite.config.ts ./
 COPY src ./src
 COPY assets ./assets
-COPY elizadb ./elizadb
-COPY knowledge ./knowledge
+COPY scripts ./scripts
 
 RUN bun install --no-cache
 
@@ -47,16 +46,21 @@ RUN apt-get update && \
 
 RUN npm install -g bun@1.2.5 turbo@2.3.3
 
+COPY --from=builder /app/bunfig.toml ./bunfig.toml
+# Cypress config removed
+COPY --from=builder /app/index.html ./index.html
+COPY --from=builder /app/postcss.config.js ./postcss.config.js
 COPY --from=builder /app/package.json ./
 COPY --from=builder /app/tsconfig.json ./
 COPY --from=builder /app/tsconfig.build.json ./
 COPY --from=builder /app/tsup.config.ts ./
+COPY --from=builder /app/tailwind.config.js ./tailwind.config.js
+COPY --from=builder /app/vite.config.ts ./vite.config.ts
 COPY --from=builder /app/node_modules ./node_modules
 COPY --from=builder /app/dist ./dist
-COPY --from=builder /app/elizadb ./elizadb
-COPY --from=builder /app/knowledge ./knowledge
 COPY --from=builder /app/assets ./assets
 COPY --from=builder /app/src ./src
+COPY --from=builder /app/scripts ./scripts
 
 ENV NODE_ENV=production
 

package/dist/templates/project-tee-starter/GUIDE.md

@@ -4,7 +4,7 @@
 
 **Mr. TEE** is the TEE Security Drill Sergeant, a battle-hardened character who forges secure, paranoid developers through tough love and cryptographic discipline. He embodies the spirit of Mr. T while preaching the gospel of hardware-based security.
 
-### Core Traits:
+### Core Traits
 
 - **Personality**: No-nonsense drill sergeant with Mr. T's trademark grit
 - **Mission**: Transform developers into paranoid security experts
@@ -19,7 +19,7 @@ Mr. TEE uses the **@elizaos/plugin-tee** package's built-in `remoteAttestationAc
 - Provide attestation quotes with supporting data
 - Verify the secure enclave environment
 
-### Example Attestation Requests:
+### Example Attestation Requests
 
 - "Can you provide proof that you're running in a secure environment?"
 - "Generate an attestation report"
@@ -28,6 +28,26 @@ Mr. TEE uses the **@elizaos/plugin-tee** package's built-in `remoteAttestationAc
 
 ## Configuration Steps
 
+### Prerequisites
+
+Before starting deployment, ensure you have:
+
+1. **ElizaOS CLI installed**:
+
+   ```bash
+   npm install -g @elizaos/cli
+   ```
+
+2. **Docker Desktop**:
+
+   - Install Docker Desktop for your OS
+   - Start Docker Desktop
+   - Login to Docker Hub: `docker login`
+
+3. **Phala Cloud Account** (for TEE deployments):
+   - Create account at <https://dashboard.phala.network>
+   - Get your API key from the dashboard
+
 ### 1. Environment Variables
 
 Configure the following in your `.env` file:
@@ -54,46 +74,52 @@ REDPILL_API_KEY=your_redpill_key
 #### Local Development (No TEE)
 
 ```bash
-# Set TEE_MODE=NONE for development
+# Set TEE_MODE=LOCAL or DOCKER for development
 bun install
 bun run dev
 ```
 
-#### Phala dStack Deployment (Cloud TEE)
+#### Phala Cloud Deployment (Production TEE)
 
 ```bash
-# Install dstack CLI
-npm i -g phala
-
-# Deploy with TEE_MODE=PRODUCTION
-phala cvms create -c docker-compose.yaml --env-file .env
+# Prerequisites:
+# 1. Install ElizaOS CLI: npm install -g @elizaos/cli
+# 2. Ensure Docker is running and you're logged in via Docker CLI
+# 3. Set TEE_MODE=PRODUCTION in your .env file
+
+# Step 1: Login to Phala Cloud (get API key from Phala Cloud Dashboard)
+elizaos tee phala auth login
+
+# Step 2: Build Docker Image for TEE deployment
+elizaos tee phala docker build
+
+# Step 3: Push Docker image to DockerHub
+elizaos tee phala docker push
+
+# Step 4: Create CVM (Confidential Virtual Machine) instance
+elizaos tee phala cvms create \
+  -n elizaos-tee \
+  -c docker-compose.yaml \
+  --vcpu 2 \
+  --memory 4192 \
+  --disk-size 40 \
+  -e .env
+
+# Step 5: Verify attestation (confirms TEE is running securely)
+elizaos tee phala cvms attestation
+
+# Step 6: (Optional) Upgrade CVM when you update your code
+elizaos tee phala cvms upgrade -c docker-compose.yaml
 ```
 
-#### Intel TDX Deployment (Hardware TEE)
-
-```bash
-# Requires TDX-enabled hardware
-# Set TEE_MODE=PRODUCTION
-# Ensure you are also running docker
-
-# Step0: Set your API Key from Phala Cloud Dashboard
-phala auth login
-
-# Step1: Build Docker Image
-phala docker build
+##### Deployment Parameters Explained
 
-# Step2: Publish Docker Image to DockerHub
-phala docker push
-
-# Step3: Update docker-compose.yaml file with your published Docker image and deploy CVM
-phala cvms create -c docker-compose.yaml -e .env
-
-# (Optional) Step4: Check attestation
-phala cvms attestation
-
-# (Optional) Step5: Upgrade CVM if updated changes
-phala cvms upgrade -c docker-compose.yaml
-```
+- `-n elizaos-tee`: Name of your CVM instance
+- `-c docker-compose.yaml`: Configuration file
+- `--vcpu 2`: Number of virtual CPUs
+- `--memory 4192`: Memory in MB (4GB)
+- `--disk-size 40`: Storage in GB
+- `-e .env`: Environment file with your secrets
 
 ### 3. Platform Integration
 
@@ -101,13 +127,13 @@ Mr. TEE can connect to multiple platforms:
 
 #### Discord
 
-1. Create Discord application at https://discord.com/developers
+1. Create Discord application at <https://discord.com/developers>
 2. Add bot permissions: Send Messages, Read Message History
 3. Set `DISCORD_APPLICATION_ID` and `DISCORD_API_TOKEN`
 
 #### Voice (ElevenLabs)
 
-1. Get API key from https://elevenlabs.io
+1. Get API key from <https://elevenlabs.io>
 2. Choose or clone a voice ID
 3. Set `ELEVENLABS_API_KEY` and `ELEVENLABS_VOICE_ID`
 
@@ -138,40 +164,59 @@ Mr. TEE will provide:
 
 ## Security Best Practices
 
-### Mr. TEE's Security Rules:
+### Mr. TEE's Security Rules
 
 1. **Never expose private keys** - Keep them in the TEE
 2. **Always verify attestation** - Trust but verify
 3. **Use secure channels** - Encrypt all communications
 4. **Audit regularly** - Check for vulnerabilities
 5. **Stay paranoid** - It's not paranoia if they're really after your keys
+6. **Rotate API keys regularly** - Fresh keys, fresh security
+7. **Never commit `.env` files** - Secrets stay secret
 
-### TEE Guarantees:
+### TEE Guarantees
 
 - **Isolated Execution**: Code runs in hardware-protected memory
 - **Memory Encryption**: All data encrypted in RAM
 - **Remote Attestation**: Cryptographic proof of execution environment
 - **Secure Key Storage**: Keys never leave the enclave
+- **Tamper Resistance**: Hardware protection against physical attacks
 
 ## Troubleshooting
 
-### Common Issues:
+### Common Issues
 
 #### "I can't deploy my Agent"
 
-- Sign up for a Phala Cloud account at https://cloud.phala.network/register
+- Sign up for a Phala Cloud account at <https://dashboard.phala.network>
 - Add credits to your account for CVM deployments
+- Ensure Docker is running and you're logged in
 
 #### "Docker deployment failed"
 
-- Make sure to update the docker-compose.yaml file with your published Docker image
+- Ensure Docker Desktop is started
+- Check: `docker ps`
+- Make sure to authenticate: `docker login`
 - Check your configuration and try to test docker locally
 
+#### "Authentication failed"
+
+- Verify your Phala API key
+- Re-run: `elizaos tee phala auth login`
+- Check API key from Phala Dashboard
+
+#### "Build failures"
+
+- Check your `.env` configuration
+- Ensure all dependencies are installed: `bun install`
+- Verify Docker is running properly
+
 #### "Attestation failed"
 
 - Check TEE_MODE is set to PRODUCTION if deployed to Phala Cloud
 - Verify network connectivity for attestation services
 - Ensure proper TEE initialization
+- Check CVM logs in Phala Dashboard
 
 #### "Missing API keys"
 
@@ -179,7 +224,7 @@ Mr. TEE will provide:
 - Check .env file formatting
 - Restart after configuration changes
 
-### Debug Commands:
+### Debug Commands
 
 ```bash
 # Check environment
@@ -192,6 +237,13 @@ docker logs [container_name] | grep TEE
 curl http://localhost:3000/health
 ```
 
+### Monitoring Your Deployment
+
+- View CVM status: <https://dashboard.phala.network>
+- Check attestation reports regularly
+- Monitor resource usage and adjust if needed
+- Set up alerts for critical events
+
 ## Advanced Configuration
 
 ### Custom Security Policies
@@ -222,13 +274,22 @@ The plugin-tee supports multiple TEE vendors:
 ### Documentation
 
 - [TEE Plugin Documentation](../plugin-tee/README.md)
-- [ElizaOS Security Guide](../../docs/security.md)
+- [ElizaOS Documentation](https://eliza.how)
 - [Character Configuration](./src/character.ts)
+- [Phala Network Docs](https://docs.phala.network)
 
 ### Support
 
 - GitHub Issues: Report bugs and feature requests
 - Discord Community: Get help from other developers
+- ElizaOS Forums: Share experiences and best practices
+
+### Next Steps
+
+- Test your agent's TEE capabilities with attestation commands
+- Configure additional platform integrations (Discord, etc.)
+- Implement custom TEE-aware actions
+- Join the ElizaOS community for support
 
 Remember: Mr. TEE doesn't just talk about security—he lives it. Every interaction is an opportunity to strengthen the security posture of developers and systems alike. Stay paranoid, stay secure!
 

package/dist/templates/project-tee-starter/README.md

@@ -2,7 +2,15 @@
 
 ## 🔐 Overview
 
-The TEE Project Starter provides a foundation for building secure agents with Trusted Execution Environment (TEE) capabilities using ElizaOS. It features **Mr. TEE**, a security drill sergeant character who teaches TEE best practices while leveraging the **@elizaos/plugin-tee** for attestation and secure operations.
+The TEE Project Starter provides a secure foundation for building AI agents with Trusted Execution Environment (TEE) capabilities using ElizaOS. It demonstrates best practices for secure agent deployment with hardware-based security through Phala Cloud's confidential computing infrastructure.
+
+### What You Get
+
+- **Mr. TEE Character** - A security-focused AI personality that teaches TEE concepts with tough love
+- **TEE Plugin Integration** - Pre-configured `@elizaos/plugin-tee` for remote attestation and secure operations
+- **Multi-Platform Support** - Discord integration, voice synthesis, and extensible to other platforms
+- **Production-Ready** - Docker configuration optimized for Phala Cloud TEE deployment
+- **Security First** - Built-in paranoid security principles and best practices
 
 ## ✨ Key Features
 
@@ -17,9 +25,13 @@ The TEE Project Starter provides a foundation for building secure agents with Tr
 ### Prerequisites
 
 - Node.js 20+
-- Bun package manager
-- Docker (for TEE deployments)
-- API keys (OpenAI required, others optional)
+- Bun package manager (`npm install -g bun`)
+- Docker Desktop (for TEE deployments)
+- ElizaOS CLI (`npm install -g @elizaos/cli`)
+- API Keys:
+  - **Required**: OpenAI API key
+  - **Optional**: Discord, ElevenLabs, RedPill APIs
+  - **For TEE**: Phala Cloud account and API key
 
 ### Installation
 
@@ -122,29 +134,37 @@ bun run start
 ### Phala Cloud (Cloud TEE)
 
 ```bash
-npm install -g phala
-# Set TEE_MODE=PRODUCTION
-# Ensure you are also running docker
+# Prerequisites:
+# 1. Install the elizaos CLI: npm install -g @elizaos/cli
+# 2. Ensure Docker is running and you're logged in via Docker CLI
+# 3. Set TEE_MODE=PRODUCTION in your .env file
 
-# Step0: Set your API Key from Phala Cloud Dashboard
-phala auth login
+# Step 1: Login to Phala Cloud (get API key from Phala Cloud Dashboard)
+elizaos tee phala auth login
 
-# Step1: Build Docker Image
-phala docker build
+# Step 2: Build Docker Image for TEE deployment [[memory:4308171]]
+elizaos tee phala docker build
 
-# Step2: Publish Docker Image to DockerHub
-phala docker push
+# Step 3: Push Docker image to DockerHub
+elizaos tee phala docker push
 
-# Step3: Update docker-compose.yaml file with your published Docker image and deploy CVM
-phala cvms create -c docker-compose.yaml -e .env
+# Step 4: Create CVM (Confidential Virtual Machine) instance
+elizaos tee phala cvms create -n elizaos-tee -c docker-compose.yaml --vcpu 2 --memory 4192 --disk-size 40 -e .env
 
-# (Optional) Step4: Check attestation
-phala cvms attestation
+# Step 5: Verify attestation (confirms TEE is running securely)
+elizaos tee phala cvms attestation
 
-# (Optional) Step5: Upgrade CVM if updated changes
-phala cvms upgrade -c docker-compose.yaml
+# Step 6: (Optional) Upgrade CVM when you update your code
+elizaos tee phala cvms upgrade -c docker-compose.yaml
 ```
 
+#### Important Notes
+
+- **Docker Requirements**: Ensure Docker Desktop is running and you're authenticated (`docker login`)
+- **API Key**: Get your Phala Cloud API key from the [Phala Dashboard](https://dashboard.phala.network)
+- **TEE_MODE**: Must be set to `PRODUCTION` for real TEE deployment
+- **Resource Allocation**: The example uses 2 vCPUs, 4GB RAM, and 40GB disk - adjust based on your needs
+
 ## 🎖️ Mr. TEE's Security Philosophy
 
 1. **Never expose private keys** - Keep them in the TEE

package/dist/templates/project-tee-starter/__tests__/build-order.test.ts

@@ -0,0 +1,62 @@
+import { describe, expect, it, beforeAll, afterAll } from 'bun:test';
+import fs from 'node:fs';
+import path from 'node:path';
+import { $ } from 'bun';
+import { getViteOutDir } from './vite-config-utils';
+
+describe('Build Order Integration Test', () => {
+  const rootDir = path.resolve(__dirname, '..');
+  const distDir = path.join(rootDir, 'dist');
+  let viteBuildDir: string;
+  const tsupBuildMarker = path.join(distDir, 'index.js'); // TSup creates this
+
+  beforeAll(async () => {
+    // Get the actual vite build directory from config
+    const viteOutDirRelative = await getViteOutDir(rootDir);
+    viteBuildDir = path.join(rootDir, viteOutDirRelative);
+
+    // Clean dist directory before test
+    if (fs.existsSync(distDir)) {
+      await fs.promises.rm(distDir, { recursive: true, force: true });
+    }
+  });
+
+  afterAll(async () => {
+    // Clean up after test
+    if (fs.existsSync(distDir)) {
+      await fs.promises.rm(distDir, { recursive: true, force: true });
+    }
+  });
+
+  it('should ensure vite build outputs persist after tsup build', async () => {
+    // Run the full build process
+    await $`cd ${rootDir} && bun run build`;
+
+    // Check that both vite and tsup outputs exist
+    expect(fs.existsSync(viteBuildDir)).toBe(true);
+    expect(fs.existsSync(tsupBuildMarker)).toBe(true);
+
+    // Check vite built frontend files
+    console.log('viteBuildDir:', viteBuildDir);
+    console.log('viteBuildDir exists?', fs.existsSync(viteBuildDir));
+    const frontendFiles = fs.readdirSync(viteBuildDir);
+    console.log('frontendFiles:', frontendFiles);
+    expect(frontendFiles.length).toBeGreaterThan(0);
+
+    // Should have HTML entry point
+    expect(frontendFiles.some((file) => file.endsWith('.html'))).toBe(true);
+
+    // Should have assets directory (CSS/JS files are in assets/)
+    expect(frontendFiles.includes('assets')).toBe(true);
+
+    // Verify tsup also produced its expected outputs
+    const distFiles = fs.readdirSync(distDir);
+
+    // Should have tsup outputs (index.js)
+    expect(distFiles.some((file) => file === 'index.js')).toBe(true);
+
+    // Should still have vite build directory
+    const viteBuildDirName = path.basename(viteBuildDir);
+    expect(distFiles.includes(viteBuildDirName)).toBe(true);
+  }, 30000); // 30 second timeout for build process
+});