update docker publish yml

.devcontainer/.bashrc

@@ -18,26 +18,14 @@ alias pgc="PGPASSWORD=postgres psql -h db -U postgres -d simstudio"
 alias check-db="PGPASSWORD=postgres psql -h db -U postgres -c '\l'"
 
 # Sim Studio specific aliases
-alias logs="cd /workspace/apps/sim && tail -f logs/*.log 2>/dev/null || echo 'No log files found'"
-alias sim-start="cd /workspace && bun run dev"
-alias sim-migrate="cd /workspace/apps/sim && bunx drizzle-kit push"
-alias sim-generate="cd /workspace/apps/sim && bunx drizzle-kit generate"
-alias sim-rebuild="cd /workspace && bun run build && bun run start"
-alias docs-dev="cd /workspace/apps/docs && bun run dev"
+alias logs="cd /workspace/sim && tail -f logs/*.log 2>/dev/null || echo 'No log files found'"
+alias sim-start="cd /workspace/sim && npm run dev"
+alias sim-migrate="cd /workspace/sim && npx drizzle-kit push"
+alias sim-generate="cd /workspace/sim && npx drizzle-kit generate"
+alias sim-rebuild="cd /workspace/sim && npm run build && npm start"
 
-# Turbo related commands
-alias turbo-build="cd /workspace && bunx turbo run build"
-alias turbo-dev="cd /workspace && bunx turbo run dev"
-alias turbo-test="cd /workspace && bunx turbo run test"
-
-# Bun specific commands
-alias bun-update="cd /workspace && bun update"
-alias bun-add="cd /workspace && bun add"
-alias bun-pm="cd /workspace && bun pm"
-alias bun-canary="bun upgrade --canary"
-
-# Default to workspace directory
-cd /workspace 2>/dev/null || true
+# Default to sim directory
+cd /workspace/sim 2>/dev/null || true
 
 # Welcome message - only show once per session
 if [ -z "$SIM_WELCOME_SHOWN" ]; then
@@ -48,22 +36,10 @@ if [ -z "$SIM_WELCOME_SHOWN" ]; then
   echo "🚀 Welcome to Sim Studio development environment!"
   echo ""
   echo "Available commands:"
-  echo "  sim-start    - Start all apps in development mode"
-  echo "  sim-migrate  - Push schema changes to the database for sim app"
-  echo "  sim-generate - Generate new migrations for sim app"
-  echo "  sim-rebuild  - Build and start all apps"
-  echo "  docs-dev     - Start only the docs app in development mode"
-  echo ""
-  echo "Turbo commands:"
-  echo "  turbo-build  - Build all apps using Turborepo"
-  echo "  turbo-dev    - Start development mode for all apps"
-  echo "  turbo-test   - Run tests for all packages"
-  echo ""
-  echo "Bun commands:"
-  echo "  bun-update   - Update dependencies"
-  echo "  bun-add      - Add a new dependency"
-  echo "  bun-pm       - Manage dependencies"
-  echo "  bun-canary   - Upgrade to the latest canary version of Bun"
+  echo "  sim-start    - Start the development server"
+  echo "  sim-migrate  - Push schema changes to the database"
+  echo "  sim-generate - Generate new migrations"
+  echo "  sim-rebuild  - Build and start the production server"
   echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
   echo ""
 fi 

.devcontainer/Dockerfile

@@ -1,19 +1,20 @@
-# Use the latest Bun canary image for development
-FROM oven/bun:canary
+FROM node:20-bullseye
 
 # Avoid warnings by switching to noninteractive
 ENV DEBIAN_FRONTEND=noninteractive
 
+# Set Node.js memory limit
+ENV NODE_OPTIONS="--max-old-space-size=4096"
+
 # Install necessary packages for development
 RUN apt-get update \
     && apt-get -y install --no-install-recommends \
-       git curl wget jq sudo postgresql-client vim nano \
-       bash-completion ca-certificates lsb-release gnupg \
+       git curl wget jq sudo postgresql-client \
     && apt-get clean -y \
     && rm -rf /var/lib/apt/lists/*
 
 # Create a non-root user
-ARG USERNAME=bun
+ARG USERNAME=node
 ARG USER_UID=1000
 ARG USER_GID=$USER_UID
 
@@ -21,15 +22,11 @@ ARG USER_GID=$USER_UID
 RUN echo "$USERNAME ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/$USERNAME \
     && chmod 0440 /etc/sudoers.d/$USERNAME
 
-# Install global packages for development
-RUN bun install -g turbo drizzle-kit typescript @types/node
+# Make sure we have the latest npm
+RUN npm install -g npm@latest
 
-# Install bun completions
-RUN bun completions > /etc/bash_completion.d/bun
-
-# Set up shell environment
-RUN echo "export PATH=$PATH:/home/$USERNAME/.bun/bin" >> /etc/profile
-RUN echo "source /etc/profile" >> /etc/bash.bashrc
+# Install global packages
+RUN npm install -g drizzle-kit
 
 # Switch back to dialog for any ad-hoc use of apt-get
 ENV DEBIAN_FRONTEND=dialog
@@ -37,6 +34,4 @@ ENV DEBIAN_FRONTEND=dialog
 WORKDIR /workspace
 
 # Expose the ports we're interested in
-EXPOSE 3000
-EXPOSE 3001
-EXPOSE 3002
+EXPOSE 3000

.devcontainer/README.md

@@ -33,7 +33,7 @@ This directory contains configuration files for Visual Studio Code Dev Container
    - Run database migrations
    - Configure helpful aliases
 
-5. Start the application with `sim-start` (alias for `bun run dev`)
+5. Start the application with `sim-start` (alias for `npm run dev`)
 
 ### Development Commands
 

.devcontainer/devcontainer.json

@@ -10,8 +10,14 @@
       "settings": {
         "editor.formatOnSave": true,
         "editor.codeActionsOnSave": {
-          "source.fixAll.biome": "explicit",
-          "source.organizeImports.biome": "explicit"
+          "source.fixAll.eslint": true
+        },
+        "editor.defaultFormatter": "esbenp.prettier-vscode",
+        "[typescript]": {
+          "editor.defaultFormatter": "esbenp.prettier-vscode"
+        },
+        "[typescriptreact]": {
+          "editor.defaultFormatter": "esbenp.prettier-vscode"
         },
         "terminal.integrated.defaultProfile.linux": "bash",
         "terminal.integrated.profiles.linux": {
@@ -23,15 +29,16 @@
         "terminal.integrated.shellIntegration.enabled": true
       },
       "extensions": [
-        "biomejs.biome",
+        "dbaeumer.vscode-eslint",
+        "esbenp.prettier-vscode",
         "bradlc.vscode-tailwindcss",
         "ms-vscode.vscode-typescript-next",
         "github.copilot",
         "github.copilot-chat",
+        "rvest.vs-code-prettier-eslint",
         "mikestead.dotenv",
         "dsznajder.es7-react-js-snippets",
-        "steoates.autoimport",
-        "oven.bun-vscode"
+        "steoates.autoimport"
       ]
     }
   },
@@ -42,11 +49,12 @@
 
   "postStartCommand": "bash -c 'if [ ! -f ~/.bashrc ] || ! grep -q \"sim-start\" ~/.bashrc; then cp .devcontainer/.bashrc ~/.bashrc; fi'",
 
-  "remoteUser": "bun",
+  "remoteUser": "node",
 
   "features": {
     "ghcr.io/devcontainers/features/git:1": {},
-    "ghcr.io/prulloac/devcontainer-features/bun:1": {
+    "ghcr.io/devcontainers-contrib/features/npm-package:1": {
+      "package": "typescript",
       "version": "latest"
     }
   }

.devcontainer/docker-compose.yml

@@ -1,3 +1,5 @@
+version: '3.8'
+
 services:
   app:
     build:
@@ -5,7 +7,6 @@ services:
       dockerfile: .devcontainer/Dockerfile
     volumes:
       - ..:/workspace:cached
-      - bun-cache:/home/bun/.bun/cache:delegated
     command: sleep infinity
     environment:
       - NODE_ENV=development
@@ -13,62 +14,15 @@ services:
       - POSTGRES_URL=postgresql://postgres:postgres@db:5432/simstudio
       - BETTER_AUTH_URL=http://localhost:3000
       - NEXT_PUBLIC_APP_URL=http://localhost:3000
-      - BUN_INSTALL_CACHE_DIR=/home/bun/.bun/cache
     depends_on:
       db:
         condition: service_healthy
-      realtime:
-        condition: service_healthy
-      migrations:
-        condition: service_completed_successfully
     ports:
       - "3000:3000"
-      - "3001:3001"
-    working_dir: /workspace
-    healthcheck:
-      test: ['CMD', 'wget', '--spider', '--quiet', 'http://127.0.0.1:3000']
-      interval: 90s
-      timeout: 5s
-      retries: 3
-      start_period: 10s
-
-  realtime:
-    build:
-      context: ..
-      dockerfile: .devcontainer/Dockerfile
-    command: sleep infinity
-    environment:
-      - NODE_ENV=development
-      - DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio
-      - BETTER_AUTH_URL=http://localhost:3000
-      - NEXT_PUBLIC_APP_URL=http://localhost:3000
-    depends_on:
-      db:
-        condition: service_healthy
-    ports:
-      - "3002:3002"
-    working_dir: /workspace
-    healthcheck:
-      test: ['CMD', 'wget', '--spider', '--quiet', 'http://127.0.0.1:3002']
-      interval: 90s
-      timeout: 5s
-      retries: 3
-      start_period: 10s
-
-  migrations:
-    build:
-      context: ..
-      dockerfile: docker/db.Dockerfile
-    environment:
-      - DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio
-    depends_on:
-      db:
-        condition: service_healthy
-    command: ['bun', 'run', 'db:migrate']
-    restart: 'no'
+    working_dir: /workspace/sim
 
   db:
-    image: pgvector/pgvector:pg17
+    image: postgres:16
     restart: unless-stopped
     volumes:
       - postgres-data:/var/lib/postgresql/data
@@ -85,5 +39,4 @@ services:
       retries: 5
 
 volumes:
-  postgres-data:
-  bun-cache:
+  postgres-data: 

.devcontainer/post-create.sh

@@ -5,8 +5,8 @@ set -e
 
 echo "🔧 Setting up Sim Studio development environment..."
 
-# Change to the workspace root directory
-cd /workspace
+# Change to the sim directory
+cd /workspace/sim
 
 # Setup .bashrc
 echo "📄 Setting up .bashrc with aliases..."
@@ -15,50 +15,27 @@ cp /workspace/.devcontainer/.bashrc ~/.bashrc
 echo 'if [ -f ~/.bashrc ]; then . ~/.bashrc; fi' >> ~/.profile
 
 # Clean and reinstall dependencies to ensure platform compatibility
-echo "📦 Cleaning and reinstalling dependencies..."
+echo "📦 Cleaning and reinstalling npm dependencies..."
 if [ -d "node_modules" ]; then
   echo "Removing existing node_modules to ensure platform compatibility..."
   rm -rf node_modules
-  rm -rf apps/sim/node_modules
-  rm -rf apps/docs/node_modules
 fi
 
-# Ensure Bun cache directory exists and has correct permissions
-mkdir -p ~/.bun/cache
-chmod 700 ~/.bun ~/.bun/cache
-
 # Install dependencies with platform-specific binaries
-echo "Installing dependencies with Bun..."
-bun install || {
-  echo "⚠️ bun install had issues but continuing setup..."
+npm install || {
+  echo "⚠️ npm install had issues but continuing setup..."
 }
 
-# Check for native dependencies
-echo "Checking for native dependencies compatibility..."
-NATIVE_DEPS=$(grep '"trustedDependencies"' apps/sim/package.json || echo "")
-if [ ! -z "$NATIVE_DEPS" ]; then
-  echo "⚠️ Native dependencies detected. Ensuring compatibility with Bun..."
-  for pkg in $(echo $NATIVE_DEPS | grep -oP '"[^"]*"' | tr -d '"' | grep -v "trustedDependencies"); do
-    echo "Checking compatibility for $pkg..."
-  done
-fi
-
-# Set up environment variables if .env doesn't exist for the sim app
-if [ ! -f "apps/sim/.env" ]; then
+# Set up environment variables if .env doesn't exist
+if [ ! -f ".env" ]; then
   echo "📄 Creating .env file from template..."
-  if [ -f "apps/sim/.env.example" ]; then
-    cp apps/sim/.env.example apps/sim/.env
-  else
-    echo "DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio" > apps/sim/.env
-  fi
+  cp .env.example .env 2>/dev/null || echo "DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio" > .env
 fi
 
 # Generate schema and run database migrations
 echo "🗃️ Running database schema generation and migrations..."
 echo "Generating schema..."
-cd apps/sim
-bunx drizzle-kit generate
-cd ../..
+npx drizzle-kit generate
 
 echo "Waiting for database to be ready..."
 # Try to connect to the database, but don't fail the script if it doesn't work
@@ -67,9 +44,7 @@ echo "Waiting for database to be ready..."
   while [ $timeout -gt 0 ]; do
     if PGPASSWORD=postgres psql -h db -U postgres -c '\q' 2>/dev/null; then
       echo "Database is ready!"
-      cd apps/sim
-      DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio bunx drizzle-kit push
-      cd ../..
+      DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio npx drizzle-kit push
       break
     fi
     echo "Database is unavailable - sleeping (${timeout}s remaining)"
@@ -86,14 +61,13 @@ echo "Waiting for database to be ready..."
 cat << EOF >> ~/.bashrc
 
 # Additional Sim Studio Development Aliases
-alias migrate="cd /workspace/apps/sim && DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio bunx drizzle-kit push"
-alias generate="cd /workspace/apps/sim && bunx drizzle-kit generate"
-alias dev="cd /workspace && bun run dev"
-alias build="cd /workspace && bun run build"
-alias start="cd /workspace && bun run dev"
-alias lint="cd /workspace/apps/sim && bun run lint"
-alias test="cd /workspace && bun run test"
-alias bun-update="cd /workspace && bun update"
+alias migrate="cd /workspace/sim && DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio npx drizzle-kit push"
+alias generate="cd /workspace/sim && npx drizzle-kit generate"
+alias dev="cd /workspace/sim && npm run dev"
+alias build="cd /workspace/sim && npm run build"
+alias start="cd /workspace/sim && npm run start"
+alias lint="cd /workspace/sim && npm run lint"
+alias test="cd /workspace/sim && npm run test"
 EOF
 
 # Source the .bashrc to make aliases available immediately

.dockerignore

@@ -1,11 +1,12 @@
-LICENSE
-NOTICE
-.prettierrc
-.prettierignore
-README.md
-.gitignore
-.husky
+# Exclude files from Docker build
+.git
 .github
-.devcontainer
-.env.example
-node_modules
+node_modules
+.next
+.vercel
+.husky
+.env
+.env.*
+npm-debug.log
+README.md
+.devcontainer 

.github/CODE_OF_CONDUCT.md

@@ -14,22 +14,22 @@ appearance, race, religion, or sexual identity and orientation.
 Examples of behaviour that contributes to a positive environment for our
 community include:
 
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologising to those affected by our mistakes,
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologising to those affected by our mistakes,
   and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the
+* Focusing on what is best not just for us as individuals, but for the
   overall community
 
 Examples of unacceptable behaviour include:
 
-- The use of sexualised language or imagery, and sexual attention or advances
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email
+* The use of sexualised language or imagery, and sexual attention or advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
   address, without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
+* Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Our Responsibilities
@@ -112,4 +112,4 @@ the community.
 This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org/), version
 [1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct/code_of_conduct.md) and
 [2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md),
-and was generated by [contributing.md](https://contributing.md/generator).
+and was generated by [contributing.md](https://contributing.md/generator).

.github/CONTRIBUTING.md

@@ -3,7 +3,7 @@
 Thank you for your interest in contributing to Sim Studio! Our goal is to provide developers with a powerful, user-friendly platform for building, testing, and optimizing agentic workflows. We welcome contributions in all forms—from bug fixes and design improvements to brand-new features.
 
 > **Project Overview:**  
-> Sim Studio is a monorepo using Turborepo, containing the main application (`apps/sim/`), documentation (`apps/docs/`), and shared packages (`packages/`). The main application is built with Next.js (app router), ReactFlow, Zustand, Shadcn, and Tailwind CSS. Please ensure your contributions follow our best practices for clarity, maintainability, and consistency.
+> Sim Studio is a monorepo containing the main application (`sim/`) and documentation (`docs/`). The main application is built with Next.js (app router), ReactFlow, Zustand, Shadcn, and Tailwind CSS. Please ensure your contributions follow our best practices for clarity, maintainability, and consistency.
 
 ---
 
@@ -15,6 +15,8 @@ Thank you for your interest in contributing to Sim Studio! Our goal is to provid
 - [Commit Message Guidelines](#commit-message-guidelines)
 - [Local Development Setup](#local-development-setup)
 - [Adding New Blocks and Tools](#adding-new-blocks-and-tools)
+- [Local Storage Mode](#local-storage-mode)
+- [Standalone Build](#standalone-build)
 - [License](#license)
 - [Contributor License Agreement (CLA)](#contributor-license-agreement-cla)
 
@@ -55,7 +57,7 @@ We strive to keep our workflow as simple as possible. To contribute:
    ```
 
 7. **Create a Pull Request**  
-   Open a pull request against the `staging` branch on GitHub. Please provide a clear description of the changes and reference any relevant issues (e.g., `fixes #123`).
+   Open a pull request against the `main` branch on GitHub. Please provide a clear description of the changes and reference any relevant issues (e.g., `fixes #123`).
 
 ---
 
@@ -83,7 +85,7 @@ If you discover a bug or have a feature request, please open an issue in our Git
 Before creating a pull request:
 
 - **Ensure Your Branch Is Up-to-Date:**  
-  Rebase your branch onto the latest `staging` branch to prevent merge conflicts.
+  Rebase your branch onto the latest `main` branch to prevent merge conflicts.
 - **Follow the Guidelines:**  
   Make sure your changes are well-tested, follow our coding standards, and include relevant documentation if necessary.
 
@@ -128,69 +130,54 @@ Using clear and consistent commit messages makes it easier for everyone to under
 
 To set up your local development environment:
 
-### Option 1: Using NPM Package (Simplest)
+### Option 1: Using Docker (Recommended)
 
-The easiest way to run Sim Studio locally is using our NPM package:
+Docker provides a consistent development environment with all dependencies pre-configured.
 
-```bash
-npx simstudio
-```
+1. **Clone the Repository:**
 
-After running this command, open [http://localhost:3000/](http://localhost:3000/) in your browser.
+   ```bash
+   git clone https://github.com/<your-username>/sim.git
+   cd sim
+   ```
 
-#### Options
+2. **Start the Docker Environment:**
 
-- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
-- `--no-pull`: Skip pulling the latest Docker images
+   ```bash
+   docker compose up -d
+   ```
 
-#### Requirements
+   Or use the convenience script which handles environment setup and migrations:
 
-- Docker must be installed and running on your machine
+   ```bash
+   chmod +x scripts/start_simstudio_docker.sh
+   ./scripts/start_simstudio_docker.sh
+   ```
 
-### Option 2: Using Docker Compose
+   This will:
 
-```bash
-# Clone the repository
-git clone https://github.com/<your-username>/sim.git
-cd sim
+   - Start a PostgreSQL database container
+   - Build and run the Next.js application with hot-reloading
+   - Set up all necessary environment variables
+   - Apply database migrations automatically
 
-# Start Sim Studio
-docker compose -f docker-compose.prod.yml up -d
-```
+3. **View Logs:**
 
-Access the application at [http://localhost:3000/](http://localhost:3000/)
+   ```bash
+   docker compose logs -f simstudio
+   ```
 
-#### Using Local Models
+4. **Make Your Changes:**
+   - Edit files in your local directory
+   - Changes will be automatically reflected thanks to hot-reloading
 
-To use local models with Sim Studio:
-
-1. Pull models using our helper script:
-
-```bash
-./apps/sim/scripts/ollama_docker.sh pull <model_name>
-```
-
-2. Start Sim Studio with local model support:
-
-```bash
-# With NVIDIA GPU support
-docker compose --profile local-gpu -f docker-compose.ollama.yml up -d
-
-# Without GPU (CPU only)
-docker compose --profile local-cpu -f docker-compose.ollama.yml up -d
-
-# If hosting on a server, update the environment variables in the docker-compose.prod.yml file
-# to include the server's public IP then start again (OLLAMA_URL to i.e. http://1.1.1.1:11434)
-docker compose -f docker-compose.prod.yml up -d
-```
-
-### Option 3: Using VS Code / Cursor Dev Containers
+### Option 2: Using VS Code / Cursor Dev Containers
 
 Dev Containers provide a consistent and easy-to-use development environment:
 
 1. **Prerequisites:**
 
-   - Visual Studio Code or Cursor
+   - Visual Studio Code
    - Docker Desktop
    - [Remote - Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) extension for VS Code
 
@@ -201,56 +188,58 @@ Dev Containers provide a consistent and easy-to-use development environment:
      git clone https://github.com/<your-username>/sim.git
      cd sim
      ```
-   - Open the project in VS Code/Cursor
+   - Open the project in VS Code
    - When prompted, click "Reopen in Container" (or press F1 and select "Remote-Containers: Reopen in Container")
    - Wait for the container to build and initialize
+   - The development environment will be set up in the `sim/` directory
 
 3. **Start Developing:**
 
-   - Run `bun run dev:full` in the terminal or use the `sim-start` alias
-   - This starts both the main application and the realtime socket server
    - All dependencies and configurations are automatically set up
+   - Use the provided aliases (like `sim-start`) to run common commands
    - Your changes will be automatically hot-reloaded
 
 4. **GitHub Codespaces:**
    - This setup also works with GitHub Codespaces if you prefer development in the browser
-   - Just click "Code" → "Codespaces" → "Create codespace on staging"
+   - Just click "Code" → "Codespaces" → "Create codespace on main"
 
-### Option 4: Manual Setup
+### Option 3: Manual Setup
 
 If you prefer not to use Docker or Dev Containers:
 
 1. **Clone the Repository:**
    ```bash
    git clone https://github.com/<your-username>/sim.git
-   cd sim
-   bun install
+   cd sim/sim
    ```
+2. **Install Dependencies:**
 
-2. **Set Up Environment:**
-
-   - Navigate to the app directory:
+   - Using NPM:
      ```bash
-     cd apps/sim
+     npm install
      ```
+
+3. **Set Up Environment:**
+
    - Copy `.env.example` to `.env`
-   - Configure required variables (DATABASE_URL, BETTER_AUTH_SECRET, BETTER_AUTH_URL)
+   - Configure database connection and other required authentication variables
 
-3. **Set Up Database:**
+4. **Set Up Database:**
 
-   ```bash
-   bunx drizzle-kit push
-   ```
+   - You need a PostgreSQL instance running
+   - Run migrations:
+     ```bash
+     npm run db:push
+     ```
 
-4. **Run the Development Server:**
+5. **Run the Development Server:**
 
-   ```bash
-   bun run dev:full
-   ```
+   - With NPM:
+     ```bash
+     npm run dev
+     ```
 
-   This command starts both the main application and the realtime socket server required for full functionality.
-
-5. **Make Your Changes and Test Locally.**
+6. **Make Your Changes and Test Locally.**
 
 ### Email Template Development
 
@@ -259,7 +248,7 @@ When working on email templates, you can preview them using a local email previe
 1. **Run the Email Preview Server:**
 
    ```bash
-   bun run email:dev
+   npm run email:dev
    ```
 
 2. **Access the Preview:**
@@ -280,26 +269,26 @@ Sim Studio is built in a modular fashion where blocks and tools extend the platf
 
 ### Where to Add Your Code
 
-- **Blocks:** Create your new block file under the `/apps/sim/blocks/blocks` directory. The name of the file should match the provider name (e.g., `pinecone.ts`).
-- **Tools:** Create a new directory under `/apps/sim/tools` with the same name as the provider (e.g., `/apps/sim/tools/pinecone`).
+- **Blocks:** Create your new block file under the `/sim/blocks/blocks` directory. The name of the file should match the provider name (e.g., `pinecone.ts`).
+- **Tools:** Create a new directory under `/sim/tools` with the same name as the provider (e.g., `/sim/tools/pinecone`).
 
 In addition, you will need to update the registries:
 
-- **Block Registry:** Update the blocks index (`/apps/sim/blocks/index.ts`) to include your new block.
-- **Tool Registry:** Update the tools registry (`/apps/sim/tools/index.ts`) to add your new tool.
+- **Block Registry:** Update the blocks index (`/sim/blocks/index.ts`) to include your new block.
+- **Tool Registry:** Update the tools registry (`/sim/tools/index.ts`) to add your new tool.
 
 ### How to Create a New Block
 
 1. **Create a New File:**  
-   Create a file for your block named after the provider (e.g., `pinecone.ts`) in the `/apps/sim/blocks/blocks` directory.
+   Create a file for your block named after the provider (e.g., `pinecone.ts`) in the `/sim/blocks/blocks` directory.
 
 2. **Create a New Icon:**
-   Create a new icon for your block in the `/apps/sim/components/icons.tsx` file. The icon should follow the same naming convention as the block (e.g., `PineconeIcon`).
+   Create a new icon for your block in the `/sim/components/icons.tsx` file. The icon should follow the same naming convention as the block (e.g., `PineconeIcon`).
 
 3. **Define the Block Configuration:**  
    Your block should export a constant of type `BlockConfig`. For example:
 
-   ```typescript:/apps/sim/blocks/blocks/pinecone.ts
+   ```typescript:/sim/blocks/blocks/pinecone.ts
    import { PineconeIcon } from '@/components/icons'
    import { PineconeResponse } from '@/tools/pinecone/types'
    import { BlockConfig } from '../types'
@@ -324,11 +313,11 @@ In addition, you will need to update the registries:
    ```
 
 4. **Register Your Block:**  
-   Add your block to the blocks registry (`/apps/sim/blocks/registry.ts`):
+   Add your block to the blocks registry (`/sim/blocks/registry.ts`):
 
-   ```typescript:/apps/sim/blocks/registry.ts
+   ```typescript:/sim/blocks/registry.ts
    import { PineconeBlock } from './blocks/pinecone'
-
+   
    // Registry of all available blocks
    export const registry: Record<string, BlockConfig> = {
      // ... existing blocks
@@ -344,7 +333,7 @@ In addition, you will need to update the registries:
 ### How to Create a New Tool
 
 1. **Create a New Directory:**  
-   Create a directory under `/apps/sim/tools` with the same name as the provider (e.g., `/apps/sim/tools/pinecone`).
+   Create a directory under `/sim/tools` with the same name as the provider (e.g., `/sim/tools/pinecone`).
 
 2. **Create Tool Files:**  
    Create separate files for each tool functionality with descriptive names (e.g., `fetch.ts`, `generate_embeddings.ts`, `search_text.ts`) in your tool directory.
@@ -355,7 +344,7 @@ In addition, you will need to update the registries:
 4. **Create an Index File:**  
    Create an `index.ts` file in your tool directory that imports and exports all tools:
 
-   ```typescript:/apps/sim/tools/pinecone/index.ts
+   ```typescript:/sim/tools/pinecone/index.ts
    import { fetchTool } from './fetch'
    import { generateEmbeddingsTool } from './generate_embeddings'
    import { searchTextTool } from './search_text'
@@ -366,7 +355,7 @@ In addition, you will need to update the registries:
 5. **Define the Tool Configuration:**  
    Your tool should export a constant with a naming convention of `{toolName}Tool`. The tool ID should follow the format `{provider}_{tool_name}`. For example:
 
-   ```typescript:/apps/sim/tools/pinecone/fetch.ts
+   ```typescript:/sim/tools/pinecone/fetch.ts
    import { ToolConfig, ToolResponse } from '../types'
    import { PineconeParams, PineconeResponse } from './types'
 
@@ -380,18 +369,7 @@ In addition, you will need to update the registries:
      provider: 'pinecone', // ID of the OAuth provider
 
      params: {
-       parameterName: {
-         type: 'string',
-         required: true,
-         visibility: 'user-or-llm', // Controls parameter visibility
-         description: 'Description of the parameter',
-       },
-       optionalParam: {
-         type: 'string',
-         required: false,
-         visibility: 'user-only',
-         description: 'Optional parameter only user can set',
-       },
+       // Tool parameters
      },
      request: {
        // Request configuration
@@ -406,9 +384,9 @@ In addition, you will need to update the registries:
    ```
 
 6. **Register Your Tool:**  
-   Update the tools registry in `/apps/sim/tools/index.ts` to include your new tool:
+   Update the tools registry in `/sim/tools/index.ts` to include your new tool:
 
-   ```typescript:/apps/sim/tools/index.ts
+   ```typescript:/sim/tools/index.ts
    import { fetchTool, generateEmbeddingsTool, searchTextTool } from './pinecone'
    // ... other imports
 
@@ -423,12 +401,6 @@ In addition, you will need to update the registries:
 7. **Test Your Tool:**  
    Ensure that your tool functions correctly by making test requests and verifying the responses.
 
-8. **Generate Documentation:**  
-   Run the documentation generator to create docs for your new tool:
-   ```bash
-   ./scripts/generate-docs.sh
-   ```
-
 ### Naming Conventions
 
 Maintaining consistent naming across the codebase is critical for auto-generation of tools and documentation. Follow these naming guidelines:
@@ -441,57 +413,11 @@ Maintaining consistent naming across the codebase is critical for auto-generatio
 - **Tool Exports:** Should be named `{toolName}Tool` (e.g., `fetchTool`)
 - **Tool IDs:** Should follow the format `{provider}_{tool_name}` (e.g., `pinecone_fetch`)
 
-### Parameter Visibility System
-
-Sim Studio implements a sophisticated parameter visibility system that controls how parameters are exposed to users and LLMs in agent workflows. Each parameter can have one of four visibility levels:
-
-| Visibility  | User Sees | LLM Sees | How It Gets Set                |
-|-------------|-----------|----------|--------------------------------|
-| `user-only` | ✅ Yes     | ❌ No     | User provides in UI            |
-| `user-or-llm` | ✅ Yes     | ✅ Yes    | User provides OR LLM generates |
-| `llm-only`  | ❌ No      | ✅ Yes    | LLM generates only             |
-| `hidden`    | ❌ No      | ❌ No     | Application injects at runtime |
-
-#### Visibility Guidelines
-
-- **`user-or-llm`**: Use for core parameters that can be provided by users or intelligently filled by the LLM (e.g., search queries, email subjects)
-- **`user-only`**: Use for configuration parameters, API keys, and settings that only users should control (e.g., number of results, authentication credentials)
-- **`llm-only`**: Use for computed values that the LLM should handle internally (e.g., dynamic calculations, contextual data)
-- **`hidden`**: Use for system-level parameters injected at runtime (e.g., OAuth tokens, internal identifiers)
-
-#### Example Implementation
-
-```typescript
-params: {
-  query: {
-    type: 'string',
-    required: true,
-    visibility: 'user-or-llm', // User can provide or LLM can generate
-    description: 'Search query to execute',
-  },
-  apiKey: {
-    type: 'string',
-    required: true,
-    visibility: 'user-only', // Only user provides this
-    description: 'API key for authentication',
-  },
-  internalId: {
-    type: 'string',
-    required: false,
-    visibility: 'hidden', // System provides this at runtime
-    description: 'Internal tracking identifier',
-  },
-}
-```
-
-This visibility system ensures clean user interfaces while maintaining full flexibility for LLM-driven workflows.
-
 ### Guidelines & Best Practices
 
 - **Code Style:** Follow the project's ESLint and Prettier configurations. Use meaningful variable names and small, focused functions.
 - **Documentation:** Clearly document the purpose, inputs, outputs, and any special behavior for your block/tool.
 - **Error Handling:** Implement robust error handling and provide user-friendly error messages.
-- **Parameter Visibility:** Always specify the appropriate visibility level for each parameter to ensure proper UI behavior and LLM integration.
 - **Testing:** Add unit or integration tests to verify your changes when possible.
 - **Commit Changes:** Update all related components and registries, and describe your changes in your pull request.
 

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,7 +1,7 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: '[BUG]'
+title: "[BUG]"
 labels: bug
 assignees: ''
 ---
@@ -11,7 +11,6 @@ A clear and concise description of what the bug is.
 
 **To Reproduce**
 Steps to reproduce the behavior:
-
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
@@ -24,4 +23,4 @@ A clear and concise description of what you expected to happen.
 If applicable, add screenshots to help explain your problem.
 
 **Additional context**
-Add any other context about the problem here.
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,7 +1,7 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: '[REQUEST]'
+title: "[REQUEST]"
 labels: feature
 assignees: ''
 ---
@@ -16,4 +16,4 @@ A clear and concise description of what you want to happen.
 A clear and concise description of any alternative solutions or features you've considered.
 
 **Additional context**
-Add any other context or screenshots about the feature request here.
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -26,7 +26,7 @@ Please describe the tests that you ran to verify your changes. Provide instructi
 - [ ] I have performed a self-review of my own code
 - [ ] I have commented my code, particularly in hard-to-understand areas
 - [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] All tests pass locally and in CI (`bun run test`)
+- [ ] All tests pass locally and in CI (`npm test`)
 - [ ] My changes generate no new warnings
 - [ ] Any dependent changes have been merged and published in downstream modules
 - [ ] I have updated version numbers as needed (if needed)

.github/SECURITY.md

@@ -6,6 +6,7 @@
 | ------- | ------------------ |
 | 0.1.x   | :white_check_mark: |
 
+
 ## Reporting a Vulnerability
 
 We take the security of Sim Studio seriously. If you believe you've found a security vulnerability, please follow these steps:
@@ -15,7 +16,6 @@ We take the security of Sim Studio seriously. If you believe you've found a secu
 2. **Email us directly** at security@simstudio.ai with details of the vulnerability.
 
 3. **Include the following information** in your report:
-
    - Description of the vulnerability
    - Steps to reproduce
    - Potential impact
@@ -23,4 +23,4 @@ We take the security of Sim Studio seriously. If you believe you've found a secu
 
 4. We will acknowledge receipt of your vulnerability report within 48 hours and provide an estimated timeline for a fix.
 
-5. Once the vulnerability is fixed, we will notify you and publicly acknowledge your contribution (unless you prefer to remain anonymous).
+5. Once the vulnerability is fixed, we will notify you and publicly acknowledge your contribution (unless you prefer to remain anonymous).

.github/dependabot.yml

@@ -0,0 +1,98 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/sim"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+      time: "09:00"
+    # Disable version updates
+    open-pull-requests-limit: 0
+    labels:
+      - "dependencies"
+      - "security"
+    commit-message:
+      prefix: "fix(deps)"
+      prefix-development: "chore(deps)"
+      include: "scope"
+    groups:
+      dependencies:
+        applies-to: security-updates
+        patterns:
+          - "*"
+    
+  # Documentation site dependencies (/docs)
+  - package-ecosystem: "npm"
+    directory: "/docs"
+    schedule:
+      interval: "weekly"
+      day: "wednesday"
+    # Disable version updates
+    open-pull-requests-limit: 0
+    labels:
+      - "dependencies"
+      - "security"
+    commit-message:
+      prefix: "docs(deps)"
+      include: "scope"
+    groups:
+      docs-dependencies:
+        applies-to: security-updates
+        patterns:
+          - "*"
+    
+  # Root-level dependencies (if any)
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "friday"
+    # Disable version updates
+    open-pull-requests-limit: 0
+    labels:
+      - "dependencies"
+      - "security"
+    commit-message:
+      prefix: "chore(deps)"
+      include: "scope"
+    groups:
+      root-dependencies:
+        applies-to: security-updates
+        patterns:
+          - "*"
+    
+  # GitHub Actions workflows
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "monthly"
+    # Disable version updates
+    open-pull-requests-limit: 0
+    labels:
+      - "dependencies"
+      - "security"
+    commit-message:
+      prefix: "ci(deps)"
+    groups:
+      actions:
+        applies-to: security-updates
+        patterns:
+          - "*"
+    
+  # Docker containers (if applicable)
+  - package-ecosystem: "docker"
+    directory: "/"
+    schedule:
+      interval: "monthly"
+    # Disable version updates
+    open-pull-requests-limit: 0
+    labels:
+      - "dependencies"
+      - "security"
+    commit-message:
+      prefix: "docker(deps)"
+    groups:
+      docker:
+        applies-to: security-updates
+        patterns:
+          - "*"

.github/workflows/build.yml

@@ -1,66 +0,0 @@
-name: Build and Publish Docker Image
-
-on:
-  push:
-    branches: [main]
-    tags: ['v*']
-
-jobs:
-  build-and-push:
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-          - dockerfile: ./docker/app.Dockerfile
-            image: ghcr.io/simstudioai/simstudio
-          - dockerfile: ./docker/db.Dockerfile
-            image: ghcr.io/simstudioai/migrations
-          - dockerfile: ./docker/realtime.Dockerfile
-            image: ghcr.io/simstudioai/realtime
-    permissions:
-      contents: read
-      packages: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Set up QEMU
-        uses: docker/setup-qemu-action@v3
-
-      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v3
-
-      - name: Log in to the Container registry
-        if: github.event_name != 'pull_request'
-        uses: docker/login-action@v3
-        with:
-          registry: ghcr.io
-          username: ${{ github.repository_owner }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Extract metadata (tags, labels) for Docker
-        id: meta
-        uses: docker/metadata-action@v5
-        with:
-          images: ${{ matrix.image }}
-          tags: |
-            type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' }}
-            type=ref,event=pr
-            type=semver,pattern={{version}}
-            type=semver,pattern={{major}}.{{minor}}
-            type=semver,pattern={{major}}.{{minor}}.{{patch}}
-            type=sha,format=long
-
-      - name: Build and push Docker image
-        uses: docker/build-push-action@v6
-        with:
-          context: .
-          file: ${{ matrix.dockerfile }}
-          platforms: linux/amd64,linux/arm64
-          push: ${{ github.event_name != 'pull_request' }}
-          tags: ${{ steps.meta.outputs.tags }}
-          labels: ${{ steps.meta.outputs.labels }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max

.github/workflows/ci.yml

@@ -2,76 +2,82 @@ name: CI
 
 on:
   push:
-    branches: [main, staging]
+    branches: [main]
   pull_request:
-    branches: [main, staging]
+    branches: [main]
 
 jobs:
   test:
     name: Test and Build
     runs-on: ubuntu-latest
-
+    
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: latest
-
-      - name: Setup Node
+        
+      - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: latest
-
+          node-version: '20'
+          cache: 'npm'
+          cache-dependency-path: './sim/package-lock.json'
+          
       - name: Install dependencies
-        run: bun install
-
+        working-directory: ./sim
+        run: npm ci
+        
+      - name: Fix Rollup module issue
+        working-directory: ./sim
+        run: |
+          rm -rf node_modules package-lock.json
+          npm install
+        
       - name: Run tests with coverage
+        working-directory: ./sim
         env:
-          NODE_OPTIONS: '--no-warnings'
-          NEXT_PUBLIC_APP_URL: 'https://www.simstudio.ai'
-          ENCRYPTION_KEY: '7cf672e460e430c1fba707575c2b0e2ad5a99dddf9b7b7e3b5646e630861db1c' # dummy key for CI only
-        run: bun run test
-
+          NODE_OPTIONS: "--no-warnings"
+        run: npm run test:coverage
+        
       - name: Build application
+        working-directory: ./sim
         env:
-          NODE_OPTIONS: '--no-warnings'
-          NEXT_PUBLIC_APP_URL: 'https://www.simstudio.ai'
-          STRIPE_SECRET_KEY: 'dummy_key_for_ci_only'
-          STRIPE_WEBHOOK_SECRET: 'dummy_secret_for_ci_only'
-          RESEND_API_KEY: 'dummy_key_for_ci_only'
-          AWS_REGION: 'us-west-2'
-          ENCRYPTION_KEY: '7cf672e460e430c1fba707575c2b0e2ad5a99dddf9b7b7e3b5646e630861db1c' # dummy key for CI only
-        run: bun run build
-
+          NODE_OPTIONS: "--no-warnings"
+          NEXT_PUBLIC_APP_URL: "https://www.simstudio.ai"
+          STRIPE_SECRET_KEY: "dummy_key_for_ci_only"
+          STRIPE_WEBHOOK_SECRET: "dummy_secret_for_ci_only"
+          RESEND_API_KEY: "dummy_key_for_ci_only"
+          AWS_REGION: "us-west-2"
+        run: npm run build
+        
       - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v5
+        uses: codecov/codecov-action@v3
         with:
-          directory: ./apps/sim/coverage
+          directory: ./sim/coverage
           fail_ci_if_error: false
-          verbose: true
+          verbose: true 
 
   migrations:
     name: Apply Database Migrations
     runs-on: ubuntu-latest
-    if: github.event_name == 'push' && (github.ref == 'refs/heads/main' || github.ref == 'refs/heads/staging')
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
     needs: test
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
+        
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
         with:
-          bun-version: latest
-
+          node-version: '20'
+          cache: 'npm'
+          cache-dependency-path: './sim/package-lock.json'
+          
       - name: Install dependencies
-        run: bun install
-
+        working-directory: ./sim
+        run: npm ci
+        
       - name: Apply migrations
-        working-directory: ./apps/sim
+        working-directory: ./sim
         env:
-          DATABASE_URL: ${{ github.ref == 'refs/heads/main' && secrets.DATABASE_URL || secrets.STAGING_DATABASE_URL }}
-        run: bunx drizzle-kit push
+          DATABASE_URL: ${{ secrets.DATABASE_URL }}
+        run: npx drizzle-kit push 

.github/workflows/docker-publish.yml

@@ -0,0 +1,58 @@
+name: Docker Build and Publish
+
+on:
+  push:
+    branches: [ main ]
+    tags: [ 'v*' ]
+  pull_request:
+    branches: [ main ]
+
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: simstudioai/sim
+
+jobs:
+  build-and-push:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      packages: write
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Log in to the Container registry
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ env.REGISTRY }}
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+          tags: |
+            type=ref,event=branch
+            type=ref,event=pr
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+            type=sha,format=short
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+        with:
+          driver: docker
+          buildkitd-flags: --debug
+
+      - name: Build and push Docker image
+        uses: docker/build-push-action@v5
+        with:
+          context: .
+          push: ${{ github.event_name != 'pull_request' }}
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=gha
+          cache-to: type=gha,mode=max 

.github/workflows/publish-cli.yml

@@ -1,58 +1,93 @@
-name: Publish CLI Package
+name: Publish Sim Studio CLI
 
 on:
   push:
-    branches: [main]
+    branches:
+      - main
     paths:
-      - 'packages/cli/**'
+      - 'packages/simstudio/**'
+      - '.github/workflows/publish-cli.yml'
 
 jobs:
-  publish-npm:
+  publish:
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      packages: write
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
         with:
-          bun-version: latest
+          fetch-depth: 0
 
-      - name: Setup Node.js for npm publishing
+      - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '18'
-          registry-url: 'https://registry.npmjs.org/'
+          node-version: '20'
+          registry-url: 'https://registry.npmjs.org'
+          cache: 'npm'
+          cache-dependency-path: 'packages/simstudio/package-lock.json'
 
       - name: Install dependencies
-        working-directory: packages/cli
-        run: bun install
+        working-directory: packages/simstudio
+        run: npm ci
 
       - name: Build package
-        working-directory: packages/cli
-        run: bun run build
+        working-directory: packages/simstudio
+        run: npm run build
 
-      - name: Get package version
-        id: package_version
-        working-directory: packages/cli
+      - name: Get version
+        working-directory: packages/simstudio
+        id: get_version
         run: echo "version=$(node -p "require('./package.json').version")" >> $GITHUB_OUTPUT
 
-      - name: Check if version already exists
-        id: version_check
+      - name: Check version update
+        working-directory: packages/simstudio
         run: |
-          if npm view simstudio@${{ steps.package_version.outputs.version }} version &> /dev/null; then
-            echo "exists=true" >> $GITHUB_OUTPUT
+          if ! git diff ${{ github.event.before }} ${{ github.sha }} packages/simstudio/package.json | grep -q '"version":'; then
+            echo "::error::Version not updated in package.json"
+            exit 1
+          fi
+
+      - name: Run tests
+        working-directory: packages/simstudio
+        run: npm test
+
+      - name: Check for changes
+        working-directory: packages/simstudio
+        id: check_changes
+        run: |
+          if git diff --quiet ${{ github.event.before }} ${{ github.sha }} packages/simstudio/; then
+            echo "changes=false" >> $GITHUB_OUTPUT
           else
-            echo "exists=false" >> $GITHUB_OUTPUT
+            echo "changes=true" >> $GITHUB_OUTPUT
           fi
 
       - name: Publish to npm
-        if: steps.version_check.outputs.exists == 'false'
-        working-directory: packages/cli
-        run: npm publish --access=public
+        if: steps.check_changes.outputs.changes == 'true'
+        working-directory: packages/simstudio
+        run: |
+          if ! npm publish; then
+            echo "::error::Failed to publish package"
+            exit 1
+          fi
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
-      - name: Log skipped publish
-        if: steps.version_check.outputs.exists == 'true'
-        run: echo "Skipped publishing because version ${{ steps.package_version.outputs.version }} already exists on npm" 
+      - name: Create Git tag
+        if: steps.check_changes.outputs.changes == 'true'
+        run: |
+          git config --local user.email "github-actions[bot]@users.noreply.github.com"
+          git config --local user.name "github-actions[bot]"
+          git tag -a "v${{ steps.get_version.outputs.version }}" -m "Release v${{ steps.get_version.outputs.version }}"
+          git push origin "v${{ steps.get_version.outputs.version }}"
+
+      - name: Create GitHub Release
+        if: steps.check_changes.outputs.changes == 'true'
+        uses: softprops/action-gh-release@v1
+        with:
+          name: "v${{ steps.get_version.outputs.version }}"
+          tag_name: "v${{ steps.get_version.outputs.version }}"
+          generate_release_notes: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 

.github/workflows/publish-python-sdk.yml

@@ -1,89 +0,0 @@
-name: Publish Python SDK
-
-on:
-  push:
-    branches: [main]
-    paths:
-      - 'packages/python-sdk/**'
-
-jobs:
-  publish-pypi:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup Python
-        uses: actions/setup-python@v5
-        with:
-          python-version: '3.12'
-          cache: 'pip'
-
-      - name: Install build dependencies
-        run: |
-          python -m pip install --upgrade pip
-          pip install build twine pytest requests tomli
-
-      - name: Run tests
-        working-directory: packages/python-sdk
-        run: |
-          PYTHONPATH=. pytest tests/ -v
-
-      - name: Get package version
-        id: package_version
-        working-directory: packages/python-sdk
-        run: echo "version=$(python -c "import tomli; print(tomli.load(open('pyproject.toml', 'rb'))['project']['version'])")" >> $GITHUB_OUTPUT
-
-      - name: Check if version already exists
-        id: version_check
-        run: |
-          if pip index versions simstudio-sdk | grep -q "${{ steps.package_version.outputs.version }}"; then
-            echo "exists=true" >> $GITHUB_OUTPUT
-          else
-            echo "exists=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Build package
-        if: steps.version_check.outputs.exists == 'false'
-        working-directory: packages/python-sdk
-        run: python -m build
-
-      - name: Check package
-        if: steps.version_check.outputs.exists == 'false'
-        working-directory: packages/python-sdk
-        run: twine check dist/*
-
-      - name: Publish to PyPI
-        if: steps.version_check.outputs.exists == 'false'
-        working-directory: packages/python-sdk
-        env:
-          TWINE_USERNAME: __token__
-          TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
-        run: twine upload dist/*
-
-      - name: Log skipped publish
-        if: steps.version_check.outputs.exists == 'true'
-        run: echo "Skipped publishing because version ${{ steps.package_version.outputs.version }} already exists on PyPI"
-
-      - name: Create GitHub Release
-        if: steps.version_check.outputs.exists == 'false'
-        uses: softprops/action-gh-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          tag_name: python-sdk-v${{ steps.package_version.outputs.version }}
-          name: Python SDK v${{ steps.package_version.outputs.version }}
-          body: |
-            ## Python SDK v${{ steps.package_version.outputs.version }}
-            
-            Published simstudio-sdk==${{ steps.package_version.outputs.version }} to PyPI.
-            
-            ### Installation
-            ```bash
-            pip install simstudio-sdk==${{ steps.package_version.outputs.version }}
-            ```
-            
-            ### Documentation
-            See the [README](https://github.com/simstudio/sim/tree/main/packages/python-sdk) for usage instructions.
-          draft: false
-          prerelease: false 

.github/workflows/publish-ts-sdk.yml

@@ -1,85 +0,0 @@
-name: Publish TypeScript SDK
-
-on:
-  push:
-    branches: [main]
-    paths:
-      - 'packages/ts-sdk/**'
-
-jobs:
-  publish-npm:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: latest
-
-      - name: Setup Node.js for npm publishing
-        uses: actions/setup-node@v4
-        with:
-          node-version: '18'
-          registry-url: 'https://registry.npmjs.org/'
-
-      - name: Install dependencies
-        working-directory: packages/ts-sdk
-        run: bun install
-
-      - name: Run tests
-        working-directory: packages/ts-sdk
-        run: bun run test
-
-      - name: Build package
-        working-directory: packages/ts-sdk
-        run: bun run build
-
-      - name: Get package version
-        id: package_version
-        working-directory: packages/ts-sdk
-        run: echo "version=$(node -p "require('./package.json').version")" >> $GITHUB_OUTPUT
-
-      - name: Check if version already exists
-        id: version_check
-        run: |
-          if npm view simstudio-ts-sdk@${{ steps.package_version.outputs.version }} version &> /dev/null; then
-            echo "exists=true" >> $GITHUB_OUTPUT
-          else
-            echo "exists=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Publish to npm
-        if: steps.version_check.outputs.exists == 'false'
-        working-directory: packages/ts-sdk
-        run: npm publish --access=public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-
-      - name: Log skipped publish
-        if: steps.version_check.outputs.exists == 'true'
-        run: echo "Skipped publishing because version ${{ steps.package_version.outputs.version }} already exists on npm"
-
-      - name: Create GitHub Release
-        if: steps.version_check.outputs.exists == 'false'
-        uses: softprops/action-gh-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          tag_name: typescript-sdk-v${{ steps.package_version.outputs.version }}
-          name: TypeScript SDK v${{ steps.package_version.outputs.version }}
-          body: |
-            ## TypeScript SDK v${{ steps.package_version.outputs.version }}
-            
-            Published simstudio-ts-sdk@${{ steps.package_version.outputs.version }} to npm.
-            
-            ### Installation
-            ```bash
-            npm install simstudio-ts-sdk@${{ steps.package_version.outputs.version }}
-            ```
-            
-            ### Documentation
-            See the [README](https://github.com/simstudio/sim/tree/main/packages/ts-sdk) for usage instructions.
-          draft: false
-          prerelease: false 

.gitignore

@@ -1,23 +1,28 @@
 # See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
 
 # dependencies
-/node_modules
-/apps/**/node_modules
+*/node_modules
+docs/node_modules
 /packages/**/node_modules
-/scripts/node_modules
-
-# bun specific
-bun-debug.log*
+/.pnp
+.pnp.*
+.yarn/*
+!.yarn/patches
+!.yarn/plugins
+!.yarn/releases
+!.yarn/versions
 
 # testing
 /coverage
-/apps/**/coverage
 
 # next.js
 /.next/
-/apps/**/out/
-/apps/**/.next/
-/apps/**/build
+sim/.next/
+sim/out/
+sim/build
+docs/.next/
+docs/out/
+docs/build
 
 # production
 /build
@@ -30,6 +35,12 @@ sim-standalone.tar.gz
 .DS_Store
 *.pem
 
+# debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+.pnpm-debug.log*
+
 # env files
 .env
 *.env
@@ -49,20 +60,17 @@ next-env.d.ts
 .cursorrules
 
 # docs
-/apps/docs/.source
-/apps/docs/.contentlayer
-/apps/docs/.content-collections
+docs/.source
+docs/.contentlayer
+docs/.content-collections
 
 # database instantiation
 **/postgres_data/
 
+# file uploads
+uploads/
+
 # collector configuration
 collector-config.yaml
 docker-compose.collector.yml
 start-collector.sh
-
-# Turborepo
-.turbo
-
-# VSCode
-.vscode

.husky/pre-commit

@@ -1 +1 @@
-bunx lint-staged
+cd sim && npx lint-staged 

.npmrc

@@ -1 +0,0 @@
-ignore-scripts=true

Dockerfile

@@ -0,0 +1,27 @@
+FROM node:20-alpine
+
+# Set working directory
+WORKDIR /app
+
+# Set Node.js memory limit
+ENV NODE_OPTIONS="--max-old-space-size=4096"
+
+# Copy package files
+COPY sim/package*.json ./
+
+# Install dependencies
+RUN npm install
+
+# Copy the rest of the application
+COPY sim/ ./
+
+# Generate database schema
+RUN npx drizzle-kit generate
+
+# Build the application
+RUN npm run build
+
+EXPOSE 3000
+
+# Run migrations and start the app
+CMD npx drizzle-kit push && npm run start

README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="apps/sim/public/static/sim.png" alt="Sim Studio Logo" width="500"/>
+  <img src="sim/public/static/sim.png" alt="Sim Studio Logo" width="500"/>
 </p>
 
 <p align="center">
@@ -14,139 +14,130 @@
   <strong>Sim Studio</strong> is a lightweight, user-friendly platform for building AI agent workflows.
 </p>
 
-<p align="center">
-  <img src="apps/sim/public/static/demo.gif" alt="Sim Studio Demo" width="800"/>
-</p>
-
 ## Getting Started
 
-1. Use our [cloud-hosted version](https://simstudio.ai)
-2. Self-host using one of the methods below
+### Run on [Sim Studio Cloud](https://simstudio.ai)
 
-## Self-Hosting Options
+The fastest way to get started is to use our [cloud-hosted version](https://simstudio.ai) - no setup required!
 
-### Option 1: NPM Package (Simplest)
+### Self-host Sim Studio
 
-The easiest way to run Sim Studio locally is using our [NPM package](https://www.npmjs.com/package/simstudio?activeTab=readme):
+If you prefer to self-host, there are several options available:
+
+### Option 1: Using CLI (Recommended)
+
+The easiest way to self-host:
 
 ```bash
 npx simstudio
+# This will set up and run Sim Studio locally with minimal configuration
 ```
 
-After running these commands, open [http://localhost:3000/](http://localhost:3000/) in your browser.
-
-#### Options
-
-- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
-- `--no-pull`: Skip pulling the latest Docker images
-
-#### Requirements
-
-- Docker must be installed and running on your machine
-
-### Option 2: Docker Compose
+### Option 2: Using Docker Compose
 
 ```bash
 # Clone the repository
 git clone https://github.com/simstudioai/sim.git
-
-# Navigate to the project directory
 cd sim
 
-# Start Sim Studio
-docker compose -f docker-compose.prod.yml up -d
+# Create environment file (update BETTER_AUTH_SECRET and ENCRYPTION_KEY with secure random values)
+cp sim/.env.example sim/.env
+
+# Start with Docker Compose
+docker compose up -d --build
 ```
 
-Access the application at [http://localhost:3000/](http://localhost:3000/)
+Once running, access the application at [http://localhost:3000/w/](http://localhost:3000/w/)
 
-#### Using Local Models
+## Working with Local Models
 
-To use local models with Sim Studio:
-
-1. Pull models using our helper script:
+Sim Studio supports integration with local LLM models:
 
 ```bash
-./apps/sim/scripts/ollama_docker.sh pull <model_name>
+# Pull local models
+./sim/scripts/ollama_docker.sh pull <model_name>
+
+# Start with local model support
+./start_simstudio_docker.sh --local
+
+# For systems with NVIDIA GPU
+docker compose up --profile local-gpu -d --build
+
+# For CPU-only systems
+docker compose up --profile local-cpu -d --build
 ```
 
-2. Start Sim Studio with local model support:
+### Connecting to Existing Ollama Instance
+
+If you already have Ollama running locally:
 
 ```bash
-# With NVIDIA GPU support
-docker compose --profile local-gpu -f docker-compose.ollama.yml up -d
-
-# Without GPU (CPU only)
-docker compose --profile local-cpu -f docker-compose.ollama.yml up -d
-
-# If hosting on a server, update the environment variables in the docker-compose.prod.yml file to include the server's public IP then start again (OLLAMA_URL to i.e. http://1.1.1.1:11434)
-docker compose -f docker-compose.prod.yml up -d
+# Using host networking (simplest)
+docker compose up --profile local-cpu -d --build --network=host
 ```
 
-### Option 3: Dev Containers
+Or add this to your docker-compose.yml:
 
-1. Open VS Code with the [Remote - Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
-2. Open the project and click "Reopen in Container" when prompted
-3. Run `bun run dev:full` in the terminal or use the `sim-start` alias
-   - This starts both the main application and the realtime socket server
+```yaml
+services:
+  simstudio:
+    # ... existing configuration ...
+    extra_hosts:
+      - "host.docker.internal:host-gateway"
+    environment:
+      - OLLAMA_HOST=http://host.docker.internal:11434
+```
 
-### Option 4: Manual Setup
+## Development Setup
 
-1. Clone and install dependencies:
+### Prerequisites
+- Node.js 20+
+- Docker (recommended)
+- PostgreSQL (if not using Docker)
 
+### Required Environment Variables
+
+For local development, create a `.env` file with these minimum variables:
+
+```env
+DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio
+BETTER_AUTH_SECRET=<generate_a_secure_random_value>
+ENCRYPTION_KEY=<generate_a_secure_random_value>
+```
+
+⚠️ **Note:** Without `RESEND_API_KEY`, verification codes will be logged to the console for local testing.
+
+### Dev Container Option
+1. Open in VS Code with the Remote-Containers extension
+2. Click "Reopen in Container" when prompted
+3. Run `npm run dev` or use the `sim-start` alias
+
+### Manual Setup
 ```bash
-git clone https://github.com/simstudioai/sim.git
-cd sim
-bun install
+cd sim/sim
+npm install
+cp .env.example .env
+npx drizzle-kit push
+npm run dev
 ```
 
-2. Set up environment:
+## Troubleshooting
 
-```bash
-cd apps/sim
-cp .env.example .env  # Configure with required variables (DATABASE_URL, BETTER_AUTH_SECRET, BETTER_AUTH_URL)
-```
+Common issues and solutions:
 
-3. Set up the database:
-
-```bash
-bunx drizzle-kit push
-```
-
-4. Start the development servers:
-
-**Recommended approach - run both servers together (from project root):**
-
-```bash
-bun run dev:full
-```
-
-This starts both the main Next.js application and the realtime socket server required for full functionality.
-
-**Alternative - run servers separately:**
-
-Next.js app (from project root):
-```bash
-bun run dev
-```
-
-Realtime socket server (from `apps/sim` directory in a separate terminal):
-```bash
-cd apps/sim
-bun run dev:sockets
-```
+- **Authentication problems**: Check console logs for verification codes if `RESEND_API_KEY` is not set
+- **Database connection errors**: Verify PostgreSQL is running and credentials are correct
+- **Port conflicts**: Check if port 3000 is already in use by another application
 
 ## Tech Stack
 
 - **Framework**: [Next.js](https://nextjs.org/) (App Router)
-- **Runtime**: [Bun](https://bun.sh/)
 - **Database**: PostgreSQL with [Drizzle ORM](https://orm.drizzle.team)
 - **Authentication**: [Better Auth](https://better-auth.com)
 - **UI**: [Shadcn](https://ui.shadcn.com/), [Tailwind CSS](https://tailwindcss.com)
 - **State Management**: [Zustand](https://zustand-demo.pmnd.rs/)
 - **Flow Editor**: [ReactFlow](https://reactflow.dev/)
 - **Docs**: [Fumadocs](https://fumadocs.vercel.app/)
-- **Monorepo**: [Turborepo](https://turborepo.org/)
-- **Realtime**: [Socket.io](https://socket.io/)
 
 ## Contributing
 
@@ -156,4 +147,4 @@ We welcome contributions! Please see our [Contributing Guide](.github/CONTRIBUTI
 
 This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.
 
-<p align="center">Made with ❤️ by the Sim Studio Team</p>
+<p align="center">Made with ❤️ by the Sim Studio Team</p>

apps/docs/.gitignore

@@ -1,39 +0,0 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
-
-# dependencies
-/node_modules
-
-# bun specific
-.bun
-bun.lockb
-bun-debug.log*
-
-# testing
-/coverage
-
-# next.js
-/.next/
-/out/
-/build
-
-# misc
-.DS_Store
-*.pem
-
-# env files
-.env
-*.env
-.env.local
-.env.development
-.env.test
-.env.production
-
-# vercel
-.vercel
-
-# typescript
-*.tsbuildinfo
-next-env.d.ts
-
-# Fumadocs
-/.source/ 

apps/docs/app/(docs)/[[...slug]]/layout.tsx

@@ -1,5 +0,0 @@
-import type { ReactNode } from 'react'
-
-export default function SlugLayout({ children }: { children: ReactNode }) {
-  return children
-}

apps/docs/app/global.css

@@ -1,24 +0,0 @@
-@import "tailwindcss";
-@import "fumadocs-ui/css/neutral.css";
-@import "fumadocs-ui/css/preset.css";
-
-@theme {
-  --color-fd-primary: #802fff; /* Purple from control-bar component */
-}
-
-/* Custom text highlighting styles */
-.text-highlight {
-  color: var(--color-fd-primary);
-}
-
-/* Override marker color for highlighted lists */
-.highlight-markers li::marker {
-  color: var(--color-fd-primary);
-}
-
-/* Tailwind v4 content sources */
-@source '../app/**/*.{js,ts,jsx,tsx,mdx}';
-@source '../components/**/*.{js,ts,jsx,tsx,mdx}';
-@source '../content/**/*.{js,ts,jsx,tsx,mdx}';
-@source '../mdx-components.tsx';
-@source '../node_modules/fumadocs-ui/dist/**/*.js';

apps/docs/app/llms.mdx/[[...slug]]/route.ts

@@ -1,18 +0,0 @@
-import { notFound } from 'next/navigation'
-import { type NextRequest, NextResponse } from 'next/server'
-import { getLLMText } from '@/lib/llms'
-import { source } from '@/lib/source'
-
-export const revalidate = false
-
-export async function GET(_req: NextRequest, { params }: { params: Promise<{ slug?: string[] }> }) {
-  const { slug } = await params
-  const page = source.getPage(slug)
-  if (!page) notFound()
-
-  return new NextResponse(await getLLMText(page))
-}
-
-export function generateStaticParams() {
-  return source.generateParams()
-}

apps/docs/app/llms.txt/route.ts

@@ -1,12 +0,0 @@
-import { getLLMText } from '@/lib/llms'
-import { source } from '@/lib/source'
-
-// cached forever
-export const revalidate = false
-
-export async function GET() {
-  const scan = source.getPages().map(getLLMText)
-  const scanned = await Promise.all(scan)
-
-  return new Response(scanned.join('\n\n'))
-}

apps/docs/content/docs/blocks/agent.mdx

@@ -1,303 +0,0 @@
----
-title: Agent
-description: Create powerful AI agents using any LLM provider
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Agent block serves as the interface between your workflow and Large Language Models (LLMs). It executes inference requests against various AI providers, processes natural language inputs according to defined instructions, and generates structured or unstructured outputs for downstream consumption.
-
-<ThemeImage
-  lightSrc="/static/light/agent-light.png"
-  darkSrc="/static/dark/agent-dark.png"
-  alt="Agent Block Configuration"
-  width={350}
-  height={175}
-/>
-
-## Overview
-
-The Agent block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Process natural language</strong>: Analyze user input and generate contextual responses
-  </Step>
-  <Step>
-    <strong>Execute AI-powered tasks</strong>: Perform content analysis, generation, and decision-making
-  </Step>
-  <Step>
-    <strong>Call external tools</strong>: Access APIs, databases, and services during processing
-  </Step>
-  <Step>
-    <strong>Generate structured output</strong>: Return JSON data that matches your schema requirements
-  </Step>
-</Steps> 
-
-## Configuration Options
-
-### System Prompt
-
-The system prompt establishes the agent's operational parameters and behavioral constraints. This configuration defines the agent's role, response methodology, and processing boundaries for all incoming requests.
-
-```markdown
-You are a helpful assistant that specializes in financial analysis.
-Always provide clear explanations and cite sources when possible.
-When responding to questions about investments, include risk disclaimers.
-```
-
-### User Prompt
-
-The user prompt represents the primary input data for inference processing. This parameter accepts natural language text or structured data that the agent will analyze and respond to. Input sources include:
-
-- **Static Configuration**: Direct text input specified in the block configuration
-- **Dynamic Input**: Data passed from upstream blocks through connection interfaces
-- **Runtime Generation**: Programmatically generated content during workflow execution
-
-### Model Selection
-
-The Agent block supports multiple LLM providers through a unified inference interface. Available models include:
-
-**OpenAI Models**: GPT-4o, o1, o3, o4-mini, gpt-4.1 (API-based inference)
-**Anthropic Models**: Claude 3.7 Sonnet (API-based inference)
-**Google Models**: Gemini 2.5 Pro, Gemini 2.0 Flash (API-based inference)
-**Alternative Providers**: Groq, Cerebras, xAI, DeepSeek (API-based inference)
-**Local Deployment**: Ollama-compatible models (self-hosted inference)
-
-<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
-  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/models.mp4"></video>
-</div>
-
-### Temperature
-
-Control the creativity and randomness of responses:
-
-<Tabs items={['Low (0-0.3)', 'Medium (0.3-0.7)', 'High (0.7-2.0)']}>
-  <Tab>
-    More deterministic, focused responses. Best for factual tasks, customer support, and
-    situations where accuracy is critical.
-  </Tab>
-  <Tab>
-    Balanced creativity and focus. Suitable for general purpose applications that require both
-    accuracy and some creativity.
-  </Tab>
-  <Tab>
-    More creative, varied responses. Ideal for creative writing, brainstorming, and generating
-    diverse ideas.
-  </Tab>
-</Tabs>
-
-<p className="mt-4 text-sm text-gray-600 dark:text-gray-400">
-  The temperature range (0-1 or 0-2) varies depending on the selected model.
-</p>
-
-### API Key
-
-Your API key for the selected LLM provider. This is securely stored and used for authentication.
-
-### Tools
-
-Tools extend the agent's capabilities through external API integrations and service connections. The tool system enables function calling, allowing the agent to execute operations beyond text generation.
-
-**Tool Integration Process**:
-1. Access the Tools configuration section within the Agent block
-2. Select from 60+ pre-built integrations or define custom functions
-3. Configure authentication parameters and operational constraints
-
-<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
-  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/tools.mp4"></video>
-</div>
-
-**Available Tool Categories**:
-- **Communication**: Gmail, Slack, Telegram, WhatsApp, Microsoft Teams
-- **Data Sources**: Notion, Google Sheets, Airtable, Supabase, Pinecone
-- **Web Services**: Firecrawl, Google Search, Exa AI, browser automation
-- **Development**: GitHub, Jira, Linear repository and issue management
-- **AI Services**: OpenAI, Perplexity, Hugging Face, ElevenLabs
-
-**Tool Execution Control**:
-- **Auto**: Model determines tool invocation based on context and necessity
-- **Required**: Tool must be called during every inference request
-- **None**: Tool definition available but excluded from model context
-
-<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
-  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/granular-tool-control.mp4"></video>
-</div>
-
-### Response Format
-
-The Response Format parameter enforces structured output generation through JSON Schema validation. This ensures consistent, machine-readable responses that conform to predefined data structures:
-
-```json
-{
-  "name": "user_analysis",
-  "schema": {
-    "type": "object",
-    "properties": {
-      "sentiment": {
-        "type": "string",
-        "enum": ["positive", "negative", "neutral"]
-      },
-      "confidence": {
-        "type": "number",
-        "minimum": 0,
-        "maximum": 1
-      }
-    },
-    "required": ["sentiment", "confidence"]
-  }
-}
-```
-
-This configuration constrains the model's output to comply with the specified schema, preventing free-form text responses and ensuring structured data generation.
-
-### Accessing Results
-
-After an agent completes, you can access its outputs:
-
-- **`<agent.content>`**: The agent's response text or structured data
-- **`<agent.tokens>`**: Token usage statistics (prompt, completion, total)
-- **`<agent.tool_calls>`**: Details of any tools the agent used during execution
-- **`<agent.cost>`**: Estimated cost of the API call (if available)
-
-## Advanced Features
-
-### Memory Integration
-
-Agents can maintain context across interactions using the memory system:
-
-```javascript
-// In a Function block before the agent
-const memory = {
-  conversation_history: previousMessages,
-  user_preferences: userProfile,
-  session_data: currentSession
-};
-```
-
-### Structured Output Validation
-
-Use JSON Schema to ensure consistent, machine-readable responses:
-
-```json
-{
-  "type": "object",
-  "properties": {
-    "analysis": {"type": "string"},
-    "confidence": {"type": "number", "minimum": 0, "maximum": 1},
-    "categories": {"type": "array", "items": {"type": "string"}}
-  },
-  "required": ["analysis", "confidence"]
-}
-```
-
-### Error Handling
-
-Agents automatically handle common errors:
-- API rate limits with exponential backoff
-- Invalid tool calls with retry logic
-- Network failures with connection recovery
-- Schema validation errors with fallback responses
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>System Prompt</strong>: Instructions defining agent behavior and role
-      </li>
-      <li>
-        <strong>User Prompt</strong>: Input text or data to process
-      </li>
-      <li>
-        <strong>Model</strong>: AI model selection (OpenAI, Anthropic, Google, etc.)
-      </li>
-      <li>
-        <strong>Temperature</strong>: Response randomness control (0-2)
-      </li>
-      <li>
-        <strong>Tools</strong>: Array of available tools for function calling
-      </li>
-      <li>
-        <strong>Response Format</strong>: JSON Schema for structured output
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>agent.content</strong>: Agent's response text or structured data
-      </li>
-      <li>
-        <strong>agent.tokens</strong>: Token usage statistics object
-      </li>
-      <li>
-        <strong>agent.tool_calls</strong>: Array of tool execution details
-      </li>
-      <li>
-        <strong>agent.cost</strong>: Estimated API call cost (if available)
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Content</strong>: Primary response output from the agent
-      </li>
-      <li>
-        <strong>Metadata</strong>: Usage statistics and execution details
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the agent
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Customer Support Automation
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Handle customer inquiries with database access</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>User submits support ticket via API block</li>
-    <li>Agent processes inquiry with product database tools</li>
-    <li>Agent generates response and creates follow-up ticket</li>
-    <li>Response block sends reply to customer</li>
-  </ol>
-</div>
-
-### Multi-Model Content Analysis
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Analyze content with different AI models</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Function block processes uploaded document</li>
-    <li>Agent with GPT-4o performs technical analysis</li>
-    <li>Agent with Claude analyzes sentiment and tone</li>
-    <li>Function block combines results for final report</li>
-  </ol>
-</div>
-
-### Tool-Powered Research Assistant
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Research assistant with web search and document access</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>User query received via input</li>
-    <li>Agent searches web using Google Search tool</li>
-    <li>Agent accesses Notion database for internal docs</li>
-    <li>Agent compiles comprehensive research report</li>
-  </ol>
-</div>
-
-## Best Practices
-
-- **Be specific in system prompts**: Clearly define the agent's role, tone, and limitations. The more specific your instructions are, the better the agent will be able to fulfill its intended purpose.
-- **Choose the right temperature setting**: Use lower temperature settings (0-0.3) when accuracy is important, or increase temperature (0.7-2.0) for more creative or varied responses
-- **Leverage tools effectively**: Integrate tools that complement the agent's purpose and enhance its capabilities. Be selective about which tools you provide to avoid overwhelming the agent. For tasks with little overlap, use another Agent block for the best results.

apps/docs/content/docs/blocks/api.mdx

@@ -1,234 +0,0 @@
----
-title: API
-description: Connect to external services through API endpoints
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The API block enables you to connect your workflow to external services through HTTP requests. It supports various methods like GET, POST, PUT, DELETE, and PATCH, allowing you to interact with virtually any API endpoint.
-
-<ThemeImage
-  lightSrc="/static/light/api-light.png"
-  darkSrc="/static/dark/api-dark.png"
-  alt="API Block"
-  width={350}
-  height={175}
-/>
-
-## Overview
-
-The API block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Connect to external services</strong>: Make HTTP requests to REST APIs and web services
-  </Step>
-  <Step>
-    <strong>Send and receive data</strong>: Process responses and transform data from external sources
-  </Step>
-  <Step>
-    <strong>Integrate third-party platforms</strong>: Connect with services like Stripe, Slack, or custom APIs
-  </Step>
-  <Step>
-    <strong>Handle authentication</strong>: Support various auth methods including Bearer tokens and API keys
-  </Step>
-</Steps>
-
-## Configuration Options
-
-### URL
-
-The endpoint URL for the API request. This can be:
-
-- A static URL entered directly in the block
-- A dynamic URL connected from another block's output
-- A URL with path parameters
-
-### Method
-
-Select the HTTP method for your request:
-
-- **GET**: Retrieve data from the server
-- **POST**: Send data to the server to create a resource
-- **PUT**: Update an existing resource on the server
-- **DELETE**: Remove a resource from the server
-- **PATCH**: Partially update an existing resource
-
-### Query Parameters
-
-Define key-value pairs that will be appended to the URL as query parameters. For example:
-
-```
-Key: apiKey
-Value: your_api_key_here
-
-Key: limit
-Value: 10
-```
-
-These would be added to the URL as `?apiKey=your_api_key_here&limit=10`.
-
-### Headers
-
-Configure HTTP headers for your request. Common headers include:
-
-```
-Key: Content-Type
-Value: application/json
-
-Key: Authorization
-Value: Bearer your_token_here
-```
-
-### Request Body
-
-For methods that support a request body (POST, PUT, PATCH), you can define the data to send. The body can be:
-
-- JSON data entered directly in the block
-- Data connected from another block's output
-- Dynamically generated during workflow execution
-
-### Accessing Results
-
-After an API request completes, you can access its outputs:
-
-- **`<api.data>`**: The response body data from the API
-- **`<api.status>`**: HTTP status code (200, 404, 500, etc.)
-- **`<api.headers>`**: Response headers from the server
-- **`<api.error>`**: Error details if the request failed
-
-## Advanced Features
-
-### Dynamic URL Construction
-
-Build URLs dynamically using variables from previous blocks:
-
-```javascript
-// In a Function block before the API
-const userId = <start.userId>;
-const apiUrl = `https://api.example.com/users/${userId}/profile`;
-```
-
-### Request Retries
-
-The API block automatically handles:
-- Network timeouts with exponential backoff
-- Rate limit responses (429 status codes)
-- Server errors (5xx status codes) with retry logic
-- Connection failures with reconnection attempts
-
-### Response Validation
-
-Validate API responses before processing:
-
-```javascript
-// In a Function block after the API
-if (<api.status> === 200) {
-  const data = <api.data>;
-  // Process successful response
-} else {
-  // Handle error response
-  console.error(`API Error: ${<api.status>}`);
-}
-```
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>URL</strong>: The endpoint to send the request to
-      </li>
-      <li>
-        <strong>Method</strong>: HTTP method (GET, POST, PUT, DELETE, PATCH)
-      </li>
-      <li>
-        <strong>Query Parameters</strong>: Key-value pairs for URL parameters
-      </li>
-      <li>
-        <strong>Headers</strong>: HTTP headers for authentication and content type
-      </li>
-      <li>
-        <strong>Body</strong>: Request payload for POST/PUT/PATCH methods
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>api.data</strong>: Response body data from the API call
-      </li>
-      <li>
-        <strong>api.status</strong>: HTTP status code returned by server
-      </li>
-      <li>
-        <strong>api.headers</strong>: Response headers from the server
-      </li>
-      <li>
-        <strong>api.error</strong>: Error details if request failed
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Response Data</strong>: Primary API response content
-      </li>
-      <li>
-        <strong>Status Information</strong>: HTTP status and error details
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the API call
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Fetch User Profile Data
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Retrieve user information from external service</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Function block constructs user ID from input</li>
-    <li>API block calls GET /users/&#123;id&#125; endpoint</li>
-    <li>Function block processes and formats user data</li>
-    <li>Response block returns formatted profile</li>
-  </ol>
-</div>
-
-### Create Support Ticket
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Submit support request to ticketing system</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Agent analyzes user issue and generates ticket data</li>
-    <li>API block POSTs ticket to support system</li>
-    <li>Condition block checks if ticket was created successfully</li>
-    <li>Response block confirms ticket creation with ID</li>
-  </ol>
-</div>
-
-### Payment Processing
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Process payment through Stripe API</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Function block validates payment data</li>
-    <li>API block creates payment intent via Stripe</li>
-    <li>Condition block handles payment success/failure</li>
-    <li>Function block updates order status in database</li>
-  </ol>
-</div>
-
-## Best Practices
-
-- **Use environment variables for sensitive data**: Don't hardcode API keys or credentials
-- **Handle errors gracefully**: Connect error handling logic for failed requests
-- **Validate responses**: Check status codes and response formats before processing data
-- **Respect rate limits**: Be mindful of API rate limits and implement appropriate throttling

apps/docs/content/docs/blocks/condition.mdx

@@ -1,236 +0,0 @@
----
-title: Condition
-description: Create conditional logic and branching in your workflows
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Condition block allows you to branch your workflow execution path based on boolean expressions. It evaluates conditions and routes the workflow accordingly, enabling you to create dynamic, responsive workflows with different execution paths.
-
-<ThemeImage
-  lightSrc="/static/light/condition-light.png"
-  darkSrc="/static/dark/condition-dark.png"
-  alt="Condition Block"
-  width={350}
-  height={175}
-/>
-
-<Callout>
-  Condition blocks enable deterministic decision-making without requiring an LLM, making them ideal
-  for straightforward branching logic.
-</Callout>
-
-## Overview
-
-The Condition block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Create branching logic</strong>: Route workflows based on boolean expressions
-  </Step>
-  <Step>
-    <strong>Make data-driven decisions</strong>: Evaluate conditions using previous block outputs
-  </Step>
-  <Step>
-    <strong>Handle multiple scenarios</strong>: Define multiple conditions with different paths
-  </Step>
-  <Step>
-    <strong>Provide deterministic routing</strong>: Make decisions without requiring an LLM
-  </Step>
-</Steps>
-
-## How It Works
-
-The Condition block operates through a sequential evaluation process:
-
-1. **Evaluate Expression** - Processes the JavaScript/TypeScript boolean expression using current workflow data
-2. **Determine Result** - Returns true or false based on the expression evaluation
-3. **Route Workflow** - Directs execution to the appropriate destination block based on the result  
-4. **Provide Context** - Generates metadata about the decision for debugging and monitoring
-
-## Configuration Options
-
-### Conditions
-
-Define one or more conditions that will be evaluated. Each condition includes:
-
-- **Expression**: A JavaScript/TypeScript expression that evaluates to true or false
-- **Path**: The destination block to route to if the condition is true
-- **Description**: Optional explanation of what the condition checks
-
-You can create multiple conditions that are evaluated in order, with the first matching condition determining the execution path.
-
-### Condition Expression Format
-
-Conditions use JavaScript syntax and can reference input values from previous blocks.
-
-<Tabs items={['Score Threshold', 'Text Analysis', 'Multiple Conditions']}>
-  <Tab>
-    ```javascript
-    // Check if a score is above a threshold
-    <agent.score> > 75
-    ```
-  </Tab>
-  <Tab>
-    ```javascript
-    // Check if a text contains specific keywords
-    <agent.text>.includes('urgent') || <agent.text>.includes('emergency')
-    ```
-  </Tab>
-  <Tab>
-    ```javascript
-    // Check multiple conditions
-    <agent.age> >= 18 && <agent.country> === 'US'
-    ```
-  </Tab>
-</Tabs>
-
-
-### Accessing Results
-
-After a condition evaluates, you can access its outputs:
-
-- **`<condition.result>`**: Boolean result of the condition evaluation
-- **`<condition.matched_condition>`**: ID of the condition that was matched
-- **`<condition.content>`**: Description of the evaluation result
-- **`<condition.path>`**: Details of the chosen routing destination
-
-## Advanced Features
-
-### Complex Expressions
-
-Use JavaScript operators and functions in conditions:
-
-```javascript
-// String operations
-<user.email>.endsWith('@company.com')
-
-// Array operations
-<api.tags>.includes('urgent')
-
-// Mathematical operations
-<agent.confidence> * 100 > 85
-
-// Date comparisons
-new Date(<api.created_at>) > new Date('2024-01-01')
-```
-
-### Multiple Condition Evaluation
-
-Conditions are evaluated in order until one matches:
-
-```javascript
-// Condition 1: Check for high priority
-<ticket.priority> === 'high'
-
-// Condition 2: Check for urgent keywords
-<ticket.subject>.toLowerCase().includes('urgent')
-
-// Condition 3: Default fallback
-true
-```
-
-### Error Handling
-
-Conditions automatically handle:
-- Undefined or null values with safe evaluation
-- Type mismatches with appropriate fallbacks
-- Invalid expressions with error logging
-- Missing variables with default values
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Conditions</strong>: Array of boolean expressions to evaluate
-      </li>
-      <li>
-        <strong>Expressions</strong>: JavaScript/TypeScript conditions using block outputs
-      </li>
-      <li>
-        <strong>Routing Paths</strong>: Destination blocks for each condition result
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>condition.result</strong>: Boolean result of condition evaluation
-      </li>
-      <li>
-        <strong>condition.matched_condition</strong>: ID of the matched condition
-      </li>
-      <li>
-        <strong>condition.content</strong>: Description of evaluation result
-      </li>
-      <li>
-        <strong>condition.path</strong>: Details of chosen routing destination
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Boolean Result</strong>: Primary condition evaluation outcome
-      </li>
-      <li>
-        <strong>Routing Information</strong>: Path selection and condition details
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the condition
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Customer Support Routing
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Route support tickets based on priority</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>API block fetches support ticket data</li>
-    <li>Condition checks if `<api.priority>` equals 'high'</li>
-    <li>High priority tickets → Agent with escalation tools</li>
-    <li>Normal priority tickets → Standard support agent</li>
-  </ol>
-</div>
-
-### Content Moderation
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Filter content based on analysis results</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Agent analyzes user-generated content</li>
-    <li>Condition checks if `<agent.toxicity_score>` > 0.7</li>
-    <li>Toxic content → Moderation workflow</li>
-    <li>Clean content → Publishing workflow</li>
-  </ol>
-</div>
-
-### User Onboarding Flow
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Personalize onboarding based on user type</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Function block processes user registration data</li>
-    <li>Condition checks if `<user.account_type>` === 'enterprise'</li>
-    <li>Enterprise users → Advanced setup workflow</li>
-    <li>Individual users → Simple onboarding workflow</li>
-  </ol>
-</div>
-
-## Best Practices
-
-- **Order conditions correctly**: Place more specific conditions before general ones to ensure specific logic takes precedence over fallbacks
-- **Include a default condition**: Add a catch-all condition (`true`) as the last condition to handle unmatched cases and prevent workflow execution from getting stuck
-- **Keep expressions simple**: Use clear, straightforward boolean expressions for better readability and easier debugging
-- **Document your conditions**: Add descriptions to explain the purpose of each condition for better team collaboration and maintenance
-- **Test edge cases**: Verify conditions handle boundary values correctly by testing with values at the edges of your condition ranges

apps/docs/content/docs/blocks/function.mdx

@@ -1,313 +0,0 @@
----
-title: Function
-description: Execute custom JavaScript or TypeScript code in your workflows
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Function block lets you run custom JavaScript or TypeScript code in your workflow. Use it to transform data, perform calculations, or implement custom logic that isn't available in other blocks.
-
-<ThemeImage
-  lightSrc="/static/light/function-light.png"
-  darkSrc="/static/dark/function-dark.png"
-  alt="Function Block with Code Editor"
-  width={350}
-  height={175}
-/>
-
-## Overview
-
-The Function block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Transform data</strong>: Convert formats, parse text, manipulate arrays and objects
-  </Step>
-  <Step>
-    <strong>Perform calculations</strong>: Math operations, statistics, financial calculations
-  </Step>
-  <Step>
-    <strong>Implement custom logic</strong>: Complex conditionals, loops, and algorithms
-  </Step>
-  <Step>
-    <strong>Process external data</strong>: Parse responses, format requests, handle authentication
-  </Step>
-</Steps>
-
-## How It Works
-
-The Function block runs your code in a secure, isolated environment:
-
-1. **Receive Input**: Access data from previous blocks via the `input` object
-2. **Execute Code**: Run your JavaScript/TypeScript code 
-3. **Return Results**: Use `return` to pass data to the next block
-4. **Handle Errors**: Built-in error handling and logging
-
-## Configuration Options
-
-### Code Editor
-
-Write your JavaScript/TypeScript code in a full-featured editor with:
-- Syntax highlighting and error checking
-- Line numbers and bracket matching
-- Support for modern JavaScript features
-- Native support for `fetch` 
-
-### Accessing Input Data
-
-Use the `input` object to access data from previous blocks:
-
-```javascript
-// Access data from connected blocks
-const userData = <agent.userData>;
-const orderData = <agent.orderData>;
-
-// Access specific fields
-const customerName = <agent.customer.name>;
-const total = <agent.order.total>;
-```
-
-### Common Examples
-
-**Data Transformation**:
-```javascript
-// Convert and format data
-const formatted = {
-  name: <agent.user.firstName> + ' ' + <agent.user.lastName>,
-  email: <agent.user.email>.toLowerCase(),
-  joinDate: new Date(<agent.user.created>).toLocaleDateString()
-};
-return formatted;
-```
-
-**Calculations**:
-```javascript
-// Calculate discounts and totals
-const subtotal = <agent.items>.reduce((sum, item) => sum + item.price, 0);
-const discount = subtotal > 100 ? 0.1 : 0;
-const total = subtotal * (1 - discount);
-
-return { subtotal, discount, total };
-```
-
-**Data Validation**:
-```javascript
-// Validate email format
-const email = <agent.email>;
-const isValid = /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(email);
-
-if (!isValid) {
-  throw new Error('Invalid email format');
-}
-return { email, isValid };
-```
-
-### Accessing Results
-
-After a function executes, you can access its outputs:
-
-- **`<function.result>`**: The value returned from your function
-- **`<function.stdout>`**: Any console.log() output from your code
-
-## Advanced Features
-
-### Async/Await Support
-
-Use async functions for complex operations:
-
-```javascript
-// Async function example
-const processData = async () => {
-  const data = <api.response>;
-  
-  // Process data with async operations
-  const processed = await Promise.all(
-    data.map(async (item) => {
-      return {
-        id: item.id,
-        processed: true,
-        timestamp: new Date().toISOString()
-      };
-    })
-  );
-  
-  return processed;
-};
-
-return await processData();
-```
-
-### Error Handling
-
-Implement robust error handling:
-
-```javascript
-try {
-  const result = <api.data>;
-  
-  if (!result || !result.length) {
-    throw new Error('No data received');
-  }
-  
-  return result.map(item => ({
-    id: item.id,
-    name: item.name.trim(),
-    valid: true
-  }));
-} catch (error) {
-  console.error('Processing failed:', error.message);
-  return { error: error.message, valid: false };
-}
-```
-
-### Performance Optimization
-
-Optimize for large datasets:
-
-```javascript
-// Efficient data processing
-const data = <api.large_dataset>;
-
-// Use efficient array methods
-const processed = data
-  .filter(item => item.status === 'active')
-  .map(item => ({
-    id: item.id,
-    summary: item.description.substring(0, 100)
-  }))
-  .slice(0, 1000); // Limit results
-
-return processed;
-```
-
-## Security and Limitations
-
-<Callout type="warning">
-  Functions run in a secure environment with these restrictions:
-  - **Execution timeout**: 30 seconds maximum to prevent infinite loops
-  - **Memory limits**: Limited memory to prevent resource exhaustion
-  - **No network access**: Cannot make HTTP requests (use API blocks instead)
-  - **Limited APIs**: Only safe JavaScript APIs are available
-</Callout>
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Code</strong>: Your JavaScript/TypeScript code to execute
-      </li>
-      <li>
-        <strong>Timeout</strong>: Maximum execution time (defaults to 30 seconds)
-      </li>
-      <li>
-        <strong>Input Data</strong>: All connected block outputs available via variables
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>function.result</strong>: The value returned from your function
-      </li>
-      <li>
-        <strong>function.stdout</strong>: Console.log() output from your code
-      </li>
-      <li>
-        <strong>function.error</strong>: Error details if function failed
-      </li>
-      <li>
-        <strong>function.execution_time</strong>: Time taken to execute
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Function Result</strong>: Primary output from your code
-      </li>
-      <li>
-        <strong>Debug Information</strong>: Logs and execution details
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the function
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Data Processing Pipeline
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Transform API response into structured data</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>API block fetches raw customer data</li>
-    <li>Function block processes and validates data</li>
-    <li>Function block calculates derived metrics</li>
-    <li>Response block returns formatted results</li>
-  </ol>
-</div>
-
-### Business Logic Implementation
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Calculate loyalty scores and tiers</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Agent retrieves customer purchase history</li>
-    <li>Function block calculates loyalty metrics</li>
-    <li>Function block determines customer tier</li>
-    <li>Condition block routes based on tier level</li>
-  </ol>
-</div>
-
-### Data Validation and Sanitization
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Validate and clean user input</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>User input received from form submission</li>
-    <li>Function block validates email format and phone numbers</li>
-    <li>Function block sanitizes and normalizes data</li>
-    <li>API block saves validated data to database</li>
-  </ol>
-</div>
-
-### Example: Loyalty Score Calculator
-
-```javascript title="loyalty-calculator.js"
-// Process customer data and calculate loyalty score
-const { purchaseHistory, accountAge, supportTickets } = <agent>;
-
-// Calculate metrics
-const totalSpent = purchaseHistory.reduce((sum, purchase) => sum + purchase.amount, 0);
-const purchaseFrequency = purchaseHistory.length / (accountAge / 365);
-const ticketRatio = supportTickets.resolved / supportTickets.total;
-
-// Calculate loyalty score (0-100)
-const spendScore = Math.min(totalSpent / 1000 * 30, 30);
-const frequencyScore = Math.min(purchaseFrequency * 20, 40);
-const supportScore = ticketRatio * 30;
-
-const loyaltyScore = Math.round(spendScore + frequencyScore + supportScore);
-
-return {
-  customer: <agent.name>,
-  loyaltyScore,
-  loyaltyTier: loyaltyScore >= 80 ? "Platinum" : loyaltyScore >= 60 ? "Gold" : "Silver",
-  metrics: { spendScore, frequencyScore, supportScore }
-};
-```
-
-## Best Practices
-
-- **Keep functions focused**: Write functions that do one thing well to improve maintainability and debugging
-- **Handle errors gracefully**: Use try/catch blocks to handle potential errors and provide meaningful error messages
-- **Test edge cases**: Ensure your code handles unusual inputs, null values, and boundary conditions correctly
-- **Optimize for performance**: Be mindful of computational complexity and memory usage for large datasets
-- **Use console.log() for debugging**: Leverage stdout output to debug and monitor function execution

apps/docs/content/docs/blocks/index.mdx

@@ -1,128 +0,0 @@
----
-title: Blocks
-description: The building components of your AI workflows
----
-
-import { Card, Cards } from 'fumadocs-ui/components/card'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { BlockTypes } from '@/components/ui/block-types'
-
-Blocks are the building components you connect together to create AI workflows. Think of them as specialized modules that each handle a specific task—from chatting with AI models to making API calls or processing data.
-
-<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
-  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/connections.mp4"></video>
-</div>
-
-## Core Block Types
-
-Sim Studio provides seven core block types that handle the essential functions of AI workflows:
-
-### Processing Blocks
-- **[Agent](/blocks/agent)** - Chat with AI models (OpenAI, Anthropic, Google, local models)
-- **[Function](/blocks/function)** - Run custom JavaScript/TypeScript code
-- **[API](/blocks/api)** - Connect to external services via HTTP requests
-
-### Logic Blocks
-- **[Condition](/blocks/condition)** - Branch workflow paths based on boolean expressions
-- **[Router](/blocks/router)** - Use AI to intelligently route requests to different paths
-- **[Evaluator](/blocks/evaluator)** - Score and assess content quality using AI
-
-### Output Blocks
-- **[Response](/blocks/response)** - Format and return final results from your workflow
-
-<BlockTypes />
-
-## How Blocks Work
-
-Each block has three main components:
-
-**Inputs**: Data coming into the block from other blocks or user input
-**Configuration**: Settings that control how the block behaves
-**Outputs**: Data the block produces for other blocks to use
-
-<Steps>
-  <Step>
-    <strong>Receive Input</strong>: Block receives data from connected blocks or user input
-  </Step>
-  <Step>
-    <strong>Process</strong>: Block processes the input according to its configuration
-  </Step>
-  <Step>
-    <strong>Output Results</strong>: Block produces output data for the next blocks in the workflow
-  </Step>
-</Steps>
-
-## Connecting Blocks
-
-You create workflows by connecting blocks together. The output of one block becomes the input of another:
-
-- **Drag to connect**: Drag from an output port to an input port
-- **Multiple connections**: One output can connect to multiple inputs
-- **Branching paths**: Some blocks can route to different paths based on conditions
-
-<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
-  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/connections.mp4"></video>
-</div>
-
-## Common Patterns
-
-### Sequential Processing
-Connect blocks in a chain where each block processes the output of the previous one:
-```
-User Input → Agent → Function → Response
-```
-
-### Conditional Branching
-Use Condition or Router blocks to create different paths:
-```
-User Input → Router → Agent A (for questions)
-                   → Agent B (for commands)
-```
-
-### Quality Control
-Use Evaluator blocks to assess and filter outputs:
-```
-Agent → Evaluator → Condition → Response (if good)
-                              → Agent (retry if bad)
-```
-
-## Block Configuration
-
-Each block type has specific configuration options:
-
-**All Blocks**:
-- Input/output connections
-- Error handling behavior
-- Execution timeout settings
-
-**AI Blocks** (Agent, Router, Evaluator):
-- Model selection (OpenAI, Anthropic, Google, local)
-- API keys and authentication
-- Temperature and other model parameters
-- System prompts and instructions
-
-**Logic Blocks** (Condition, Function):
-- Custom expressions or code
-- Variable references
-- Execution environment settings
-
-**Integration Blocks** (API, Response):
-- Endpoint configuration
-- Headers and authentication
-- Request/response formatting
-
-<Cards>
-  <Card title="Agent Block" href="/blocks/agent">
-    Connect to AI models and create intelligent responses
-  </Card>
-  <Card title="Function Block" href="/blocks/function">
-    Run custom code to process and transform data
-  </Card>
-  <Card title="API Block" href="/blocks/api">
-    Integrate with external services and APIs
-  </Card>
-  <Card title="Condition Block" href="/blocks/condition">
-    Create branching logic based on data evaluation
-  </Card>
-</Cards>

apps/docs/content/docs/blocks/loop.mdx

@@ -1,175 +0,0 @@
----
-title: Loop
-description: Create iterative workflows with loops that execute blocks repeatedly
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Loop block is a container block in Sim Studio that allows you to execute a group of blocks repeatedly. Loops enable iterative processing in your workflows.
-
-<ThemeImage
-  lightSrc="/static/light/loop-light.png"
-  darkSrc="/static/dark/loop-dark.png"
-  alt="Loop Block"
-  width={500}
-  height={300}
-/>
-
-<Callout type="info">
-  Loop blocks are container nodes that can hold other blocks inside them. The blocks inside a loop will execute multiple times based on your configuration.
-</Callout>
-
-## Overview
-
-The Loop block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Iterate over collections</strong>: Process arrays or objects one item at a time
-  </Step>
-  <Step>
-    <strong>Repeat operations</strong>: Execute blocks a fixed number of times
-  </Step>
-</Steps>
-
-## Configuration Options
-
-### Loop Type
-
-Choose between two types of loops:
-
-<Tabs items={['For Loop', 'ForEach Loop']}>
-  <Tab>
-    A numeric loop that executes a fixed number of times. Use this when you need to repeat an operation a specific number of times.
-    
-    ```
-    Example: Run 5 times
-    - Iteration 1
-    - Iteration 2
-    - Iteration 3
-    - Iteration 4
-    - Iteration 5
-    ```
-  </Tab>
-  <Tab>
-    A collection-based loop that iterates over each item in an array or object. Use this when you need to process a collection of items.
-    
-    ```
-    Example: Process ["apple", "banana", "orange"]
-    - Iteration 1: Process "apple"
-    - Iteration 2: Process "banana"
-    - Iteration 3: Process "orange"
-    ```
-  </Tab>
-</Tabs>
-
-## How to Use Loops
-
-### Creating a Loop
-
-1. Drag a Loop block from the toolbar onto your canvas
-2. Configure the loop type and parameters
-3. Drag other blocks inside the loop container
-4. Connect the blocks as needed
-
-### Accessing Results
-
-After a loop completes, you can access aggregated results:
-
-- **`<loop.results>`**: Array of results from all loop iterations
-
-## Example Use Cases
-
-### Processing API Results
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Process multiple customer records</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>API block fetches customer list</li>
-    <li>ForEach loop iterates over each customer</li>
-    <li>Inside loop: Agent analyzes customer data</li>
-    <li>Inside loop: Function stores analysis results</li>
-  </ol>
-</div>
-
-### Iterative Content Generation
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Generate multiple variations</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Set For loop to 5 iterations</li>
-    <li>Inside loop: Agent generates content variation</li>
-    <li>Inside loop: Evaluator scores the content</li>
-    <li>After loop: Function selects best variation</li>
-  </ol>
-</div>
-
-## Advanced Features
-
-### Limitations
-
-<Callout type="warning">
-  Container blocks (Loops and Parallels) cannot be nested inside each other. This means:
-  - You cannot place a Loop block inside another Loop block
-  - You cannot place a Parallel block inside a Loop block
-  - You cannot place any container block inside another container block
-  
-  If you need multi-dimensional iteration, consider restructuring your workflow to use sequential loops or process data in stages.
-</Callout>
-
-<Callout type="info">
-  Loops execute sequentially, not in parallel. If you need concurrent execution, use the Parallel block instead.
-</Callout>
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Loop Type</strong>: Choose between 'for' or 'forEach'
-      </li>
-      <li>
-        <strong>Iterations</strong>: Number of times to execute (for loops)
-      </li>
-      <li>
-        <strong>Collection</strong>: Array or object to iterate over (forEach loops)
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>loop.currentItem</strong>: Current item being processed
-      </li>
-      <li>
-        <strong>loop.index</strong>: Current iteration number (0-based)
-      </li>
-      <li>
-        <strong>loop.items</strong>: Full collection (forEach loops)
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>loop.results</strong>: Array of all iteration results
-      </li>
-      <li>
-        <strong>Structure</strong>: Results maintain iteration order
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the loop
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Best Practices
-
-- **Set reasonable limits**: Keep iteration counts reasonable to avoid long execution times
-- **Use ForEach for collections**: When processing arrays or objects, use ForEach instead of For loops
-- **Handle errors gracefully**: Consider adding error handling inside loops for robust workflows 

apps/docs/content/docs/blocks/meta.json

@@ -1,15 +0,0 @@
-{
-  "title": "Blocks",
-  "pages": [
-    "agent",
-    "api",
-    "condition",
-    "function",
-    "evaluator",
-    "router",
-    "response",
-    "workflow",
-    "loop",
-    "parallel"
-  ]
-}

apps/docs/content/docs/blocks/parallel.mdx

@@ -1,210 +0,0 @@
----
-title: Parallel
-description: Execute multiple blocks concurrently for faster workflow processing
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Parallel block is a container block in Sim Studio that allows you to execute multiple instances of blocks concurrently.
-
-<ThemeImage
-  lightSrc="/static/light/parallel-light.png"
-  darkSrc="/static/dark/parallel-dark.png"
-  alt="Parallel Block"
-  width={500}
-  height={300}
-/>
-
-<Callout type="info">
-  Parallel blocks are container nodes that execute their contents multiple times simultaneously, unlike loops which execute sequentially.
-</Callout>
-
-## Overview
-
-The Parallel block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Distribute work</strong>: Process multiple items concurrently
-  </Step>
-  <Step>
-    <strong>Speed up execution</strong>: Run independent operations simultaneously
-  </Step>
-  <Step>
-    <strong>Handle bulk operations</strong>: Process large datasets efficiently
-  </Step>
-  <Step>
-    <strong>Aggregate results</strong>: Collect outputs from all parallel executions
-  </Step>
-</Steps>
-
-## Configuration Options
-
-### Parallel Type
-
-Choose between two types of parallel execution:
-
-<Tabs items={['Count-based', 'Collection-based']}>
-  <Tab>
-    Execute a fixed number of parallel instances. Use this when you need to run the same operation multiple times concurrently.
-    
-    ```
-    Example: Run 5 parallel instances
-    - Instance 1 ┐
-    - Instance 2 ├─ All execute simultaneously
-    - Instance 3 │
-    - Instance 4 │
-    - Instance 5 ┘
-    ```
-  </Tab>
-  <Tab>
-    Distribute a collection across parallel instances. Each instance processes one item from the collection simultaneously.
-    
-    ```
-    Example: Process ["task1", "task2", "task3"] in parallel
-    - Instance 1: Process "task1" ┐
-    - Instance 2: Process "task2" ├─ All execute simultaneously
-    - Instance 3: Process "task3" ┘
-    ```
-  </Tab>
-</Tabs>
-
-## How to Use Parallel Blocks
-
-### Creating a Parallel Block
-
-1. Drag a Parallel block from the toolbar onto your canvas
-2. Configure the parallel type and parameters
-3. Drag a single block inside the parallel container
-4. Connect the block as needed
-
-### Accessing Results
-
-After a parallel block completes, you can access aggregated results:
-
-- **`<parallel.results>`**: Array of results from all parallel instances
-
-## Example Use Cases
-
-### Batch API Processing
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Process multiple API calls simultaneously</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Parallel block with collection of API endpoints</li>
-    <li>Inside parallel: API block calls each endpoint</li>
-    <li>After parallel: Process all responses together</li>
-  </ol>
-</div>
-
-### Multi-Model AI Processing
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Get responses from multiple AI models</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Count-based parallel set to 3 instances</li>
-    <li>Inside parallel: Agent configured with different model per instance</li>
-    <li>After parallel: Compare and select best response</li>
-  </ol>
-</div>
-
-## Advanced Features
-
-### Result Aggregation
-
-Results from all parallel instances are automatically collected:
-
-```javascript
-// In a Function block after the parallel
-const allResults = input.parallel.results;
-// Returns: [result1, result2, result3, ...]
-```
-
-### Instance Isolation
-
-Each parallel instance runs independently:
-- Separate variable scopes
-- No shared state between instances
-- Failures in one instance don't affect others
-
-### Limitations
-
-<Callout type="warning">
-  Container blocks (Loops and Parallels) cannot be nested inside each other. This means:
-  - You cannot place a Loop block inside a Parallel block
-  - You cannot place another Parallel block inside a Parallel block
-  - You cannot place any container block inside another container block
-</Callout>
-
-<Callout type="warning">
-  Parallel blocks can only contain a single block. You cannot have multiple blocks connected to each other inside a parallel - only the first block would execute in that case.
-</Callout>
-
-<Callout type="info">
-  While parallel execution is faster, be mindful of:
-  - API rate limits when making concurrent requests
-  - Memory usage with large datasets
-  - Maximum of 20 concurrent instances to prevent resource exhaustion
-</Callout>
-
-## Parallel vs Loop
-
-Understanding when to use each:
-
-| Feature | Parallel | Loop |
-|---------|----------|------|
-| Execution | Concurrent | Sequential |
-| Speed | Faster for independent operations | Slower but ordered |
-| Order | No guaranteed order | Maintains order |
-| Use case | Independent operations | Dependent operations |
-| Resource usage | Higher | Lower |
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Parallel Type</strong>: Choose between 'count' or 'collection'
-      </li>
-      <li>
-        <strong>Count</strong>: Number of instances to run (count-based)
-      </li>
-      <li>
-        <strong>Collection</strong>: Array or object to distribute (collection-based)
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>parallel.currentItem</strong>: Item for this instance
-      </li>
-      <li>
-        <strong>parallel.index</strong>: Instance number (0-based)
-      </li>
-      <li>
-        <strong>parallel.items</strong>: Full collection (collection-based)
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>parallel.results</strong>: Array of all instance results
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the parallel
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Best Practices
-
-- **Independent operations only**: Ensure operations don't depend on each other
-- **Handle rate limits**: Add delays or throttling for API-heavy workflows
-- **Error handling**: Each instance should handle its own errors gracefully 

apps/docs/content/docs/blocks/response.mdx

@@ -1,185 +0,0 @@
----
-title: Response
-description: Send a structured response back to API calls
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Response block is the final step in your workflow that formats and returns data to whoever called your workflow. It's like the "return" statement for your entire workflow—it packages up results and sends them back.
-
-<ThemeImage
-  lightSrc="/static/light/response-light.png"
-  darkSrc="/static/dark/response-dark.png"
-  alt="Response Block Configuration"
-  width={350}
-  height={175}
-/>
-
-<Callout type="info">
-  Response blocks are terminal blocks - they end the workflow execution and cannot connect to other blocks.
-</Callout>
-
-## When You Need Response Blocks
-
-**API Endpoints**: When your workflow is called via API, Response blocks format the return data
-**Webhooks**: Return confirmation or data back to the calling system
-**Testing**: See formatted results when testing your workflow
-**Data Export**: Structure data for external systems or reports
-
-## Two Ways to Build Responses
-
-### Builder Mode (Recommended)
-Visual interface for building response structure:
-- Drag and drop fields
-- Reference workflow variables easily
-- Visual preview of response structure
-
-### Editor Mode (Advanced)
-Write JSON directly:
-- Full control over response format
-- Support for complex nested structures
-- Use `<variable.name>` syntax for dynamic values
-
-## Configuration Options
-
-### Response Data
-
-The response data is the main content that will be sent back to the API caller. This should be formatted as JSON and can include:
-
-- Static values
-- Dynamic references to workflow variables using the `<variable.name>` syntax
-- Nested objects and arrays
-- Any valid JSON structure
-
-### Status Code
-
-Set the HTTP status code for the response. Common status codes include:
-
-<Tabs items={['Success (2xx)', 'Client Error (4xx)', 'Server Error (5xx)']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>200</strong>: OK - Standard success response</li>
-      <li><strong>201</strong>: Created - Resource successfully created</li>
-      <li><strong>204</strong>: No Content - Success with no response body</li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>400</strong>: Bad Request - Invalid request parameters</li>
-      <li><strong>401</strong>: Unauthorized - Authentication required</li>
-      <li><strong>404</strong>: Not Found - Resource doesn't exist</li>
-      <li><strong>422</strong>: Unprocessable Entity - Validation errors</li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>500</strong>: Internal Server Error - Server-side error</li>
-      <li><strong>502</strong>: Bad Gateway - External service error</li>
-      <li><strong>503</strong>: Service Unavailable - Service temporarily down</li>
-    </ul>
-  </Tab>
-</Tabs>
-
-<p className="mt-4 text-sm text-gray-600 dark:text-gray-400">
-  Default status code is 200 if not specified.
-</p>
-
-### Response Headers
-
-Configure additional HTTP headers to include in the response.
-
-Headers are configured as key-value pairs:
-
-| Key | Value |
-|-----|-------|
-| Content-Type | application/json |
-| Cache-Control | no-cache |
-| X-API-Version | 1.0 |
-
-## Inputs and Outputs
-
-<Tabs items={['Inputs', 'Outputs']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>data</strong> (JSON, optional): The JSON data to send in the response body
-      </li>
-      <li>
-        <strong>status</strong> (number, optional): HTTP status code (default: 200)
-      </li>
-      <li>
-        <strong>headers</strong> (JSON, optional): Additional response headers
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>data</strong>: The response body data</li>
-      <li><strong>status</strong>: HTTP status code</li>
-      <li><strong>headers</strong>: Response headers</li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Variable References
-
-Use the `<variable.name>` syntax to dynamically insert workflow variables into your response:
-
-```json
-{
-  "user": {
-    "id": "<variable.userId>",
-    "name": "<variable.userName>",
-    "email": "<variable.userEmail>"
-  },
-  "query": "<variable.searchQuery>",
-  "results": "<variable.searchResults>",
-  "totalFound": "<variable.resultCount>",
-  "processingTime": "<variable.executionTime>ms"
-}
-```
-
-<Callout type="warning">
-  Variable names are case-sensitive and must match exactly with the variables available in your workflow.
-</Callout>
-
-## Example Usage
-
-Here's an example of how a Response block might be configured for a user search API:
-
-```yaml
-data: |
-  {
-    "success": true,
-    "data": {
-      "users": "<variable.searchResults>",
-      "pagination": {
-        "page": "<variable.currentPage>",
-        "limit": "<variable.pageSize>",
-        "total": "<variable.totalUsers>"
-      }
-    },
-    "query": {
-      "searchTerm": "<variable.searchTerm>",
-      "filters": "<variable.appliedFilters>"
-    },
-    "timestamp": "<variable.timestamp>"
-  }
-status: 200
-headers:
-  - key: X-Total-Count
-    value: <variable.totalUsers>
-  - key: Cache-Control
-    value: public, max-age=300
-```
-
-## Best Practices
-
-- **Use meaningful status codes**: Choose appropriate HTTP status codes that accurately reflect the outcome of the workflow
-- **Structure your responses consistently**: Maintain a consistent JSON structure across all your API endpoints for better developer experience
-- **Include relevant metadata**: Add timestamps and version information to help with debugging and monitoring
-- **Handle errors gracefully**: Use conditional logic in your workflow to set appropriate error responses with descriptive messages
-- **Validate variable references**: Ensure all referenced variables exist and contain the expected data types before the Response block executes

apps/docs/content/docs/blocks/router.mdx

@@ -1,258 +0,0 @@
----
-title: Router
-description: Route workflow execution based on specific conditions or logic
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Router block uses AI to intelligently decide which path your workflow should take next. Unlike Condition blocks that use simple rules, Router blocks can understand context and make smart routing decisions based on content analysis.
-
-<ThemeImage
-  lightSrc="/static/light/router-light.png"
-  darkSrc="/static/dark/router-dark.png"
-  alt="Router Block with Multiple Paths"
-  width={350}
-  height={175}
-/>
-
-## Overview
-
-The Router block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Intelligent content routing</strong>: Use AI to understand intent and context
-  </Step>
-  <Step>
-    <strong>Dynamic path selection</strong>: Route workflows based on unstructured content analysis
-  </Step>
-  <Step>
-    <strong>Context-aware decisions</strong>: Make smart routing choices beyond simple rules
-  </Step>
-  <Step>
-    <strong>Multi-path management</strong>: Handle complex workflows with multiple potential destinations
-  </Step>
-</Steps>
-
-## Router vs Condition Blocks
-
-<Accordions>
-  <Accordion title="When to Use Router">
-    - AI-powered content analysis needed
-    - Unstructured or varying content types
-    - Intent-based routing (e.g., "route support tickets to departments")
-    - Context-aware decision making required
-  </Accordion>
-  <Accordion title="When to Use Condition">
-    - Simple, rule-based decisions
-    - Structured data or numeric comparisons
-    - Fast, deterministic routing needed
-    - Boolean logic sufficient
-  </Accordion>
-</Accordions>
-
-## How It Works
-
-The Router block:
-
-<Steps>
-  <Step>
-    <strong>Analyze content</strong>: Uses an LLM to understand input content and context
-  </Step>
-  <Step>
-    <strong>Evaluate targets</strong>: Compares content against available destination blocks
-  </Step>
-  <Step>
-    <strong>Select destination</strong>: Identifies the most appropriate path based on intent
-  </Step>
-  <Step>
-    <strong>Route execution</strong>: Directs workflow to the selected block
-  </Step>
-</Steps>
-
-## Configuration Options
-
-### Content/Prompt
-
-The content or prompt that the Router will analyze to make routing decisions. This can be:
-
-- A direct user query or input
-- Output from a previous block
-- A system-generated message
-
-### Target Blocks
-
-The possible destination blocks that the Router can select from. The Router will automatically detect connected blocks, but you can also:
-
-- Customize the descriptions of target blocks to improve routing accuracy
-- Specify routing criteria for each target block
-- Exclude certain blocks from being considered as routing targets
-
-### Model Selection
-
-Choose an AI model to power the routing decision:
-
-**OpenAI**: GPT-4o, o1, o3, o4-mini, gpt-4.1  \
-**Anthropic**: Claude 3.7 Sonnet \
-**Google**: Gemini 2.5 Pro, Gemini 2.0 Flash \
-**Other Providers**: Groq, Cerebras, xAI, DeepSeek \
-**Local Models**: Any model running on Ollama 
-
-<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
-  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/router-model-dropdown.mp4"></video>
-</div>
-
-**Recommendation**: Use models with strong reasoning capabilities like GPT-4o or Claude 3.7 Sonnet for more accurate routing decisions.
-
-### API Key
-
-Your API key for the selected LLM provider. This is securely stored and used for authentication.
-
-### Accessing Results
-
-After a router makes a decision, you can access its outputs:
-
-- **`<router.content>`**: Summary of the routing decision made
-- **`<router.selected_path>`**: Details of the chosen destination block
-- **`<router.tokens>`**: Token usage statistics from the LLM
-- **`<router.model>`**: The model used for decision-making
-
-## Advanced Features
-
-### Custom Routing Criteria
-
-Define specific criteria for each target block:
-
-```javascript
-// Example routing descriptions
-Target Block 1: "Technical support issues, API problems, integration questions"
-Target Block 2: "Billing inquiries, subscription changes, payment issues"
-Target Block 3: "General questions, feedback, feature requests"
-```
-
-### Multi-Model Routing
-
-Use different models for different routing scenarios:
-
-```javascript
-// Fast routing for simple cases
-Model: GPT-4o-mini
-Criteria: Simple, common routing patterns
-
-// Complex routing for nuanced decisions
-Model: Claude 3.7 Sonnet
-Criteria: Complex content analysis required
-```
-
-### Fallback Handling
-
-Implement robust fallback mechanisms:
-
-```javascript
-// Router configuration
-Primary Targets: ["Support", "Sales", "Technical"]
-Fallback Target: "General" // Default when no specific match
-Confidence Threshold: 0.7 // Minimum confidence for routing
-```
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Content/Prompt</strong>: Text to analyze for routing decisions
-      </li>
-      <li>
-        <strong>Target Blocks</strong>: Connected blocks as potential destinations
-      </li>
-      <li>
-        <strong>Model</strong>: AI model for routing analysis
-      </li>
-      <li>
-        <strong>API Key</strong>: Authentication for selected LLM provider
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>router.content</strong>: Summary of routing decision
-      </li>
-      <li>
-        <strong>router.selected_path</strong>: Details of chosen destination
-      </li>
-      <li>
-        <strong>router.tokens</strong>: Token usage statistics
-      </li>
-      <li>
-        <strong>router.model</strong>: Model used for decision-making
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Routing Decision</strong>: Primary path selection result
-      </li>
-      <li>
-        <strong>Decision Context</strong>: Analysis summary and reasoning
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the router
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Customer Support Triage
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Route support tickets to specialized departments</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>User submits support request via form</li>
-    <li>Router analyzes ticket content and context</li>
-    <li>Technical issues → Engineering support agent</li>
-    <li>Billing questions → Finance support agent</li>
-  </ol>
-</div>
-
-### Content Classification
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Classify and route user-generated content</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>User submits content or feedback</li>
-    <li>Router analyzes content type and sentiment</li>
-    <li>Feature requests → Product team workflow</li>
-    <li>Bug reports → Technical support workflow</li>
-  </ol>
-</div>
-
-### Lead Qualification
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Route leads based on qualification criteria</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Lead information captured from form</li>
-    <li>Router analyzes company size, industry, and needs</li>
-    <li>Enterprise leads → Sales team with custom pricing</li>
-    <li>SMB leads → Self-service onboarding flow</li>
-  </ol>
-</div>
-
-
-## Best Practices
-
-- **Provide clear target descriptions**: Help the Router understand when to select each destination with specific, detailed descriptions
-- **Use specific routing criteria**: Define clear conditions and examples for each path to improve accuracy
-- **Implement fallback paths**: Connect a default destination for when no specific path is appropriate
-- **Test with diverse inputs**: Ensure the Router handles various input types, edge cases, and unexpected content
-- **Monitor routing performance**: Review routing decisions regularly and refine criteria based on actual usage patterns
-- **Choose appropriate models**: Use models with strong reasoning capabilities for complex routing decisions

apps/docs/content/docs/blocks/workflow.mdx

@@ -1,259 +0,0 @@
----
-title: Workflow
-description: Execute other workflows as reusable components within your current workflow
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Workflow block allows you to execute other workflows as reusable components within your current workflow. This powerful feature enables modular design, code reuse, and the creation of complex nested workflows that can be composed from smaller, focused workflows.
-
-<ThemeImage
-  lightSrc="/static/light/workflow-light.png"
-  darkSrc="/static/dark/workflow-dark.png"
-  alt="Workflow Block"
-  width={300}
-  height={175}
-/>
-
-<Callout type="info">
-  Workflow blocks enable modular design by allowing you to compose complex workflows from smaller, reusable components.
-</Callout>
-
-## Overview
-
-The Workflow block serves as a bridge between workflows, enabling you to:
-
-<Steps>
-  <Step>
-    <strong>Reuse existing workflows</strong>: Execute previously created workflows as components within new workflows
-  </Step>
-  <Step>
-    <strong>Create modular designs</strong>: Break down complex processes into smaller, manageable workflows
-  </Step>
-  <Step>
-    <strong>Maintain separation of concerns</strong>: Keep different business logic isolated in separate workflows
-  </Step>
-  <Step>
-    <strong>Enable team collaboration</strong>: Share and reuse workflows across different projects and team members
-  </Step>
-</Steps>
-
-## How It Works
-
-The Workflow block:
-
-1. Takes a reference to another workflow in your workspace
-2. Passes input data from the current workflow to the child workflow
-3. Executes the child workflow in an isolated context
-4. Returns the results back to the parent workflow for further processing
-
-## Configuration Options
-
-### Workflow Selection
-
-Choose which workflow to execute from a dropdown list of available workflows in your workspace. The list includes:
-
-- All workflows you have access to in the current workspace
-- Workflows shared with you by other team members
-- Both enabled and disabled workflows (though only enabled workflows can be executed)
-
-### Input Data
-
-Define the data to pass to the child workflow:
-
-- **Single Variable Input**: Select a variable or block output to pass to the child workflow
-- **Variable References**: Use `<variable.name>` to reference workflow variables
-- **Block References**: Use `<blockName.field>` to reference outputs from previous blocks
-- **Automatic Mapping**: The selected data is automatically available as `start.input` in the child workflow
-- **Optional**: The input field is optional - child workflows can run without input data
-- **Type Preservation**: Variable types (strings, numbers, objects, etc.) are preserved when passed to the child workflow
-
-### Accessing Results
-
-After a workflow executes, you can access its outputs:
-
-- **`<workflow.response>`**: The complete output from the child workflow
-- **`<workflow.name>`**: The name of the executed child workflow
-- **`<workflow.success>`**: Boolean indicating successful completion
-- **`<workflow.error>`**: Error details if the workflow failed
-- **`<workflow.execution_time>`**: Time taken to execute the workflow
-
-### Execution Context
-
-The child workflow executes with:
-
-- Its own isolated execution context
-- Access to the same workspace resources (API keys, environment variables)
-- Proper workspace membership and permission checks
-- Independent logging and monitoring
-
-## Safety and Limitations
-
-To prevent infinite recursion and ensure system stability, the Workflow block includes several safety mechanisms:
-
-<Callout type="warning">
-  **Cycle Detection**: The system automatically detects and prevents circular dependencies between workflows to avoid infinite loops.
-</Callout>
-
-- **Maximum Depth Limit**: Nested workflows are limited to a maximum depth of 10 levels
-- **Cycle Detection**: Automatic detection and prevention of circular workflow dependencies
-- **Timeout Protection**: Child workflows inherit timeout settings to prevent indefinite execution
-- **Resource Limits**: Memory and execution time limits apply to prevent resource exhaustion
-
-## Advanced Features
-
-### Dynamic Workflow Selection
-
-Select workflows dynamically based on runtime conditions:
-
-```javascript
-// In a Function block before the Workflow block
-const workflowId = <condition.result> ? 'premium-workflow' : 'standard-workflow';
-return { selectedWorkflow: workflowId };
-```
-
-### Error Handling and Fallbacks
-
-Implement robust error handling for child workflows:
-
-```javascript
-// In a Function block after the Workflow block
-if (!<workflow.success>) {
-  console.error('Child workflow failed:', <workflow.error>);
-  // Implement fallback logic
-  return { fallback: true, error: <workflow.error> };
-}
-return <workflow.response>;
-```
-
-### Workflow Chaining
-
-Chain multiple workflows together:
-
-```javascript
-// Pass output from one workflow to another
-Workflow 1 Input: <start.input>
-Workflow 2 Input: <workflow1.response>
-Workflow 3 Input: <workflow2.response>
-```
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Workflow Selection</strong>: Choose which workflow to execute
-      </li>
-      <li>
-        <strong>Input Data</strong>: Variable or block reference to pass to child workflow
-      </li>
-      <li>
-        <strong>Execution Context</strong>: Isolated environment with workspace resources
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>workflow.response</strong>: Complete output from child workflow
-      </li>
-      <li>
-        <strong>workflow.name</strong>: Name of executed child workflow
-      </li>
-      <li>
-        <strong>workflow.success</strong>: Boolean indicating completion status
-      </li>
-      <li>
-        <strong>workflow.error</strong>: Error details if workflow failed
-      </li>
-      <li>
-        <strong>workflow.execution_time</strong>: Time taken to execute
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Workflow Response</strong>: Primary output from child workflow
-      </li>
-      <li>
-        <strong>Execution Status</strong>: Success status and error information
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the workflow
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Modular Customer Onboarding
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Break down complex onboarding into reusable components</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Main workflow receives customer data</li>
-    <li>Workflow block executes validation workflow</li>
-    <li>Workflow block executes account setup workflow</li>
-    <li>Workflow block executes welcome email workflow</li>
-  </ol>
-</div>
-
-### Microservice Architecture
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Create independent service workflows</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Payment processing workflow handles transactions</li>
-    <li>Inventory management workflow updates stock</li>
-    <li>Notification workflow sends confirmations</li>
-    <li>Main workflow orchestrates all services</li>
-  </ol>
-</div>
-
-### Conditional Processing
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Execute different workflows based on conditions</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Condition block evaluates user type</li>
-    <li>Enterprise users → Complex approval workflow</li>
-    <li>Standard users → Simple approval workflow</li>
-    <li>Free users → Basic processing workflow</li>
-  </ol>
-</div>
-
-### Example: Customer Validation Workflow
-
-```javascript title="validation-workflow.js"
-// Main workflow passes customer data to validation workflow
-const customerData = <start.input>;
-
-// Validation workflow processes the data
-const emailValid = /^[^\s@]+@[^\s@]+\.[^\s@]+$/.test(customerData.email);
-const phoneValid = /^\+?[1-9]\d{1,14}$/.test(customerData.phone);
-
-return {
-  customer: customerData,
-  validation: {
-    email: emailValid,
-    phone: phoneValid,
-    overall: emailValid && phoneValid
-  }
-};
-```
-
-## Best Practices
-
-- **Keep workflows focused**: Design child workflows to handle specific, well-defined tasks with clear inputs and outputs
-- **Minimize nesting depth**: Avoid deeply nested workflow hierarchies for better maintainability and performance
-- **Handle errors gracefully**: Implement proper error handling for child workflow failures and provide fallback mechanisms
-- **Document dependencies**: Clearly document which workflows depend on others and maintain dependency maps
-- **Test independently**: Ensure child workflows can be tested and validated independently from parent workflows
-- **Monitor performance**: Be aware that nested workflows can impact overall execution time and resource usage
-- **Use semantic naming**: Give workflows descriptive names that clearly indicate their purpose and functionality 

apps/docs/content/docs/execution/advanced.mdx

@@ -1,208 +0,0 @@
----
-title: Logging and Cost Calculation
-description: Understanding workflow logs and how execution costs are calculated in Sim Studio
----
-
-import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-Sim Studio provides comprehensive logging for workflow executions and automatic cost calculation for AI model usage.
-
-## Logging System
-
-Sim Studio offers two complementary logging interfaces:
-
-### Real-Time Console (Manual Executions)
-
-During manual workflow execution, logs appear in real-time in the Console panel on the right side of the workflow editor:
-
-<ThemeImage
-  lightSrc="/static/light/console-panel-light.png"
-  darkSrc="/static/dark/console-panel-dark.png"
-  alt="Real-time Console Panel"
-  width={600}
-  height={400}
-/>
-
-The console shows:
-- Block execution progress with active block highlighting
-- Real-time outputs as blocks complete
-- Execution timing for each block
-- Success/error status indicators
-
-### Logs Page (All Executions)
-
-All workflow executions—whether triggered manually, via API, Chat, Schedule, or Webhook—are logged to the dedicated Logs page:
-
-<ThemeImage
-  lightSrc="/static/light/logs-page-light.png"
-  darkSrc="/static/dark/logs-page-dark.png"
-  alt="Logs Page"
-  width={600}
-  height={400}
-/>
-
-The Logs page provides:
-- Comprehensive filtering by time range, status, trigger type, folder, and workflow
-- Search functionality across all logs
-- Live mode for real-time updates
-- 7-day log retention (upgradeable for longer retention)
-
-## Log Details Sidebar
-
-Clicking on any log entry opens a detailed sidebar view:
-
-<ThemeImage
-  lightSrc="/static/light/logs-sidebar-light.png"
-  darkSrc="/static/dark/logs-sidebar-dark.png"
-  alt="Logs Sidebar Details"
-  width={600}
-  height={400}
-/>
-
-### Block Input/Output
-
-View the complete data flow for each block with tabs to switch between:
-
-<Tabs items={['Output', 'Input']}>
-  <Tab>
-    **Output Tab** shows the block's execution result:
-    - Structured data with JSON formatting
-    - Markdown rendering for AI-generated content
-    - Copy button for easy data extraction
-  </Tab>
-  
-  <Tab>
-    **Input Tab** displays what was passed to the block:
-    - Resolved variable values
-    - Referenced outputs from other blocks
-    - Environment variables used
-    - API keys are automatically redacted for security
-  </Tab>
-</Tabs>
-
-### Execution Timeline
-
-For workflow-level logs, view detailed execution metrics:
-- Start and end timestamps
-- Total workflow duration
-- Individual block execution times
-- Performance bottleneck identification
-
-### Model Breakdown
-
-For workflows using AI blocks, expand the Model Breakdown section to see:
-
-<ThemeImage
-  lightSrc="/static/light/model-breakdown-light.png"
-  darkSrc="/static/dark/model-breakdown-dark.png"
-  alt="Model Breakdown"
-  width={600}
-  height={400}
-/>
-
-- **Token Usage**: Input and output token counts for each model
-- **Cost Breakdown**: Individual costs per model and operation
-- **Model Distribution**: Which models were used and how many times
-- **Total Cost**: Aggregate cost for the entire workflow execution
-
-### Workflow Snapshot
-
-For any logged execution, click "View Snapshot" to see the exact workflow state at execution time:
-
-<ThemeImage
-  lightSrc="/static/light/workflow-snapshot-light.png"
-  darkSrc="/static/dark/workflow-snapshot-dark.png"
-  alt="Workflow Snapshot"
-  width={600}
-  height={400}
-/>
-
-The snapshot provides:
-- Frozen canvas showing the workflow structure
-- Block states and connections as they were during execution
-- Click any block to see its inputs and outputs
-- Useful for debugging workflows that have since been modified
-
-<Callout type="info">
-  Workflow snapshots are only available for executions after the enhanced logging system was introduced. Older migrated logs show a "Logged State Not Found" message.
-</Callout>
-
-## Cost Calculation
-
-Sim Studio automatically calculates costs for all AI model usage:
-
-### How Costs Are Calculated
-
-```javascript
-cost = (inputTokens × inputPrice + outputTokens × outputPrice) / 1,000,000
-```
-
-<Callout type="info">
-  Prices are per million tokens. The calculation divides by 1,000,000 to get the actual cost.
-</Callout>
-
-### Pricing Options
-
-<Tabs items={['Hosted Models', 'Bring Your Own API Key']}>
-  <Tab>
-    **Hosted Models** - Sim Studio provides API keys with a 2.5x pricing multiplier:
-    
-    | Model | Base Price (Input/Output) | Hosted Price (Input/Output) |
-    |-------|---------------------------|----------------------------|
-    | GPT-4o | $2.50 / $10.00 | $6.25 / $25.00 |
-    | GPT-4.1 | $2.00 / $8.00 | $5.00 / $20.00 |
-    | o1 | $15.00 / $60.00 | $37.50 / $150.00 |
-    | o3 | $2.00 / $8.00 | $5.00 / $20.00 |
-    | Claude 3.5 Sonnet | $3.00 / $15.00 | $7.50 / $37.50 |
-    | Claude Opus 4.0 | $15.00 / $75.00 | $37.50 / $187.50 |
-    
-    *The 2.5x multiplier covers infrastructure and API management costs.*
-  </Tab>
-  
-  <Tab>
-    **Your Own API Keys** - Use any model at base pricing:
-    
-    | Provider | Models | Input / Output |
-    |----------|---------|----------------|
-    | Google | Gemini 2.5 | $0.15 / $0.60 |
-    | Deepseek | V3, R1 | $0.75 / $1.00 |
-    | xAI | Grok 4, Grok 3 | $5.00 / $25.00 |
-    | Groq | Llama 4 Scout | $0.40 / $0.60 |
-    | Cerebras | Llama 3.3 70B | $0.94 / $0.94 |
-    | Ollama | Local models | Free |
-    
-    *Pay providers directly with no markup*
-  </Tab>
-</Tabs>
-
-<Callout type="warning">
-  Pricing shown reflects rates as of July 14, 2025. Check provider documentation for current pricing.
-</Callout>
-
-### Cost Optimization
-
-<Accordions>
-  <Accordion title="Model Selection">
-    Choose models based on task complexity. Simple tasks can use GPT-4.1-nano ($0.10/$0.40) while complex reasoning might need o1 or Claude Opus.
-  </Accordion>
-  
-  <Accordion title="Prompt Engineering">
-    Well-structured, concise prompts reduce token usage without sacrificing quality.
-  </Accordion>
-  
-  <Accordion title="Local Models">
-    Use Ollama for non-critical tasks to eliminate API costs entirely.
-  </Accordion>
-</Accordions>
-
-## Usage Monitoring
-
-Monitor your usage and billing in Settings → Subscription:
-
-- **Current Usage**: Real-time usage and costs for the current period
-- **Usage Limits**: Plan limits with visual progress indicators
-- **Billing Details**: Projected charges and minimum commitments
-- **Plan Management**: Upgrade options and billing history

apps/docs/content/docs/execution/basics.mdx

@@ -1,248 +0,0 @@
----
-title: Execution Basics
-description: Understanding the fundamental execution flow in Sim Studio
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { File, Files, Folder } from 'fumadocs-ui/components/files'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-import {
-  AgentIcon,
-  ApiIcon,
-  ChartBarIcon,
-  CodeIcon,
-  ConditionalIcon,
-  ConnectIcon,
-  ResponseIcon,
-  StarterIcon,
-  LoopIcon,
-  ParallelIcon,
-} from '@/components/icons'
-
-When you run a workflow in Sim Studio, the execution engine follows a systematic process to ensure blocks are executed in the correct order with proper data flow.
-
-## Execution Flow
-
-The execution engine runs workflows in layers, processing blocks based on their dependencies:
-
-<Steps>
-  <Step>
-    <strong>Validation</strong>: Ensures the workflow has a starter block with no incoming connections and all blocks are properly connected.
-  </Step>
-
-  <Step>
-    <strong>Layer-based Execution</strong>: Identifies which blocks can execute next based on completed dependencies and executes them in parallel.
-  </Step>
-
-  <Step>
-    <strong>Path Updates</strong>: Router and Condition blocks update the active execution path, determining which blocks execute next.
-  </Step>
-
-  <Step>
-    <strong>Iteration Processing</strong>: Loop and Parallel blocks manage iterations and create virtual instances for concurrent execution.
-  </Step>
-
-  <Step>
-    <strong>Result Collection</strong>: Outputs from the final blocks are collected and returned as the workflow result.
-  </Step>
-</Steps>
-
-## Block Types and Execution
-
-Different block types have different execution behaviors:
-
-<Tabs items={['Orchestration Blocks', 'Processing Blocks', 'Integration Blocks']}>
-  <Tab>
-    <Card>
-      Orchestration blocks control the flow of execution through your workflow.
-      <Files>
-        <File
-          name="Starter Block"
-          icon={<StarterIcon className="h-4 w-4" />}
-          annotation="Initiates workflow execution and provides initial input values. Every workflow must have exactly one starter block."
-        />
-        <File
-          name="Router Block"
-          icon={<ConnectIcon className="h-4 w-4" />}
-          annotation="Directs execution along specific paths based on dynamic decisions. Uses an AI model to select one of multiple possible paths."
-        />
-        <File
-          name="Condition Block"
-          icon={<ConditionalIcon className="h-4 w-4" />}
-          annotation="Executes different paths based on conditional logic. Evaluates JavaScript expressions to determine which path to follow."
-        />
-        <File
-          name="Loop Block"
-          icon={<LoopIcon className="h-4 w-4" />}
-          annotation="Executes blocks repeatedly for a fixed number of iterations or over a collection. Manages iteration state and provides access to current item."
-        />
-        <File
-          name="Parallel Block"
-          icon={<ParallelIcon className="h-4 w-4" />}
-          annotation="Executes blocks concurrently across multiple instances. Distributes work based on count or collection for faster processing."
-        />
-      </Files>
-    </Card>
-  </Tab>
-
-<Tab>
-  <Card>
-    Processing blocks transform data and generate new outputs.
-    <Files>
-      <File
-        name="Agent Block"
-        icon={<AgentIcon className="h-4 w-4" />}
-        annotation="Interacts with AI models to generate content. Executes prompts against various LLM providers."
-      />
-      <File
-        name="Function Block"
-        icon={<CodeIcon className="h-4 w-4" />}
-        annotation="Executes custom JavaScript/TypeScript code. Runs in a secure sandbox environment with access to connected block outputs."
-      />
-      <File
-        name="Evaluator Block"
-        icon={<ChartBarIcon className="h-4 w-4" />}
-        annotation="Assesses outputs against defined criteria. Uses AI to evaluate content based on custom metrics."
-      />
-      <File
-        name="Workflow Block"
-        icon={<ConnectIcon className="h-4 w-4" />}
-        annotation="Execute nested workflows as a single block. Allows modular workflow design by embedding one workflow inside another."
-      />
-    </Files>
-  </Card>
-</Tab>
-
-  <Tab>
-    <Card>
-      Integration blocks connect with external systems.
-      <Files>
-        <File
-          name="API Block"
-          icon={<ApiIcon className="h-4 w-4" />}
-          annotation="Makes HTTP requests to external services. Configurable with headers, body, and authentication."
-        />
-        <File
-          name="Knowledge Base Block"
-          icon={
-            <svg className="h-4 w-4" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
-              <path d="M12 2L3 9V20C3 20.55 3.45 21 4 21H9V14H15V21H20C20.55 21 21 20.55 21 20V9L12 2Z" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round"/>
-              <circle cx="12" cy="10" r="2" stroke="currentColor" strokeWidth="2"/>
-            </svg>
-          }
-          annotation="Search and interact with knowledge bases. Performs semantic search, retrieves documents, and manages knowledge data."
-        />
-        <File
-          name="Response Block"
-          icon={<ResponseIcon className="h-4 w-4" />}
-          annotation="Format and return responses from workflows. Configure response data, status codes, and headers."
-        />
-        <File
-          name="Tool Blocks"
-          icon={<CodeIcon className="h-4 w-4" />}
-          annotation="Specialized blocks for specific services (Gmail, Slack, GitHub, etc.). Each has its own execution logic for the specific service."
-        />
-      </Files>
-    </Card>
-  </Tab>
-</Tabs>
-
-## Execution Methods
-
-Sim Studio offers multiple ways to trigger workflow execution:
-
-### Manual Execution
-
-Run workflows on-demand through the Sim Studio interface by clicking the "Run" button. This is perfect for:
-
-- Testing during development
-- One-off tasks
-- Workflows that need human supervision
-
-<ThemeImage
-  lightSrc="/static/light/manual-execution-light.png"
-  darkSrc="/static/dark/manual-execution-dark.png"
-  alt="Manual Execution"
-  width={600}
-  height={400}
-/>
-
-### Scheduled Execution
-
-Configure workflows to run automatically on a specified schedule:
-
-- Set up recurring executions using cron expressions
-- Define start times and frequency
-- Configure timezone settings
-- Set minimum and maximum execution intervals
-
-<ThemeImage
-  lightSrc="/static/light/scheduled-execution-light.png"
-  darkSrc="/static/dark/scheduled-execution-dark.png"
-  alt="Scheduled Execution"
-  width={600}
-  height={400}
-/>
-
-### API Endpoints
-
-Each workflow can be exposed as an API endpoint:
-
-- Get a unique URL for your workflow
-- Configure authentication requirements
-- Send custom inputs via POST requests
-- Receive execution results as JSON responses
-
-<ThemeImage
-  lightSrc="/static/light/api-execution-light.png"
-  darkSrc="/static/dark/api-execution-dark.png"
-  alt="API Execution"
-  width={600}
-  height={400}
-/>
-
-### Webhooks
-
-Configure workflows to execute in response to external events:
-
-- Set up webhook triggers from third-party services
-- Process incoming webhook data as workflow input
-- Configure webhook security settings
-- Support for specialized webhooks (GitHub, Stripe, etc.)
-
-<ThemeImage
-  lightSrc="/static/light/webhook-execution-light.png"
-  darkSrc="/static/dark/webhook-execution-dark.png"
-  alt="Webhook Execution"
-  width={600}
-  height={400}
-/>
-
-<Callout type="info">
-  The execution method you choose depends on your workflow's purpose. Manual execution is great for
-  development, while scheduled execution, API endpoints, and webhooks are better for production use
-  cases.
-</Callout>
-
-## Execution Context
-
-Each workflow execution maintains a context that tracks:
-
-- **Block States**: Outputs and execution status of each block
-- **Execution Path**: Active blocks based on routing decisions
-- **Loop/Parallel State**: Current iterations and distribution items
-- **Environment Variables**: Configuration values available during execution
-- **Execution Logs**: Detailed records of each block's execution
-
-## Real-Time Monitoring
-
-Monitor your workflow execution in real-time:
-
-- **Active Block Highlighting**: Currently executing blocks pulse with animation
-- **Live Logs**: Execution logs appear instantly in the logs panel
-- **Block States**: Visual indicators show success, error, or pending states
-- **Performance Metrics**: Execution time for each block
-
-These monitoring features help you understand workflow behavior and quickly identify any issues.

apps/docs/content/docs/execution/index.mdx

@@ -1,128 +0,0 @@
----
-title: Execution
-description: Understand how workflows are executed in Sim Studio
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Card, Cards } from 'fumadocs-ui/components/card'
-
-Sim Studio's execution engine brings your workflows to life by processing blocks in the correct order, managing data flow, and handling errors gracefully.
-
-<Callout type="info">
-  Every workflow execution follows a deterministic path based on your block connections and logic, ensuring predictable and reliable results.
-</Callout>
-
-## Documentation Overview
-
-<Cards>
-  <Card title="Execution Basics" href="/execution/basics">
-    Learn about the fundamental execution flow, block types, and how data flows through your
-    workflow
-  </Card>
-
-  <Card title="Logging and Cost Calculation" href="/execution/advanced">
-    Understand workflow logs and how execution costs are calculated in Sim Studio
-  </Card>
-</Cards>
-
-## Key Concepts
-
-### Topological Execution
-Blocks execute in dependency order, similar to how a spreadsheet recalculates cells. The execution engine automatically determines which blocks can run based on completed dependencies.
-
-### Path Tracking
-The engine actively tracks execution paths through your workflow. Router and Condition blocks dynamically update these paths, ensuring only relevant blocks execute.
-
-### Layer-Based Processing
-Instead of executing blocks one-by-one, the engine identifies layers of blocks that can run in parallel, optimizing performance for complex workflows.
-
-### Execution Context
-Each workflow maintains a rich context during execution containing:
-- Block outputs and states
-- Active execution paths
-- Loop and parallel iteration tracking
-- Environment variables
-- Routing decisions
-
-## Execution Triggers
-
-Workflows can be executed through multiple channels:
-
-- **Manual**: Test and debug directly in the editor
-- **Deploy as API**: Create an HTTP endpoint secured with API keys
-- **Deploy as Chat**: Create a conversational interface on a custom subdomain
-- **Webhooks**: Respond to external events from third-party services
-- **Scheduled**: Run on a recurring schedule using cron expressions
-
-### Deploy as API
-
-When you deploy a workflow as an API, Sim Studio:
-- Creates a unique HTTP endpoint: `https://simstudio.ai/api/workflows/{workflowId}/execute`
-- Generates an API key for authentication
-- Accepts POST requests with JSON payloads
-- Returns workflow execution results as JSON
-
-Example API call:
-```bash
-curl -X POST https://simstudio.ai/api/workflows/your-workflow-id/execute \
-  -H "X-API-Key: your-api-key" \
-  -H "Content-Type: application/json" \
-  -d '{"input": "your data here"}'
-```
-
-### Deploy as Chat
-
-Chat deployment creates a conversational interface for your workflow:
-- Hosted on a custom subdomain: `https://your-name.simstudio.ai`
-- Optional authentication (public, password, or email-based)
-- Customizable UI with your branding
-- Streaming responses for real-time interaction
-- Perfect for AI assistants, support bots, or interactive tools
-
-Each deployment method passes data to your workflow's starter block, beginning the execution flow.
-
-## Programmatic Execution
-
-Execute workflows from your applications using our official SDKs:
-
-```bash
-# TypeScript/JavaScript
-npm install simstudio-ts-sdk
-
-# Python
-pip install simstudio-sdk
-```
-
-```typescript
-// TypeScript Example
-import { SimStudioClient } from 'simstudio-ts-sdk';
-
-const client = new SimStudioClient({ 
-  apiKey: 'your-api-key' 
-});
-
-const result = await client.executeWorkflow('workflow-id', {
-  input: { message: 'Hello' }
-});
-```
-
-## Best Practices
-
-### Design for Reliability
-- Handle errors gracefully with appropriate fallback paths
-- Use environment variables for sensitive data
-- Add logging to Function blocks for debugging
-
-### Optimize Performance
-- Minimize external API calls where possible
-- Use parallel execution for independent operations
-- Cache results with Memory blocks when appropriate
-
-### Monitor Executions
-- Review logs regularly to understand performance patterns
-- Track costs for AI model usage
-- Use workflow snapshots to debug issues
-
-## What's Next?
-
-Start with [Execution Basics](/execution/basics) to understand how workflows run, then explore [Logging and Cost Calculation](/execution/advanced) to monitor and optimize your executions.

apps/docs/content/docs/execution/meta.json

@@ -1,4 +0,0 @@
-{
-  "title": "Execution",
-  "pages": ["basics", "advanced"]
-}

apps/docs/content/docs/getting-started/index.mdx

@@ -1,194 +0,0 @@
----
-title: Getting Started
-description: Build your first AI workflow in 5 minutes
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Card, Cards } from 'fumadocs-ui/components/card'
-import { File, Files, Folder } from 'fumadocs-ui/components/files'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { ThemeImage } from '@/components/ui/theme-image'
-import {
-  AgentIcon,
-  ApiIcon,
-  ChartBarIcon,
-  CodeIcon,
-  ConditionalIcon,
-  ConnectIcon,
-  ExaAIIcon,
-  FirecrawlIcon,
-  GmailIcon,
-  NotionIcon,
-  PerplexityIcon,
-  SlackIcon,
-} from '@/components/icons'
-
-This tutorial will guide you through building your first AI workflow in Sim Studio. We'll create a people research agent that can find information about individuals using state-of-the-art LLM-Search tools.
-
-<Callout type="info">
-  This tutorial takes about 10 minutes and covers the essential concepts of building workflows in Sim Studio.
-</Callout>
-
-## What We're Building
-
-A people research agent that:
-1. Receives a person's name via chat interface
-2. Uses an AI agent with advanced search capabilities
-3. Searches the web using state-of-the-art LLM-Search tools (Exa and Linkup)
-4. Extracts structured information using a response format
-5. Returns comprehensive data about the person
-
-<ThemeImage
-  lightSrc="/static/examples/started/started-1.png"
-  darkSrc="/static/examples/started/started-1.png"
-  alt="Getting Started Example"
-  width={800}
-  height={500}
-/>
-
-## Step-by-Step Tutorial
-
-<Steps>
-  <Step title="Create workflow and add AI agent">
-    Open Sim Studio and click "New Workflow" in the dashboard. Name it "Getting Started".
-    
-    When you create a new workflow, it automatically includes a **Start block** - this is the entry point that receives input from users. For this example, we'll be triggering the workflow via chat, so we don't need to configure anything on the Start block.
-    
-    Now drag an **Agent Block** onto the canvas from the blocks panel on the left.
-    
-    Configure the Agent Block:
-    - **Model**: Select "OpenAI GPT-4o"
-    - **System Prompt**: "You are a people research agent. When given a person's name, use your available search tools to find comprehensive information about them including their location, profession, educational background, and other relevant details."
-    - **User Prompt**: Drag the connection from the Start block's output into this field (this connects `<start.input>` to the user prompt)
-    
-    <div className="mx-auto w-full overflow-hidden rounded-lg">
-      <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/static/examples/started/started-2.mp4"></video>
-    </div>
-  </Step>
-  
-  <Step title="Add tools to the agent">
-    Let's enhance our agent with tools for better capabilities. Click on the Agent block to select it.
-    
-    In the **Tools** section:
-    - Click **Add Tool**
-    - Select **Exa** from the available tools
-    - Select **Linkup** from the available tools
-    - Add your API keys for both tools (this allows the agent to search the web and access additional information)
-    
-    <div className="mx-auto w-3/5 overflow-hidden rounded-lg">
-      <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/static/examples/started/started-3.mp4"></video>
-    </div>
-  </Step>
-  
-  <Step title="Test the basic workflow">
-    Now let's test our workflow. Go to the **Chat panel** on the right side of the screen.
-    
-    In the chat panel:
-    - Click the dropdown and select `agent1.content` (this will show us the output of our agent)
-    - Enter a test message like: "John is a software engineer from San Francisco who studied Computer Science at Stanford University."
-    - Click "Send" to run the workflow
-    
-    You should see the agent's response analyzing the person described in your text.
-    
-    <div className="mx-auto w-full overflow-hidden rounded-lg">
-      <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/static/examples/started/started-4.mp4"></video>
-    </div>
-  </Step>
-  
-  <Step title="Add structured output">
-    Now let's make our agent return structured data. Click on the Agent block to select it.
-    
-    In the **Response Format** section:
-    - Click the **magic wand icon** (✨) next to the schema field
-    - In the prompt that appears, type: "create a schema named person, that contains location, profession, and education"
-    - The AI will generate a JSON schema for you automatically
-    
-    <div className="mx-auto w-full overflow-hidden rounded-lg">
-      <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/static/examples/started/started-5.mp4"></video>
-    </div>
-  </Step>
-  
-  <Step title="Test the structured output">
-    Go back to the **Chat panel**.
-    
-    Since we added a response format, new output options are now available:
-    - Click the dropdown and select the new structured output option (the schema we just created)
-    - Enter a new test message like: "Sarah is a marketing manager from New York who has an MBA from Harvard Business School."
-    - Click "Send" to run the workflow again
-    
-    You should now see structured JSON output with the person's information organized into location, profession, and education fields.
-    
-    <div className="mx-auto w-full overflow-hidden rounded-lg">
-      <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/static/examples/started/started-6.mp4"></video>
-    </div>
-  </Step>
-</Steps>
-
-## What You Just Built
-
-Congratulations! You've created your first AI workflow that:
-- ✅ Receives text input via chat interface
-- ✅ Uses AI to extract information from unstructured text
-- ✅ Integrates external tools (Exa and Linkup) for enhanced capabilities
-- ✅ Returns structured JSON data using AI-generated schemas
-- ✅ Demonstrates workflow testing and iteration
-- ✅ Shows the power of visual workflow building
-
-## Key Concepts You Learned
-
-### Block Types Used
-
-<Files>
-  <File
-    name="Start Block"
-    icon={<ConnectIcon className="h-4 w-4" />}
-    annotation="Entry point for user input (auto-included)"
-  />
-  <File
-    name="Agent Block"
-    icon={<AgentIcon className="h-4 w-4" />}
-    annotation="AI model for text processing and analysis"
-  />
-</Files>
-
-### Core Workflow Concepts
-
-**Data Flow**: Variables flow between blocks by dragging connections
-
-**Chat Interface**: Test workflows in real-time using the chat panel with different output options
-
-**Tool Integration**: Enhance agent capabilities by adding external tools like Exa and Linkup
-
-**Variable References**: Access block outputs using `<blockName.output>` syntax
-
-**Structured Output**: Use JSON schemas to get consistent, structured data from AI
-
-**AI-Generated Schemas**: Use the magic wand (✨) to generate schemas with natural language
-
-**Iterative Development**: Test, modify, and re-test workflows easily
-
-## Next Steps
-
-<Cards>
-  <Card title="Add More Blocks" href="/blocks">
-    Learn about API, Function, and Condition blocks
-  </Card>
-  <Card title="Use Tools" href="/tools">
-    Integrate with external services like Gmail, Slack, and Notion
-  </Card>
-  <Card title="Add Custom Logic" href="/blocks/function">
-    Use Function blocks for custom data processing
-  </Card>
-  <Card title="Deploy Your Workflow" href="/execution">
-    Make your workflow accessible via REST API
-  </Card>
-</Cards>
-
-## Need Help?
-
-**Stuck on a step?** Check our [Blocks documentation](/blocks) for detailed explanations of each component.
-
-**Want to see more examples?** Browse our [Tools documentation](/tools) to see what integrations are available.
-
-**Ready to deploy?** Learn about [Execution and Deployment](/execution) to make your workflows live.

apps/docs/content/docs/introduction/index.mdx

@@ -1,94 +0,0 @@
----
-title: Introduction
-description: Build AI workflows visually without code
----
-
-import { Card, Cards } from 'fumadocs-ui/components/card'
-import { File, Files, Folder } from 'fumadocs-ui/components/files'
-import { Features } from '@/components/ui/features'
-
-Sim Studio is a visual workflow editor that enables you to build AI-powered applications by connecting blocks on a canvas. Drag and drop components to create chatbots, automation workflows, and data processing pipelines without writing code.
-
-## What Makes Sim Studio Powerful
-
-**Multi-Model AI Support** - Connect to OpenAI, Anthropic, Google, Groq, Cerebras, and local models through Ollama. Switch providers without rebuilding workflows.
-
-**60+ Pre-Built Tools** - Gmail, Slack, Notion, Google Sheets, Airtable, Supabase, Pinecone, and more. Extensible architecture allows custom tool integration.
-
-**Flexible Execution** - Run workflows via chat interface, REST API, webhooks, scheduled jobs, or trigger from external systems.
-
-**Production Deployment** - Deploy as APIs, integrate with existing systems using our SDK, or embed as plugins. Built-in monitoring, logging, and error handling.
-
-**Real-time Collaboration** - Work simultaneously with team members on the same workflow, like Google Docs for AI development.
-
-Connect multiple AI models, integrate with 60+ services, and deploy production-ready applications through an intuitive visual interface designed specifically for AI development.
-
-## Core Building Blocks
-
-**Processing Blocks**
-
-- **Agent** - Execute AI model inference with any LLM provider
-- **API** - Connect to REST endpoints and external services  
-- **Function** - Run custom JavaScript for data processing
-
-**Logic Blocks**
-
-- **Condition** - Create branching logic based on data evaluation
-- **Router** - Route execution paths using AI-powered decision making
-- **Loop** - Iterate over collections sequentially
-- **Parallel** - Execute multiple operations concurrently
-
-**Output Blocks**
-
-- **Response** - Format and return final workflow results
-- **Evaluator** - Validate outputs against defined criteria
-
-## Built-in Integrations
-
-**AI Models**: OpenAI, Anthropic, Google, Groq, Cerebras, Ollama
-
-**Communication**: Gmail, Slack, Telegram, WhatsApp, Microsoft Teams
-
-**Data Sources**: Notion, Google Sheets, Airtable, Supabase, Pinecone
-
-**Web Services**: Firecrawl, Google Search, Exa AI, Perplexity
-
-**Development**: GitHub, Jira, Linear, browser automation
-
-## Use Cases
-
-**AI Assistants** - Build chatbots with web search, calendar access, and email capabilities
-
-**Content Generation** - Create blog posts, social media content, and marketing materials
-
-**Data Processing** - Extract insights from documents, analyze datasets, and generate reports
-
-**Process Automation** - Automate business workflows with event-driven triggers
-
-**API Orchestration** - Combine multiple services into unified endpoints
-
-## Key Features
-
-**Multi-Provider AI Support** - Switch between OpenAI, Anthropic, Google, and local models without rebuilding workflows
-
-**Real-time Collaboration** - Work simultaneously with team members on the same workflow
-
-**Production-Ready** - Built-in error handling, logging, and monitoring for production deployments
-
-**Local Development** - Test with Ollama locally, then deploy with cloud providers
-
-## Getting Started
-
-Ready to build your first workflow? Our [Getting Started guide](/getting-started) will walk you through creating a customer support assistant in under 10 minutes.
-
-<Cards>
-  <Card title="Getting Started" href="/getting-started">
-    Build your first workflow
-  </Card>
-  <Card title="Blocks" href="/blocks">
-    Learn about workflow components
-  </Card>
-  <Card title="Tools" href="/tools">
-    Explore integrations
-  </Card>
-</Cards>

apps/docs/content/docs/sdks/python.mdx

@@ -1,409 +0,0 @@
----
-title: Python SDK
-description: The official Python SDK for Sim Studio
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Card, Cards } from 'fumadocs-ui/components/card'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-
-The official Python SDK for Sim Studio allows you to execute workflows programmatically from your Python applications.
-
-<Callout type="info">
-  The Python SDK supports Python 3.8+ and provides synchronous workflow execution. All workflow executions are currently synchronous.
-</Callout>
-
-## Installation
-
-Install the SDK using pip:
-
-```bash
-pip install simstudio-sdk
-```
-
-## Quick Start
-
-Here's a simple example to get you started:
-
-```python
-from simstudio import SimStudioClient
-
-# Initialize the client
-client = SimStudioClient(
-    api_key="your-api-key-here",
-    base_url="https://simstudio.ai"  # optional, defaults to https://simstudio.ai
-)
-
-# Execute a workflow
-try:
-    result = client.execute_workflow("workflow-id")
-    print("Workflow executed successfully:", result)
-except Exception as error:
-    print("Workflow execution failed:", error)
-```
-
-## API Reference
-
-### SimStudioClient
-
-#### Constructor
-
-```python
-SimStudioClient(api_key: str, base_url: str = "https://simstudio.ai")
-```
-
-**Parameters:**
-- `api_key` (str): Your Sim Studio API key
-- `base_url` (str, optional): Base URL for the Sim Studio API
-
-#### Methods
-
-##### execute_workflow()
-
-Execute a workflow with optional input data.
-
-```python
-result = client.execute_workflow(
-    "workflow-id",
-    input_data={"message": "Hello, world!"},
-    timeout=30.0  # 30 seconds
-)
-```
-
-**Parameters:**
-- `workflow_id` (str): The ID of the workflow to execute
-- `input_data` (dict, optional): Input data to pass to the workflow
-- `timeout` (float, optional): Timeout in seconds (default: 30.0)
-
-**Returns:** `WorkflowExecutionResult`
-
-##### get_workflow_status()
-
-Get the status of a workflow (deployment status, etc.).
-
-```python
-status = client.get_workflow_status("workflow-id")
-print("Is deployed:", status.is_deployed)
-```
-
-**Parameters:**
-- `workflow_id` (str): The ID of the workflow
-
-**Returns:** `WorkflowStatus`
-
-##### validate_workflow()
-
-Validate that a workflow is ready for execution.
-
-```python
-is_ready = client.validate_workflow("workflow-id")
-if is_ready:
-    # Workflow is deployed and ready
-    pass
-```
-
-**Parameters:**
-- `workflow_id` (str): The ID of the workflow
-
-**Returns:** `bool`
-
-##### execute_workflow_sync()
-
-<Callout type="info">
-  Currently, this method is identical to `execute_workflow()` since all executions are synchronous. This method is provided for future compatibility when asynchronous execution is added.
-</Callout>
-
-Execute a workflow (currently synchronous, same as `execute_workflow()`).
-
-```python
-result = client.execute_workflow_sync(
-    "workflow-id",
-    input_data={"data": "some input"},
-    timeout=60.0
-)
-```
-
-**Parameters:**
-- `workflow_id` (str): The ID of the workflow to execute
-- `input_data` (dict, optional): Input data to pass to the workflow
-- `timeout` (float): Timeout for the initial request in seconds
-
-**Returns:** `WorkflowExecutionResult`
-
-##### set_api_key()
-
-Update the API key.
-
-```python
-client.set_api_key("new-api-key")
-```
-
-##### set_base_url()
-
-Update the base URL.
-
-```python
-client.set_base_url("https://my-custom-domain.com")
-```
-
-##### close()
-
-Close the underlying HTTP session.
-
-```python
-client.close()
-```
-
-## Data Classes
-
-### WorkflowExecutionResult
-
-```python
-@dataclass
-class WorkflowExecutionResult:
-    success: bool
-    output: Optional[Any] = None
-    error: Optional[str] = None
-    logs: Optional[List[Any]] = None
-    metadata: Optional[Dict[str, Any]] = None
-    trace_spans: Optional[List[Any]] = None
-    total_duration: Optional[float] = None
-```
-
-### WorkflowStatus
-
-```python
-@dataclass
-class WorkflowStatus:
-    is_deployed: bool
-    deployed_at: Optional[str] = None
-    is_published: bool = False
-    needs_redeployment: bool = False
-```
-
-### SimStudioError
-
-```python
-class SimStudioError(Exception):
-    def __init__(self, message: str, code: Optional[str] = None, status: Optional[int] = None):
-        super().__init__(message)
-        self.code = code
-        self.status = status
-```
-
-## Examples
-
-### Basic Workflow Execution
-
-<Steps>
-  <Step title="Initialize the client">
-    Set up the SimStudioClient with your API key.
-  </Step>
-  <Step title="Validate the workflow">
-    Check if the workflow is deployed and ready for execution.
-  </Step>
-  <Step title="Execute the workflow">
-    Run the workflow with your input data.
-  </Step>
-  <Step title="Handle the result">
-    Process the execution result and handle any errors.
-  </Step>
-</Steps>
-
-```python
-import os
-from simstudio import SimStudioClient
-
-client = SimStudioClient(api_key=os.getenv("SIMSTUDIO_API_KEY"))
-
-def run_workflow():
-    try:
-        # Check if workflow is ready
-        is_ready = client.validate_workflow("my-workflow-id")
-        if not is_ready:
-            raise Exception("Workflow is not deployed or ready")
-
-        # Execute the workflow
-        result = client.execute_workflow(
-            "my-workflow-id",
-            input_data={
-                "message": "Process this data",
-                "user_id": "12345"
-            }
-        )
-
-        if result.success:
-            print("Output:", result.output)
-            print("Duration:", result.metadata.get("duration") if result.metadata else None)
-        else:
-            print("Workflow failed:", result.error)
-            
-    except Exception as error:
-        print("Error:", error)
-
-run_workflow()
-```
-
-### Error Handling
-
-Handle different types of errors that may occur during workflow execution:
-
-```python
-from simstudio import SimStudioClient, SimStudioError
-import os
-
-client = SimStudioClient(api_key=os.getenv("SIMSTUDIO_API_KEY"))
-
-def execute_with_error_handling():
-    try:
-        result = client.execute_workflow("workflow-id")
-        return result
-    except SimStudioError as error:
-        if error.code == "UNAUTHORIZED":
-            print("Invalid API key")
-        elif error.code == "TIMEOUT":
-            print("Workflow execution timed out")
-        elif error.code == "USAGE_LIMIT_EXCEEDED":
-            print("Usage limit exceeded")
-        elif error.code == "INVALID_JSON":
-            print("Invalid JSON in request body")
-        else:
-            print(f"Workflow error: {error}")
-        raise
-    except Exception as error:
-        print(f"Unexpected error: {error}")
-        raise
-```
-
-### Context Manager Usage
-
-Use the client as a context manager to automatically handle resource cleanup:
-
-```python
-from simstudio import SimStudioClient
-import os
-
-# Using context manager to automatically close the session
-with SimStudioClient(api_key=os.getenv("SIMSTUDIO_API_KEY")) as client:
-    result = client.execute_workflow("workflow-id")
-    print("Result:", result)
-# Session is automatically closed here
-```
-
-### Batch Workflow Execution
-
-Execute multiple workflows efficiently:
-
-```python
-from simstudio import SimStudioClient
-import os
-
-client = SimStudioClient(api_key=os.getenv("SIMSTUDIO_API_KEY"))
-
-def execute_workflows_batch(workflow_data_pairs):
-    """Execute multiple workflows with different input data."""
-    results = []
-    
-    for workflow_id, input_data in workflow_data_pairs:
-        try:
-            # Validate workflow before execution
-            if not client.validate_workflow(workflow_id):
-                print(f"Skipping {workflow_id}: not deployed")
-                continue
-                
-            result = client.execute_workflow(workflow_id, input_data)
-            results.append({
-                "workflow_id": workflow_id,
-                "success": result.success,
-                "output": result.output,
-                "error": result.error
-            })
-            
-        except Exception as error:
-            results.append({
-                "workflow_id": workflow_id,
-                "success": False,
-                "error": str(error)
-            })
-    
-    return results
-
-# Example usage
-workflows = [
-    ("workflow-1", {"type": "analysis", "data": "sample1"}),
-    ("workflow-2", {"type": "processing", "data": "sample2"}),
-]
-
-results = execute_workflows_batch(workflows)
-for result in results:
-    print(f"Workflow {result['workflow_id']}: {'Success' if result['success'] else 'Failed'}")
-```
-
-### Environment Configuration
-
-Configure the client using environment variables:
-
-<Tabs items={['Development', 'Production']}>
-  <Tab value="Development">
-    ```python
-    import os
-    from simstudio import SimStudioClient
-
-    # Development configuration
-    client = SimStudioClient(
-        api_key=os.getenv("SIMSTUDIO_API_KEY"),
-        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://simstudio.ai")
-    )
-    ```
-  </Tab>
-  <Tab value="Production">
-    ```python
-    import os
-    from simstudio import SimStudioClient
-
-    # Production configuration with error handling
-    api_key = os.getenv("SIMSTUDIO_API_KEY")
-    if not api_key:
-        raise ValueError("SIMSTUDIO_API_KEY environment variable is required")
-
-    client = SimStudioClient(
-        api_key=api_key,
-        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://simstudio.ai")
-    )
-    ```
-  </Tab>
-</Tabs>
-
-## Getting Your API Key
-
-<Steps>
-  <Step title="Log in to Sim Studio">
-    Navigate to [Sim Studio](https://simstudio.ai) and log in to your account.
-  </Step>
-  <Step title="Open your workflow">
-    Navigate to the workflow you want to execute programmatically.
-  </Step>
-  <Step title="Deploy your workflow">
-    Click on "Deploy" to deploy your workflow if it hasn't been deployed yet.
-  </Step>
-  <Step title="Create or select an API key">
-    During the deployment process, select or create an API key.
-  </Step>
-  <Step title="Copy the API key">
-    Copy the API key to use in your Python application.
-  </Step>
-</Steps>
-
-<Callout type="warning">
-  Keep your API key secure and never commit it to version control. Use environment variables or secure configuration management.
-</Callout>
-
-## Requirements
-
-- Python 3.8+
-- requests >= 2.25.0
-
-## License
-
-Apache-2.0 

apps/docs/content/docs/sdks/typescript.mdx

@@ -1,598 +0,0 @@
----
-title: TypeScript/JavaScript SDK
-description: The official TypeScript/JavaScript SDK for Sim Studio
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Card, Cards } from 'fumadocs-ui/components/card'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-
-The official TypeScript/JavaScript SDK for Sim Studio allows you to execute workflows programmatically from your Node.js applications, web applications, and other JavaScript environments.
-
-<Callout type="info">
-  The TypeScript SDK provides full type safety and supports both Node.js and browser environments. All workflow executions are currently synchronous.
-</Callout>
-
-## Installation
-
-Install the SDK using your preferred package manager:
-
-<Tabs items={['npm', 'yarn', 'bun']}>
-  <Tab value="npm">
-    ```bash
-    npm install simstudio-ts-sdk
-    ```
-  </Tab>
-  <Tab value="yarn">
-    ```bash
-    yarn add simstudio-ts-sdk
-    ```
-  </Tab>
-  <Tab value="bun">
-    ```bash
-    bun add simstudio-ts-sdk
-    ```
-  </Tab>
-</Tabs>
-
-## Quick Start
-
-Here's a simple example to get you started:
-
-```typescript
-import { SimStudioClient } from 'simstudio-ts-sdk';
-
-// Initialize the client
-const client = new SimStudioClient({
-  apiKey: 'your-api-key-here',
-  baseUrl: 'https://simstudio.ai' // optional, defaults to https://simstudio.ai
-});
-
-// Execute a workflow
-try {
-  const result = await client.executeWorkflow('workflow-id');
-  console.log('Workflow executed successfully:', result);
-} catch (error) {
-  console.error('Workflow execution failed:', error);
-}
-```
-
-## API Reference
-
-### SimStudioClient
-
-#### Constructor
-
-```typescript
-new SimStudioClient(config: SimStudioConfig)
-```
-
-**Configuration:**
-- `config.apiKey` (string): Your Sim Studio API key
-- `config.baseUrl` (string, optional): Base URL for the Sim Studio API (defaults to `https://simstudio.ai`)
-
-#### Methods
-
-##### executeWorkflow()
-
-Execute a workflow with optional input data.
-
-```typescript
-const result = await client.executeWorkflow('workflow-id', {
-  input: { message: 'Hello, world!' },
-  timeout: 30000 // 30 seconds
-});
-```
-
-**Parameters:**
-- `workflowId` (string): The ID of the workflow to execute
-- `options` (ExecutionOptions, optional):
-  - `input` (any): Input data to pass to the workflow
-  - `timeout` (number): Timeout in milliseconds (default: 30000)
-
-**Returns:** `Promise<WorkflowExecutionResult>`
-
-##### getWorkflowStatus()
-
-Get the status of a workflow (deployment status, etc.).
-
-```typescript
-const status = await client.getWorkflowStatus('workflow-id');
-console.log('Is deployed:', status.isDeployed);
-```
-
-**Parameters:**
-- `workflowId` (string): The ID of the workflow
-
-**Returns:** `Promise<WorkflowStatus>`
-
-##### validateWorkflow()
-
-Validate that a workflow is ready for execution.
-
-```typescript
-const isReady = await client.validateWorkflow('workflow-id');
-if (isReady) {
-  // Workflow is deployed and ready
-}
-```
-
-**Parameters:**
-- `workflowId` (string): The ID of the workflow
-
-**Returns:** `Promise<boolean>`
-
-##### executeWorkflowSync()
-
-<Callout type="info">
-  Currently, this method is identical to `executeWorkflow()` since all executions are synchronous. This method is provided for future compatibility when asynchronous execution is added.
-</Callout>
-
-Execute a workflow (currently synchronous, same as `executeWorkflow()`).
-
-```typescript
-const result = await client.executeWorkflowSync('workflow-id', {
-  input: { data: 'some input' },
-  timeout: 60000
-});
-```
-
-**Parameters:**
-- `workflowId` (string): The ID of the workflow to execute
-- `options` (ExecutionOptions, optional):
-  - `input` (any): Input data to pass to the workflow
-  - `timeout` (number): Timeout for the initial request in milliseconds
-
-**Returns:** `Promise<WorkflowExecutionResult>`
-
-##### setApiKey()
-
-Update the API key.
-
-```typescript
-client.setApiKey('new-api-key');
-```
-
-##### setBaseUrl()
-
-Update the base URL.
-
-```typescript
-client.setBaseUrl('https://my-custom-domain.com');
-```
-
-## Types
-
-### WorkflowExecutionResult
-
-```typescript
-interface WorkflowExecutionResult {
-  success: boolean;
-  output?: any;
-  error?: string;
-  logs?: any[];
-  metadata?: {
-    duration?: number;
-    executionId?: string;
-    [key: string]: any;
-  };
-  traceSpans?: any[];
-  totalDuration?: number;
-}
-```
-
-### WorkflowStatus
-
-```typescript
-interface WorkflowStatus {
-  isDeployed: boolean;
-  deployedAt?: string;
-  isPublished: boolean;
-  needsRedeployment: boolean;
-}
-```
-
-### SimStudioError
-
-```typescript
-class SimStudioError extends Error {
-  code?: string;
-  status?: number;
-}
-```
-
-## Examples
-
-### Basic Workflow Execution
-
-<Steps>
-  <Step title="Initialize the client">
-    Set up the SimStudioClient with your API key.
-  </Step>
-  <Step title="Validate the workflow">
-    Check if the workflow is deployed and ready for execution.
-  </Step>
-  <Step title="Execute the workflow">
-    Run the workflow with your input data.
-  </Step>
-  <Step title="Handle the result">
-    Process the execution result and handle any errors.
-  </Step>
-</Steps>
-
-```typescript
-import { SimStudioClient } from 'simstudio-ts-sdk';
-
-const client = new SimStudioClient({
-  apiKey: process.env.SIMSTUDIO_API_KEY!
-});
-
-async function runWorkflow() {
-  try {
-    // Check if workflow is ready
-    const isReady = await client.validateWorkflow('my-workflow-id');
-    if (!isReady) {
-      throw new Error('Workflow is not deployed or ready');
-    }
-
-    // Execute the workflow
-    const result = await client.executeWorkflow('my-workflow-id', {
-      input: {
-        message: 'Process this data',
-        userId: '12345'
-      }
-    });
-
-    if (result.success) {
-      console.log('Output:', result.output);
-      console.log('Duration:', result.metadata?.duration);
-    } else {
-      console.error('Workflow failed:', result.error);
-    }
-  } catch (error) {
-    console.error('Error:', error);
-  }
-}
-
-runWorkflow();
-```
-
-### Error Handling
-
-Handle different types of errors that may occur during workflow execution:
-
-```typescript
-import { SimStudioClient, SimStudioError } from 'simstudio-ts-sdk';
-
-const client = new SimStudioClient({
-  apiKey: process.env.SIMSTUDIO_API_KEY!
-});
-
-async function executeWithErrorHandling() {
-  try {
-    const result = await client.executeWorkflow('workflow-id');
-    return result;
-  } catch (error) {
-    if (error instanceof SimStudioError) {
-      switch (error.code) {
-        case 'UNAUTHORIZED':
-          console.error('Invalid API key');
-          break;
-        case 'TIMEOUT':
-          console.error('Workflow execution timed out');
-          break;
-        case 'USAGE_LIMIT_EXCEEDED':
-          console.error('Usage limit exceeded');
-          break;
-        case 'INVALID_JSON':
-          console.error('Invalid JSON in request body');
-          break;
-        default:
-          console.error('Workflow error:', error.message);
-      }
-    } else {
-      console.error('Unexpected error:', error);
-    }
-    throw error;
-  }
-}
-```
-
-### Environment Configuration
-
-Configure the client using environment variables:
-
-<Tabs items={['Development', 'Production']}>
-  <Tab value="Development">
-    ```typescript
-    import { SimStudioClient } from 'simstudio-ts-sdk';
-
-    // Development configuration
-    const apiKey = process.env.SIMSTUDIO_API_KEY;
-    if (!apiKey) {
-      throw new Error('SIMSTUDIO_API_KEY environment variable is required');
-    }
-
-    const client = new SimStudioClient({
-      apiKey,
-      baseUrl: process.env.SIMSTUDIO_BASE_URL // optional
-    });
-    ```
-  </Tab>
-  <Tab value="Production">
-    ```typescript
-    import { SimStudioClient } from 'simstudio-ts-sdk';
-
-    // Production configuration with validation
-    const apiKey = process.env.SIMSTUDIO_API_KEY;
-    if (!apiKey) {
-      throw new Error('SIMSTUDIO_API_KEY environment variable is required');
-    }
-
-    const client = new SimStudioClient({
-      apiKey,
-      baseUrl: process.env.SIMSTUDIO_BASE_URL || 'https://simstudio.ai'
-    });
-    ```
-  </Tab>
-</Tabs>
-
-### Node.js Express Integration
-
-Integrate with an Express.js server:
-
-```typescript
-import express from 'express';
-import { SimStudioClient } from 'simstudio-ts-sdk';
-
-const app = express();
-const client = new SimStudioClient({
-  apiKey: process.env.SIMSTUDIO_API_KEY!
-});
-
-app.use(express.json());
-
-app.post('/execute-workflow', async (req, res) => {
-  try {
-    const { workflowId, input } = req.body;
-    
-    const result = await client.executeWorkflow(workflowId, {
-      input,
-      timeout: 60000
-    });
-
-    res.json({
-      success: true,
-      data: result
-    });
-  } catch (error) {
-    console.error('Workflow execution error:', error);
-    res.status(500).json({
-      success: false,
-      error: error instanceof Error ? error.message : 'Unknown error'
-    });
-  }
-});
-
-app.listen(3000, () => {
-  console.log('Server running on port 3000');
-});
-```
-
-### Next.js API Route
-
-Use with Next.js API routes:
-
-```typescript
-// pages/api/workflow.ts or app/api/workflow/route.ts
-import { NextApiRequest, NextApiResponse } from 'next';
-import { SimStudioClient } from 'simstudio-ts-sdk';
-
-const client = new SimStudioClient({
-  apiKey: process.env.SIMSTUDIO_API_KEY!
-});
-
-export default async function handler(
-  req: NextApiRequest,
-  res: NextApiResponse
-) {
-  if (req.method !== 'POST') {
-    return res.status(405).json({ error: 'Method not allowed' });
-  }
-
-  try {
-    const { workflowId, input } = req.body;
-
-    const result = await client.executeWorkflow(workflowId, {
-      input,
-      timeout: 30000
-    });
-
-    res.status(200).json(result);
-  } catch (error) {
-    console.error('Error executing workflow:', error);
-    res.status(500).json({
-      error: 'Failed to execute workflow'
-    });
-  }
-}
-```
-
-### Browser Usage
-
-Use in the browser (with proper CORS configuration):
-
-```typescript
-import { SimStudioClient } from 'simstudio-ts-sdk';
-
-// Note: In production, use a proxy server to avoid exposing API keys
-const client = new SimStudioClient({
-  apiKey: 'your-public-api-key', // Use with caution in browser
-  baseUrl: 'https://simstudio.ai'
-});
-
-async function executeClientSideWorkflow() {
-  try {
-    const result = await client.executeWorkflow('workflow-id', {
-      input: {
-        userInput: 'Hello from browser'
-      }
-    });
-
-    console.log('Workflow result:', result);
-    
-    // Update UI with result
-    document.getElementById('result')!.textContent = 
-      JSON.stringify(result.output, null, 2);
-  } catch (error) {
-    console.error('Error:', error);
-  }
-}
-
-// Attach to button click
-document.getElementById('executeBtn')?.addEventListener('click', executeClientSideWorkflow);
-```
-
-<Callout type="warning">
-  When using the SDK in the browser, be careful not to expose sensitive API keys. Consider using a backend proxy or public API keys with limited permissions.
-</Callout>
-
-### React Hook Example
-
-Create a custom React hook for workflow execution:
-
-```typescript
-import { useState, useCallback } from 'react';
-import { SimStudioClient, WorkflowExecutionResult } from 'simstudio-ts-sdk';
-
-const client = new SimStudioClient({
-  apiKey: process.env.NEXT_PUBLIC_SIMSTUDIO_API_KEY!
-});
-
-interface UseWorkflowResult {
-  result: WorkflowExecutionResult | null;
-  loading: boolean;
-  error: Error | null;
-  executeWorkflow: (workflowId: string, input?: any) => Promise<void>;
-}
-
-export function useWorkflow(): UseWorkflowResult {
-  const [result, setResult] = useState<WorkflowExecutionResult | null>(null);
-  const [loading, setLoading] = useState(false);
-  const [error, setError] = useState<Error | null>(null);
-
-  const executeWorkflow = useCallback(async (workflowId: string, input?: any) => {
-    setLoading(true);
-    setError(null);
-    setResult(null);
-
-    try {
-      const workflowResult = await client.executeWorkflow(workflowId, {
-        input,
-        timeout: 30000
-      });
-      setResult(workflowResult);
-    } catch (err) {
-      setError(err instanceof Error ? err : new Error('Unknown error'));
-    } finally {
-      setLoading(false);
-    }
-  }, []);
-
-  return {
-    result,
-    loading,
-    error,
-    executeWorkflow
-  };
-}
-
-// Usage in component
-function WorkflowComponent() {
-  const { result, loading, error, executeWorkflow } = useWorkflow();
-
-  const handleExecute = () => {
-    executeWorkflow('my-workflow-id', {
-      message: 'Hello from React!'
-    });
-  };
-
-  return (
-    <div>
-      <button onClick={handleExecute} disabled={loading}>
-        {loading ? 'Executing...' : 'Execute Workflow'}
-      </button>
-      
-      {error && <div>Error: {error.message}</div>}
-      {result && (
-        <div>
-          <h3>Result:</h3>
-          <pre>{JSON.stringify(result, null, 2)}</pre>
-        </div>
-      )}
-    </div>
-  );
-}
-```
-
-## Getting Your API Key
-
-<Steps>
-  <Step title="Log in to Sim Studio">
-    Navigate to [Sim Studio](https://simstudio.ai) and log in to your account.
-  </Step>
-  <Step title="Open your workflow">
-    Navigate to the workflow you want to execute programmatically.
-  </Step>
-  <Step title="Deploy your workflow">
-    Click on "Deploy" to deploy your workflow if it hasn't been deployed yet.
-  </Step>
-  <Step title="Create or select an API key">
-    During the deployment process, select or create an API key.
-  </Step>
-  <Step title="Copy the API key">
-    Copy the API key to use in your TypeScript/JavaScript application.
-  </Step>
-</Steps>
-
-<Callout type="warning">
-  Keep your API key secure and never commit it to version control. Use environment variables or secure configuration management.
-</Callout>
-
-## Requirements
-
-- Node.js 16+
-- TypeScript 5.0+ (for TypeScript projects)
-
-## TypeScript Support
-
-The SDK is written in TypeScript and provides full type safety:
-
-```typescript
-import { 
-  SimStudioClient, 
-  WorkflowExecutionResult, 
-  WorkflowStatus,
-  SimStudioError 
-} from 'simstudio-ts-sdk';
-
-// Type-safe client initialization
-const client: SimStudioClient = new SimStudioClient({
-  apiKey: process.env.SIMSTUDIO_API_KEY!
-});
-
-// Type-safe workflow execution
-const result: WorkflowExecutionResult = await client.executeWorkflow('workflow-id', {
-  input: {
-    message: 'Hello, TypeScript!'
-  }
-});
-
-// Type-safe status checking
-const status: WorkflowStatus = await client.getWorkflowStatus('workflow-id');
-```
-
-## License
-
-Apache-2.0 

apps/docs/content/docs/tools/discord.mdx

@@ -1,160 +0,0 @@
----
-title: Discord
-description: Interact with Discord
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="discord"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      
-      
-      viewBox='0 -28.5 256 256'
-      version='1.1'
-      xmlns='http://www.w3.org/2000/svg'
-      xmlnsXlink='http://www.w3.org/1999/xlink'
-      preserveAspectRatio='xMidYMid'
-    >
-      <g>
-        <path
-          d='M216.856339,16.5966031 C200.285002,8.84328665 182.566144,3.2084988 164.041564,0 C161.766523,4.11318106 159.108624,9.64549908 157.276099,14.0464379 C137.583995,11.0849896 118.072967,11.0849896 98.7430163,14.0464379 C96.9108417,9.64549908 94.1925838,4.11318106 91.8971895,0 C73.3526068,3.2084988 55.6133949,8.86399117 39.0420583,16.6376612 C5.61752293,67.146514 -3.4433191,116.400813 1.08711069,164.955721 C23.2560196,181.510915 44.7403634,191.567697 65.8621325,198.148576 C71.0772151,190.971126 75.7283628,183.341335 79.7352139,175.300261 C72.104019,172.400575 64.7949724,168.822202 57.8887866,164.667963 C59.7209612,163.310589 61.5131304,161.891452 63.2445898,160.431257 C105.36741,180.133187 151.134928,180.133187 192.754523,160.431257 C194.506336,161.891452 196.298154,163.310589 198.110326,164.667963 C191.183787,168.842556 183.854737,172.420929 176.223542,175.320965 C180.230393,183.341335 184.861538,190.991831 190.096624,198.16893 C211.238746,191.588051 232.743023,181.531619 254.911949,164.955721 C260.227747,108.668201 245.831087,59.8662432 216.856339,16.5966031 Z M85.4738752,135.09489 C72.8290281,135.09489 62.4592217,123.290155 62.4592217,108.914901 C62.4592217,94.5396472 72.607595,82.7145587 85.4738752,82.7145587 C98.3405064,82.7145587 108.709962,94.5189427 108.488529,108.914901 C108.508531,123.290155 98.3405064,135.09489 85.4738752,135.09489 Z M170.525237,135.09489 C157.88039,135.09489 147.510584,123.290155 147.510584,108.914901 C147.510584,94.5396472 157.658606,82.7145587 170.525237,82.7145587 C183.391518,82.7145587 193.761324,94.5189427 193.539891,108.914901 C193.539891,123.290155 183.391518,135.09489 170.525237,135.09489 Z'
-          fill='#5865F2'
-          fillRule='nonzero'
-        />
-      </g>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Discord](https://discord.com) is a powerful communication platform that allows you to connect with friends, communities, and teams. It offers a range of features for team collaboration, including text channels, voice channels, and video calls.
-
-With a Discord account or bot, you can:
-
-- **Send messages**: Send messages to a specific channel
-- **Get messages**: Get messages from a specific channel
-- **Get server**: Get information about a specific server
-- **Get user**: Get information about a specific user
-
-In Sim Studio, the Discord integration enables your agents to access and leverage your organization's Discord servers. Agents can retrieve information from Discord channels, search for specific users, get server information, and send messages. This allows your workflows to integrate with your Discord communities, automate notifications, and create interactive experiences.
-
-> **Important:** To read message content, your Discord bot needs the "Message Content Intent" enabled in the Discord Developer Portal. Without this permission, you'll still receive message metadata but the content field will appear empty.
-
-Discord components in Sim Studio use efficient lazy loading, only fetching data when needed to minimize API calls and prevent rate limiting. Token refreshing happens automatically in the background to maintain your connection.
-
-### Setting Up Your Discord Bot
-
-1. Go to the [Discord Developer Portal](https://discord.com/developers/applications)
-2. Create a new application and navigate to the "Bot" tab
-3. Create a bot and copy your bot token
-4. Under "Privileged Gateway Intents", enable the **Message Content Intent** to read message content
-5. Invite your bot to your servers with appropriate permissions
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Connect to Discord to send messages, manage channels, and interact with servers. Automate notifications, community management, and integrate Discord into your workflows.
-
-
-
-## Tools
-
-### `discord_send_message`
-
-Send a message to a Discord channel
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `botToken` | string | Yes | The bot token for authentication |
-| `channelId` | string | Yes | The Discord channel ID to send the message to |
-| `content` | string | No | The text content of the message |
-| `serverId` | string | Yes | The Discord server ID \(guild ID\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-
-### `discord_get_messages`
-
-Retrieve messages from a Discord channel
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `botToken` | string | Yes | The bot token for authentication |
-| `channelId` | string | Yes | The Discord channel ID to retrieve messages from |
-| `limit` | number | No | Maximum number of messages to retrieve \(default: 10, max: 100\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-
-### `discord_get_server`
-
-Retrieve information about a Discord server (guild)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `botToken` | string | Yes | The bot token for authentication |
-| `serverId` | string | Yes | The Discord server ID \(guild ID\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-
-### `discord_get_user`
-
-Retrieve information about a Discord user
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `botToken` | string | Yes | Discord bot token for authentication |
-| `userId` | string | Yes | The Discord user ID |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `message` | string | message output from the block |
-| `data` | any | data output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `discord`

apps/docs/content/docs/tools/google_calendar.mdx

@@ -1,238 +0,0 @@
----
-title: Google Calendar
-description: Manage Google Calendar events
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="google_calendar"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      version='1.1'
-      xmlns='http://www.w3.org/2000/svg'
-      xmlnsXlink='http://www.w3.org/1999/xlink'
-      x='0px'
-      y='0px'
-      viewBox='0 0 200 200'
-      enableBackground='new 0 0 200 200'
-      xmlSpace='preserve'
-    >
-      <g>
-        <g transform='translate(3.75 3.75)'>
-          <path
-            fill='#FFFFFF'
-            d='M148.882,43.618l-47.368-5.263l-57.895,5.263L38.355,96.25l5.263,52.632l52.632,6.579l52.632-6.579
-			l5.263-53.947L148.882,43.618z'
-          />
-          <path
-            fill='#1A73E8'
-            d='M65.211,125.276c-3.934-2.658-6.658-6.539-8.145-11.671l9.132-3.763c0.829,3.158,2.276,5.605,4.342,7.342
-			c2.053,1.737,4.553,2.592,7.474,2.592c2.987,0,5.553-0.908,7.697-2.724s3.224-4.132,3.224-6.934c0-2.868-1.132-5.211-3.395-7.026
-			s-5.105-2.724-8.5-2.724h-5.276v-9.039H76.5c2.921,0,5.382-0.789,7.382-2.368c2-1.579,3-3.737,3-6.487
-			c0-2.447-0.895-4.395-2.684-5.855s-4.053-2.197-6.803-2.197c-2.684,0-4.816,0.711-6.395,2.145s-2.724,3.197-3.447,5.276
-			l-9.039-3.763c1.197-3.395,3.395-6.395,6.618-8.987c3.224-2.592,7.342-3.895,12.342-3.895c3.697,0,7.026,0.711,9.974,2.145
-			c2.947,1.434,5.263,3.421,6.934,5.947c1.671,2.539,2.5,5.382,2.5,8.539c0,3.224-0.776,5.947-2.329,8.184
-			c-1.553,2.237-3.461,3.947-5.724,5.145v0.539c2.987,1.25,5.421,3.158,7.342,5.724c1.908,2.566,2.868,5.632,2.868,9.211
-			s-0.908,6.776-2.724,9.579c-1.816,2.803-4.329,5.013-7.513,6.618c-3.197,1.605-6.789,2.421-10.776,2.421
-			C73.408,129.263,69.145,127.934,65.211,125.276z'
-          />
-          <path
-            fill='#1A73E8'
-            d='M121.25,79.961l-9.974,7.25l-5.013-7.605l17.987-12.974h6.895v61.197h-9.895L121.25,79.961z'
-          />
-          <path
-            fill='#EA4335'
-            d='M148.882,196.25l47.368-47.368l-23.684-10.526l-23.684,10.526l-10.526,23.684L148.882,196.25z'
-          />
-          <path
-            fill='#34A853'
-            d='M33.092,172.566l10.526,23.684h105.263v-47.368H43.618L33.092,172.566z'
-          />
-          <path
-            fill='#4285F4'
-            d='M12.039-3.75C3.316-3.75-3.75,3.316-3.75,12.039v136.842l23.684,10.526l23.684-10.526V43.618h105.263
-			l10.526-23.684L148.882-3.75H12.039z'
-          />
-          <path
-            fill='#188038'
-            d='M-3.75,148.882v31.579c0,8.724,7.066,15.789,15.789,15.789h31.579v-47.368H-3.75z'
-          />
-          <path
-            fill='#FBBC04'
-            d='M148.882,43.618v105.263h47.368V43.618l-23.684-10.526L148.882,43.618z'
-          />
-          <path
-            fill='#1967D2'
-            d='M196.25,43.618V12.039c0-8.724-7.066-15.789-15.789-15.789h-31.579v47.368H196.25z'
-          />
-        </g>
-      </g>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Google Calendar](https://calendar.google.com) is Google's powerful calendar and scheduling service that provides a comprehensive platform for managing events, meetings, and appointments. With seamless integration across Google's ecosystem and widespread adoption, Google Calendar offers robust features for both personal and professional scheduling needs.
-
-With Google Calendar, you can:
-
-- **Create and manage events**: Schedule meetings, appointments, and reminders with detailed information
-- **Send calendar invites**: Automatically notify and coordinate with attendees through email invitations
-- **Natural language event creation**: Quickly add events using conversational language like "Meeting with John tomorrow at 3pm"
-- **View and search events**: Easily find and access your scheduled events across multiple calendars
-- **Manage multiple calendars**: Organize different types of events across various calendars
-
-In Sim Studio, the Google Calendar integration enables your agents to programmatically create, read, and manage calendar events. This allows for powerful automation scenarios such as scheduling meetings, sending calendar invites, checking availability, and managing event details. Your agents can create events with natural language input, send automated calendar invitations to attendees, retrieve event information, and list upcoming events. This integration bridges the gap between your AI workflows and calendar management, enabling seamless scheduling automation and coordination with one of the world's most widely used calendar platforms.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Google Calendar functionality to create, read, update, and list calendar events within your workflow. Automate scheduling, check availability, and manage events using OAuth authentication. Email invitations are sent asynchronously and delivery depends on recipients
-
-
-
-## Tools
-
-### `google_calendar_create`
-
-Create a new event in Google Calendar
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
-| `calendarId` | string | No | Calendar ID \(defaults to primary\) |
-| `summary` | string | Yes | Event title/summary |
-| `description` | string | No | Event description |
-| `location` | string | No | Event location |
-| `startDateTime` | string | Yes | Start date and time \(RFC3339 format, e.g., 2025-06-03T10:00:00-08:00\) |
-| `endDateTime` | string | Yes | End date and time \(RFC3339 format, e.g., 2025-06-03T11:00:00-08:00\) |
-| `timeZone` | string | No | Time zone \(e.g., America/Los_Angeles\) |
-| `attendees` | array | No | Array of attendee email addresses |
-| `sendUpdates` | string | No | How to send updates to attendees: all, externalOnly, or none |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-
-### `google_calendar_list`
-
-List events from Google Calendar
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
-| `calendarId` | string | No | Calendar ID \(defaults to primary\) |
-| `timeMin` | string | No | Lower bound for events \(RFC3339 timestamp, e.g., 2025-06-03T00:00:00Z\) |
-| `timeMax` | string | No | Upper bound for events \(RFC3339 timestamp, e.g., 2025-06-04T00:00:00Z\) |
-| `orderBy` | string | No | Order of events returned \(startTime or updated\) |
-| `showDeleted` | boolean | No | Include deleted events |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-
-### `google_calendar_get`
-
-Get a specific event from Google Calendar
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
-| `calendarId` | string | No | Calendar ID \(defaults to primary\) |
-| `eventId` | string | Yes | Event ID to retrieve |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-
-### `google_calendar_quick_add`
-
-Create events from natural language text
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
-| `calendarId` | string | No | Calendar ID \(defaults to primary\) |
-| `text` | string | Yes | Natural language text describing the event \(e.g.,  |
-| `attendees` | array | No | Array of attendee email addresses \(comma-separated string also accepted\) |
-| `sendUpdates` | string | No | How to send updates to attendees: all, externalOnly, or none |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-
-### `google_calendar_invite`
-
-Invite attendees to an existing Google Calendar event
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Google Calendar API |
-| `calendarId` | string | No | Calendar ID \(defaults to primary\) |
-| `eventId` | string | Yes | Event ID to invite attendees to |
-| `attendees` | array | Yes | Array of attendee email addresses to invite |
-| `sendUpdates` | string | No | How to send updates to attendees: all, externalOnly, or none |
-| `replaceExisting` | boolean | No | Whether to replace existing attendees or add to them \(defaults to false\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `htmlLink` | string |
-| `status` | string |
-| `summary` | string |
-| `description` | string |
-| `location` | string |
-| `start` | string |
-| `end` | string |
-| `attendees` | string |
-| `creator` | string |
-| `organizer` | string |
-| `content` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `content` | string | content output from the block |
-| `metadata` | json | metadata output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `google_calendar`

apps/docs/content/docs/tools/knowledge.mdx

@@ -1,161 +0,0 @@
----
-title: Knowledge
-description: Use vector search
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="knowledge"
-  color="#00B0B0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      
-      
-      viewBox='0 0 24 24'
-      fill='none'
-      stroke='currentColor'
-      strokeWidth='1.5'
-      strokeLinecap='round'
-      strokeLinejoin='round'
-    >
-      <path d='M21 10V8a2 2 0 0 0-1-1.73l-7-4a2 2 0 0 0-2 0l-7 4A2 2 0 0 0 3 8v8a2 2 0 0 0 1 1.73l7 4a2 2 0 0 0 2 0l2-1.14' />
-      <path d='m7.5 4.27 9 5.15' />
-      <polyline points='3.29 7 12 12 20.71 7' />
-      <line x1='12' x2='12' y1='22' y2='12' />
-      <circle cx='18.5' cy='15.5' r='2.5' />
-      <path d='M20.27 17.27 22 19' />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-Sim Studio's Knowledge Base is a powerful native feature that enables you to create, manage, and query custom knowledge bases directly within the platform. Using advanced AI embeddings and vector search technology, the Knowledge Base block allows you to build intelligent search capabilities into your workflows, making it easy to find and utilize relevant information across your organization.
-
-The Knowledge Base system provides a comprehensive solution for managing organizational knowledge through its flexible and scalable architecture. With its built-in vector search capabilities, teams can perform semantic searches that understand meaning and context, going beyond traditional keyword matching.
-
-Key features of the Knowledge Base include:
-
-- Semantic Search: Advanced AI-powered search that understands meaning and context, not just keywords
-- Vector Embeddings: Automatic conversion of text into high-dimensional vectors for intelligent similarity matching
-- Custom Knowledge Bases: Create and manage multiple knowledge bases for different purposes or departments
-- Flexible Content Types: Support for various document formats and content types
-- Real-time Updates: Immediate indexing of new content for instant searchability
-
-In Sim Studio, the Knowledge Base block enables your agents to perform intelligent semantic searches across your custom knowledge bases. This creates opportunities for automated information retrieval, content recommendations, and knowledge discovery as part of your AI workflows. The integration allows agents to search and retrieve relevant information programmatically, facilitating automated knowledge management tasks and ensuring that important information is easily accessible. By leveraging the Knowledge Base block, you can build intelligent agents that enhance information discovery while automating routine knowledge management tasks, improving team efficiency and ensuring consistent access to organizational knowledge.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Perform semantic vector search across knowledge bases, upload individual chunks to existing documents, or create new documents from text content. Uses advanced AI embeddings to understand meaning and context for search operations.
-
-
-
-## Tools
-
-### `knowledge_search`
-
-Search for similar content in one or more knowledge bases using vector similarity
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `knowledgeBaseIds` | string | Yes | ID of the knowledge base to search in, or comma-separated IDs for multiple knowledge bases |
-| `query` | string | Yes | Search query text |
-| `topK` | number | No | Number of most similar results to return \(1-100\) |
-| `tag1` | string | No | Filter by tag 1 value |
-| `tag2` | string | No | Filter by tag 2 value |
-| `tag3` | string | No | Filter by tag 3 value |
-| `tag4` | string | No | Filter by tag 4 value |
-| `tag5` | string | No | Filter by tag 5 value |
-| `tag6` | string | No | Filter by tag 6 value |
-| `tag7` | string | No | Filter by tag 7 value |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `results` | string |
-| `query` | string |
-| `totalResults` | string |
-| `cost` | string |
-
-### `knowledge_upload_chunk`
-
-Upload a new chunk to a document in a knowledge base
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `knowledgeBaseId` | string | Yes | ID of the knowledge base containing the document |
-| `documentId` | string | Yes | ID of the document to upload the chunk to |
-| `content` | string | Yes | Content of the chunk to upload |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `chunkIndex` | string |
-| `content` | string |
-| `contentLength` | string |
-| `tokenCount` | string |
-| `enabled` | string |
-| `createdAt` | string |
-| `updatedAt` | string |
-
-### `knowledge_create_document`
-
-Create a new document in a knowledge base
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `knowledgeBaseId` | string | Yes | ID of the knowledge base containing the document |
-| `name` | string | Yes | Name of the document |
-| `content` | string | Yes | Content of the document |
-| `tag1` | string | No | Tag 1 value for the document |
-| `tag2` | string | No | Tag 2 value for the document |
-| `tag3` | string | No | Tag 3 value for the document |
-| `tag4` | string | No | Tag 4 value for the document |
-| `tag5` | string | No | Tag 5 value for the document |
-| `tag6` | string | No | Tag 6 value for the document |
-| `tag7` | string | No | Tag 7 value for the document |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `name` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `results` | json | results output from the block |
-| `query` | string | query output from the block |
-| `totalResults` | number | totalResults output from the block |
-
-
-## Notes
-
-- Category: `blocks`
-- Type: `knowledge`

apps/docs/content/docs/tools/linear.mdx

@@ -1,115 +0,0 @@
----
-title: Linear
-description: Read and create issues in Linear
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="linear"
-  color="#5E6AD2"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      fill='currentColor'
-      
-      
-      viewBox='0 0 100 100'
-    >
-      <path
-        fill='currentColor'
-        d='M1.22541 61.5228c-.2225-.9485.90748-1.5459 1.59638-.857L39.3342 97.1782c.6889.6889.0915 1.8189-.857 1.5964C20.0515 94.4522 5.54779 79.9485 1.22541 61.5228ZM.00189135 46.8891c-.01764375.2833.08887215.5599.28957165.7606L52.3503 99.7085c.2007.2007.4773.3075.7606.2896 2.3692-.1476 4.6938-.46 6.9624-.9259.7645-.157 1.0301-1.0963.4782-1.6481L2.57595 39.4485c-.55186-.5519-1.49117-.2863-1.648174.4782-.465915 2.2686-.77832 4.5932-.92588465 6.9624ZM4.21093 29.7054c-.16649.3738-.08169.8106.20765 1.1l64.77602 64.776c.2894.2894.7262.3742 1.1.2077 1.7861-.7956 3.5171-1.6927 5.1855-2.684.5521-.328.6373-1.0867.1832-1.5407L8.43566 24.3367c-.45409-.4541-1.21271-.3689-1.54074.1832-.99132 1.6684-1.88843 3.3994-2.68399 5.1855ZM12.6587 18.074c-.3701-.3701-.393-.9637-.0443-1.3541C21.7795 6.45931 35.1114 0 49.9519 0 77.5927 0 100 22.4073 100 50.0481c0 14.8405-6.4593 28.1724-16.7199 37.3375-.3903.3487-.984.3258-1.3542-.0443L12.6587 18.074Z'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Linear](https://linear.app) is a leading project management and issue tracking platform that helps teams plan, track, and manage their work effectively. As a modern project management tool, Linear has become increasingly popular among software development teams and project management professionals for its streamlined interface and powerful features.
-
-Linear provides a comprehensive set of tools for managing complex projects through its flexible and customizable workflow system. With its robust API and integration capabilities, Linear enables teams to streamline their development processes and maintain clear visibility of project progress.
-
-Key features of Linear include:
-
-- Agile Project Management: Support for Scrum and Kanban methodologies with customizable boards and workflows
-- Issue Tracking: Sophisticated tracking system for bugs, stories, epics, and tasks with detailed reporting
-- Workflow Automation: Powerful automation rules to streamline repetitive tasks and processes
-- Advanced Search: Complex filtering and reporting capabilities for efficient issue management
-
-In Sim Studio, the Linear integration allows your agents to seamlessly interact with your project management workflow. This creates opportunities for automated issue creation, updates, and tracking as part of your AI workflows. The integration enables agents to read existing issues and create new ones programmatically, facilitating automated project management tasks and ensuring that important information is properly tracked and documented. By connecting Sim Studio with Linear, you can build intelligent agents that maintain project visibility while automating routine project management tasks, enhancing team productivity and ensuring consistent project tracking.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate with Linear to fetch, filter, and create issues directly from your workflow.
-
-
-
-## Tools
-
-### `linear_read_issues`
-
-Fetch and filter issues from Linear
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `teamId` | string | Yes | Linear team ID |
-| `projectId` | string | Yes | Linear project ID |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `issues` | string |
-
-### `linear_create_issue`
-
-Create a new issue in Linear
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `teamId` | string | Yes | Linear team ID |
-| `projectId` | string | Yes | Linear project ID |
-| `title` | string | Yes | Issue title |
-| `description` | string | No | Issue description |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `issue` | string |
-| `title` | string |
-| `description` | string |
-| `state` | string |
-| `teamId` | string |
-| `projectId` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `issues` | json | issues output from the block |
-| `issue` | json | issue output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `linear`

apps/docs/content/docs/tools/memory.mdx

@@ -1,134 +0,0 @@
----
-title: Memory
-description: Add memory store
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="memory"
-  color="#F64F9E"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      
-      
-      viewBox='0 0 24 24'
-      fill='none'
-      stroke='currentColor'
-      strokeWidth='2'
-      strokeLinecap='round'
-      strokeLinejoin='round'
-    >
-      <path d='M12 5a3 3 0 1 0-5.997.125 4 4 0 0 0-2.526 5.77 4 4 0 0 0 .556 6.588A4 4 0 1 0 12 18Z' />
-      <path d='M12 5a3 3 0 1 1 5.997.125 4 4 0 0 1 2.526 5.77 4 4 0 0 1-.556 6.588A4 4 0 1 1 12 18Z' />
-      <path d='M15 13a4.5 4.5 0 0 1-3-4 4.5 4.5 0 0 1-3 4' />
-      <path d='M17.599 6.5a3 3 0 0 0 .399-1.375' />
-      <path d='M6.003 5.125A3 3 0 0 0 6.401 6.5' />
-      <path d='M3.477 10.896a4 4 0 0 1 .585-.396' />
-      <path d='M19.938 10.5a4 4 0 0 1 .585.396' />
-      <path d='M6 18a4 4 0 0 1-1.967-.516' />
-      <path d='M19.967 17.484A4 4 0 0 1 18 18' />
-    </svg>`}
-/>
-
-## Usage Instructions
-
-Create persistent storage for data that needs to be accessed across multiple workflow steps. Store and retrieve information throughout your workflow execution to maintain context and state.
-
-
-
-## Tools
-
-### `memory_add`
-
-Add a new memory to the database or append to existing memory with the same ID.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `id` | string | Yes | Identifier for the memory. If a memory with this ID already exists, the new data will be appended to it. |
-| `role` | string | Yes | Role for agent memory \(user, assistant, or system\) |
-| `content` | string | Yes | Content for agent memory |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
-
-### `memory_get`
-
-Retrieve a specific memory by its ID
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `id` | string | Yes | Identifier for the memory to retrieve |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
-| `message` | string |
-
-### `memory_get_all`
-
-Retrieve all memories from the database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `memories` | string |
-
-### `memory_delete`
-
-Delete a specific memory by its ID
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `id` | string | Yes | Identifier for the memory to delete |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `memories` | any | memories output from the block |
-| `id` | string | id output from the block |
-
-
-## Notes
-
-- Category: `blocks`
-- Type: `memory`

apps/docs/content/docs/tools/microsoft_excel.mdx

@@ -1,196 +0,0 @@
----
-title: Microsoft Excel
-description: Read, write, and update data
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="microsoft_excel"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      version='1.1'
-      id='Livello_1'
-      x='0px'
-      y='0px'
-      viewBox='0 0 2289.75 2130'
-      enableBackground='new 0 0 2289.75 2130'
-    >
-      <path
-        fill='#185C37'
-        d='M1437.75,1011.75L532.5,852v1180.393c0,53.907,43.7,97.607,97.607,97.607l0,0h1562.036  c53.907,0,97.607-43.7,97.607-97.607l0,0V1597.5L1437.75,1011.75z'
-      />
-      <path
-        fill='#21A366'
-        d='M1437.75,0H630.107C576.2,0,532.5,43.7,532.5,97.607c0,0,0,0,0,0V532.5l905.25,532.5L1917,1224.75  L2289.75,1065V532.5L1437.75,0z'
-      />
-      <path fill='#107C41' d='M532.5,532.5h905.25V1065H532.5V532.5z' />
-      <path
-        opacity='0.1'
-        enableBackground='new'
-        d='M1180.393,426H532.5v1331.25h647.893c53.834-0.175,97.432-43.773,97.607-97.607  V523.607C1277.825,469.773,1234.227,426.175,1180.393,426z'
-      />
-      <path
-        opacity='0.2'
-        enableBackground='new'
-        d='M1127.143,479.25H532.5V1810.5h594.643  c53.834-0.175,97.432-43.773,97.607-97.607V576.857C1224.575,523.023,1180.977,479.425,1127.143,479.25z'
-      />
-      <path
-        opacity='0.2'
-        enableBackground='new'
-        d='M1127.143,479.25H532.5V1704h594.643c53.834-0.175,97.432-43.773,97.607-97.607  V576.857C1224.575,523.023,1180.977,479.425,1127.143,479.25z'
-      />
-      <path
-        opacity='0.2'
-        enableBackground='new'
-        d='M1073.893,479.25H532.5V1704h541.393c53.834-0.175,97.432-43.773,97.607-97.607  V576.857C1171.325,523.023,1127.727,479.425,1073.893,479.25z'
-      />
-      <linearGradient
-        id='SVGID_1_'
-        gradientUnits='userSpaceOnUse'
-        x1='203.5132'
-        y1='1729.0183'
-        x2='967.9868'
-        y2='404.9817'
-        gradientTransform='matrix(1 0 0 -1 0 2132)'
-      >
-        <stop offset='0' style={{ stopColor: '#18884F' }} />
-        <stop offset='0.5' style={{ stopColor: '#117E43' }} />
-        <stop offset='1' style={{ stopColor: '#0B6631' }} />
-      </linearGradient>
-      <path
-        fill='url(#SVGID_1_)'
-        d='M97.607,479.25h976.285c53.907,0,97.607,43.7,97.607,97.607v976.285  c0,53.907-43.7,97.607-97.607,97.607H97.607C43.7,1650.75,0,1607.05,0,1553.143V576.857C0,522.95,43.7,479.25,97.607,479.25z'
-      />
-      <path
-        fill='#FFFFFF'
-        d='M302.3,1382.264l205.332-318.169L319.5,747.683h151.336l102.666,202.35  c9.479,19.223,15.975,33.494,19.49,42.919h1.331c6.745-15.336,13.845-30.228,21.3-44.677L725.371,747.79h138.929l-192.925,314.548  L869.2,1382.263H721.378L602.79,1160.158c-5.586-9.45-10.326-19.376-14.164-29.66h-1.757c-3.474,10.075-8.083,19.722-13.739,28.755  l-122.102,223.011H302.3z'
-      />
-      <path
-        fill='#33C481'
-        d='M2192.143,0H1437.75v532.5h852V97.607C2289.75,43.7,2246.05,0,2192.143,0L2192.143,0z'
-      />
-      <path fill='#107C41' d='M1437.75,1065h852v532.5h-852V1065z' />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Microsoft Teams](https://www.microsoft.com/en-us/microsoft-365/excel) is a powerful spreadsheet application that enables data management, analysis, and visualization. Through the Microsoft Excel integration in Sim Studio, you can programmatically read, write, and manipulate spreadsheet data to support your workflow automation needs.
-
-With Microsoft Excel integration, you can:
-
-- **Read Spreadsheet Data**: Access data from specific ranges, sheets, and cells
-- **Write and Update Data**: Add new data or modify existing spreadsheet content
-- **Manage Tables**: Create and manipulate tabular data structures
-- **Handle Multiple Sheets**: Work with multiple worksheets in a workbook
-- **Process Data**: Import, export, and transform spreadsheet data
-
-In Sim Studio, the Microsoft Excel integration provides seamless access to spreadsheet functionality through OAuth authentication. You can read data from specific ranges, write new information, update existing cells, and handle various data formats. The integration supports both reading and writing operations with flexible input and output options. This enables you to build workflows that can effectively manage spreadsheet data, whether you're extracting information for analysis, updating records automatically, or maintaining data consistency across your applications.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Microsoft Excel functionality to manage spreadsheet data. Read data from specific ranges, write new data, update existing cells, and manipulate table data using OAuth authentication. Supports various input and output formats for flexible data handling.
-
-
-
-## Tools
-
-### `microsoft_excel_read`
-
-Read data from a Microsoft Excel spreadsheet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Excel API |
-| `spreadsheetId` | string | Yes | The ID of the spreadsheet to read from |
-| `range` | string | No | The range of cells to read from |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
-
-### `microsoft_excel_write`
-
-Write data to a Microsoft Excel spreadsheet
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Excel API |
-| `spreadsheetId` | string | Yes | The ID of the spreadsheet to write to |
-| `range` | string | No | The range of cells to write to |
-| `values` | array | Yes | The data to write to the spreadsheet |
-| `valueInputOption` | string | No | The format of the data to write |
-| `includeValuesInResponse` | boolean | No | Whether to include the written values in the response |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `updatedRange` | string |
-| `updatedRows` | string |
-| `updatedColumns` | string |
-| `updatedCells` | string |
-| `metadata` | string |
-| `spreadsheetId` | string |
-| `spreadsheetUrl` | string |
-
-### `microsoft_excel_table_add`
-
-Add new rows to a Microsoft Excel table
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Excel API |
-| `spreadsheetId` | string | Yes | The ID of the spreadsheet containing the table |
-| `tableName` | string | Yes | The name of the table to add rows to |
-| `values` | array | Yes | The data to add to the table \(array of arrays or array of objects\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `data` | json | data output from the block |
-| `metadata` | json | metadata output from the block |
-| `updatedRange` | string | updatedRange output from the block |
-| `updatedRows` | number | updatedRows output from the block |
-| `updatedColumns` | number | updatedColumns output from the block |
-| `updatedCells` | number | updatedCells output from the block |
-| `index` | number | index output from the block |
-| `values` | json | values output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `microsoft_excel`

apps/docs/content/docs/tools/microsoft_teams.mdx

@@ -1,216 +0,0 @@
----
-title: Microsoft Teams
-description: Read, write, and create messages
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="microsoft_teams"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"  xmlns='http://www.w3.org/2000/svg' viewBox='0 0 2228.833 2073.333'>
-      <path
-        fill='#5059C9'
-        d='M1554.637,777.5h575.713c54.391,0,98.483,44.092,98.483,98.483c0,0,0,0,0,0v524.398 c0,199.901-162.051,361.952-361.952,361.952h0h-1.711c-199.901,0.028-361.975-162-362.004-361.901c0-0.017,0-0.034,0-0.052V828.971 C1503.167,800.544,1526.211,777.5,1554.637,777.5L1554.637,777.5z'
-      />
-      <circle fill='#5059C9' cx='1943.75' cy='440.583' r='233.25' />
-      <circle fill='#7B83EB' cx='1218.083' cy='336.917' r='336.917' />
-      <path
-        fill='#7B83EB'
-        d='M1667.323,777.5H717.01c-53.743,1.33-96.257,45.931-95.01,99.676v598.105 c-7.505,322.519,247.657,590.16,570.167,598.053c322.51-7.893,577.671-275.534,570.167-598.053V877.176 C1763.579,823.431,1721.066,778.83,1667.323,777.5z'
-      />
-      <path
-        opacity='.1'
-        d='M1244,777.5v838.145c-0.258,38.435-23.549,72.964-59.09,87.598 c-11.316,4.787-23.478,7.254-35.765,7.257H667.613c-6.738-17.105-12.958-34.21-18.142-51.833 c-18.144-59.477-27.402-121.307-27.472-183.49V877.02c-1.246-53.659,41.198-98.19,94.855-99.52H1244z'
-      />
-      <path
-        opacity='.2'
-        d='M1192.167,777.5v889.978c-0.002,12.287-2.47,24.449-7.257,35.765 c-14.634,35.541-49.163,58.833-87.598,59.09H691.975c-8.812-17.105-17.105-34.21-24.362-51.833 c-7.257-17.623-12.958-34.21-18.142-51.833c-18.144-59.476-27.402-121.307-27.472-183.49V877.02 c-1.246-53.659,41.198-98.19,94.855-99.52H1192.167z'
-      />
-      <path
-        opacity='.2'
-        d='M1192.167,777.5v786.312c-0.395,52.223-42.632,94.46-94.855,94.855h-447.84 c-18.144-59.476-27.402-121.307-27.472-183.49V877.02c-1.246-53.659,41.198-98.19,94.855-99.52H1192.167z'
-      />
-      <path
-        opacity='.2'
-        d='M1140.333,777.5v786.312c-0.395,52.223-42.632,94.46-94.855,94.855H649.472 c-18.144-59.476-27.402-121.307-27.472-183.49V877.02c-1.246-53.659,41.198-98.19,94.855-99.52H1140.333z'
-      />
-      <path
-        opacity='.1'
-        d='M1244,509.522v163.275c-8.812,0.518-17.105,1.037-25.917,1.037 c-8.812,0-17.105-0.518-25.917-1.037c-17.496-1.161-34.848-3.937-51.833-8.293c-104.963-24.857-191.679-98.469-233.25-198.003 c-7.153-16.715-12.706-34.071-16.587-51.833h258.648C1201.449,414.866,1243.801,457.217,1244,509.522z'
-      />
-      <path
-        opacity='.2'
-        d='M1192.167,561.355v111.442c-17.496-1.161-34.848-3.937-51.833-8.293 c-104.963-24.857-191.679-98.469-233.25-198.003h190.228C1149.616,466.699,1191.968,509.051,1192.167,561.355z'
-      />
-      <path
-        opacity='.2'
-        d='M1192.167,561.355v111.442c-17.496-1.161-34.848-3.937-51.833-8.293 c-104.963-24.857-191.679-98.469-233.25-198.003h190.228C1149.616,466.699,1191.968,509.051,1192.167,561.355z'
-      />
-      <path
-        opacity='.2'
-        d='M1140.333,561.355v103.148c-104.963-24.857-191.679-98.469-233.25-198.003 h138.395C1097.783,466.699,1140.134,509.051,1140.333,561.355z'
-      />
-      <linearGradient
-        id='a'
-        gradientUnits='userSpaceOnUse'
-        x1='198.099'
-        y1='1683.0726'
-        x2='942.2344'
-        y2='394.2607'
-        gradientTransform='matrix(1 0 0 -1 0 2075.3333)'
-      >
-        <stop offset='0' stopColor='#5a62c3' />
-        <stop offset='.5' stopColor='#4d55bd' />
-        <stop offset='1' stopColor='#3940ab' />
-        <stop offset='0' stopColor='#5a62c3' />
-        <stop offset='.5' stopColor='#4d55bd' />
-        <stop offset='1' stopColor='#3940ab' />
-      </linearGradient>
-      <path
-        fill='url(#a)'
-        d='M95.01,466.5h950.312c52.473,0,95.01,42.538,95.01,95.01v950.312c0,52.473-42.538,95.01-95.01,95.01 H95.01c-52.473,0-95.01-42.538-95.01-95.01V561.51C0,509.038,42.538,466.5,95.01,466.5z'
-      />
-      <path
-        fill='#FFF'
-        d='M820.211,828.193H630.241v517.297H509.211V828.193H320.123V727.844h500.088V828.193z'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Microsoft Teams](https://teams.microsoft.com) is a robust communication and collaboration platform that enables users to engage in real-time messaging, meetings, and content sharing within teams and organizations. As part of Microsoft's productivity ecosystem, Microsoft Teams offers seamless chat functionality integrated with Office 365, allowing users to post messages, coordinate work, and stay connected across devices and workflows.
-
-With Microsoft Teams, you can:
-
-- **Send and receive messages**: Communicate instantly with individuals or groups in chat threads  
-- **Collaborate in real-time**: Share updates and information across teams within channels and chats  
-- **Organize conversations**: Maintain context with threaded discussions and persistent chat history  
-- **Share files and content**: Attach and view documents, images, and links directly in chat  
-- **Integrate with Microsoft 365**: Seamlessly connect with Outlook, SharePoint, OneDrive, and more  
-- **Access across devices**: Use Teams on desktop, web, and mobile with cloud-synced conversations  
-- **Secure communication**: Leverage enterprise-grade security and compliance features
-
-In Sim Studio, the Microsoft Teams integration enables your agents to interact directly with chat messages programmatically. This allows for powerful automation scenarios such as sending updates, posting alerts, coordinating tasks, and responding to conversations in real time. Your agents can write new messages to chats or channels, update content based on workflow data, and engage with users where collaboration happens. By integrating Sim Studio with Microsoft Teams, you bridge the gap between intelligent workflows and team communication — empowering your agents to streamline collaboration, automate communication tasks, and keep your teams aligned.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Microsoft Teams functionality to manage messages. Read content from existing messages and write to messages using OAuth authentication. Supports text content manipulation for message creation and editing.
-
-
-
-## Tools
-
-### `microsoft_teams_read_chat`
-
-Read content from a Microsoft Teams chat
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Teams API |
-| `chatId` | string | Yes | The ID of the chat to read from |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
-| `messageCount` | string |
-| `messages` | string |
-| `totalAttachments` | string |
-| `attachmentTypes` | string |
-
-### `microsoft_teams_write_chat`
-
-Write or update content in a Microsoft Teams chat
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Teams API |
-| `chatId` | string | Yes | The ID of the chat to write to |
-| `content` | string | Yes | The content to write to the message |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `updatedContent` | string |
-| `metadata` | string |
-
-### `microsoft_teams_read_channel`
-
-Read content from a Microsoft Teams channel
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Teams API |
-| `teamId` | string | Yes | The ID of the team to read from |
-| `channelId` | string | Yes | The ID of the channel to read from |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
-| `channelId` | string |
-| `messageCount` | string |
-| `messages` | string |
-| `totalAttachments` | string |
-| `attachmentTypes` | string |
-
-### `microsoft_teams_write_channel`
-
-Write or send a message to a Microsoft Teams channel
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Microsoft Teams API |
-| `teamId` | string | Yes | The ID of the team to write to |
-| `channelId` | string | Yes | The ID of the channel to write to |
-| `content` | string | Yes | The content to write to the channel |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `updatedContent` | string |
-| `metadata` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `content` | string | content output from the block |
-| `metadata` | json | metadata output from the block |
-| `updatedContent` | boolean | updatedContent output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `microsoft_teams`

apps/docs/content/docs/tools/mistral_parse.mdx

@@ -1,132 +0,0 @@
----
-title: Mistral Parser
-description: Extract text from PDF documents
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="mistral_parse"
-  color="#000000"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      
-      
-      viewBox='1 0.5 24 22'
-      fill='none'
-      xmlns='http://www.w3.org/2000/svg'
-      preserveAspectRatio='xMidYMid meet'
-    >
-      <g clipPath='url(#clip0_1621_58)'>
-        <path d='M17.4541 0H21.8177V4.39481H17.4541V0Z' fill='black' />
-        <path d='M19.6367 0H24.0003V4.39481H19.6367V0Z' fill='#F7D046' />
-        <path
-          d='M0 0H4.36359V4.39481H0V0ZM0 4.39481H4.36359V8.78961H0V4.39481ZM0 8.78971H4.36359V13.1845H0V8.78971ZM0 13.1845H4.36359V17.5793H0V13.1845ZM0 17.5794H4.36359V21.9742H0V17.5794Z'
-          fill='black'
-        />
-        <path d='M2.18164 0H6.54523V4.39481H2.18164V0Z' fill='#F7D046' />
-        <path
-          d='M19.6362 4.39478H23.9998V8.78958H19.6362V4.39478ZM2.18164 4.39478H6.54523V8.78958H2.18164V4.39478Z'
-          fill='#F2A73B'
-        />
-        <path d='M13.0908 4.39478H17.4544V8.78958H13.0908V4.39478Z' fill='black' />
-        <path
-          d='M15.2732 4.39478H19.6368V8.78958H15.2732V4.39478ZM6.5459 4.39478H10.9095V8.78958H6.5459V4.39478Z'
-          fill='#F2A73B'
-        />
-        <path
-          d='M10.9096 8.78979H15.2732V13.1846H10.9096V8.78979ZM15.2732 8.78979H19.6368V13.1846H15.2732V8.78979ZM6.5459 8.78979H10.9096V13.1846H6.5459V8.78979Z'
-          fill='#EE792F'
-        />
-        <path d='M8.72754 13.1846H13.0911V17.5794H8.72754V13.1846Z' fill='black' />
-        <path d='M10.9092 13.1846H15.2728V17.5794H10.9092V13.1846Z' fill='#EB5829' />
-        <path
-          d='M19.6362 8.78979H23.9998V13.1846H19.6362V8.78979ZM2.18164 8.78979H6.54523V13.1846H2.18164V8.78979Z'
-          fill='#EE792F'
-        />
-        <path d='M17.4541 13.1846H21.8177V17.5794H17.4541V13.1846Z' fill='black' />
-        <path d='M19.6367 13.1846H24.0003V17.5794H19.6367V13.1846Z' fill='#EB5829' />
-        <path d='M17.4541 17.5793H21.8177V21.9742H17.4541V17.5793Z' fill='black' />
-        <path d='M2.18164 13.1846H6.54523V17.5794H2.18164V13.1846Z' fill='#EB5829' />
-        <path
-          d='M19.6362 17.5793H23.9998V21.9742H19.6362V17.5793ZM2.18164 17.5793H6.54523V21.9742H2.18164V17.5793Z'
-          fill='#EA3326'
-        />
-      </g>
-      <defs>
-        <clipPath id='clip0_1621_58'>
-          <rect   fill='white' />
-        </clipPath>
-      </defs>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-The Mistral Parse tool provides a powerful way to extract and process content from PDF documents using [Mistral's OCR API](https://mistral.ai/). This tool leverages advanced optical character recognition to accurately extract text and structure from PDF files, making it easy to incorporate document data into your agent workflows.
-
-With the Mistral Parse tool, you can:
-
-- **Extract text from PDFs**: Accurately convert PDF content to text, markdown, or JSON formats
-- **Process PDFs from URLs**: Directly extract content from PDFs hosted online by providing their URLs
-- **Maintain document structure**: Preserve formatting, tables, and layout from the original PDFs
-- **Extract images**: Optionally include embedded images from the PDFs
-- **Select specific pages**: Process only the pages you need from multi-page documents
-
-The Mistral Parse tool is particularly useful for scenarios where your agents need to work with PDF content, such as analyzing reports, extracting data from forms, or processing text from scanned documents. It simplifies the process of making PDF content available to your agents, allowing them to work with information stored in PDFs just as easily as with direct text input.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Extract text and structure from PDF documents using Mistral's OCR API. Configure processing options and get the content in your preferred format. For URLs, they must be publicly accessible and point to a valid PDF file. Note: Google Drive, Dropbox, and other cloud storage links are not supported; use a direct download URL from a web server instead.
-
-
-
-## Tools
-
-### `mistral_parser`
-
-Parse PDF documents using Mistral OCR API
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `filePath` | string | Yes | URL to a PDF document to be processed |
-| `fileUpload` | object | No | File upload data from file-upload component |
-| `resultType` | string | No | Type of parsed result \(markdown, text, or json\). Defaults to markdown. |
-| `includeImageBase64` | boolean | No | Include base64-encoded images in the response |
-| `pages` | array | No | Specific pages to process \(array of page numbers, starting from 0\) |
-| `imageLimit` | number | No | Maximum number of images to extract from the PDF |
-| `imageMinSize` | number | No | Minimum height and width of images to extract from the PDF |
-| `apiKey` | string | Yes | Mistral API key \(MISTRAL_API_KEY\) |
-
-#### Output
-
-This tool does not produce any outputs.
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `inputMethod` | string | No |  |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `content` | string | content output from the block |
-| `metadata` | json | metadata output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `mistral_parse`

apps/docs/content/docs/tools/outlook.mdx

@@ -1,235 +0,0 @@
----
-title: Outlook
-description: Access Outlook
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="outlook"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      version='1.1'
-      id='Livello_1'
-      x='0px'
-      y='0px'
-      viewBox='0 0 1831.085 1703.335'
-      enableBackground='new 0 0 1831.085 1703.335'
-    >
-      <path
-        fill='#0A2767'
-        d='M1831.083,894.25c0.1-14.318-7.298-27.644-19.503-35.131h-0.213l-0.767-0.426l-634.492-375.585  c-2.74-1.851-5.583-3.543-8.517-5.067c-24.498-12.639-53.599-12.639-78.098,0c-2.934,1.525-5.777,3.216-8.517,5.067L446.486,858.693  l-0.766,0.426c-19.392,12.059-25.337,37.556-13.278,56.948c3.553,5.714,8.447,10.474,14.257,13.868l634.492,375.585  c2.749,1.835,5.592,3.527,8.517,5.068c24.498,12.639,53.599,12.639,78.098,0c2.925-1.541,5.767-3.232,8.517-5.068l634.492-375.585  C1823.49,922.545,1831.228,908.923,1831.083,894.25z'
-      />
-      <path
-        fill='#0364B8'
-        d='M520.453,643.477h416.38v381.674h-416.38V643.477z M1745.917,255.5V80.908  c1-43.652-33.552-79.862-77.203-80.908H588.204C544.552,1.046,510,37.256,511,80.908V255.5l638.75,170.333L1745.917,255.5z'
-      />
-      <path fill='#0078D4' d='M511,255.5h425.833v383.25H511V255.5z' />
-      <path
-        fill='#28A8EA'
-        d='M1362.667,255.5H936.833v383.25L1362.667,1022h383.25V638.75L1362.667,255.5z'
-      />
-      <path fill='#0078D4' d='M936.833,638.75h425.833V1022H936.833V638.75z' />
-      <path fill='#0364B8' d='M936.833,1022h425.833v383.25H936.833V1022z' />
-      <path fill='#14447D' d='M520.453,1025.151h416.38v346.969h-416.38V1025.151z' />
-      <path fill='#0078D4' d='M1362.667,1022h383.25v383.25h-383.25V1022z' />
-      <linearGradient
-        id='SVGID_1_'
-        gradientUnits='userSpaceOnUse'
-        x1='1128.4584'
-        y1='811.0833'
-        x2='1128.4584'
-        y2='1.9982'
-        gradientTransform='matrix(1 0 0 -1 0 1705.3334)'
-      >
-        <stop offset='0' style={{ stopColor: '#35B8F1' }} />
-        <stop offset='1' style={{ stopColor: '#28A8EA' }} />
-      </linearGradient>
-      <path
-        fill='url(#SVGID_1_)'
-        d='M1811.58,927.593l-0.809,0.426l-634.492,356.848c-2.768,1.703-5.578,3.321-8.517,4.769  c-10.777,5.132-22.481,8.029-34.407,8.517l-34.663-20.27c-2.929-1.47-5.773-3.105-8.517-4.897L447.167,906.003h-0.298  l-21.036-11.753v722.384c0.328,48.196,39.653,87.006,87.849,86.7h1230.914c0.724,0,1.363-0.341,2.129-0.341  c10.18-0.651,20.216-2.745,29.808-6.217c4.145-1.756,8.146-3.835,11.966-6.217c2.853-1.618,7.75-5.152,7.75-5.152  c21.814-16.142,34.726-41.635,34.833-68.772V894.25C1831.068,908.067,1823.616,920.807,1811.58,927.593z'
-      />
-      <path
-        opacity='0.5'
-        fill='#0A2767'
-        enableBackground='new    '
-        d='M1797.017,891.397v44.287l-663.448,456.791L446.699,906.301  c0-0.235-0.191-0.426-0.426-0.426l0,0l-63.023-37.899v-31.938l25.976-0.426l54.932,31.512l1.277,0.426l4.684,2.981  c0,0,645.563,368.346,647.267,369.197l24.698,14.478c2.129-0.852,4.258-1.703,6.813-2.555  c1.278-0.852,640.879-360.681,640.879-360.681L1797.017,891.397z'
-      />
-      <path
-        fill='#1490DF'
-        d='M1811.58,927.593l-0.809,0.468l-634.492,356.848c-2.768,1.703-5.578,3.321-8.517,4.769  c-24.641,12.038-53.457,12.038-78.098,0c-2.918-1.445-5.76-3.037-8.517-4.769L446.657,928.061l-0.766-0.468  c-12.25-6.642-19.93-19.409-20.057-33.343v722.384c0.305,48.188,39.616,87.004,87.803,86.7c0.001,0,0.002,0,0.004,0h1229.636  c48.188,0.307,87.5-38.509,87.807-86.696c0-0.001,0-0.002,0-0.004V894.25C1831.068,908.067,1823.616,920.807,1811.58,927.593z'
-      />
-      <path
-        opacity='0.1'
-        enableBackground='new    '
-        d='M1185.52,1279.629l-9.496,5.323c-2.752,1.752-5.595,3.359-8.517,4.812  c-10.462,5.135-21.838,8.146-33.47,8.857l241.405,285.479l421.107,101.476c11.539-8.716,20.717-20.178,26.7-33.343L1185.52,1279.629  z'
-      />
-      <path
-        opacity='0.05'
-        enableBackground='new    '
-        d='M1228.529,1255.442l-52.505,29.51c-2.752,1.752-5.595,3.359-8.517,4.812  c-10.462,5.135-21.838,8.146-33.47,8.857l113.101,311.838l549.538,74.989c21.649-16.254,34.394-41.743,34.407-68.815v-9.326  L1228.529,1255.442z'
-      />
-      <path
-        fill='#28A8EA'
-        d='M514.833,1703.333h1228.316c18.901,0.096,37.335-5.874,52.59-17.033l-697.089-408.331  c-2.929-1.47-5.773-3.105-8.517-4.897L447.125,906.088h-0.298l-20.993-11.838v719.914  C425.786,1663.364,465.632,1703.286,514.833,1703.333C514.832,1703.333,514.832,1703.333,514.833,1703.333z'
-      />
-      <path
-        opacity='0.1'
-        enableBackground='new    '
-        d='M1022,418.722v908.303c-0.076,31.846-19.44,60.471-48.971,72.392  c-9.148,3.931-19,5.96-28.957,5.962H425.833V383.25H511v-42.583h433.073C987.092,340.83,1021.907,375.702,1022,418.722z'
-      />
-      <path
-        opacity='0.2'
-        enableBackground='new    '
-        d='M979.417,461.305v908.302c0.107,10.287-2.074,20.469-6.388,29.808  c-11.826,29.149-40.083,48.273-71.54,48.417H425.833V383.25h475.656c12.356-0.124,24.533,2.958,35.344,8.943  C962.937,405.344,979.407,432.076,979.417,461.305z'
-      />
-      <path
-        opacity='0.2'
-        enableBackground='new    '
-        d='M979.417,461.305v823.136c-0.208,43-34.928,77.853-77.927,78.225H425.833V383.25  h475.656c12.356-0.124,24.533,2.958,35.344,8.943C962.937,405.344,979.407,432.076,979.417,461.305z'
-      />
-      <path
-        opacity='0.2'
-        enableBackground='new    '
-        d='M936.833,461.305v823.136c-0.046,43.067-34.861,78.015-77.927,78.225H425.833  V383.25h433.072c43.062,0.023,77.951,34.951,77.927,78.013C936.833,461.277,936.833,461.291,936.833,461.305z'
-      />
-      <linearGradient
-        id='SVGID_2_'
-        gradientUnits='userSpaceOnUse'
-        x1='162.7469'
-        y1='1383.0741'
-        x2='774.0864'
-        y2='324.2592'
-        gradientTransform='matrix(1 0 0 -1 0 1705.3334)'
-      >
-        <stop offset='0' style={{ stopColor: '#1784D9' }} />
-        <stop offset='0.5' style={{ stopColor: '#107AD5' }} />
-        <stop offset='1' style={{ stopColor: '#0A63C9' }} />
-      </linearGradient>
-      <path
-        fill='url(#SVGID_2_)'
-        d='M78.055,383.25h780.723c43.109,0,78.055,34.947,78.055,78.055v780.723  c0,43.109-34.946,78.055-78.055,78.055H78.055c-43.109,0-78.055-34.947-78.055-78.055V461.305  C0,418.197,34.947,383.25,78.055,383.25z'
-      />
-      <path
-        fill='#FFFFFF'
-        d='M243.96,710.631c19.238-40.988,50.29-75.289,89.17-98.495c43.057-24.651,92.081-36.94,141.675-35.515  c45.965-0.997,91.321,10.655,131.114,33.683c37.414,22.312,67.547,55.004,86.742,94.109c20.904,43.09,31.322,90.512,30.405,138.396  c1.013,50.043-9.706,99.628-31.299,144.783c-19.652,40.503-50.741,74.36-89.425,97.388c-41.327,23.734-88.367,35.692-136.011,34.578  c-46.947,1.133-93.303-10.651-134.01-34.067c-37.738-22.341-68.249-55.07-87.892-94.28c-21.028-42.467-31.57-89.355-30.745-136.735  C212.808,804.859,223.158,755.686,243.96,710.631z M339.006,941.858c10.257,25.912,27.651,48.385,50.163,64.812  c22.93,16.026,50.387,24.294,78.353,23.591c29.783,1.178,59.14-7.372,83.634-24.358c22.227-16.375,39.164-38.909,48.715-64.812  c10.677-28.928,15.946-59.572,15.543-90.404c0.33-31.127-4.623-62.084-14.649-91.554c-8.855-26.607-25.246-50.069-47.182-67.537  c-23.88-17.79-53.158-26.813-82.91-25.55c-28.572-0.74-56.644,7.593-80.184,23.804c-22.893,16.496-40.617,39.168-51.1,65.365  c-23.255,60.049-23.376,126.595-0.341,186.728L339.006,941.858z'
-      />
-      <path fill='#50D9FF' d='M1362.667,255.5h383.25v383.25h-383.25V255.5z' />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Microsoft Outlook](https://outlook.office365.com) is a comprehensive email and calendar platform that helps users manage communications, schedules, and tasks efficiently. As part of Microsoft's productivity suite, Outlook offers robust tools for sending and organizing emails, coordinating meetings, and integrating seamlessly with Microsoft 365 applications — enabling individuals and teams to stay organized and connected across devices.
-
-With Microsoft Outlook, you can:
-
-- **Send and receive emails**: Communicate clearly and professionally with individuals or distribution lists  
-- **Manage calendars and events**: Schedule meetings, set reminders, and view availability  
-- **Organize your inbox**: Use folders, categories, and rules to keep your email streamlined  
-- **Access contacts and tasks**: Keep track of key people and action items in one place  
-- **Integrate with Microsoft 365**: Work seamlessly with Word, Excel, Teams, and other Microsoft apps  
-- **Access across devices**: Use Outlook on desktop, web, and mobile with real-time sync  
-- **Maintain privacy and security**: Leverage enterprise-grade encryption and compliance controls
-
-In Sim Studio, the Microsoft Outlook integration enables your agents to interact directly with email and calendar data programmatically. This allows for powerful automation scenarios such as sending custom email updates, parsing incoming messages for workflow triggers, creating calendar events, and managing task reminders. By connecting Sim Studio with Microsoft Outlook, you enable intelligent agents to automate communications, streamline scheduling, and maintain visibility into organizational correspondence — all within your workflow ecosystem.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Outlook functionality to read, draft, andsend email messages within your workflow. Automate email communications and process email content using OAuth authentication.
-
-
-
-## Tools
-
-### `outlook_send`
-
-Send emails using Outlook
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Outlook API |
-| `to` | string | Yes | Recipient email address |
-| `subject` | string | Yes | Email subject |
-| `body` | string | Yes | Email body content |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `results` | string |
-| `timestamp` | string |
-
-### `outlook_draft`
-
-Draft emails using Outlook
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Outlook API |
-| `to` | string | Yes | Recipient email address |
-| `subject` | string | Yes | Email subject |
-| `body` | string | Yes | Email body content |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `results` | string |
-| `subject` | string |
-| `status` | string |
-| `timestamp` | string |
-
-### `outlook_read`
-
-Read emails from Outlook
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Outlook |
-| `folder` | string | No | Folder ID to read emails from \(default: Inbox\) |
-| `maxResults` | number | No | Maximum number of emails to retrieve \(default: 1, max: 10\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `results` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `message` | string | message output from the block |
-| `results` | json | results output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `outlook`

apps/docs/content/docs/tools/s3.mdx

@@ -1,116 +0,0 @@
----
-title: S3
-description: View S3 files
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="s3"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-    
-    
-    preserveAspectRatio='xMidYMid'
-    viewBox='0 0 256 310'
-    
-    xmlns='http://www.w3.org/2000/svg'
-  >
-    <path d='m20.624 53.686-20.624 10.314v181.02l20.624 10.254.124-.149v-201.297z' fill='#8c3123' />
-    <path d='m131 229-110.376 26.274v-201.588l110.376 25.701z' fill='#e05243' />
-    <path d='m81.178 187.866 46.818 5.96.294-.678.263-76.77-.557-.6-46.818 5.874z' fill='#8c3123' />
-    <path
-      d='m127.996 229.295 107.371 26.035.169-.269-.003-201.195-.17-.18-107.367 25.996z'
-      fill='#8c3123'
-    />
-    <path d='m174.827 187.866-46.831 5.96v-78.048l46.831 5.874z' fill='#e05243' />
-    <path d='m174.827 89.631-46.831 8.535-46.818-8.535 46.759-12.256z' fill='#5e1f18' />
-    <path d='m174.827 219.801-46.831-8.591-46.818 8.591 46.761 13.053z' fill='#f2b0a9' />
-    <path
-      d='m81.178 89.631 46.818-11.586.379-.117v-77.615l-.379-.313-46.818 23.413z'
-      fill='#8c3123'
-    />
-    <path d='m174.827 89.631-46.831-11.586v-78.045l46.831 23.413z' fill='#e05243' />
-    <path
-      d='m127.996 309.428-46.823-23.405v-66.217l46.823 11.582.689.783-.187 75.906z'
-      fill='#8c3123'
-    />
-    <g fill='#e05243'>
-      <path d='m127.996 309.428 46.827-23.405v-66.217l-46.827 11.582z' />
-      <path d='m235.367 53.686 20.633 10.314v181.02l-20.633 10.31z' />
-    </g>
-  </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Amazon S3](https://aws.amazon.com/s3/) is a highly scalable, secure, and durable cloud storage service provided by Amazon Web Services. It's designed to store and retrieve any amount of data from anywhere on the web, making it one of the most widely used cloud storage solutions for businesses of all sizes.
-
-With Amazon S3, you can:
-
-- **Store unlimited data**: Upload files of any size and type with virtually unlimited storage capacity
-- **Access from anywhere**: Retrieve your files from anywhere in the world with low-latency access
-- **Ensure data durability**: Benefit from 99.999999999% (11 9's) durability with automatic data replication
-- **Control access**: Manage permissions and access controls with fine-grained security policies
-- **Scale automatically**: Handle varying workloads without manual intervention or capacity planning
-- **Integrate seamlessly**: Connect with other AWS services and third-party applications easily
-- **Optimize costs**: Choose from multiple storage classes to optimize costs based on access patterns
-
-In Sim Studio, the S3 integration enables your agents to retrieve and access files stored in your Amazon S3 buckets using secure presigned URLs. This allows for powerful automation scenarios such as processing documents, analyzing stored data, retrieving configuration files, and accessing media content as part of your workflows. Your agents can securely fetch files from S3 without exposing your AWS credentials, making it easy to incorporate cloud-stored assets into your automation processes. This integration bridges the gap between your cloud storage and AI workflows, enabling seamless access to your stored data while maintaining security best practices through AWS's robust authentication mechanisms.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Retrieve and view files from Amazon S3 buckets using presigned URLs.
-
-
-
-## Tools
-
-### `s3_get_object`
-
-Retrieve an object from an AWS S3 bucket
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessKeyId` | string | Yes | Your AWS Access Key ID |
-| `secretAccessKey` | string | Yes | Your AWS Secret Access Key |
-| `s3Uri` | string | Yes | S3 Object URL \(e.g., https://bucket-name.s3.region.amazonaws.com/path/to/file\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `size` | string |
-| `name` | string |
-| `lastModified` | string |
-| `url` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `accessKeyId` | string | Yes | Access Key ID - Enter your AWS Access Key ID |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `url` | string | url output from the block |
-| `metadata` | json | metadata output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `s3`

apps/docs/content/docs/tools/serper.mdx

@@ -1,130 +0,0 @@
----
-title: Serper
-description: Search the web using Serper
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="serper"
-  color="#2B3543"
-  icon={true}
-  iconSvg={`<svg className="block-icon" viewBox='0 0 654 600' xmlns='http://www.w3.org/2000/svg' >
-      <path
-        d='M324 38C356 37 389 36 417 47C452 56 484 72 509 94C539 118 561 145 577 176C593 205 601 238 606 271C610 343 590 403 552 452C528 482 499 507 467 523C438 539 404 547 372 552C297 556 235 534 184 492C133 449 103 392 93 330C93 292 89 255 102 224C112 189 128 158 149 132C194 78 255 46 322 38'
-        fill='rgb(71,97,118)'
-      />
-      <path
-        d='M326 39C286 43 250 55 217 75C185 94 156 120 137 150C100 204 87 266 95 336C107 402 142 462 198 502C249 538 309 556 378 551C415 545 449 533 477 516C511 497 535 472 557 445C592 393 611 333 605 265C595 196 563 140 511 95C484 73 452 57 419 48C390 38 359 38 327 39'
-        fill='rgb(71,97,119)'
-      />
-      <path
-        d='M342 40C407 42 465 61 513 103C541 126 562 155 576 184C592 217 600 251 600 288C602 357 579 416 535 465C510 493 478 515 445 528C416 541 385 546 352 546C284 548 225 523 178 481C130 436 103 379 96 313C94 244 113 186 151 138C179 103 209 80 245 64C276 50 307 44 340 41'
-        fill='rgb(71,97,119)'
-      />
-      <path
-        d='M344 42C309 44 277 51 247 64C209 81 180 103 153 136C114 186 95 244 96 312C104 379 131 435 177 480C225 522 284 547 351 546C385 545 416 540 443 528C478 514 509 492 533 466C578 416 601 357 600 289C599 251 591 217 576 187C561 156 541 127 515 105C466 63 409 44 346 41'
-        fill='rgb(71,97,118)'
-      />
-      <path
-        d='M327 81C378 78 423 89 462 114C511 144 546 196 557 248C567 306 559 363 530 406C498 457 448 492 395 503C338 513 282 506 239 477C192 450 156 402 143 351C126 296 137 235 163 190C198 130 258 89 325 82'
-        fill='rgb(44,56,71)'
-      />
-      <path
-        d='M329 83C260 89 199 129 165 189C138 235 127 296 144 349C157 401 193 449 237 475C282 505 338 512 393 503C448 491 497 457 529 408C558 363 566 306 557 250C545 196 511 145 464 116C424 91 380 79 330 82'
-        fill='rgb(43,55,70)'
-      />
-      <path
-        d='M334 87C381 83 423 94 458 117C510 148 544 201 554 258C562 317 551 370 521 412C487 460 440 491 385 500C331 507 281 499 241 473C191 444 157 394 145 339C136 284 143 227 171 186C207 129 265 91 332 87'
-        fill='rgb(41,53,67)'
-      />
-      <path
-        d='M335 88C267 90 208 129 173 184C144 227 137 284 145 338C158 393 191 443 240 471C281 498 331 506 384 500C439 490 487 459 519 413C550 370 561 317 554 259C543 201 509 149 460 119C424 96 383 85 337 88'
-        fill='rgb(41,53,67)'
-      />
-      <path
-        d='M347 166C361 164 373 169 387 168C412 180 437 193 447 221C449 232 443 243 434 248C403 245 398 204 365 207C338 206 315 210 297 228C294 238 289 257 303 260C337 280 382 276 417 292C436 300 448 314 455 330C457 349 462 373 449 385C435 408 413 418 391 427C361 429 328 436 304 421C280 413 260 392 250 370C246 356 255 343 268 343C293 360 316 398 356 389C382 390 409 380 416 357C389 295 298 335 260 276C246 256 248 233 258 214C279 184 309 167 346 167'
-        fill='rgb(121,172,205)'
-      />
-      <path
-        d='M349 168C312 167 280 183 259 212C249 233 247 256 260 274C299 334 390 294 422 354C409 381 382 391 357 389C316 399 293 361 272 342C255 344 247 356 251 368C260 391 280 412 302 420C328 435 361 428 389 428C412 417 434 407 447 386C461 373 456 349 456 332C428 270 351 289 304 262C288 258 293 239 295 229C314 209 338 204 363 204C398 203 403 244 431 249C443 242 448 232 449 222C436 193 412 181 388 172C374 170 363 166 350 167'
-        fill='rgb(125,177,211)'
-      />
-      <path
-        d='M349 169C386 169 425 185 441 220C444 231 441 240 432 243C409 237 402 209 380 206C347 200 314 201 293 226C290 238 286 256 297 262C332 283 375 281 411 295C431 304 446 317 452 337C455 360 452 383 434 396C415 415 391 421 366 426C338 430 316 422 295 413C276 402 261 385 254 366C254 353 261 343 275 348C290 381 325 398 360 394C388 395 411 382 420 360C425 342 413 334 404 327C359 304 298 318 265 276C253 254 255 235 261 214C280 187 314 173 346 170'
-        fill='rgb(137,195,233)'
-      />
-      <path
-        d='M349 171C316 173 281 187 263 214C256 235 254 254 266 273C300 316 359 304 401 325C413 333 426 342 422 358C412 382 388 396 363 395C326 399 290 382 278 348C262 345 254 353 253 365C261 384 277 401 292 411C316 421 338 429 365 426C390 420 415 414 432 398C451 383 454 360 453 338C445 317 430 305 413 296C375 282 332 284 299 264C285 257 288 239 291 228C304 212 319 205 336 202C378 193 403 213 423 244C438 244 443 232 441 222C425 186 388 171 352 170'
-        fill='rgb(139,198,236)'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Serper](https://www.serper.com/) is a Google Search API that provides developers with programmatic access to Google search results. It offers a reliable, high-performance way to integrate Google search capabilities into applications without the complexity of web scraping or the limitations of other search APIs.
-
-With Serper, you can:
-
-- **Access Google search results**: Get structured data from Google search results programmatically
-- **Perform different search types**: Run web searches, image searches, news searches, and more
-- **Retrieve rich metadata**: Obtain titles, snippets, URLs, and other relevant information from search results
-- **Scale your applications**: Build search-powered features with a reliable and fast API
-- **Avoid rate limiting**: Get consistent access to search results without worrying about IP blocks
-
-In Sim Studio, the Serper integration enables your agents to leverage the power of web search as part of their workflows. This allows for sophisticated automation scenarios that require up-to-date information from the internet. Your agents can formulate search queries, retrieve relevant results, and use this information to make decisions or provide responses. This integration bridges the gap between your workflow automation and the vast knowledge available on the web, enabling your agents to access real-time information without manual intervention. By connecting Sim Studio with Serper, you can create agents that stay current with the latest information, provide more accurate responses, and deliver more value to users.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Access real-time web search results with Serper
-
-
-
-## Tools
-
-### `serper_search`
-
-A powerful web search tool that provides access to Google search results through Serper.dev API. Supports different types of searches including regular web search, news, places, and images, with each result containing relevant metadata like titles, URLs, snippets, and type-specific information.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `query` | string | Yes | The search query |
-| `num` | number | No | Number of results to return |
-| `gl` | string | No | Country code for search results |
-| `hl` | string | No | Language code for search results |
-| `type` | string | No | Type of search to perform |
-| `apiKey` | string | Yes | Serper API Key |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `searchResults` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `query` | string | Yes | Search Query - Enter your search query... |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `searchResults` | json | searchResults output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `serper`

apps/docs/content/docs/tools/slack.mdx

@@ -1,109 +0,0 @@
----
-title: Slack
-description: Send messages to Slack
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="slack"
-  color="#611f69"
-  icon={true}
-  iconSvg={`<svg className="block-icon" viewBox='0 0 256 256' xmlns='http://www.w3.org/2000/svg' >
-      <g>
-        <path
-          d='M53.8412698,161.320635 C53.8412698,176.152381 41.8539683,188.139683 27.0222222,188.139683 C12.1904762,188.139683 0.203174603,176.152381 0.203174603,161.320635 C0.203174603,146.488889 12.1904762,134.501587 27.0222222,134.501587 L53.8412698,134.501587 L53.8412698,161.320635 Z M67.2507937,161.320635 C67.2507937,146.488889 79.2380952,134.501587 94.0698413,134.501587 C108.901587,134.501587 120.888889,146.488889 120.888889,161.320635 L120.888889,228.368254 C120.888889,243.2 108.901587,255.187302 94.0698413,255.187302 C79.2380952,255.187302 67.2507937,243.2 67.2507937,228.368254 L67.2507937,161.320635 Z'
-          fill='#E01E5A'
-        />
-        <path
-          d='M94.0698413,53.6380952 C79.2380952,53.6380952 67.2507937,41.6507937 67.2507937,26.8190476 C67.2507937,11.9873016 79.2380952,-7.10542736e-15 94.0698413,-7.10542736e-15 C108.901587,-7.10542736e-15 120.888889,11.9873016 120.888889,26.8190476 L120.888889,53.6380952 L94.0698413,53.6380952 Z M94.0698413,67.2507937 C108.901587,67.2507937 120.888889,79.2380952 120.888889,94.0698413 C120.888889,108.901587 108.901587,120.888889 94.0698413,120.888889 L26.8190476,120.888889 C11.9873016,120.888889 0,108.901587 0,94.0698413 C0,79.2380952 11.9873016,67.2507937 26.8190476,67.2507937 L94.0698413,67.2507937 Z'
-          fill='#36C5F0'
-        />
-        <path
-          d='M201.549206,94.0698413 C201.549206,79.2380952 213.536508,67.2507937 228.368254,67.2507937 C243.2,67.2507937 255.187302,79.2380952 255.187302,94.0698413 C255.187302,108.901587 243.2,120.888889 228.368254,120.888889 L201.549206,120.888889 L201.549206,94.0698413 Z M188.139683,94.0698413 C188.139683,108.901587 176.152381,120.888889 161.320635,120.888889 C146.488889,120.888889 134.501587,108.901587 134.501587,94.0698413 L134.501587,26.8190476 C134.501587,11.9873016 146.488889,-1.42108547e-14 161.320635,-1.42108547e-14 C176.152381,-1.42108547e-14 188.139683,11.9873016 188.139683,26.8190476 L188.139683,94.0698413 Z'
-          fill='#2EB67D'
-        />
-        <path
-          d='M161.320635,201.549206 C176.152381,201.549206 188.139683,213.536508 188.139683,228.368254 C188.139683,243.2 176.152381,255.187302 161.320635,255.187302 C146.488889,255.187302 134.501587,243.2 134.501587,228.368254 L134.501587,201.549206 L161.320635,201.549206 Z M161.320635,188.139683 C146.488889,188.139683 134.501587,176.152381 134.501587,161.320635 C134.501587,146.488889 146.488889,134.501587 161.320635,134.501587 L228.571429,134.501587 C243.403175,134.501587 255.390476,146.488889 255.390476,161.320635 C255.390476,176.152381 243.403175,188.139683 228.571429,188.139683 L161.320635,188.139683 Z'
-          fill='#ECB22E'
-        />
-      </g>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Slack](https://www.slack.com/) is a business communication platform that offers teams a unified place for messaging, tools, and files.
-
-<iframe
-  width="100%"
-  height="400"
-  src="https://www.youtube.com/embed/J5jz3UaWmE8"
-  title="Slack Integration with Sim Studio"
-  frameBorder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
-  allowFullScreen
-></iframe>
-
-With Slack, you can:
-
-- **Automate agent notifications**: Send real-time updates from your Sim Studio agents to any Slack channel
-- **Create webhook endpoints**: Configure Slack bots as webhooks to trigger Sim Studio workflows from Slack activities
-- **Enhance agent workflows**: Integrate Slack messaging into your agents to deliver results, alerts, and status updates
-
-In Sim Studio, the Slack integration enables your agents to programmatically send messages to any Slack channel or user as part of their workflows. This allows for powerful automation scenarios such as sending notifications, alerts, updates, and reports directly to your team's communication hub. Your agents can deliver timely information, share results from processes they've completed, or alert team members when attention is needed. This integration bridges the gap between your AI workflows and your team's communication, ensuring everyone stays informed without manual intervention. By connecting Sim Studio with Slack, you can create agents that keep your team updated with relevant information at the right time, enhance collaboration by sharing insights automatically, and reduce the need for manual status updates - all while leveraging your existing Slack workspace where your team already communicates.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Comprehensive Slack integration with OAuth authentication. Send formatted messages using Slack
-
-
-
-## Tools
-
-### `slack_message`
-
-Send messages to Slack channels or users through the Slack API. Supports Slack mrkdwn formatting.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `authMethod` | string | No | Authentication method: oauth or bot_token |
-| `botToken` | string | No | Bot token for Custom Bot |
-| `accessToken` | string | No | OAuth access token or bot token for Slack API |
-| `channel` | string | Yes | Target Slack channel \(e.g., #general\) |
-| `text` | string | Yes | Message text to send \(supports Slack mrkdwn formatting\) |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `channel` | string |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `ts` | string | ts output from the block |
-| `channel` | string | channel output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `slack`

apps/docs/content/docs/tools/wealthbox.mdx

@@ -1,200 +0,0 @@
----
-title: Wealthbox
-description: Interact with Wealthbox
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="wealthbox"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      version='1.0'
-      
-      
-      viewBox='50 -50 200 200'
-    >
-      <g fill='#106ED4' stroke='none' transform='translate(0, 200) scale(0.15, -0.15)'>
-        <path d='M764 1542 c-110 -64 -230 -134 -266 -156 -42 -24 -71 -49 -78 -65 -7 -19 -10 -126 -8 -334 3 -291 4 -307 23 -326 11 -11 103 -67 205 -126 102 -59 219 -127 261 -151 42 -24 85 -44 96 -44 23 0 527 288 561 320 22 22 22 23 22 340 0 288 -2 320 -17 338 -32 37 -537 322 -569 321 -18 0 -107 -46 -230 -117z m445 -144 c108 -62 206 -123 219 -135 22 -22 22 -26 22 -261 0 -214 -2 -242 -17 -260 -23 -26 -414 -252 -437 -252 -9 0 -70 31 -134 69 -64 37 -161 94 -215 125 l-97 57 2 261 3 261 210 123 c116 67 219 123 229 123 10 1 107 -50 215 -111z' />
-        <path d='M700 1246 l-55 -32 -3 -211 -2 -211 37 -23 c21 -12 52 -30 69 -40 l30 -18 103 59 c56 33 109 60 117 60 8 0 62 -27 119 -60 l104 -60 63 37 c35 21 66 42 70 48 4 5 8 101 8 212 l0 202 -62 35 -63 35 -3 -197 c-1 -108 -6 -200 -11 -205 -5 -5 -54 17 -114 52 -58 34 -108 61 -111 61 -2 0 -51 -27 -107 -60 -56 -32 -106 -57 -111 -54 -4 3 -8 95 -8 205 0 109 -3 199 -7 199 -5 -1 -33 -16 -63 -34z' />
-      </g>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Wealthbox](https://www.wealthbox.com/) is a comprehensive CRM platform designed specifically for financial advisors and wealth management professionals. It provides a centralized system for managing client relationships, tracking interactions, and organizing business workflows in the financial services industry.
-
-With Wealthbox, you can:
-
-- **Manage client relationships**: Store detailed contact information, background data, and relationship histories for all your clients
-- **Track interactions**: Create and maintain notes about meetings, calls, and other client touchpoints
-- **Organize tasks**: Schedule and manage follow-up activities, deadlines, and important action items
-- **Document workflows**: Keep comprehensive records of client communications and business processes
-- **Access client data**: Retrieve information quickly with organized contact management and search capabilities
-- **Automate follow-ups**: Set reminders and schedule tasks to ensure consistent client engagement
-
-In Sim Studio, the Wealthbox integration enables your agents to seamlessly interact with your CRM data through OAuth authentication. This allows for powerful automation scenarios such as automatically creating client notes from meeting transcripts, updating contact information, scheduling follow-up tasks, and retrieving client details for personalized communications. Your agents can read existing notes, contacts, and tasks to understand client history, while also creating new entries to maintain up-to-date records. This integration bridges the gap between your AI workflows and your client relationship management, enabling automated data entry, intelligent client insights, and streamlined administrative processes that free up time for more valuable client-facing activities.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Wealthbox functionality to manage notes, contacts, and tasks. Read content from existing notes, contacts, and tasks and write to them using OAuth authentication. Supports text content manipulation for note creation and editing.
-
-
-
-## Tools
-
-### `wealthbox_read_note`
-
-Read content from a Wealthbox note
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Wealthbox API |
-| `noteId` | string | No | The ID of the note to read |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `note` | string |
-| `metadata` | string |
-| `noteId` | string |
-| `itemType` | string |
-
-### `wealthbox_write_note`
-
-Create or update a Wealthbox note
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Wealthbox API |
-| `content` | string | Yes | The main body of the note |
-| `contactId` | string | No | ID of contact to link to this note |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
-
-### `wealthbox_read_contact`
-
-Read content from a Wealthbox contact
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Wealthbox API |
-| `contactId` | string | No | The ID of the contact to read |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `contact` | string |
-| `metadata` | string |
-| `contactId` | string |
-| `itemType` | string |
-
-### `wealthbox_write_contact`
-
-Create a new Wealthbox contact
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Wealthbox API |
-| `firstName` | string | Yes | The first name of the contact |
-| `lastName` | string | Yes | The last name of the contact |
-| `emailAddress` | string | No | The email address of the contact |
-| `backgroundInformation` | string | No | Background information about the contact |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `contact` | string |
-| `metadata` | string |
-| `itemType` | string |
-
-### `wealthbox_read_task`
-
-Read content from a Wealthbox task
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Wealthbox API |
-| `taskId` | string | No | The ID of the task to read |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `task` | string |
-| `metadata` | string |
-| `taskId` | string |
-| `itemType` | string |
-
-### `wealthbox_write_task`
-
-Create or update a Wealthbox task
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Wealthbox API |
-| `title` | string | Yes | The name/title of the task |
-| `dueDate` | string | Yes | The due date and time of the task \(format:  |
-| `contactId` | string | No | ID of contact to link to this task |
-| `description` | string | No | Description or notes about the task |
-
-#### Output
-
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
-
-
-
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `note` | any | note output from the block |
-| `notes` | any | notes output from the block |
-| `contact` | any | contact output from the block |
-| `contacts` | any | contacts output from the block |
-| `task` | any | task output from the block |
-| `tasks` | any | tasks output from the block |
-| `metadata` | json | metadata output from the block |
-| `success` | any | success output from the block |
-
-
-## Notes
-
-- Category: `tools`
-- Type: `wealthbox`

apps/docs/lib/llms.ts

@@ -1,22 +0,0 @@
-import type { InferPageType } from 'fumadocs-core/source'
-import { remarkInclude } from 'fumadocs-mdx/config'
-import { remark } from 'remark'
-import remarkGfm from 'remark-gfm'
-import remarkMdx from 'remark-mdx'
-import type { source } from '@/lib/source'
-
-const processor = remark().use(remarkMdx).use(remarkInclude).use(remarkGfm)
-
-export async function getLLMText(page: InferPageType<typeof source>) {
-  const processed = await processor.process({
-    path: page.data._file.absolutePath,
-    value: page.data.content,
-  })
-
-  return `# ${page.data.title}
-URL: ${page.url}
-
-${page.data.description}
-
-${processed.value}`
-}

apps/docs/next.config.ts

@@ -1,24 +0,0 @@
-import { createMDX } from 'fumadocs-mdx/next'
-
-const withMDX = createMDX()
-
-/** @type {import('next').NextConfig} */
-const config = {
-  reactStrictMode: true,
-  async redirects() {
-    return [
-      {
-        source: '/',
-        destination: '/introduction',
-        permanent: true,
-      },
-      {
-        source: '/docs/:path*.mdx',
-        destination: '/llms.mdx/:path*',
-        permanent: true,
-      },
-    ]
-  },
-}
-
-export default withMDX(config)