duplicated subflow

Co-authored-by: Adam Gough <adamgough@Mac.attlocal.net>

.devcontainer/.bashrc

@@ -1,4 +1,4 @@
-# Sim Studio Development Environment Bashrc
+# Sim Development Environment Bashrc
 # This gets sourced by post-create.sh
 
 # Enhanced prompt with git branch info
@@ -17,7 +17,7 @@ alias ...="cd ../.."
 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
+# Sim 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"
@@ -45,7 +45,7 @@ if [ -z "$SIM_WELCOME_SHOWN" ]; then
   
   echo ""
   echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo "🚀 Welcome to Sim Studio development environment!"
+  echo "🚀 Welcome to Sim development environment!"
   echo ""
   echo "Available commands:"
   echo "  sim-start    - Start all apps in development mode"

.devcontainer/README.md

@@ -1,4 +1,4 @@
-# Sim Studio Development Container
+# Sim Development Container
 
 This directory contains configuration files for Visual Studio Code Dev Containers / GitHub Codespaces. Dev containers provide a consistent, isolated development environment for this project.
 

.devcontainer/devcontainer.json

@@ -1,5 +1,5 @@
 {
-  "name": "Sim Studio Dev Environment",
+  "name": "Sim Dev Environment",
   "dockerComposeFile": "docker-compose.yml",
   "service": "app",
   "workspaceFolder": "/workspace",

.devcontainer/docker-compose.yml

@@ -77,7 +77,7 @@ services:
       - POSTGRES_PASSWORD=postgres
       - POSTGRES_DB=simstudio
     ports:
-      - "5432:5432"
+      - "${POSTGRES_PORT:-5432}:5432"
     healthcheck:
       test: ["CMD-SHELL", "pg_isready -U postgres"]
       interval: 5s

.devcontainer/post-create.sh

@@ -3,7 +3,7 @@
 # Exit on error, but with some error handling
 set -e
 
-echo "🔧 Setting up Sim Studio development environment..."
+echo "🔧 Setting up Sim development environment..."
 
 # Change to the workspace root directory
 cd /workspace
@@ -85,7 +85,7 @@ echo "Waiting for database to be ready..."
 # Add additional helpful aliases to .bashrc
 cat << EOF >> ~/.bashrc
 
-# Additional Sim Studio Development Aliases
+# Additional Sim 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"
@@ -104,7 +104,7 @@ unset SIM_WELCOME_SHOWN
 
 echo ""
 echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo "✅ Sim Studio development environment setup complete!"
+echo "✅ Sim development environment setup complete!"
 echo ""
 echo "Your environment is now ready. A new terminal session will show"
 echo "available commands. You can start the development server with:"

.github/CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
-# Code of Conduct - Sim Studio
+# Code of Conduct - Sim
 
 ## Our Pledge
 
@@ -55,7 +55,7 @@ representative at an online or offline event.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behaviour may be
-reported to the community leaders responsible for enforcement at <waleed@simstudio.ai>.
+reported to the community leaders responsible for enforcement at <waleed@sim.ai>.
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

.github/CONTRIBUTING.md

@@ -1,9 +1,9 @@
-# Contributing to Sim Studio
+# Contributing to Sim
 
-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.
+Thank you for your interest in contributing to Sim! 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 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.
 
 ---
 
@@ -130,7 +130,7 @@ To set up your local development environment:
 
 ### Option 1: Using NPM Package (Simplest)
 
-The easiest way to run Sim Studio locally is using our NPM package:
+The easiest way to run Sim locally is using our NPM package:
 
 ```bash
 npx simstudio
@@ -140,7 +140,7 @@ After running this command, open [http://localhost:3000/](http://localhost:3000/
 
 #### Options
 
-- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
+- `-p, --port <port>`: Specify the port to run Sim on (default: 3000)
 - `--no-pull`: Skip pulling the latest Docker images
 
 #### Requirements
@@ -154,7 +154,7 @@ After running this command, open [http://localhost:3000/](http://localhost:3000/
 git clone https://github.com/<your-username>/sim.git
 cd sim
 
-# Start Sim Studio
+# Start Sim
 docker compose -f docker-compose.prod.yml up -d
 ```
 
@@ -162,15 +162,19 @@ Access the application at [http://localhost:3000/](http://localhost:3000/)
 
 #### Using Local Models
 
-To use local models with Sim Studio:
+To use local models with Sim:
 
-1. Pull models using our helper script:
+1. Install Ollama and pull models:
 
 ```bash
-./apps/sim/scripts/ollama_docker.sh pull <model_name>
+# Install Ollama (if not already installed)
+curl -fsSL https://ollama.ai/install.sh | sh
+
+# Pull a model (e.g., gemma3:4b)
+ollama pull gemma3:4b
 ```
 
-2. Start Sim Studio with local model support:
+2. Start Sim with local model support:
 
 ```bash
 # With NVIDIA GPU support
@@ -276,7 +280,7 @@ When working on email templates, you can preview them using a local email previe
 
 ## Adding New Blocks and Tools
 
-Sim Studio is built in a modular fashion where blocks and tools extend the platform's functionality. To maintain consistency and quality, please follow the guidelines below when adding a new block or tool.
+Sim is built in a modular fashion where blocks and tools extend the platform's functionality. To maintain consistency and quality, please follow the guidelines below when adding a new block or tool.
 
 ### Where to Add Your Code
 
@@ -301,8 +305,8 @@ In addition, you will need to update the registries:
 
    ```typescript:/apps/sim/blocks/blocks/pinecone.ts
    import { PineconeIcon } from '@/components/icons'
-   import { PineconeResponse } from '@/tools/pinecone/types'
-   import { BlockConfig } from '../types'
+   import type { BlockConfig } from '@/blocks/types'
+   import type { PineconeResponse } from '@/tools/pinecone/types'
 
    export const PineconeBlock: BlockConfig<PineconeResponse> = {
      type: 'pinecone',
@@ -313,13 +317,58 @@ In addition, you will need to update the registries:
      bgColor: '#123456',
      icon: PineconeIcon,
 
-     // If this block requires OAuth authentication
-     provider: 'pinecone',
-
-     // Define subBlocks for the UI configuration
      subBlocks: [
-       // Block configuration options
+       {
+         id: 'operation',
+         title: 'Operation',
+         type: 'dropdown',
+         layout: 'full',
+         required: true,
+         options: [
+           { label: 'Generate Embeddings', id: 'generate' },
+           { label: 'Search Text', id: 'search_text' },
+         ],
+         value: () => 'generate',
+       },
+       {
+         id: 'apiKey',
+         title: 'API Key',
+         type: 'short-input',
+         layout: 'full',
+         placeholder: 'Your Pinecone API key',
+         password: true,
+         required: true,
+       },
      ],
+
+     tools: {
+       access: ['pinecone_generate_embeddings', 'pinecone_search_text'],
+       config: {
+         tool: (params: Record<string, any>) => {
+           switch (params.operation) {
+             case 'generate':
+               return 'pinecone_generate_embeddings'
+             case 'search_text':
+               return 'pinecone_search_text'
+             default:
+               throw new Error('Invalid operation selected')
+           }
+         },
+       },
+     },
+
+     inputs: {
+       operation: { type: 'string', description: 'Operation to perform' },
+       apiKey: { type: 'string', description: 'Pinecone API key' },
+       searchQuery: { type: 'string', description: 'Search query text' },
+       topK: { type: 'string', description: 'Number of results to return' },
+     },
+
+     outputs: {
+       matches: { type: 'any', description: 'Search results or generated embeddings' },
+       data: { type: 'any', description: 'Response data from Pinecone' },
+       usage: { type: 'any', description: 'API usage statistics' },
+     },
    }
    ```
 
@@ -367,8 +416,8 @@ In addition, you will need to update the registries:
    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
-   import { ToolConfig, ToolResponse } from '../types'
-   import { PineconeParams, PineconeResponse } from './types'
+   import { ToolConfig, ToolResponse } from '@/tools/types'
+   import { PineconeParams, PineconeResponse } from '@/tools/pinecone/types'
 
    export const fetchTool: ToolConfig<PineconeParams, PineconeResponse> = {
      id: 'pinecone_fetch', // Follow the {provider}_{tool_name} format
@@ -399,9 +448,6 @@ In addition, you will need to update the registries:
      transformResponse: async (response: Response) => {
        // Transform response
      },
-     transformError: (error) => {
-       // Handle errors
-     },
    }
    ```
 
@@ -409,7 +455,7 @@ In addition, you will need to update the registries:
    Update the tools registry in `/apps/sim/tools/index.ts` to include your new tool:
 
    ```typescript:/apps/sim/tools/index.ts
-   import { fetchTool, generateEmbeddingsTool, searchTextTool } from './pinecone'
+   import { fetchTool, generateEmbeddingsTool, searchTextTool } from '/@tools/pinecone'
    // ... other imports
 
    export const tools: Record<string, ToolConfig> = {
@@ -443,7 +489,7 @@ Maintaining consistent naming across the codebase is critical for auto-generatio
 
 ### 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:
+Sim 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                |
 |-------------|-----------|----------|--------------------------------|
@@ -488,7 +534,7 @@ This visibility system ensures clean user interfaces while maintaining full flex
 
 ### Guidelines & Best Practices
 
-- **Code Style:** Follow the project's ESLint and Prettier configurations. Use meaningful variable names and small, focused functions.
+- **Code Style:** Follow the project's Biome 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.
@@ -509,7 +555,7 @@ This project is licensed under the Apache License 2.0. By contributing, you agre
 
 By contributing to this repository, you agree that your contributions are provided under the terms of the Apache License Version 2.0, as included in the LICENSE file of this repository.
 
-In addition, by submitting your contributions, you grant Sim Studio, Inc. ("The Licensor") a perpetual, irrevocable, worldwide, royalty-free, sublicensable right and license to:
+In addition, by submitting your contributions, you grant Sim, Inc. ("The Licensor") a perpetual, irrevocable, worldwide, royalty-free, sublicensable right and license to:
 
 - Use, copy, modify, distribute, publicly display, publicly perform, and prepare derivative works of your contributions.
 - Incorporate your contributions into other works or products.
@@ -521,4 +567,4 @@ If you do not agree with these terms, you must not contribute your work to this
 
 ---
 
-Thank you for taking the time to contribute to Sim Studio. We truly appreciate your efforts and look forward to collaborating with you!
+Thank you for taking the time to contribute to Sim. We truly appreciate your efforts and look forward to collaborating with you!

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,42 +1,25 @@
-## Description
+## Summary
+Brief description of what this PR does and why.
 
-Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
+Fixes #(issue)
 
-Fixes # (issue)
+## Type of Change
+- [ ] Bug fix
+- [ ] New feature  
+- [ ] Breaking change
+- [ ] Documentation
+- [ ] Other: ___________
 
-## Type of change
+## Testing
+How has this been tested? What should reviewers focus on?
 
-Please delete options that are not relevant.
-
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] Documentation update
-- [ ] Security enhancement
-- [ ] Performance improvement
-- [ ] Code refactoring (no functional changes)
-
-## How Has This Been Tested?
-
-Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
-
-## Checklist:
-
-- [ ] My code follows the style guidelines of this project
-- [ ] 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`)
-- [ ] 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)
+## Checklist
+- [ ] Code follows project style guidelines
+- [ ] Self-reviewed my changes
+- [ ] Tests added/updated and passing
+- [ ] No new warnings introduced
 - [ ] I confirm that I have read and agree to the terms outlined in the [Contributor License Agreement (CLA)](./CONTRIBUTING.md#contributor-license-agreement-cla)
 
-## Security Considerations:
-
-- [ ] My changes do not introduce any new security vulnerabilities
-- [ ] I have considered the security implications of my changes
-
-## Additional Information:
-
-Any additional information, configuration or data that might be necessary to reproduce the issue or use the feature.
+## Screenshots/Videos
+<!-- If applicable, add screenshots or videos to help explain your changes -->
+<!-- For UI changes, before/after screenshots are especially helpful -->

.github/SECURITY.md

@@ -8,11 +8,11 @@
 
 ## Reporting a Vulnerability
 
-We take the security of Sim Studio seriously. If you believe you've found a security vulnerability, please follow these steps:
+We take the security of Sim seriously. If you believe you've found a security vulnerability, please follow these steps:
 
 1. **Do not disclose the vulnerability publicly** or to any third parties.
 
-2. **Email us directly** at security@simstudio.ai with details of the vulnerability.
+2. **Email us directly** at security@sim.ai with details of the vulnerability.
 
 3. **Include the following information** in your report:
 

.github/workflows/build.yml

@@ -2,22 +2,47 @@ name: Build and Publish Docker Image
 
 on:
   push:
-    branches: [main]
-    tags: ['v*']
+    branches: [main, staging]
 
 jobs:
   build-and-push:
-    runs-on: ubuntu-latest
     strategy:
       fail-fast: false
       matrix:
         include:
+          # AMD64 builds on x86 runners
           - dockerfile: ./docker/app.Dockerfile
             image: ghcr.io/simstudioai/simstudio
+            platform: linux/amd64
+            arch: amd64
+            runner: linux-x64-8-core
           - dockerfile: ./docker/db.Dockerfile
             image: ghcr.io/simstudioai/migrations
+            platform: linux/amd64
+            arch: amd64
+            runner: linux-x64-8-core
           - dockerfile: ./docker/realtime.Dockerfile
             image: ghcr.io/simstudioai/realtime
+            platform: linux/amd64
+            arch: amd64
+            runner: linux-x64-8-core
+          # ARM64 builds on native ARM64 runners
+          - dockerfile: ./docker/app.Dockerfile
+            image: ghcr.io/simstudioai/simstudio
+            platform: linux/arm64
+            arch: arm64
+            runner: linux-arm64-8-core
+          - dockerfile: ./docker/db.Dockerfile
+            image: ghcr.io/simstudioai/migrations
+            platform: linux/arm64
+            arch: arm64
+            runner: linux-arm64-8-core
+          - dockerfile: ./docker/realtime.Dockerfile
+            image: ghcr.io/simstudioai/realtime
+            platform: linux/arm64
+            arch: arm64
+            runner: linux-arm64-8-core
+    runs-on: ${{ matrix.runner }}
     permissions:
       contents: read
       packages: write
@@ -26,14 +51,11 @@ jobs:
       - 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'
+        if: github.event_name != 'pull_request' && github.ref == 'refs/heads/main'
         uses: docker/login-action@v3
         with:
           registry: ghcr.io
@@ -46,21 +68,84 @@ jobs:
         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
+            type=raw,value=latest-${{ matrix.arch }},enable=${{ github.ref == 'refs/heads/main' }}
+            type=raw,value=staging-${{ github.sha }}-${{ matrix.arch }},enable=${{ github.ref == 'refs/heads/staging' }}
+            type=sha,format=long,suffix=-${{ matrix.arch }}
 
       - 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' }}
+          platforms: ${{ matrix.platform }}
+          push: ${{ github.event_name != 'pull_request' && github.ref == 'refs/heads/main' }}
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
+          cache-from: type=gha,scope=build-v3
+          cache-to: type=gha,mode=max,scope=build-v3
+          provenance: false
+          sbom: false
+
+  create-manifests:
+    runs-on: ubuntu-latest
+    needs: build-and-push
+    if: github.event_name != 'pull_request' && github.ref == 'refs/heads/main'
+    strategy:
+      matrix:
+        include:
+          - image: ghcr.io/simstudioai/simstudio
+          - image: ghcr.io/simstudioai/migrations
+          - image: ghcr.io/simstudioai/realtime
+    permissions:
+      contents: read
+      packages: write
+
+    steps:
+      - name: Log in to the Container registry
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.repository_owner }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Extract metadata for manifest
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: ${{ matrix.image }}
+          tags: |
+            type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' }}
+            type=sha,format=long
+
+      - name: Create and push manifest
+        run: |
+          # Extract the tags from metadata (these are the final manifest tags we want)
+          MANIFEST_TAGS="${{ steps.meta.outputs.tags }}"
+
+          # Create manifest for each tag
+          for manifest_tag in $MANIFEST_TAGS; do
+            echo "Creating manifest for $manifest_tag"
+
+            # The architecture-specific images have -amd64 and -arm64 suffixes
+            amd64_image="${manifest_tag}-amd64"
+            arm64_image="${manifest_tag}-arm64"
+
+            echo "Looking for images: $amd64_image and $arm64_image"
+
+            # Check if both architecture images exist
+            if docker manifest inspect "$amd64_image" >/dev/null 2>&1 && docker manifest inspect "$arm64_image" >/dev/null 2>&1; then
+              echo "Both images found, creating manifest..."
+              docker manifest create "$manifest_tag" \
+                "$amd64_image" \
+                "$arm64_image"
+              docker manifest push "$manifest_tag"
+              echo "Successfully created and pushed manifest for $manifest_tag"
+            else
+              echo "Error: One or both architecture images not found"
+              echo "Checking AMD64 image: $amd64_image"
+              docker manifest inspect "$amd64_image" || echo "AMD64 image not found"
+              echo "Checking ARM64 image: $arm64_image"
+              docker manifest inspect "$arm64_image" || echo "ARM64 image not found"
+              exit 1
+            fi
+          done

.github/workflows/ci.yml

@@ -26,19 +26,19 @@ jobs:
           node-version: latest
 
       - name: Install dependencies
-        run: bun install
+        run: bun install --frozen-lockfile
 
       - name: Run tests with coverage
         env:
           NODE_OPTIONS: '--no-warnings'
-          NEXT_PUBLIC_APP_URL: 'https://www.simstudio.ai'
+          NEXT_PUBLIC_APP_URL: 'https://www.sim.ai'
           ENCRYPTION_KEY: '7cf672e460e430c1fba707575c2b0e2ad5a99dddf9b7b7e3b5646e630861db1c' # dummy key for CI only
         run: bun run test
 
       - name: Build application
         env:
           NODE_OPTIONS: '--no-warnings'
-          NEXT_PUBLIC_APP_URL: 'https://www.simstudio.ai'
+          NEXT_PUBLIC_APP_URL: 'https://www.sim.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'
@@ -74,4 +74,4 @@ jobs:
         working-directory: ./apps/sim
         env:
           DATABASE_URL: ${{ github.ref == 'refs/heads/main' && secrets.DATABASE_URL || secrets.STAGING_DATABASE_URL }}
-        run: bunx drizzle-kit push
+        run: bunx drizzle-kit migrate

.github/workflows/docs-embeddings.yml

@@ -0,0 +1,38 @@
+name: Process Docs Embeddings
+
+on:
+  push:
+    branches: [main, staging]
+    paths:
+      - 'apps/docs/**'
+  workflow_dispatch: # Allow manual triggering
+
+jobs:
+  process-docs-embeddings:
+    name: Process Documentation Embeddings
+    runs-on: ubuntu-latest
+    if: github.ref == 'refs/heads/main' || github.ref == 'refs/heads/staging'
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Process docs embeddings
+        working-directory: ./apps/sim
+        env:
+          DATABASE_URL: ${{ github.ref == 'refs/heads/main' && secrets.DATABASE_URL || secrets.STAGING_DATABASE_URL }}
+          OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
+        run: bun run scripts/process-docs-embeddings.ts --clear 

.github/workflows/trigger-deploy.yml

@@ -0,0 +1,44 @@
+name: Trigger.dev Deploy
+
+on:
+  push:
+    branches:
+      - main
+      - staging
+
+jobs:
+  deploy:
+    name: Trigger.dev Deploy
+    runs-on: ubuntu-latest
+    concurrency:
+      group: trigger-deploy-${{ github.ref }}
+      cancel-in-progress: false
+    env:
+      TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 'lts/*'
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Deploy to Staging
+        if: github.ref == 'refs/heads/staging'
+        working-directory: ./apps/sim
+        run: npx --yes trigger.dev@4.0.1 deploy -e staging
+
+      - name: Deploy to Production
+        if: github.ref == 'refs/heads/main'
+        working-directory: ./apps/sim
+        run: npx --yes trigger.dev@4.0.1 deploy
+

.gitignore

@@ -65,4 +65,7 @@ start-collector.sh
 .turbo
 
 # VSCode
-.vscode
+.vscode
+
+## Helm Chart Tests
+helm/sim/test

NOTICE

@@ -1,4 +1,4 @@
 Sim Studio
 Copyright 2025 Sim Studio
 
-This product includes software developed for the Sim Studio project. 
+This product includes software developed for the Sim project. 

README.md

@@ -1,50 +1,46 @@
 <p align="center">
-  <img src="apps/sim/public/static/sim.png" alt="Sim Studio Logo" width="500"/>
+  <a href="https://sim.ai" target="_blank" rel="noopener noreferrer">
+    <img src="apps/sim/public/logo/reverse/text/large.png" alt="Sim Logo" width="500"/>
+  </a>
+</p>
+
+<p align="center">Build and deploy AI agent workflows in minutes.</p>
+
+<p align="center">
+  <a href="https://sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/sim.ai-6F3DFA" alt="Sim.ai"></a>
+  <a href="https://discord.gg/Hr4UWYEcTT" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/Discord-Join%20Server-5865F2?logo=discord&logoColor=white" alt="Discord"></a>
+  <a href="https://x.com/simdotai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/twitter/follow/simstudioai?style=social" alt="Twitter"></a>
+  <a href="https://docs.sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/Docs-6F3DFA.svg" alt="Documentation"></a>
 </p>
 
 <p align="center">
-  <a href="https://www.apache.org/licenses/LICENSE-2.0"><img src="https://img.shields.io/badge/License-Apache%202.0-blue.svg" alt="License: Apache-2.0"></a>
-  <a href="https://discord.gg/Hr4UWYEcTT"><img src="https://img.shields.io/badge/Discord-Join%20Server-7289DA?logo=discord&logoColor=white" alt="Discord"></a>
-  <a href="https://x.com/simstudioai"><img src="https://img.shields.io/twitter/follow/simstudioai?style=social" alt="Twitter"></a>
-  <a href="https://github.com/simstudioai/sim/pulls"><img src="https://img.shields.io/badge/PRs-welcome-brightgreen.svg" alt="PRs welcome"></a>
-  <a href="https://docs.simstudio.ai"><img src="https://img.shields.io/badge/Docs-visit%20documentation-blue.svg" alt="Documentation"></a>
+  <img src="apps/sim/public/static/demo.gif" alt="Sim Demo" width="800"/>
 </p>
 
-<p align="center">
-  <strong>Sim Studio</strong> is a lightweight, user-friendly platform for building AI agent workflows.
-</p>
+## Quickstart
 
-<p align="center">
-  <img src="apps/sim/public/static/demo.gif" alt="Sim Studio Demo" width="800"/>
-</p>
+### Cloud-hosted: [sim.ai](https://sim.ai)
 
-## Getting Started
+<a href="https://sim.ai" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/sim.ai-6F3DFA?logo=data:image/svg%2bxml;base64,PHN2ZyB3aWR0aD0iNjE2IiBoZWlnaHQ9IjYxNiIgdmlld0JveD0iMCAwIDYxNiA2MTYiIGZpbGw9Im5vbmUiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI+CjxnIGNsaXAtcGF0aD0idXJsKCNjbGlwMF8xMTU5XzMxMykiPgo8cGF0aCBkPSJNNjE2IDBIMFY2MTZINjE2VjBaIiBmaWxsPSIjNkYzREZBIi8+CjxwYXRoIGQ9Ik04MyAzNjUuNTY3SDExM0MxMTMgMzczLjgwNSAxMTYgMzgwLjM3MyAxMjIgMzg1LjI3MkMxMjggMzg5Ljk0OCAxMzYuMTExIDM5Mi4yODUgMTQ2LjMzMyAzOTIuMjg1QzE1Ny40NDQgMzkyLjI4NSAxNjYgMzkwLjE3MSAxNzIgMzg1LjkzOUMxNzcuOTk5IDM4MS40ODcgMTgxIDM3NS41ODYgMTgxIDM2OC4yMzlDMTgxIDM2Mi44OTUgMTc5LjMzMyAzNTguNDQyIDE3NiAzNTQuODhDMTcyLjg4OSAzNTEuMzE4IDE2Ny4xMTEgMzQ4LjQyMiAxNTguNjY3IDM0Ni4xOTZMMTMwIDMzOS41MTdDMTE1LjU1NSAzMzUuOTU1IDEwNC43NzggMzMwLjQ5OSA5Ny42NjY1IDMyMy4xNTFDOTAuNzc3NSAzMTUuODA0IDg3LjMzMzQgMzA2LjExOSA4Ny4zMzM0IDI5NC4wOTZDODcuMzMzNCAyODQuMDc2IDg5Ljg4OSAyNzUuMzkyIDk0Ljk5OTYgMjY4LjA0NUMxMDAuMzMzIDI2MC42OTcgMTA3LjU1NSAyNTUuMDIgMTE2LjY2NiAyNTEuMDEyQzEyNiAyNDcuMDA0IDEzNi42NjcgMjQ1IDE0OC42NjYgMjQ1QzE2MC42NjcgMjQ1IDE3MSAyNDcuMTE2IDE3OS42NjcgMjUxLjM0NkMxODguNTU1IDI1NS41NzYgMTk1LjQ0NCAyNjEuNDc3IDIwMC4zMzMgMjY5LjA0N0MyMDUuNDQ0IDI3Ni42MTcgMjA4LjExMSAyODUuNjM0IDIwOC4zMzMgMjk2LjA5OUgxNzguMzMzQzE3OC4xMTEgMjg3LjYzOCAxNzUuMzMzIDI4MS4wNyAxNjkuOTk5IDI3Ni4zOTRDMTY0LjY2NiAyNzEuNzE5IDE1Ny4yMjIgMjY5LjM4MSAxNDcuNjY3IDI2OS4zODFDMTM3Ljg4OSAyNjkuMzgxIDEzMC4zMzMgMjcxLjQ5NiAxMjUgMjc1LjcyNkMxMTkuNjY2IDI3OS45NTcgMTE3IDI4NS43NDYgMTE3IDI5My4wOTNDMTE3IDMwNC4wMDMgMTI1IDMxMS40NjIgMTQxIDMxNS40N0wxNjkuNjY3IDMyMi40ODNDMTgzLjQ0NSAzMjUuNiAxOTMuNzc4IDMzMC43MjIgMjAwLjY2NyAzMzcuODQ3QzIwNy41NTUgMzQ0Ljc0OSAyMTEgMzU0LjIxMiAyMTEgMzY2LjIzNUMyMTEgMzc2LjQ3NyAyMDguMjIyIDM4NS40OTQgMjAyLjY2NiAzOTMuMjg3QzE5Ny4xMTEgNDAwLjg1NyAxODkuNDQ0IDQwNi43NTggMTc5LjY2NyA0MTAuOTg5QzE3MC4xMTEgNDE0Ljk5NiAxNTguNzc4IDQxNyAxNDUuNjY3IDQxN0MxMjYuNTU1IDQxNyAxMTEuMzMzIDQxMi4zMjUgOTkuOTk5NyA0MDIuOTczQzg4LjY2NjggMzkzLjYyMSA4MyAzODEuMTUzIDgzIDM2NS41NjdaIiBmaWxsPSJ3aGl0ZSIvPgo8cGF0aCBkPSJNMjMyLjI5MSA0MTNWMjUwLjA4MkMyNDQuNjg0IDI1NC42MTQgMjUwLjE0OCAyNTQuNjE0IDI2My4zNzEgMjUwLjA4MlY0MTNIMjMyLjI5MVpNMjQ3LjUgMjM5LjMxM0MyNDEuOTkgMjM5LjMxMyAyMzcuMTQgMjM3LjMxMyAyMzIuOTUyIDIzMy4zMTZDMjI4Ljk4NCAyMjkuMDk1IDIyNyAyMjQuMjA5IDIyNyAyMTguNjU2QzIyNyAyMTIuODgyIDIyOC45ODQgMjA3Ljk5NSAyMzIuOTUyIDIwMy45OTdDMjM3LjE0IDE5OS45OTkgMjQxLjk5IDE5OCAyNDcuNSAxOThDMjUzLjIzMSAxOTggMjU4LjA4IDE5OS45OTkgMjYyLjA0OSAyMDMuOTk3QzI2Ni4wMTYgMjA3Ljk5NSAyNjggMjEyLjg4MiAyNjggMjE4LjY1NkMyNjggMjI0LjIwOSAyNjYuMDE2IDIyOS4wOTUgMjYyLjA0OSAyMzMuMzE2QzI1OC4wOCAyMzcuMzEzIDI1My4yMzEgMjM5LjMxMyAyNDcuNSAyMzkuMzEzWiIgZmlsbD0id2hpdGUiLz4KPHBhdGggZD0iTTMxOS4zMzMgNDEzSDI4OFYyNDkuNjc2SDMxNlYyNzcuMjMzQzMxOS4zMzMgMjY4LjEwNCAzMjUuNzc4IDI2MC4zNjQgMzM0LjY2NyAyNTQuMzUyQzM0My43NzggMjQ4LjExNyAzNTQuNzc4IDI0NSAzNjcuNjY3IDI0NUMzODIuMTExIDI0NSAzOTQuMTEyIDI0OC44OTcgNDAzLjY2NyAyNTYuNjlDNDEzLjIyMiAyNjQuNDg0IDQxOS40NDQgMjc0LjgzNyA0MjIuMzM0IDI4Ny43NTJINDE2LjY2N0M0MTguODg5IDI3NC44MzcgNDI1IDI2NC40ODQgNDM1IDI1Ni42OUM0NDUgMjQ4Ljg5NyA0NTcuMzM0IDI0NSA0NzIgMjQ1QzQ5MC42NjYgMjQ1IDUwNS4zMzQgMjUwLjQ1NSA1MTYgMjYxLjM2NkM1MjYuNjY3IDI3Mi4yNzYgNTMyIDI4Ny4xOTUgNTMyIDMwNi4xMjFWNDEzSDUwMS4zMzNWMzEzLjgwNEM1MDEuMzMzIDMwMC44ODkgNDk4IDI5MC45ODEgNDkxLjMzMyAyODQuMDc4QzQ4NC44ODkgMjc2Ljk1MiA0NzYuMTExIDI3My4zOSA0NjUgMjczLjM5QzQ1Ny4yMjIgMjczLjM5IDQ1MC4zMzMgMjc1LjE3MSA0NDQuMzM0IDI3OC43MzRDNDM4LjU1NiAyODIuMDc0IDQzNCAyODYuOTcyIDQzMC42NjcgMjkzLjQzQzQyNy4zMzMgMjk5Ljg4NyA0MjUuNjY3IDMwNy40NTcgNDI1LjY2NyAzMTYuMTQxVjQxM0gzOTQuNjY3VjMxMy40NjlDMzk0LjY2NyAzMDAuNTU1IDM5MS40NDUgMjkwLjc1OCAzODUgMjg0LjA3OEMzNzguNTU2IDI3Ny4xNzUgMzY5Ljc3OCAyNzMuNzI0IDM1OC42NjcgMjczLjcyNEMzNTAuODg5IDI3My43MjQgMzQ0IDI3NS41MDUgMzM4IDI3OS4wNjhDMzMyLjIyMiAyODIuNDA4IDMyNy42NjcgMjg3LjMwNyAzMjQuMzMzIDI5My43NjNDMzIxIDI5OS45OTggMzE5LjMzMyAzMDcuNDU3IDMxOS4zMzMgMzE2LjE0MVY0MTNaIiBmaWxsPSJ3aGl0ZSIvPgo8L2c+CjxkZWZzPgo8Y2xpcFBhdGggaWQ9ImNsaXAwXzExNTlfMzEzIj4KPHJlY3Qgd2lkdGg9IjYxNiIgaGVpZ2h0PSI2MTYiIGZpbGw9IndoaXRlIi8+CjwvY2xpcFBhdGg+CjwvZGVmcz4KPC9zdmc+Cg==&logoColor=white" alt="Sim.ai"></a>
 
-1. Use our [cloud-hosted version](https://simstudio.ai)
-2. Self-host using one of the methods below
-
-## Self-Hosting Options
-
-### Option 1: NPM Package (Simplest)
-
-The easiest way to run Sim Studio locally is using our [NPM package](https://www.npmjs.com/package/simstudio?activeTab=readme):
+### Self-hosted: NPM Package
 
 ```bash
 npx simstudio
 ```
+→ http://localhost:3000
 
-After running these commands, open [http://localhost:3000/](http://localhost:3000/) in your browser.
+#### Note
+Docker must be installed and running on your machine.
 
 #### Options
 
-- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
-- `--no-pull`: Skip pulling the latest Docker images
+| Flag | Description |
+|------|-------------|
+| `-p, --port <port>` | Port to run Sim on (default `3000`) |
+| `--no-pull` | Skip pulling latest Docker images |
 
-#### Requirements
-
-- Docker must be installed and running on your machine
-
-### Option 2: Docker Compose
+### Self-hosted: Docker Compose
 
 ```bash
 # Clone the repository
@@ -53,43 +49,43 @@ git clone https://github.com/simstudioai/sim.git
 # Navigate to the project directory
 cd sim
 
-# Start Sim Studio
+# Start Sim
 docker compose -f docker-compose.prod.yml up -d
 ```
 
 Access the application at [http://localhost:3000/](http://localhost:3000/)
 
-#### Using Local Models
+#### Using Local Models with Ollama
 
-To use local models with Sim Studio:
-
-1. Pull models using our helper script:
+Run Sim with local AI models using [Ollama](https://ollama.ai) - no external APIs required:
 
 ```bash
-./apps/sim/scripts/ollama_docker.sh pull <model_name>
+# Start with GPU support (automatically downloads gemma3:4b model)
+docker compose -f docker-compose.ollama.yml --profile setup up -d
+
+# For CPU-only systems:
+docker compose -f docker-compose.ollama.yml --profile cpu --profile setup up -d
 ```
 
-2. Start Sim Studio with local model support:
-
+Wait for the model to download, then visit [http://localhost:3000](http://localhost:3000). Add more models with:
 ```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
+docker compose -f docker-compose.ollama.yml exec ollama ollama pull llama3.1:8b
 ```
 
-### Option 3: Dev Containers
+### Self-hosted: Dev Containers
 
 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
 
-### Option 4: Manual Setup
+### Self-hosted: Manual Setup
+
+**Requirements:**
+- [Bun](https://bun.sh/) runtime
+- PostgreSQL 12+ with [pgvector extension](https://github.com/pgvector/pgvector) (required for AI embeddings)
+
+**Note:** Sim uses vector embeddings for AI features like knowledge bases and semantic search, which requires the `pgvector` PostgreSQL extension.
 
 1. Clone and install dependencies:
 
@@ -99,20 +95,43 @@ cd sim
 bun install
 ```
 
-2. Set up environment:
+2. Set up PostgreSQL with pgvector:
+
+You need PostgreSQL with the `vector` extension for embedding support. Choose one option:
+
+**Option A: Using Docker (Recommended)**
+```bash
+# Start PostgreSQL with pgvector extension
+docker run --name simstudio-db \
+  -e POSTGRES_PASSWORD=your_password \
+  -e POSTGRES_DB=simstudio \
+  -p 5432:5432 -d \
+  pgvector/pgvector:pg17
+```
+
+**Option B: Manual Installation**
+- Install PostgreSQL 12+ and the pgvector extension
+- See [pgvector installation guide](https://github.com/pgvector/pgvector#installation)
+
+3. Set up environment:
 
 ```bash
 cd apps/sim
 cp .env.example .env  # Configure with required variables (DATABASE_URL, BETTER_AUTH_SECRET, BETTER_AUTH_URL)
 ```
 
-3. Set up the database:
-
+Update your `.env` file with the database URL:
 ```bash
-bunx drizzle-kit push
+DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio"
 ```
 
-4. Start the development servers:
+4. Set up the database:
+
+```bash
+bunx drizzle-kit migrate 
+```
+
+5. Start the development servers:
 
 **Recommended approach - run both servers together (from project root):**
 
@@ -135,6 +154,13 @@ cd apps/sim
 bun run dev:sockets
 ```
 
+## Copilot API Keys
+
+Copilot is a Sim-managed service. To use Copilot on a self-hosted instance:
+
+- Go to https://sim.ai → Settings → Copilot and generate a Copilot API key
+- Set `COPILOT_API_KEY` environment variable in your self-hosted apps/sim/.env file to that value
+
 ## Tech Stack
 
 - **Framework**: [Next.js](https://nextjs.org/) (App Router)
@@ -148,6 +174,7 @@ bun run dev:sockets
 - **Monorepo**: [Turborepo](https://turborepo.org/)
 - **Realtime**: [Socket.io](https://socket.io/)
 - **Background Jobs**: [Trigger.dev](https://trigger.dev/)
+- **Remote Code Execution**: [E2B](https://www.e2b.dev/)
 
 ## Contributing
 
@@ -157,4 +184,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 Team</p>

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

@@ -1,6 +1,6 @@
+import defaultMdxComponents from 'fumadocs-ui/mdx'
 import { DocsBody, DocsDescription, DocsPage, DocsTitle } from 'fumadocs-ui/page'
 import { notFound } from 'next/navigation'
-import mdxComponents from '@/components/mdx-components'
 import { source } from '@/lib/source'
 
 export const dynamic = 'force-dynamic'
@@ -36,7 +36,7 @@ export default async function Page(props: { params: Promise<{ slug?: string[] }>
       <DocsTitle>{page.data.title}</DocsTitle>
       <DocsDescription>{page.data.description}</DocsDescription>
       <DocsBody>
-        <MDX components={mdxComponents} />
+        <MDX components={defaultMdxComponents} />
       </DocsBody>
     </DocsPage>
   )

apps/docs/app/(docs)/layout.tsx

@@ -1,6 +1,7 @@
 import type { ReactNode } from 'react'
 import { DocsLayout } from 'fumadocs-ui/layouts/docs'
 import { ExternalLink, GithubIcon } from 'lucide-react'
+import Image from 'next/image'
 import Link from 'next/link'
 import { source } from '@/lib/source'
 
@@ -23,19 +24,30 @@ export default function Layout({ children }: { children: ReactNode }) {
       <DocsLayout
         tree={source.pageTree}
         nav={{
-          title: <div className='flex items-center font-medium'>Sim Studio</div>,
+          title: (
+            <div className='flex items-center'>
+              <Image
+                src='/static/logo.png'
+                alt='Sim'
+                width={60}
+                height={24}
+                className='h-6 w-auto'
+              />
+            </div>
+          ),
         }}
         links={[
           {
-            text: 'Visit Sim Studio',
-            url: 'https://simstudio.ai',
+            text: 'Visit Sim',
+            url: 'https://sim.ai',
             icon: <ExternalLink className='h-4 w-4' />,
           },
         ]}
         sidebar={{
-          defaultOpenLevel: 1,
+          defaultOpenLevel: 0,
           collapsible: true,
           footer: null,
+          banner: null,
         }}
       >
         {children}

apps/docs/app/global.css

@@ -6,6 +6,150 @@
   --color-fd-primary: #802fff; /* Purple from control-bar component */
 }
 
+/* Target any potential border classes */
+* {
+  --fd-border-sidebar: transparent !important;
+}
+
+/* Override any CSS custom properties for borders */
+:root {
+  --fd-border: transparent !important;
+  --fd-border-sidebar: transparent !important;
+}
+
+/* Sidebar improvements for cleaner design */
+[data-sidebar] {
+  --fd-sidebar-width: 280px;
+  background-color: rgb(255 255 255);
+  padding-top: 16px;
+}
+
+/* Clean sidebar container */
+[data-sidebar] > div {
+  padding: 0 16px;
+}
+
+/* Section headers/separators styling */
+[data-sidebar] .text-sm.font-medium.text-muted-foreground,
+[data-sidebar] [data-separator] {
+  font-size: 11px;
+  font-weight: 600;
+  text-transform: uppercase;
+  letter-spacing: 0.05em;
+  margin-top: 20px;
+  margin-bottom: 6px;
+  padding-left: 12px;
+  padding-right: 12px;
+  color: rgb(115 115 115);
+  border: none;
+  background: none;
+}
+
+/* First separator should have less top margin */
+[data-sidebar] [data-separator]:first-of-type {
+  margin-top: 12px;
+}
+
+/* Clean sidebar item styling */
+[data-sidebar] a {
+  padding: 8px 12px;
+  margin: 1px 0;
+  border-radius: 6px;
+  font-size: 14px;
+  font-weight: 400;
+  line-height: 1.4;
+  transition: all 0.15s ease;
+  display: block;
+  color: rgb(71 85 105);
+  text-decoration: none;
+}
+
+[data-sidebar] a[data-active="true"] {
+  background-color: rgba(128, 47, 255, 0.08);
+  color: var(--color-fd-primary);
+  font-weight: 500;
+}
+
+[data-sidebar] a:hover:not([data-active="true"]) {
+  background-color: rgb(248 250 252);
+  color: rgb(51 65 85);
+}
+
+/* Improve spacing between sidebar items */
+[data-sidebar] nav > * + * {
+  margin-top: 2px;
+}
+
+/* Section group styling */
+[data-sidebar] [data-folder] {
+  margin-bottom: 4px;
+}
+
+[data-sidebar] [data-folder] > div:first-child {
+  font-weight: 500;
+  font-size: 13px;
+  color: rgb(15 23 42);
+  padding: 6px 12px;
+  margin-bottom: 4px;
+}
+
+/* Clean up folder toggle buttons */
+[data-sidebar] button[data-folder-toggle] {
+  padding: 4px 8px 4px 12px;
+  border-radius: 6px;
+  font-size: 13px;
+  font-weight: 500;
+  color: rgb(51 65 85);
+}
+
+[data-sidebar] button[data-folder-toggle]:hover {
+  background-color: rgb(248 250 252);
+}
+
+/* Nested item indentation */
+[data-sidebar] [data-folder] a {
+  padding-left: 24px;
+  font-size: 14px;
+}
+
+/* Dark mode adjustments */
+@media (prefers-color-scheme: dark) {
+  [data-sidebar] {
+    background-color: rgb(2 8 23);
+  }
+
+  [data-sidebar] a {
+    color: rgb(148 163 184);
+  }
+
+  [data-sidebar] a:hover:not([data-active="true"]) {
+    background-color: rgb(30 41 59);
+    color: rgb(226 232 240);
+  }
+
+  [data-sidebar] a[data-active="true"] {
+    background-color: rgba(128, 47, 255, 0.15);
+    color: var(--color-fd-primary);
+  }
+
+  [data-sidebar] .text-sm.font-medium.text-muted-foreground,
+  [data-sidebar] [data-separator] {
+    color: rgb(148 163 184);
+  }
+
+  [data-sidebar] [data-folder] > div:first-child {
+    color: rgb(226 232 240);
+  }
+
+  [data-sidebar] button[data-folder-toggle] {
+    color: rgb(148 163 184);
+  }
+
+  [data-sidebar] button[data-folder-toggle]:hover {
+    background-color: rgb(30 41 59);
+  }
+}
+
 /* Custom text highlighting styles */
 .text-highlight {
   color: var(--color-fd-primary);
@@ -16,6 +160,23 @@
   color: var(--color-fd-primary);
 }
 
+/* Add bottom spacing to prevent abrupt page endings */
+[data-content] {
+  padding-bottom: 4rem;
+}
+
+/* Alternative fallback for different Fumadocs versions */
+main article,
+.docs-page main {
+  padding-bottom: 4rem;
+}
+
+/* Remove any unwanted borders/outlines from video elements */
+video {
+  outline: none !important;
+  border-style: solid !important;
+}
+
 /* Tailwind v4 content sources */
 @source '../app/**/*.{js,ts,jsx,tsx,mdx}';
 @source '../components/**/*.{js,ts,jsx,tsx,mdx}';

apps/docs/app/layout.tsx

@@ -22,7 +22,7 @@ export default function Layout({ children }: { children: ReactNode }) {
 }
 
 export const metadata = {
-  title: 'Sim Studio',
+  title: 'Sim',
   description:
     'Build agents in seconds with a drag and drop workflow builder. Access comprehensive documentation to help you create efficient workflows and maximize your automation capabilities.',
   manifest: '/favicon/site.webmanifest',
@@ -37,6 +37,6 @@ export const metadata = {
   appleWebApp: {
     capable: true,
     statusBarStyle: 'default',
-    title: 'Sim Studio Docs',
+    title: 'Sim Docs',
   },
 }

apps/docs/components/mdx-components.tsx

@@ -1,10 +0,0 @@
-import defaultMdxComponents from 'fumadocs-ui/mdx'
-import { ThemeImage } from './ui/theme-image'
-
-// Extend the default MDX components with our custom components
-const mdxComponents = {
-  ...defaultMdxComponents,
-  ThemeImage,
-}
-
-export default mdxComponents

apps/docs/components/ui/block-types.tsx

@@ -1,163 +0,0 @@
-import { cn } from '@/lib/utils'
-import {
-  AgentIcon,
-  ApiIcon,
-  ChartBarIcon,
-  CodeIcon,
-  ConditionalIcon,
-  ConnectIcon,
-  ResponseIcon,
-} from '../icons'
-
-// Custom Feature component specifically for BlockTypes to handle the 6-item layout
-const BlockFeature = ({
-  title,
-  description,
-  icon,
-  href,
-  index,
-  totalItems,
-  itemsPerRow,
-}: {
-  title: string
-  description: string
-  icon: React.ReactNode
-  href?: string
-  index: number
-  totalItems: number
-  itemsPerRow: number
-}) => {
-  const blockColor = {
-    '--block-color':
-      title === 'Agent'
-        ? '#8b5cf6'
-        : title === 'API'
-          ? '#3b82f6'
-          : title === 'Condition'
-            ? '#f59e0b'
-            : title === 'Function'
-              ? '#10b981'
-              : title === 'Router'
-                ? '#6366f1'
-                : title === 'Evaluator'
-                  ? '#ef4444'
-                  : '#8b5cf6',
-  } as React.CSSProperties
-
-  const content = (
-    <>
-      {index < itemsPerRow && (
-        <div className='pointer-events-none absolute inset-0 h-full w-full bg-gradient-to-t from-neutral-100 to-transparent opacity-0 transition duration-200 group-hover/feature:opacity-100 dark:from-neutral-800' />
-      )}
-      {index >= itemsPerRow && (
-        <div className='pointer-events-none absolute inset-0 h-full w-full bg-gradient-to-b from-neutral-100 to-transparent opacity-0 transition duration-200 group-hover/feature:opacity-100 dark:from-neutral-800' />
-      )}
-      <div
-        className='relative z-10 mb-4 px-10 text-neutral-500 transition-colors duration-200 group-hover/feature:text-[color:var(--block-color,#8b5cf6)] dark:text-neutral-400 dark:group-hover/feature:text-[color:var(--block-color,#a78bfa)]'
-        style={blockColor}
-      >
-        {icon}
-      </div>
-      <div className='relative z-10 mb-2 px-10 font-bold text-lg'>
-        <div
-          className='absolute inset-y-0 left-0 h-6 w-1 origin-center rounded-tr-full rounded-br-full bg-neutral-300 transition-all duration-200 group-hover/feature:h-8 group-hover/feature:bg-[color:var(--block-color,#8b5cf6)] dark:bg-neutral-700'
-          style={blockColor}
-        />
-        <span className='inline-block text-neutral-800 transition duration-200 group-hover/feature:translate-x-2 dark:text-neutral-100'>
-          {title}
-        </span>
-      </div>
-      <p className='relative z-10 max-w-xs px-10 text-neutral-600 text-sm dark:text-neutral-300'>
-        {description}
-      </p>
-    </>
-  )
-
-  const containerClasses = cn(
-    'flex flex-col lg:border-r py-5 relative group/feature dark:border-neutral-800',
-    (index === 0 || index === itemsPerRow) && 'lg:border-l dark:border-neutral-800',
-    index < itemsPerRow && 'lg:border-b dark:border-neutral-800',
-    href && 'cursor-pointer hover:bg-neutral-50 dark:hover:bg-neutral-900/50 transition-colors'
-  )
-
-  if (href) {
-    return (
-      <a href={href} className={containerClasses} style={{ textDecoration: 'none' }}>
-        {content}
-      </a>
-    )
-  }
-
-  return <div className={containerClasses}>{content}</div>
-}
-
-export function BlockTypes() {
-  const features = [
-    {
-      title: 'Agent',
-      description:
-        'Create powerful AI agents using any LLM provider with customizable system prompts and tool integrations.',
-      icon: <AgentIcon className='h-6 w-6' />,
-      href: '/blocks/agent',
-    },
-    {
-      title: 'API',
-      description:
-        'Connect to any external API with support for all standard HTTP methods and customizable request parameters.',
-      icon: <ApiIcon className='h-6 w-6' />,
-      href: '/blocks/api',
-    },
-    {
-      title: 'Condition',
-      description:
-        'Add a condition to the workflow to branch the execution path based on a boolean expression.',
-      icon: <ConditionalIcon className='h-6 w-6' />,
-      href: '/blocks/condition',
-    },
-    {
-      title: 'Function',
-      description:
-        'Execute custom JavaScript or TypeScript code within your workflow to transform data or implement complex logic.',
-      icon: <CodeIcon className='h-6 w-6' />,
-      href: '/blocks/function',
-    },
-    {
-      title: 'Router',
-      description:
-        'Intelligently direct workflow execution to different paths based on input analysis.',
-      icon: <ConnectIcon className='h-6 w-6' />,
-      href: '/blocks/router',
-    },
-    {
-      title: 'Evaluator',
-      description:
-        'Assess content using customizable evaluation metrics and scoring criteria across multiple dimensions.',
-      icon: <ChartBarIcon className='h-6 w-6' />,
-      href: '/blocks/evaluator',
-    },
-    {
-      title: 'Response',
-      description:
-        'Send a response back to the caller with customizable data, status, and headers.',
-      icon: <ResponseIcon className='h-6 w-6' />,
-      href: '/blocks/response',
-    },
-  ]
-
-  const totalItems = features.length
-  const itemsPerRow = 3 // For large screens
-
-  return (
-    <div className='relative z-10 mx-auto grid max-w-7xl grid-cols-1 py-10 md:grid-cols-2 lg:grid-cols-3'>
-      {features.map((feature, index) => (
-        <BlockFeature
-          key={feature.title}
-          {...feature}
-          index={index}
-          totalItems={totalItems}
-          itemsPerRow={itemsPerRow}
-        />
-      ))}
-    </div>
-  )
-}

apps/docs/components/ui/features.tsx

@@ -1,102 +0,0 @@
-import {
-  IconAdjustmentsBolt,
-  IconCloud,
-  IconEaseInOut,
-  IconHeart,
-  IconHelp,
-  IconHistory,
-  IconRouteAltLeft,
-  IconTerminal2,
-} from '@tabler/icons-react'
-import { cn } from '@/lib/utils'
-
-export function Features() {
-  const features = [
-    {
-      title: 'Multi-LLM Support',
-      description: 'Connect to any LLM provider including OpenAI, Anthropic, and more',
-      icon: <IconCloud />,
-    },
-    {
-      title: 'API Deployment',
-      description: 'Deploy your workflows as secure, scalable APIs',
-      icon: <IconTerminal2 />,
-    },
-    {
-      title: 'Webhook Integration',
-      description: 'Trigger workflows via webhooks from external services',
-      icon: <IconRouteAltLeft />,
-    },
-    {
-      title: 'Scheduled Execution',
-      description: 'Schedule workflows to run at specific times or intervals',
-      icon: <IconEaseInOut />,
-    },
-    {
-      title: '40+ Integrations',
-      description: 'Connect to hundreds of external services and data sources',
-      icon: <IconAdjustmentsBolt />,
-    },
-    {
-      title: 'Visual Debugging',
-      description: 'Debug workflows visually with detailed execution logs',
-      icon: <IconHelp />,
-    },
-    {
-      title: 'Version Control',
-      description: 'Track changes and roll back to previous versions',
-      icon: <IconHistory />,
-    },
-    {
-      title: 'Team Collaboration',
-      description: 'Collaborate with team members on workflow development',
-      icon: <IconHeart />,
-    },
-  ]
-  return (
-    <div className='relative z-20 mx-auto grid max-w-7xl grid-cols-1 py-10 md:grid-cols-2 lg:grid-cols-4'>
-      {features.map((feature, index) => (
-        <Feature key={feature.title} {...feature} index={index} />
-      ))}
-    </div>
-  )
-}
-
-export const Feature = ({
-  title,
-  description,
-  icon,
-  index,
-}: {
-  title: string
-  description: string
-  icon: React.ReactNode
-  index: number
-}) => {
-  return (
-    <div
-      className={cn(
-        'group/feature relative flex flex-col py-5 lg:border-r dark:border-neutral-800',
-        (index === 0 || index === 4) && 'lg:border-l dark:border-neutral-800',
-        index < 4 && 'lg:border-b dark:border-neutral-800'
-      )}
-    >
-      {index < 4 && (
-        <div className='pointer-events-none absolute inset-0 h-full w-full bg-gradient-to-t from-neutral-100 to-transparent opacity-0 transition duration-200 group-hover/feature:opacity-100 dark:from-neutral-800' />
-      )}
-      {index >= 4 && (
-        <div className='pointer-events-none absolute inset-0 h-full w-full bg-gradient-to-b from-neutral-100 to-transparent opacity-0 transition duration-200 group-hover/feature:opacity-100 dark:from-neutral-800' />
-      )}
-      <div className='relative z-10 mb-4 px-10 text-neutral-600 dark:text-neutral-400'>{icon}</div>
-      <div className='relative z-10 mb-2 px-10 font-bold text-lg'>
-        <div className='absolute inset-y-0 left-0 h-6 w-1 origin-center rounded-tr-full rounded-br-full bg-neutral-300 transition-all duration-200 group-hover/feature:h-8 group-hover/feature:bg-purple-500 dark:bg-neutral-700' />
-        <span className='inline-block text-neutral-800 transition duration-200 group-hover/feature:translate-x-2 dark:text-neutral-100'>
-          {title}
-        </span>
-      </div>
-      <p className='relative z-10 max-w-xs px-10 text-neutral-600 text-sm dark:text-neutral-300'>
-        {description}
-      </p>
-    </div>
-  )
-}

apps/docs/components/ui/image.tsx

@@ -0,0 +1,53 @@
+'use client'
+
+import { useState } from 'react'
+import NextImage, { type ImageProps as NextImageProps } from 'next/image'
+import { cn } from '@/lib/utils'
+import { Lightbox } from './lightbox'
+
+interface ImageProps extends Omit<NextImageProps, 'className'> {
+  className?: string
+  enableLightbox?: boolean
+}
+
+export function Image({
+  className = 'w-full rounded-xl border border-border shadow-sm overflow-hidden',
+  enableLightbox = true,
+  alt = '',
+  src,
+  ...props
+}: ImageProps) {
+  const [isLightboxOpen, setIsLightboxOpen] = useState(false)
+
+  const handleImageClick = () => {
+    if (enableLightbox) {
+      setIsLightboxOpen(true)
+    }
+  }
+
+  return (
+    <>
+      <NextImage
+        className={cn(
+          'object-cover',
+          enableLightbox && 'cursor-pointer transition-opacity hover:opacity-90',
+          className
+        )}
+        alt={alt}
+        src={src}
+        onClick={handleImageClick}
+        {...props}
+      />
+
+      {enableLightbox && (
+        <Lightbox
+          isOpen={isLightboxOpen}
+          onClose={() => setIsLightboxOpen(false)}
+          src={typeof src === 'string' ? src : String(src)}
+          alt={alt}
+          type='image'
+        />
+      )}
+    </>
+  )
+}

apps/docs/components/ui/lightbox.tsx

@@ -0,0 +1,74 @@
+'use client'
+
+import { useEffect, useRef } from 'react'
+import { getVideoUrl } from '@/lib/utils'
+
+interface LightboxProps {
+  isOpen: boolean
+  onClose: () => void
+  src: string
+  alt: string
+  type: 'image' | 'video'
+}
+
+export function Lightbox({ isOpen, onClose, src, alt, type }: LightboxProps) {
+  const overlayRef = useRef<HTMLDivElement>(null)
+
+  useEffect(() => {
+    const handleKeyDown = (event: KeyboardEvent) => {
+      if (event.key === 'Escape') {
+        onClose()
+      }
+    }
+
+    const handleClickOutside = (event: MouseEvent) => {
+      if (overlayRef.current && event.target === overlayRef.current) {
+        onClose()
+      }
+    }
+
+    if (isOpen) {
+      document.addEventListener('keydown', handleKeyDown)
+      document.addEventListener('click', handleClickOutside)
+      document.body.style.overflow = 'hidden'
+    }
+
+    return () => {
+      document.removeEventListener('keydown', handleKeyDown)
+      document.removeEventListener('click', handleClickOutside)
+      document.body.style.overflow = 'unset'
+    }
+  }, [isOpen, onClose])
+
+  if (!isOpen) return null
+
+  return (
+    <div
+      ref={overlayRef}
+      className='fixed inset-0 z-50 flex items-center justify-center bg-black/80 p-12 backdrop-blur-sm'
+      role='dialog'
+      aria-modal='true'
+      aria-label='Media viewer'
+    >
+      <div className='relative max-h-full max-w-full overflow-hidden rounded-xl shadow-2xl'>
+        {type === 'image' ? (
+          <img
+            src={src}
+            alt={alt}
+            className='max-h-[calc(100vh-6rem)] max-w-[calc(100vw-6rem)] rounded-xl object-contain'
+            loading='lazy'
+          />
+        ) : (
+          <video
+            src={getVideoUrl(src)}
+            autoPlay
+            loop
+            muted
+            playsInline
+            className='max-h-[calc(100vh-6rem)] max-w-[calc(100vw-6rem)] rounded-xl outline-none focus:outline-none'
+          />
+        )}
+      </div>
+    </div>
+  )
+}

apps/docs/components/ui/theme-image.tsx

@@ -1,48 +0,0 @@
-'use client'
-
-import { useEffect, useState } from 'react'
-import Image from 'next/image'
-import { useTheme } from 'next-themes'
-
-interface ThemeImageProps {
-  lightSrc: string
-  darkSrc: string
-  alt: string
-  width?: number
-  height?: number
-  className?: string
-}
-
-export function ThemeImage({
-  lightSrc,
-  darkSrc,
-  alt,
-  width = 600,
-  height = 400,
-  className = 'rounded-lg border border-border my-6',
-}: ThemeImageProps) {
-  const { resolvedTheme } = useTheme()
-  const [imageSrc, setImageSrc] = useState(lightSrc)
-  const [mounted, setMounted] = useState(false)
-
-  // Wait until component is mounted to avoid hydration mismatch
-  useEffect(() => {
-    setMounted(true)
-  }, [])
-
-  useEffect(() => {
-    if (mounted) {
-      setImageSrc(resolvedTheme === 'dark' ? darkSrc : lightSrc)
-    }
-  }, [resolvedTheme, lightSrc, darkSrc, mounted])
-
-  if (!mounted) {
-    return null
-  }
-
-  return (
-    <div className='flex justify-center'>
-      <Image src={imageSrc} alt={alt} width={width} height={height} className={className} />
-    </div>
-  )
-}

apps/docs/components/ui/video.tsx

@@ -0,0 +1,57 @@
+'use client'
+
+import { useState } from 'react'
+import { getVideoUrl } from '@/lib/utils'
+import { Lightbox } from './lightbox'
+
+interface VideoProps {
+  src: string
+  className?: string
+  autoPlay?: boolean
+  loop?: boolean
+  muted?: boolean
+  playsInline?: boolean
+  enableLightbox?: boolean
+}
+
+export function Video({
+  src,
+  className = 'w-full rounded-xl border border-border shadow-sm overflow-hidden outline-none focus:outline-none',
+  autoPlay = true,
+  loop = true,
+  muted = true,
+  playsInline = true,
+  enableLightbox = true,
+}: VideoProps) {
+  const [isLightboxOpen, setIsLightboxOpen] = useState(false)
+
+  const handleVideoClick = () => {
+    if (enableLightbox) {
+      setIsLightboxOpen(true)
+    }
+  }
+
+  return (
+    <>
+      <video
+        autoPlay={autoPlay}
+        loop={loop}
+        muted={muted}
+        playsInline={playsInline}
+        className={`${className} ${enableLightbox ? 'cursor-pointer transition-opacity hover:opacity-90' : ''}`}
+        src={getVideoUrl(src)}
+        onClick={handleVideoClick}
+      />
+
+      {enableLightbox && (
+        <Lightbox
+          isOpen={isLightboxOpen}
+          onClose={() => setIsLightboxOpen(false)}
+          src={src}
+          alt={`Video: ${src}`}
+          type='video'
+        />
+      )}
+    </>
+  )
+}

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

@@ -1,22 +1,24 @@
 ---
 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'
+import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
 
 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}
-/>
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/agent.png"
+    alt="Agent Block Configuration"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
 
 ## Overview
 
@@ -61,14 +63,14 @@ The user prompt represents the primary input data for inference processing. This
 
 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)
+**OpenAI Models**: GPT-5, 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>
+  <Video src="models.mp4" width={500} height={350} />
 </div>
 
 ### Temperature
@@ -90,9 +92,9 @@ Control the creativity and randomness of responses:
   </Tab>
 </Tabs>
 
-<p className="mt-4 text-sm text-gray-600 dark:text-gray-400">
+<div 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>
+</div>
 
 ### API Key
 
@@ -108,7 +110,7 @@ Tools extend the agent's capabilities through external API integrations and serv
 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>
+  <Video src="tools.mp4" width={500} height={350} />
 </div>
 
 **Available Tool Categories**:
@@ -124,7 +126,7 @@ Tools extend the agent's capabilities through external API integrations and serv
 - **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>
+  <Video src="granular-tool-control.mp4" width={500} height={350} />
 </div>
 
 ### Response Format
@@ -165,42 +167,41 @@ After an agent completes, you can access its outputs:
 
 ## Advanced Features
 
-### Memory Integration
+### Memory + Agent: Conversation History
 
-Agents can maintain context across interactions using the memory system:
+Use a `Memory` block with a consistent `id` (for example, `chat`) to persist messages between runs, and include that history in the Agent's prompt.
 
-```javascript
-// In a Function block before the agent
-const memory = {
-  conversation_history: previousMessages,
-  user_preferences: userProfile,
-  session_data: currentSession
-};
+- Add the user's message before the Agent
+- Read the conversation history for context
+- Append the Agent's reply after it runs
+
+```yaml
+# 1) Add latest user message
+- Memory (operation: add)
+  id: chat
+  role: user
+  content: {{input}}
+
+# 2) Load conversation history
+- Memory (operation: get)
+  id: chat
+
+# 3) Run the agent with prior messages available
+- Agent
+  System Prompt: ...
+  User Prompt: |
+    Use the conversation so far:
+    {{memory_get.memories}}
+    Current user message: {{input}}
+
+# 4) Store the agent reply
+- Memory (operation: add)
+  id: chat
+  role: assistant
+  content: {{agent.content}}
 ```
 
-### 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
+See the `Memory` block reference for details: [/tools/memory](/tools/memory).
 
 ## Inputs and Outputs
 
@@ -265,10 +266,12 @@ Agents automatically handle common errors:
 <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>
+    <li>User submits a support ticket via the API block</li>
+    <li>Agent checks orders/subscriptions in Postgres and searches the knowledge base for guidance</li>
+    <li>If escalation is needed, the Agent creates a Linear issue with relevant context</li>
+    <li>Agent drafts a clear email reply</li>
+    <li>Gmail sends the reply to the customer</li>
+    <li>Conversation is saved to Memory to maintain history for future messages</li>
   </ol>
 </div>
 

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

@@ -1,22 +1,23 @@
 ---
 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'
+import { Image } from '@/components/ui/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.
+The API block enables you to connect your workflow to external services through API endpoints using 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}
-/>
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/api.png"
+    alt="API Block"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
 
 ## Overview
 
@@ -37,6 +38,15 @@ The API block enables you to:
   </Step>
 </Steps>
 
+## How It Works
+
+The API block processes HTTP requests through a structured approach:
+
+1. **Configure Request** - Set URL, method, headers, and body parameters
+2. **Execute Request** - Send HTTP request to the specified endpoint
+3. **Process Response** - Handle response data, status codes, and headers
+4. **Error Handling** - Manage timeouts, retries, and error conditions
+
 ## Configuration Options
 
 ### URL
@@ -202,18 +212,6 @@ if (<api.status> === 200) {
   </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">
@@ -222,7 +220,7 @@ if (<api.status> === 200) {
     <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>
+    <li>Supabase block updates order status in database</li>
   </ol>
 </div>
 

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

@@ -1,23 +1,24 @@
 ---
 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'
+import { Image } from '@/components/ui/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.
+The Condition block allows you to branch your workflow execution path based on boolean expressions, enabling you to create dynamic, responsive workflows with different execution paths. It evaluates conditions and routes the workflow accordingly, letting you control execution flow based on data or logic without requiring an LLM.
 
-<ThemeImage
-  lightSrc="/static/light/condition-light.png"
-  darkSrc="/static/dark/condition-dark.png"
-  alt="Condition Block"
-  width={350}
-  height={175}
-/>
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/condition.png"
+    alt="Condition Block"
+    width={500}
+    height={350}
+    className="my-6"
+  />
+</div>
 
 <Callout>
   Condition blocks enable deterministic decision-making without requiring an LLM, making them ideal

apps/docs/content/docs/blocks/evaluator.mdx

@@ -1,30 +1,52 @@
 ---
 title: Evaluator
-description: Assess content quality using customizable evaluation metrics
 ---
 
 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'
+import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
 
-The Evaluator block uses AI to score and assess content quality based on metrics you define. Perfect for quality control, A/B testing, and ensuring your AI outputs meet specific standards.
+The Evaluator block uses AI to score and assess content quality using customizable evaluation metrics that you define. Perfect for quality control, A/B testing, and ensuring your AI outputs meet specific standards.
 
-<ThemeImage
-  lightSrc="/static/light/evaluator-light.png"
-  darkSrc="/static/dark/evaluator-dark.png"
-  alt="Evaluator Block Configuration"
-  width={350}
-  height={175}
-/>
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/evaluator.png"
+    alt="Evaluator Block Configuration"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
 
-## What You Can Evaluate
+## Overview
 
-**AI-Generated Content**: Score chatbot responses, generated articles, or marketing copy
-**User Input**: Evaluate customer feedback, survey responses, or form submissions  
-**Content Quality**: Assess clarity, accuracy, relevance, and tone
-**Performance Metrics**: Track improvements over time with consistent scoring
-**A/B Testing**: Compare different approaches with objective metrics
+The Evaluator block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Score Content Quality</strong>: Use AI to evaluate content against custom metrics with numeric scores
+  </Step>
+  <Step>
+    <strong>Define Custom Metrics</strong>: Create specific evaluation criteria tailored to your use case  
+  </Step>
+  <Step>
+    <strong>Automate Quality Control</strong>: Build workflows that automatically assess and filter content
+  </Step>
+  <Step>
+    <strong>Track Performance</strong>: Monitor improvements and consistency over time with objective scoring
+  </Step>
+</Steps>
+
+## How It Works
+
+The Evaluator block processes content through AI-powered assessment:
+
+1. **Receive Content** - Takes input content from previous blocks in your workflow
+2. **Apply Metrics** - Evaluates content against your defined custom metrics  
+3. **Generate Scores** - AI model assigns numeric scores for each metric
+4. **Provide Summary** - Returns detailed evaluation with scores and explanations
 
 ## Configuration Options
 
@@ -63,7 +85,7 @@ Choose an AI model to perform the evaluation:
 **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="/models.mp4"></video>
+  <Video src="models.mp4" width={500} height={350} />
 </div>
 
 **Recommendation**: Use models with strong reasoning capabilities like GPT-4o or Claude 3.7 Sonnet for more accurate evaluations.
@@ -80,46 +102,93 @@ Your API key for the selected LLM provider. This is securely stored and used for
 4. The LLM evaluates the content and returns numeric scores for each metric
 5. The Evaluator block formats these scores as structured output for use in your workflow
 
+## Example Use Cases
+
+### Content Quality Assessment
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Evaluate blog post quality before publication</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Agent block generates blog post content</li>
+    <li>Evaluator assesses accuracy, readability, and engagement</li>
+    <li>Condition block checks if scores meet minimum thresholds</li>
+    <li>High scores → Publish, Low scores → Revise and retry</li>
+  </ol>
+</div>
+
+### A/B Testing Content
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Compare multiple AI-generated responses</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Parallel block generates multiple response variations</li>
+    <li>Evaluator scores each variation on clarity and relevance</li>
+    <li>Function block selects highest-scoring response</li>
+    <li>Response block returns the best result</li>
+  </ol>
+</div>
+
+### Customer Support Quality Control
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Ensure support responses meet quality standards</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Support agent generates response to customer inquiry</li>
+    <li>Evaluator scores helpfulness, empathy, and accuracy</li>
+    <li>Scores logged for training and performance monitoring</li>
+    <li>Low scores trigger human review process</li>
+  </ol>
+</div>
+
 ## Inputs and Outputs
 
-### Inputs
-
-- **Content**: The text or structured data to evaluate
-- **Metrics**: Custom evaluation criteria with scoring ranges
-- **Model Settings**: LLM provider and parameters
-
-### Outputs
-
-- **Content**: A summary of the evaluation
-- **Model**: The model used for evaluation
-- **Tokens**: Usage statistics
-- **Metric Scores**: Numeric scores for each defined metric
-
-## Example Usage
-
-Here's an example of how an Evaluator block might be configured for assessing customer service responses:
-
-```yaml
-# Example Evaluator Configuration
-metrics:
-  - name: Empathy
-    description: How well does the response acknowledge and address the customer's emotional state?
-    range:
-      min: 1
-      max: 5
-  - name: Solution
-    description: How effectively does the response solve the customer's problem?
-    range:
-      min: 1
-      max: 5
-  - name: Clarity
-    description: How clear and easy to understand is the response?
-    range:
-      min: 1
-      max: 5
-
-model: Anthropic/claude-3-opus
-```
+<Tabs items={['Configuration', 'Variables', 'Results']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Content</strong>: The text or structured data to evaluate
+      </li>
+      <li>
+        <strong>Evaluation Metrics</strong>: Custom criteria with scoring ranges
+      </li>
+      <li>
+        <strong>Model</strong>: AI model for evaluation 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>evaluator.content</strong>: Summary of the evaluation
+      </li>
+      <li>
+        <strong>evaluator.model</strong>: Model used for evaluation
+      </li>
+      <li>
+        <strong>evaluator.tokens</strong>: Token usage statistics
+      </li>
+      <li>
+        <strong>evaluator.cost</strong>: Cost summary for the evaluation call
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Metric Scores</strong>: Numeric scores for each defined metric
+      </li>
+      <li>
+        <strong>Evaluation Summary</strong>: Detailed assessment with explanations
+      </li>
+      <li>
+        <strong>Access</strong>: Available in blocks after the evaluator
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
 
 ## Best Practices
 

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

@@ -1,22 +1,23 @@
 ---
 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'
+import { Image } from '@/components/ui/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.
+The Function block lets you execute custom JavaScript or TypeScript code in your workflows. 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}
-/>
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/function.png"
+    alt="Function Block with Code Editor"
+    width={500}
+    height={350}
+    className="my-6"
+  />
+</div>
 
 ## Overview
 
@@ -42,164 +43,25 @@ The Function block enables you to:
 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 
+2. **Execute Code**: Run your JavaScript/Python code 
 3. **Return Results**: Use `return` to pass data to the next block
 4. **Handle Errors**: Built-in error handling and logging
 
-## Configuration Options
+## Remote Execution (E2B)
 
-### 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>
+  - **Languages**: Run JavaScript and Python in an isolated E2B sandbox.
+  - **How to enable**: Toggle “Remote Code Execution” in the Function block.
+  - **When to use**: Heavier logic, external libraries, or Python-specific code.
+  - **Performance**: Slower than local JS due to sandbox startup and network overhead.
+  - **Notes**: Requires `E2B_API_KEY` if running locally. For lowest latency, use natively local JS (Fast Mode).
 
 ## Inputs and Outputs
 
-<Tabs items={['Configuration', 'Variables', 'Results']}>
+<Tabs items={['Configuration', 'Variables']}>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
-        <strong>Code</strong>: Your JavaScript/TypeScript code to execute
+        <strong>Code</strong>: Your JavaScript/Python code to execute
       </li>
       <li>
         <strong>Timeout</strong>: Maximum execution time (defaults to 30 seconds)
@@ -217,25 +79,6 @@ return processed;
       <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>

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

@@ -6,17 +6,17 @@ 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'
+import { Video } from '@/components/ui/video'
 
 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>
+  <Video src="connections.mp4" width={700} height={450} />
 </div>
 
 ## Core Block Types
 
-Sim Studio provides seven core block types that handle the essential functions of AI workflows:
+Sim 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)
@@ -31,8 +31,6 @@ Sim Studio provides seven core block types that handle the essential functions o
 ### Output Blocks
 - **[Response](/blocks/response)** - Format and return final results from your workflow
 
-<BlockTypes />
-
 ## How Blocks Work
 
 Each block has three main components:
@@ -62,7 +60,7 @@ You create workflows by connecting blocks together. The output of one block beco
 - **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>
+  <Video src="connections.mp4" width={700} height={450} />
 </div>
 
 ## Common Patterns

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

@@ -1,22 +1,15 @@
 ---
 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'
+import { Image } from '@/components/ui/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.
+The Loop block is a container block in Sim that allows you to create iterative workflows by executing 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}
-/>
+The Loop block supports two types of iteration:
 
 <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.
@@ -33,8 +26,23 @@ The Loop block enables you to:
   <Step>
     <strong>Repeat operations</strong>: Execute blocks a fixed number of times
   </Step>
+  <Step>
+    <strong>Sequential processing</strong>: Handle data transformation in ordered iterations
+  </Step>
+  <Step>
+    <strong>Aggregate results</strong>: Collect outputs from all loop iterations
+  </Step>
 </Steps>
 
+## How It Works
+
+The Loop block executes contained blocks through sequential iteration:
+
+1. **Initialize Loop** - Set up iteration parameters (count or collection)
+2. **Execute Iteration** - Run contained blocks for current iteration
+3. **Collect Results** - Store output from each iteration
+4. **Continue or Complete** - Move to next iteration or finish loop
+
 ## Configuration Options
 
 ### Loop Type
@@ -43,7 +51,19 @@ 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.
+    **For Loop (Iterations)** - A numeric loop that executes a fixed number of times:
+    
+    <div className="flex justify-center">
+      <Image
+        src="/static/blocks/loop-1.png"
+        alt="For Loop with iterations"
+        width={500}
+        height={400}
+        className="my-6"
+      />
+    </div>
+    
+    Use this when you need to repeat an operation a specific number of times.
     
     ```
     Example: Run 5 times
@@ -55,7 +75,19 @@ Choose between two types of loops:
     ```
   </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.
+    **ForEach Loop (Collection)** - A collection-based loop that iterates over each item in an array or object:
+    
+    <div className="flex justify-center">
+      <Image
+        src="/static/blocks/loop-2.png"
+        alt="ForEach Loop with collection"
+        width={500}
+        height={400}
+        className="my-6"
+      />
+    </div>
+    
+    Use this when you need to process a collection of items.
     
     ```
     Example: Process ["apple", "banana", "orange"]
@@ -172,4 +204,4 @@ After a loop completes, you can access aggregated results:
 
 - **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 
+- **Handle errors gracefully**: Consider adding error handling inside loops for robust workflows

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

@@ -10,7 +10,7 @@
     "parallel",
     "response",
     "router",
-    "webhook_trigger",
     "workflow"
-  ]
+  ],
+  "defaultOpen": false
 }

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

@@ -1,22 +1,15 @@
 ---
 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'
+import { Image } from '@/components/ui/image'
 
-The Parallel block is a container block in Sim Studio that allows you to execute multiple instances of blocks concurrently.
+The Parallel block is a container block in Sim that allows you to execute multiple instances of blocks concurrently for faster workflow processing.
 
-<ThemeImage
-  lightSrc="/static/light/parallel-light.png"
-  darkSrc="/static/dark/parallel-dark.png"
-  alt="Parallel Block"
-  width={500}
-  height={300}
-/>
+The Parallel block supports two types of concurrent execution:
 
 <Callout type="info">
   Parallel blocks are container nodes that execute their contents multiple times simultaneously, unlike loops which execute sequentially.
@@ -49,7 +42,19 @@ 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.
+    **Count-based Parallel** - Execute a fixed number of parallel instances:
+    
+    <div className="flex justify-center">
+      <Image
+        src="/static/blocks/parallel-1.png"
+        alt="Count-based parallel execution"
+        width={500}
+        height={400}
+        className="my-6"
+      />
+    </div>
+    
+    Use this when you need to run the same operation multiple times concurrently.
     
     ```
     Example: Run 5 parallel instances
@@ -61,7 +66,19 @@ Choose between two types of parallel execution:
     ```
   </Tab>
   <Tab>
-    Distribute a collection across parallel instances. Each instance processes one item from the collection simultaneously.
+    **Collection-based Parallel** - Distribute a collection across parallel instances:
+    
+    <div className="flex justify-center">
+      <Image
+        src="/static/blocks/parallel-2.png"
+        alt="Collection-based parallel execution"
+        width={500}
+        height={400}
+        className="my-6"
+      />
+    </div>
+    
+    Each instance processes one item from the collection simultaneously.
     
     ```
     Example: Process ["task1", "task2", "task3"] in parallel
@@ -105,8 +122,8 @@ After a parallel block completes, you can access aggregated results:
 <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>Collection-based parallel over a list of model IDs (e.g., ["gpt-4o", "claude-3.7-sonnet", "gemini-2.5-pro"])</li>
+    <li>Inside parallel: Agent's model is set to the current item from the collection</li>
     <li>After parallel: Compare and select best response</li>
   </ol>
 </div>
@@ -207,4 +224,4 @@ Understanding when to use each:
 
 - **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 
+- **Error handling**: Each instance should handle its own errors gracefully

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

@@ -1,33 +1,61 @@
 ---
 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'
+import { Image } from '@/components/ui/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.
+The Response block is the final step in your workflow that formats and sends a structured response back to API calls. 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}
-/>
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/response.png"
+    alt="Response Block Configuration"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
 
 <Callout type="info">
   Response blocks are terminal blocks - they end the workflow execution and cannot connect to other blocks.
 </Callout>
 
+## Overview
+
+The Response block enables you to:
+
+<Steps>
+  <Step>
+    <strong>Format API Responses</strong>: Structure workflow results into proper HTTP responses
+  </Step>
+  <Step>
+    <strong>Set Status Codes</strong>: Configure appropriate HTTP status codes based on workflow outcomes
+  </Step>
+  <Step>
+    <strong>Control Headers</strong>: Add custom headers for API responses and webhooks
+  </Step>
+  <Step>
+    <strong>Transform Data</strong>: Convert workflow variables into client-friendly response formats
+  </Step>
+</Steps>
+
+## How It Works
+
+The Response block finalizes workflow execution:
+
+1. **Collect Data** - Gathers variables and outputs from previous blocks
+2. **Format Response** - Structures data according to your configuration
+3. **Set HTTP Details** - Applies status codes and headers
+4. **Send Response** - Returns the formatted response to the API caller
+
 ## 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
+- **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
 
 ## Two Ways to Build Responses
 
@@ -83,9 +111,9 @@ Set the HTTP status code for the response. Common status codes include:
   </Tab>
 </Tabs>
 
-<p className="mt-4 text-sm text-gray-600 dark:text-gray-400">
+<div className="mt-4 text-sm text-gray-600 dark:text-gray-400">
   Default status code is 200 if not specified.
-</p>
+</div>
 
 ### Response Headers
 
@@ -99,27 +127,90 @@ Headers are configured as key-value pairs:
 | Cache-Control | no-cache |
 | X-API-Version | 1.0 |
 
+## Example Use Cases
+
+### API Endpoint Response
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Return structured data from a search API</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Workflow processes search query and retrieves results</li>
+    <li>Function block formats and paginates results</li>
+    <li>Response block returns JSON with data, pagination, and metadata</li>
+    <li>Client receives structured response with 200 status</li>
+  </ol>
+</div>
+
+### Webhook Confirmation
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Acknowledge webhook receipt and processing</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Webhook trigger receives external system data</li>
+    <li>Workflow processes the incoming data</li>
+    <li>Response block returns confirmation with processing status</li>
+    <li>External system receives acknowledgment</li>
+  </ol>
+</div>
+
+### Error Response Handling
+
+<div className="mb-4 rounded-md border p-4">
+  <h4 className="font-medium">Scenario: Return appropriate error responses</h4>
+  <ol className="list-decimal pl-5 text-sm">
+    <li>Condition block detects validation failure or system error</li>
+    <li>Router directs to error handling path</li>
+    <li>Response block returns 400/500 status with error details</li>
+    <li>Client receives structured error information</li>
+  </ol>
+</div>
+
 ## Inputs and Outputs
 
-<Tabs items={['Inputs', 'Outputs']}>
+<Tabs items={['Configuration', 'Variables', 'Results']}>
   <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
+        <strong>Response Data</strong>: JSON structure for response body
       </li>
       <li>
-        <strong>status</strong> (number, optional): HTTP status code (default: 200)
+        <strong>Status Code</strong>: HTTP status code (default: 200)
       </li>
       <li>
-        <strong>headers</strong> (JSON, optional): Additional response headers
+        <strong>Headers</strong>: Custom HTTP headers as key-value pairs
+      </li>
+      <li>
+        <strong>Mode</strong>: Builder or Editor mode for response construction
       </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>
+      <li>
+        <strong>response.data</strong>: The structured response body
+      </li>
+      <li>
+        <strong>response.status</strong>: HTTP status code sent
+      </li>
+      <li>
+        <strong>response.headers</strong>: Headers included in response
+      </li>
+      <li>
+        <strong>response.success</strong>: Boolean indicating successful completion
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>HTTP Response</strong>: Complete response sent to API caller
+      </li>
+      <li>
+        <strong>Workflow Termination</strong>: Ends workflow execution
+      </li>
+      <li>
+        <strong>Access</strong>: Response blocks are terminal - no subsequent blocks
+      </li>
     </ul>
   </Tab>
 </Tabs>
@@ -146,40 +237,11 @@ Use the `<variable.name>` syntax to dynamically insert workflow variables into y
   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
+- **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,23 +1,25 @@
 ---
 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'
+import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
 
-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.
+The Router block uses AI to intelligently decide which path your workflow should take next, routing workflow execution based on specific conditions or logic. 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}
-/>
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/router.png"
+    alt="Router Block with Multiple Paths"
+    width={500}
+    height={400}
+    className="my-6"
+  />
+</div>
 
 ## Overview
 
@@ -103,7 +105,7 @@ Choose an AI model to power the routing decision:
 **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>
+  <Video src="router-model-dropdown.mp4" width={500} height={350} />
 </div>
 
 **Recommendation**: Use models with strong reasoning capabilities like GPT-4o or Claude 3.7 Sonnet for more accurate routing decisions.
@@ -116,9 +118,10 @@ Your API key for the selected LLM provider. This is securely stored and used for
 
 After a router makes a decision, you can access its outputs:
 
-- **`<router.content>`**: Summary of the routing decision made
+- **`<router.prompt>`**: Summary of the routing prompt used
 - **`<router.selected_path>`**: Details of the chosen destination block
 - **`<router.tokens>`**: Token usage statistics from the LLM
+- **`<router.cost>`**: Cost summary for the routing call (input, output, total)
 - **`<router.model>`**: The model used for decision-making
 
 ## Advanced Features
@@ -134,34 +137,9 @@ 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']}>
+<Tabs items={['Configuration', 'Variables']}>
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
@@ -181,7 +159,7 @@ Confidence Threshold: 0.7 // Minimum confidence for routing
   <Tab>
     <ul className="list-disc space-y-2 pl-6">
       <li>
-        <strong>router.content</strong>: Summary of routing decision
+        <strong>router.prompt</strong>: Summary of routing prompt used
       </li>
       <li>
         <strong>router.selected_path</strong>: Details of chosen destination
@@ -189,24 +167,14 @@ Confidence Threshold: 0.7 // Minimum confidence for routing
       <li>
         <strong>router.tokens</strong>: Token usage statistics
       </li>
+      <li>
+        <strong>router.cost</strong>: Cost summary for the routing call (input, output, total)
+      </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

apps/docs/content/docs/blocks/webhook_trigger.mdx

@@ -1,113 +0,0 @@
----
-title: Webhook Trigger
-description: Trigger workflow execution from external webhooks
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { Card, Cards } from 'fumadocs-ui/components/card'
-import { ThemeImage } from '@/components/ui/theme-image'
-
-The Webhook Trigger block allows external services to trigger your workflow execution through HTTP webhooks. Unlike starter blocks, webhook triggers are pure input sources that start workflows without requiring manual intervention.
-
-<ThemeImage
-  lightSrc="/static/light/webhooktrigger-light.png"
-  darkSrc="/static/dark/webhooktrigger-dark.png"
-  alt="Webhook Trigger Block"
-  width={350}
-  height={175}
-/>
-
-<Callout>
-  Webhook triggers cannot receive incoming connections and do not expose webhook data to the workflow. They serve as pure execution triggers.
-</Callout>
-
-## Overview
-
-The Webhook Trigger block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Receive external triggers</strong>: Accept HTTP requests from external services
-  </Step>
-  <Step>
-    <strong>Support multiple providers</strong>: Handle webhooks from Slack, Gmail, GitHub, and more
-  </Step>
-  <Step>
-    <strong>Start workflows automatically</strong>: Execute workflows without manual intervention
-  </Step>
-  <Step>
-    <strong>Provide secure endpoints</strong>: Generate unique webhook URLs for each trigger
-  </Step>
-</Steps>
-
-## How It Works
-
-The Webhook Trigger block operates as a pure input source:
-
-1. **Generate Endpoint** - Creates a unique webhook URL when configured
-2. **Receive Request** - Accepts HTTP POST requests from external services
-3. **Trigger Execution** - Starts the workflow when a valid request is received
-
-## Configuration Options
-
-### Webhook Provider
-
-Choose from supported service providers:
-
-<Cards>
-  <Card title="Slack" href="#">
-    Receive events from Slack apps and bots
-  </Card>
-  <Card title="Gmail" href="#">
-    Handle email-based triggers and notifications
-  </Card>
-  <Card title="Airtable" href="#">
-    Respond to database changes
-  </Card>
-  <Card title="Telegram" href="#">
-    Process bot messages and updates
-  </Card>
-  <Card title="WhatsApp" href="#">
-    Handle messaging events
-  </Card>
-  <Card title="GitHub" href="#">
-    Process repository events and pull requests
-  </Card>
-  <Card title="Discord" href="#">
-    Respond to Discord server events
-  </Card>
-  <Card title="Stripe" href="#">
-    Handle payment and subscription events
-  </Card>
-</Cards>
-
-### Generic Webhooks
-
-For custom integrations or services not listed above, use the **Generic** provider. This option accepts HTTP POST requests from any client and provides flexible authentication options:
-
-- **Optional Authentication** - Configure Bearer token or custom header authentication
-- **IP Restrictions** - Limit access to specific IP addresses
-- **Request Deduplication** - Automatic duplicate request detection using content hashing
-- **Flexible Headers** - Support for custom authentication header names
-
-The Generic provider is ideal for internal services, custom applications, or third-party tools that need to trigger workflows via standard HTTP requests.
-
-### Webhook Configuration
-
-Configure provider-specific settings:
-
-- **Webhook URL** - Automatically generated unique endpoint
-- **Provider Settings** - Authentication and validation options
-- **Security** - Built-in rate limiting and provider-specific authentication
-
-## Best Practices
-
-- **Use unique webhook URLs** for each integration to maintain security
-- **Configure proper authentication** when supported by the provider
-- **Keep workflows independent** of webhook payload structure
-- **Test webhook endpoints** before deploying to production
-- **Monitor webhook delivery** through provider dashboards
-
-

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

@@ -1,22 +1,23 @@
 ---
 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'
+import { Image } from '@/components/ui/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.
+The Workflow block allows you to execute other workflows as reusable components within your current workflow. This 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}
-/>
+<div className="flex justify-center">
+  <Image
+    src="/static/blocks/workflow.png"
+    alt="Workflow Block"
+    width={500}
+    height={350}
+    className="my-6"
+  />
+</div>
 
 <Callout type="info">
   Workflow blocks enable modular design by allowing you to compose complex workflows from smaller, reusable components.
@@ -46,9 +47,9 @@ The Workflow block serves as a bridge between workflows, enabling you to:
 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
+2. Passes input data from the current workflow to the child workflow (available via start.input)
 3. Executes the child workflow in an isolated context
-4. Returns the results back to the parent workflow for further processing
+4. Returns the result back to the parent workflow for further processing
 
 ## Configuration Options
 
@@ -60,26 +61,6 @@ Choose which workflow to execute from a dropdown list of available workflows in
 - 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
 
@@ -88,58 +69,12 @@ 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:
+- Nested tracespan in the execution log
 
 <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']}>
@@ -158,20 +93,17 @@ Workflow 3 Input: <workflow2.response>
   </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
+        <strong>workflow.childWorkflowName</strong>: Name of executed child workflow
       </li>
       <li>
-        <strong>workflow.execution_time</strong>: Time taken to execute
+        <strong>workflow.result</strong>: Result returned by the child workflow
+      </li>
+      <li>
+        <strong>workflow.error</strong>: Error details if workflow failed
       </li>
     </ul>
   </Tab>
@@ -228,32 +160,10 @@ Workflow 3 Input: <workflow2.response>
   </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 
+- **Use semantic naming**: Give workflows descriptive names that clearly indicate their purpose and functionality

apps/docs/content/docs/connections/accessing-data.mdx

@@ -1,190 +0,0 @@
----
-title: Accessing Connected Data
-description: Techniques for accessing and manipulating data from connected blocks
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { File, Files, Folder } from 'fumadocs-ui/components/files'
-
-Once blocks are connected, you can access data from source blocks in destination blocks using connection tags and various data access techniques.
-
-## Basic Data Access
-
-The simplest way to access data is through direct references using connection tags:
-
-<Files>
-  <File name="Simple Property" annotation="<block.content>" />
-  <File name="Nested Property" annotation="<block.tokens.total>" />
-  <File name="Array Element" annotation="<block.items[0].name>" />
-  <File name="Complex Path" annotation="<block.data.users[2].profile.email>" />
-</Files>
-
-## Advanced Data Access Techniques
-
-### Array Access
-
-You can access array elements using square bracket notation:
-
-```javascript
-// Access the first item in an array
-<block.items[0]>
-
-// Access a specific property of an array item
-<block.items[2].name>
-
-// Access the last item in an array (in Function blocks)
-const items = input.block.items;
-const lastItem = items[items.length - 1];
-```
-
-### Object Property Access
-
-Access object properties using dot notation:
-
-```javascript
-// Access a simple property
-<block.content>
-
-// Access a nested property
-<block.data.user.profile.name>
-
-// Access a property with special characters (in Function blocks)
-const data = input.block.data;
-const specialProp = data['property-with-dashes'];
-```
-
-### Dynamic References
-
-Connection references are evaluated at runtime, allowing for dynamic data flow through your workflow:
-
-```javascript
-// In a Function block, you can access connected data
-const userName = input.userBlock.name;
-const orderTotal = input.apiBlock.body.order.total;
-
-// Process the data
-const discount = orderTotal > 100 ? 0.1 : 0;
-const finalPrice = orderTotal * (1 - discount);
-
-// Return the result
-return {
-  userName,
-  originalTotal: orderTotal,
-  discount: discount * 100 + '%',
-  finalPrice
-};
-```
-
-## Data Transformation
-
-### Using Function Blocks
-
-Function blocks are the most powerful way to transform data between connections:
-
-```javascript
-// Example: Transform API response data
-const apiResponse = input.apiBlock.data;
-const transformedData = {
-  users: apiResponse.results.map(user => ({
-    id: user.id,
-    fullName: `${user.firstName} ${user.lastName}`,
-    email: user.email.toLowerCase(),
-    isActive: user.status === 'active'
-  })),
-  totalCount: apiResponse.count,
-  timestamp: new Date().toISOString()
-};
-
-return transformedData;
-```
-
-### String Interpolation
-
-You can combine connection tags with static text:
-
-```
-Hello, <userBlock.name>! Your order #<orderBlock.id> has been processed.
-```
-
-### Conditional Content
-
-In Function blocks, you can create conditional content based on connected data:
-
-```javascript
-const user = input.userBlock;
-const orderTotal = input.orderBlock.total;
-
-let message = `Thank you for your order, ${user.name}!`;
-
-if (orderTotal > 100) {
-  message += " You've qualified for free shipping!";
-} else {
-  message += ` Add $${(100 - orderTotal).toFixed(2)} more to qualify for free shipping.`;
-}
-
-return { message };
-```
-
-## Handling Missing Data
-
-It's important to handle cases where connected data might be missing or null:
-
-<Callout type="warning">
-  Always validate connected data before using it, especially when accessing nested properties or
-  array elements.
-</Callout>
-
-### Default Values
-
-In Function blocks, you can provide default values for missing data:
-
-```javascript
-const userName = input.userBlock?.name || 'Guest'
-const items = input.orderBlock?.items || []
-const total = input.orderBlock?.total ?? 0
-```
-
-### Conditional Checks
-
-Check if data exists before accessing nested properties:
-
-```javascript
-let userEmail = 'No email provided'
-if (input.userBlock && input.userBlock.contact && input.userBlock.contact.email) {
-  userEmail = input.userBlock.contact.email
-}
-```
-
-### Optional Chaining
-
-In Function blocks, use optional chaining to safely access nested properties:
-
-```javascript
-const userCity = input.userBlock?.address?.city
-const firstItemName = input.orderBlock?.items?.[0]?.name
-```
-
-## Debugging Connection Data
-
-When troubleshooting connection issues, these techniques can help:
-
-1. **Log Data**: In Function blocks, use `console.log()` to inspect connected data
-2. **Return Full Objects**: Return the full input object to see all available data
-3. **Check Types**: Verify the data types of connected values
-4. **Validate Paths**: Ensure you're using the correct path to access nested data
-
-```javascript
-// Example debugging function
-function debugConnections() {
-  console.log('All inputs:', input)
-  console.log('User data type:', typeof input.userBlock)
-  console.log('Order items:', input.orderBlock?.items)
-
-  return {
-    debug: true,
-    allInputs: input,
-    userExists: !!input.userBlock,
-    orderItemCount: input.orderBlock?.items?.length || 0,
-  }
-}
-```

apps/docs/content/docs/connections/basics.mdx

@@ -1,6 +1,5 @@
 ---
 title: Connection Basics
-description: Learn how connections work in Sim Studio
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,7 +7,7 @@ import { Step, Steps } from 'fumadocs-ui/components/steps'
 
 ## How Connections Work
 
-Connections are the pathways that allow data to flow between blocks in your workflow. When you connect two blocks in Sim Studio, you're establishing a data flow relationship that defines how information passes from one block to another.
+Connections are the pathways that allow data to flow between blocks in your workflow. In Sim, connections define how information passes from one block to another, enabling data flow throughout your workflow.
 
 <Callout type="info">
   Each connection represents a directed relationship where data flows from a source block's output
@@ -28,9 +27,6 @@ Connections are the pathways that allow data to flow between blocks in your work
   <Step>
     <strong>Confirm Connection</strong>: Release to create the connection
   </Step>
-  <Step>
-    <strong>Configure (Optional)</strong>: Some connections may require additional configuration
-  </Step>
 </Steps>
 
 ### Connection Flow
@@ -42,35 +38,7 @@ The flow of data through connections follows these principles:
 3. **Data Transformation**: Data may be transformed as it passes between blocks
 4. **Conditional Paths**: Some blocks (like Router and Condition) can direct flow to different paths
 
-### Connection Visualization
-
-Connections are visually represented in the workflow editor:
-
-- **Solid Lines**: Active connections that will pass data
-- **Animated Flow**: During execution, data flow is visualized along connections
-- **Color Coding**: Different connection types may have different colors
-- **Connection Tags**: Visual indicators showing what data is available
-
-### Managing Connections
-
-You can manage your connections in several ways:
-
-- **Delete**: Click on a connection and press Delete or use the context menu
-- **Reroute**: Drag a connection to change its path
-- **Inspect**: Click on a connection to see details about the data being passed
-- **Disable**: Temporarily disable a connection without deleting it
-
 <Callout type="warning">
   Deleting a connection will immediately stop data flow between the blocks. Make sure this is
   intended before removing connections.
 </Callout>
-
-## Connection Compatibility
-
-Not all blocks can be connected to each other. Compatibility depends on:
-
-1. **Data Type Compatibility**: The output type must be compatible with the input type
-2. **Block Restrictions**: Some blocks may have restrictions on what they can connect to
-3. **Workflow Logic**: Connections must make logical sense in the context of your workflow
-
-The editor will indicate when connections are invalid or incompatible.

apps/docs/content/docs/connections/best-practices.mdx

@@ -1,208 +0,0 @@
----
-title: Connection Best Practices
-description: Recommended patterns for effective connection management
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-
-## Workflow Organization
-
-### Organize Your Connections
-
-Keep your workflow clean and understandable by organizing connections logically:
-
-- **Minimize crossing connections** when possible to reduce visual complexity
-- **Group related blocks together** to make data flow more intuitive
-- **Use consistent flow direction** (typically left-to-right or top-to-bottom)
-- **Label complex connections** with descriptive names
-
-<Callout type="info">
-  A well-organized workflow is easier to understand, debug, and maintain. Take time to arrange your
-  blocks and connections in a logical manner.
-</Callout>
-
-### Connection Naming Conventions
-
-When working with multiple connections, consistent naming helps maintain clarity:
-
-<Steps>
-  <Step>
-    <strong>Use descriptive block names</strong>: Name blocks based on their function (e.g.,
-    "UserDataFetcher", "ResponseGenerator")
-  </Step>
-  <Step>
-    <strong>Be specific with connection references</strong>: Use clear variable names when
-    referencing connections in code
-  </Step>
-  <Step>
-    <strong>Document complex connections</strong>: Add comments explaining non-obvious data
-    transformations
-  </Step>
-</Steps>
-
-## Data Validation
-
-### Validate Data Flow
-
-Ensure that the data being passed between blocks is compatible:
-
-- **Check that required fields are available** in the source block
-- **Verify data types match expectations** before using them
-- **Use Function blocks to transform data** when necessary
-- **Handle missing or null values** with default values or conditional logic
-
-```javascript
-// Example: Validating and transforming data in a Function block
-function processUserData() {
-  // Validate required fields
-  if (!input.userBlock || !input.userBlock.id) {
-    return { error: 'Missing user data', valid: false }
-  }
-
-  // Transform and validate data types
-  const userId = String(input.userBlock.id)
-  const userName = input.userBlock.name || 'Unknown User'
-  const userScore = Number(input.userBlock.score) || 0
-
-  return {
-    valid: true,
-    user: {
-      id: userId,
-      name: userName,
-      score: userScore,
-      isHighScore: userScore > 100,
-    },
-  }
-}
-```
-
-## Documentation
-
-### Document Connection Purpose
-
-Add comments or descriptions to clarify the purpose of connections, especially in complex workflows:
-
-- **What data is being passed**: Document the key fields and their purpose
-- **Why this connection exists**: Explain the relationship between blocks
-- **Any transformations or conditions applied**: Note any data processing that occurs
-
-```javascript
-// Example: Documenting connection purpose in a Function block
-/*
- * This function processes user data from the UserFetcher block
- * and order history from the OrderHistory block to generate
- * personalized product recommendations.
- *
- * Input:
- * - userBlock: User profile data (id, preferences, history)
- * - orderBlock: Recent order history (items, dates, amounts)
- *
- * Output:
- * - recommendations: Array of recommended product IDs
- * - userSegment: Calculated user segment for marketing
- * - conversionProbability: Estimated likelihood of purchase
- */
-function generateRecommendations() {
-  // Implementation...
-}
-```
-
-## Testing and Debugging
-
-### Test Connection References
-
-Verify that connection references work as expected:
-
-- **Test with different input values** to ensure robustness
-- **Check edge cases** (empty values, large datasets, special characters)
-- **Ensure error handling for missing or invalid data**
-- **Use console logging in Function blocks** to debug connection issues
-
-```javascript
-// Example: Testing connection references with edge cases
-function testConnections() {
-  console.log('Testing connections...')
-
-  // Log all inputs for debugging
-  console.log('All inputs:', JSON.stringify(input, null, 2))
-
-  // Test for missing data
-  const hasUserData = !!input.userBlock
-  console.log('Has user data:', hasUserData)
-
-  // Test edge cases
-  const items = input.orderBlock?.items || []
-  console.log('Item count:', items.length)
-  console.log('Empty items test:', items.length === 0 ? 'Passed' : 'Failed')
-
-  // Return test results
-  return {
-    tests: {
-      hasUserData,
-      hasItems: items.length > 0,
-      hasLargeOrder: items.length > 10,
-    },
-  }
-}
-```
-
-## Performance Considerations
-
-### Optimize Data Flow
-
-Keep your workflows efficient by optimizing how data flows through connections:
-
-- **Pass only necessary data** between blocks to reduce memory usage
-- **Use Function blocks to filter large datasets** before passing them on
-- **Consider caching results** for expensive operations
-- **Break complex workflows into smaller, reusable components**
-
-```javascript
-// Example: Optimizing data flow by filtering
-function optimizeUserData() {
-  const userData = input.userBlock
-
-  // Only pass necessary fields to downstream blocks
-  return {
-    id: userData.id,
-    name: userData.name,
-    email: userData.email,
-    // Filter out unnecessary profile data, history, etc.
-  }
-}
-```
-
-## Security Best Practices
-
-### Secure Sensitive Data
-
-Protect sensitive information when using connections:
-
-- **Never expose API keys or credentials** in connection data
-- **Sanitize user input** before processing it
-- **Redact sensitive information** when logging connection data
-- **Use secure connections** for external API calls
-
-<Callout type="warning">
-  Be careful when logging connection data that might contain sensitive information. Always redact or
-  mask sensitive fields like passwords, API keys, or personal information.
-</Callout>
-
-## Advanced Patterns
-
-### Conditional Connections
-
-Use Condition blocks to create dynamic workflows:
-
-- **Route data based on content** to different processing paths
-- **Implement fallback paths** for error handling
-- **Create decision trees** for complex business logic
-
-### Feedback Loops
-
-Create more sophisticated workflows with feedback connections:
-
-- **Implement iterative processing** by connecting later blocks back to earlier ones
-- **Use Memory blocks** to store state between iterations
-- **Set termination conditions** to prevent infinite loops

apps/docs/content/docs/connections/data-structure.mdx

@@ -1,12 +1,11 @@
 ---
 title: Connection Data Structure
-description: Understanding the data structure of different block outputs
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
 
-When you connect blocks, the output data structure from the source block determines what values are available in the destination block. Each block type produces a specific output structure that you can reference in downstream blocks.
+When you connect blocks, understanding the data structure of different block outputs is important because the output data structure from the source block determines what values are available in the destination block. Each block type produces a specific output structure that you can reference in downstream blocks.
 
 <Callout type="info">
   Understanding these data structures is essential for effectively using connection tags and
@@ -84,7 +83,7 @@ Different block types produce different output structures. Here's what you can e
     ```json
     {
       "content": "Evaluation summary",
-      "model": "gpt-4o",
+      "model": "gpt-5",
       "tokens": {
         "prompt": 120,
         "completion": 85,
@@ -180,7 +179,7 @@ Some blocks may produce custom output structures based on their configuration:
 Many block outputs contain nested data structures. You can access these using dot notation in connection tags:
 
 ```
-<blockId.path.to.nested.data>
+<blockName.path.to.nested.data>
 ```
 
 For example:

apps/docs/content/docs/connections/index.mdx

@@ -6,6 +6,7 @@ description: Connect your blocks to one another.
 import { Callout } from 'fumadocs-ui/components/callout'
 import { Card, Cards } from 'fumadocs-ui/components/card'
 import { ConnectIcon } from '@/components/icons'
+import { Video } from '@/components/ui/video'
 
 Connections are the pathways that allow data to flow between blocks in your workflow. They define how information is passed from one block to another, enabling you to create sophisticated, multi-step processes.
 
@@ -15,12 +16,12 @@ Connections are the pathways that allow data to flow between blocks in your work
 </Callout>
 
 <div className="mx-auto w-full overflow-hidden rounded-lg">
-  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/connections.mp4"></video>
+  <Video src="connections.mp4" />
 </div>
 
 ## Connection Types
 
-Sim Studio supports different types of connections that enable various workflow patterns:
+Sim supports different types of connections that enable various workflow patterns:
 
 <Cards>
   <Card title="Connection Basics" href="/connections/basics">

apps/docs/content/docs/connections/meta.json

@@ -1,4 +1,5 @@
 {
   "title": "Connections",
-  "pages": ["basics", "tags", "data-structure", "accessing-data", "best-practices"]
+  "pages": ["basics", "tags", "data-structure"],
+  "defaultOpen": false
 }

apps/docs/content/docs/connections/tags.mdx

@@ -1,14 +1,14 @@
 ---
 title: Connection Tags
-description: Using connection tags to reference data between blocks
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
+import { Video } from '@/components/ui/video'
 
-Connection tags are visual representations of the data available from connected blocks. They provide an easy way to reference outputs from previous blocks in your workflow.
+Connection tags are visual representations of the data available from connected blocks, providing an easy way to reference data between blocks and outputs from previous blocks in your workflow.
 
 <div className="mx-auto w-full overflow-hidden rounded-lg">
-  <video autoPlay loop muted playsInline className="w-full -mb-2 rounded-lg" src="/connections.mp4"></video>
+  <Video src="connections.mp4" />
 </div>
 
 ### What Are Connection Tags?
@@ -65,12 +65,12 @@ There are two primary ways to use connection tags in your workflows:
 Connection tags use a simple syntax to reference data:
 
 ```
-<blockId.path.to.data>
+<blockName.path.to.data>
 ```
 
 Where:
 
-- `blockId` is the identifier of the source block
+- `blockName` is the name of the source block
 - `path.to.data` is the path to the specific data field
 
 For example:

apps/docs/content/docs/copilot/index.mdx

@@ -0,0 +1,162 @@
+---
+title: Copilot
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Card, Cards } from 'fumadocs-ui/components/card'
+import { Image } from '@/components/ui/image'
+import { MessageCircle, Package, Zap, Infinity as InfinityIcon, Brain, BrainCircuit } from 'lucide-react'
+
+Copilot is your in-editor assistant that helps you build and edit workflows with Sim Copilot, as well as understand and improve them. It can:
+
+- **Explain**: Answer questions about Sim and your current workflow
+- **Guide**: Suggest edits and best practices
+- **Edit**: Make changes to blocks, connections, and settings when you approve
+
+<Callout type="info">
+  Copilot is a Sim-managed service. For self-hosted deployments, generate a Copilot API key in the hosted app (sim.ai → Settings → Copilot)
+  1. Go to [sim.ai](https://sim.ai) → Settings → Copilot and generate a Copilot API key
+  2. Set `COPILOT_API_KEY` in your self-hosted environment to that value
+</Callout>
+
+## Context Menu (@)
+
+Use the `@` symbol to reference various resources and give Copilot more context about your workspace:
+
+<Image
+  src="/static/copilot/copilot-menu.png"
+  alt="Copilot context menu showing available reference options"
+  width={600}
+  height={400}
+/>
+
+The `@` menu provides access to:
+- **Chats**: Reference previous copilot conversations
+- **All workflows**: Reference any workflow in your workspace
+- **Workflow Blocks**: Reference specific blocks from workflows
+- **Blocks**: Reference block types and templates
+- **Knowledge**: Reference your uploaded documents and knowledgebase
+- **Docs**: Reference Sim documentation
+- **Templates**: Reference workflow templates
+- **Logs**: Reference execution logs and results
+
+This contextual information helps Copilot provide more accurate and relevant assistance for your specific use case.
+
+## Modes
+
+<Cards>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <MessageCircle className="h-4 w-4 text-muted-foreground" />
+        Ask
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">
+      Q&A mode for explanations, guidance, and suggestions without making changes to your workflow.
+    </div>
+  </Card>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <Package className="h-4 w-4 text-muted-foreground" />
+        Agent
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">
+      Build-and-edit mode. Copilot proposes specific edits (add blocks, wire variables, tweak settings) and applies them when you approve.
+    </div>
+  </Card>
+</Cards>
+
+## Depth Levels
+
+<Cards>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <Zap className="h-4 w-4 text-muted-foreground" />
+        Fast
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">Quickest and cheapest. Best for small edits, simple workflows, and minor tweaks.</div>
+  </Card>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <InfinityIcon className="h-4 w-4 text-muted-foreground" />
+        Auto
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">Balanced speed and reasoning. Recommended default for most tasks.</div>
+  </Card>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <Brain className="h-4 w-4 text-muted-foreground" />
+        Advanced
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">More reasoning for larger workflows and complex edits while staying performant.</div>
+  </Card>
+  <Card
+    title={
+      <span className="inline-flex items-center gap-2">
+        <BrainCircuit className="h-4 w-4 text-muted-foreground" />
+        Behemoth
+      </span>
+    }
+  >
+    <div className="m-0 text-sm">Maximum reasoning for deep planning, debugging, and complex architectural changes.</div>
+  </Card>
+</Cards>
+
+### Mode Selection Interface
+
+You can easily switch between different reasoning modes using the mode selector in the Copilot interface:
+
+<Image
+  src="/static/copilot/copilot-models.png"
+  alt="Copilot mode selection showing Advanced mode with MAX toggle"
+  width={600}
+  height={300}
+/>
+
+The interface allows you to:
+- **Select reasoning level**: Choose from Fast, Auto, Advanced, or Behemoth
+- **Enable MAX mode**: Toggle for maximum reasoning capabilities when you need the most thorough analysis
+- **See mode descriptions**: Understand what each mode is optimized for
+
+Choose your mode based on the complexity of your task - use Fast for simple questions and Behemoth for complex architectural changes.
+
+## Billing and Cost Calculation
+
+### How Costs Are Calculated
+
+Copilot usage is billed per token from the underlying LLM:
+
+- **Input tokens**: billed at the provider's base rate (**at-cost**)
+- **Output tokens**: billed at **1.5×** the provider's base output rate
+
+```javascript
+copilotCost = (inputTokens × inputPrice + outputTokens × (outputPrice × 1.5)) / 1,000,000
+```
+
+| Component | Rate Applied         |
+|----------|----------------------|
+| Input    | inputPrice           |
+| Output   | outputPrice × 1.5    |
+
+<Callout type="warning">
+  Pricing shown reflects rates as of September 4, 2025. Check provider documentation for current pricing.
+</Callout>
+
+<Callout type="info">
+  Model prices are per million tokens. The calculation divides by 1,000,000 to get the actual cost. See <a href="/execution/costs">the Cost Calculation page</a> for background and examples.
+</Callout>
+

apps/docs/content/docs/copilot/meta.json

@@ -0,0 +1,5 @@
+{
+  "title": "Copilot",
+  "pages": ["index"],
+  "defaultOpen": false
+}

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/api.mdx

@@ -0,0 +1,536 @@
+---
+title: External API
+---
+
+import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { CodeBlock } from 'fumadocs-ui/components/codeblock'
+import { Video } from '@/components/ui/video'
+
+Sim provides a comprehensive external API for querying workflow execution logs and setting up webhooks for real-time notifications when workflows complete.
+
+## Authentication
+
+All API requests require an API key passed in the `x-api-key` header:
+
+```bash
+curl -H "x-api-key: YOUR_API_KEY" \
+  https://sim.ai/api/v1/logs?workspaceId=YOUR_WORKSPACE_ID
+```
+
+You can generate API keys from your user settings in the Sim dashboard.
+
+## Logs API
+
+All API responses include information about your workflow execution limits and usage:
+
+```json
+"limits": {
+  "workflowExecutionRateLimit": {
+    "sync": {
+      "limit": 60,        // Max sync workflow executions per minute
+      "remaining": 58,    // Remaining sync workflow executions
+      "resetAt": "..."    // When the window resets
+    },
+    "async": {
+      "limit": 60,        // Max async workflow executions per minute
+      "remaining": 59,    // Remaining async workflow executions
+      "resetAt": "..."    // When the window resets
+    }
+  },
+  "usage": {
+    "currentPeriodCost": 1.234,  // Current billing period usage in USD
+    "limit": 10,                  // Usage limit in USD
+    "plan": "pro",                // Current subscription plan
+    "isExceeded": false           // Whether limit is exceeded
+  }
+}
+```
+
+**Note:** The rate limits in the response body are for workflow executions. The rate limits for calling this API endpoint are in the response headers (`X-RateLimit-*`).
+
+### Query Logs
+
+Query workflow execution logs with extensive filtering options.
+
+<Tabs items={['Request', 'Response']}>
+  <Tab value="Request">
+    ```http
+    GET /api/v1/logs
+    ```
+
+    **Required Parameters:**
+    - `workspaceId` - Your workspace ID
+
+    **Optional Filters:**
+    - `workflowIds` - Comma-separated workflow IDs
+    - `folderIds` - Comma-separated folder IDs
+    - `triggers` - Comma-separated trigger types: `api`, `webhook`, `schedule`, `manual`, `chat`
+    - `level` - Filter by level: `info`, `error`
+    - `startDate` - ISO timestamp for date range start
+    - `endDate` - ISO timestamp for date range end
+    - `executionId` - Exact execution ID match
+    - `minDurationMs` - Minimum execution duration in milliseconds
+    - `maxDurationMs` - Maximum execution duration in milliseconds
+    - `minCost` - Minimum execution cost
+    - `maxCost` - Maximum execution cost
+    - `model` - Filter by AI model used
+
+    **Pagination:**
+    - `limit` - Results per page (default: 100)
+    - `cursor` - Cursor for next page
+    - `order` - Sort order: `desc`, `asc` (default: desc)
+
+    **Detail Level:**
+    - `details` - Response detail level: `basic`, `full` (default: basic)
+    - `includeTraceSpans` - Include trace spans (default: false)
+    - `includeFinalOutput` - Include final output (default: false)
+  </Tab>
+  <Tab value="Response">
+    ```json
+    {
+      "data": [
+        {
+          "id": "log_abc123",
+          "workflowId": "wf_xyz789",
+          "executionId": "exec_def456",
+          "level": "info",
+          "trigger": "api",
+          "startedAt": "2025-01-01T12:34:56.789Z",
+          "endedAt": "2025-01-01T12:34:57.123Z",
+          "totalDurationMs": 334,
+          "cost": {
+            "total": 0.00234
+          },
+          "files": null
+        }
+      ],
+      "nextCursor": "eyJzIjoiMjAyNS0wMS0wMVQxMjozNDo1Ni43ODlaIiwiaWQiOiJsb2dfYWJjMTIzIn0",
+      "limits": {
+        "workflowExecutionRateLimit": {
+          "sync": {
+            "limit": 60,
+            "remaining": 58,
+            "resetAt": "2025-01-01T12:35:56.789Z"
+          },
+          "async": {
+            "limit": 60,
+            "remaining": 59,
+            "resetAt": "2025-01-01T12:35:56.789Z"
+          }
+        },
+        "usage": {
+          "currentPeriodCost": 1.234,
+          "limit": 10,
+          "plan": "pro",
+          "isExceeded": false
+        }
+      }
+    }
+    ```
+  </Tab>
+</Tabs>
+
+### Get Log Details
+
+Retrieve detailed information about a specific log entry.
+
+<Tabs items={['Request', 'Response']}>
+  <Tab value="Request">
+    ```http
+    GET /api/v1/logs/{id}
+    ```
+  </Tab>
+  <Tab value="Response">
+    ```json
+    {
+      "data": {
+        "id": "log_abc123",
+        "workflowId": "wf_xyz789",
+        "executionId": "exec_def456",
+        "level": "info",
+        "trigger": "api",
+        "startedAt": "2025-01-01T12:34:56.789Z",
+        "endedAt": "2025-01-01T12:34:57.123Z",
+        "totalDurationMs": 334,
+        "workflow": {
+          "id": "wf_xyz789",
+          "name": "My Workflow",
+          "description": "Process customer data"
+        },
+        "executionData": {
+          "traceSpans": [...],
+          "finalOutput": {...}
+        },
+        "cost": {
+          "total": 0.00234,
+          "tokens": {
+            "prompt": 123,
+            "completion": 456,
+            "total": 579
+          },
+          "models": {
+            "gpt-4o": {
+              "input": 0.001,
+              "output": 0.00134,
+              "total": 0.00234,
+              "tokens": {
+                "prompt": 123,
+                "completion": 456,
+                "total": 579
+              }
+            }
+          }
+        },
+        "limits": {
+          "workflowExecutionRateLimit": {
+            "sync": {
+              "limit": 60,
+              "remaining": 58,
+              "resetAt": "2025-01-01T12:35:56.789Z"
+            },
+            "async": {
+              "limit": 60,
+              "remaining": 59,
+              "resetAt": "2025-01-01T12:35:56.789Z"
+            }
+          },
+          "usage": {
+            "currentPeriodCost": 1.234,
+            "limit": 10,
+            "plan": "pro",
+            "isExceeded": false
+          }
+        }
+      }
+    }
+    ```
+  </Tab>
+</Tabs>
+
+### Get Execution Details
+
+Retrieve execution details including the workflow state snapshot.
+
+<Tabs items={['Request', 'Response']}>
+  <Tab value="Request">
+    ```http
+    GET /api/v1/logs/executions/{executionId}
+    ```
+  </Tab>
+  <Tab value="Response">
+    ```json
+    {
+      "executionId": "exec_def456",
+      "workflowId": "wf_xyz789",
+      "workflowState": {
+        "blocks": {...},
+        "edges": [...],
+        "loops": {...},
+        "parallels": {...}
+      },
+      "executionMetadata": {
+        "trigger": "api",
+        "startedAt": "2025-01-01T12:34:56.789Z",
+        "endedAt": "2025-01-01T12:34:57.123Z",
+        "totalDurationMs": 334,
+        "cost": {...}
+      }
+    }
+    ```
+  </Tab>
+</Tabs>
+
+## Webhook Subscriptions
+
+Get real-time notifications when workflow executions complete. Webhooks are configured through the Sim UI in the workflow editor.
+
+### Configuration
+
+Webhooks can be configured for each workflow through the workflow editor UI. Click the webhook icon in the control bar to set up your webhook subscriptions.
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="configure-webhook.mp4" width={700} height={450} />
+</div>
+
+**Available Configuration Options:**
+- `url`: Your webhook endpoint URL
+- `secret`: Optional secret for HMAC signature verification
+- `includeFinalOutput`: Include the workflow's final output in the payload
+- `includeTraceSpans`: Include detailed execution trace spans
+- `includeRateLimits`: Include the workflow owner's rate limit information
+- `includeUsageData`: Include the workflow owner's usage and billing data
+- `levelFilter`: Array of log levels to receive (`info`, `error`)
+- `triggerFilter`: Array of trigger types to receive (`api`, `webhook`, `schedule`, `manual`, `chat`)
+- `active`: Enable/disable the webhook subscription
+
+### Webhook Payload
+
+When a workflow execution completes, Sim sends a POST request to your webhook URL:
+
+```json
+{
+  "id": "evt_123",
+  "type": "workflow.execution.completed",
+  "timestamp": 1735925767890,
+  "data": {
+    "workflowId": "wf_xyz789",
+    "executionId": "exec_def456",
+    "status": "success",
+    "level": "info",
+    "trigger": "api",
+    "startedAt": "2025-01-01T12:34:56.789Z",
+    "endedAt": "2025-01-01T12:34:57.123Z",
+    "totalDurationMs": 334,
+    "cost": {
+      "total": 0.00234,
+      "tokens": {
+        "prompt": 123,
+        "completion": 456,
+        "total": 579
+      },
+      "models": {
+        "gpt-4o": {
+          "input": 0.001,
+          "output": 0.00134,
+          "total": 0.00234,
+          "tokens": {
+            "prompt": 123,
+            "completion": 456,
+            "total": 579
+          }
+        }
+      }
+    },
+    "files": null,
+    "finalOutput": {...},  // Only if includeFinalOutput=true
+    "traceSpans": [...],   // Only if includeTraceSpans=true
+    "rateLimits": {...},   // Only if includeRateLimits=true
+    "usage": {...}         // Only if includeUsageData=true
+  },
+  "links": {
+    "log": "/v1/logs/log_abc123",
+    "execution": "/v1/logs/executions/exec_def456"
+  }
+}
+```
+
+### Webhook Headers
+
+Each webhook request includes these headers:
+
+- `sim-event`: Event type (always `workflow.execution.completed`)
+- `sim-timestamp`: Unix timestamp in milliseconds
+- `sim-delivery-id`: Unique delivery ID for idempotency
+- `sim-signature`: HMAC-SHA256 signature for verification (if secret configured)
+- `Idempotency-Key`: Same as delivery ID for duplicate detection
+
+### Signature Verification
+
+If you configure a webhook secret, verify the signature to ensure the webhook is from Sim:
+
+<Tabs items={['Node.js', 'Python']}>
+  <Tab value="Node.js">
+    ```javascript
+    import crypto from 'crypto';
+
+    function verifyWebhookSignature(body, signature, secret) {
+      const [timestampPart, signaturePart] = signature.split(',');
+      const timestamp = timestampPart.replace('t=', '');
+      const expectedSignature = signaturePart.replace('v1=', '');
+      
+      const signatureBase = `${timestamp}.${body}`;
+      const hmac = crypto.createHmac('sha256', secret);
+      hmac.update(signatureBase);
+      const computedSignature = hmac.digest('hex');
+      
+      return computedSignature === expectedSignature;
+    }
+
+    // In your webhook handler
+    app.post('/webhook', (req, res) => {
+      const signature = req.headers['sim-signature'];
+      const body = JSON.stringify(req.body);
+      
+      if (!verifyWebhookSignature(body, signature, process.env.WEBHOOK_SECRET)) {
+        return res.status(401).send('Invalid signature');
+      }
+      
+      // Process the webhook...
+    });
+    ```
+  </Tab>
+  <Tab value="Python">
+    ```python
+    import hmac
+    import hashlib
+    import json
+
+    def verify_webhook_signature(body: str, signature: str, secret: str) -> bool:
+        timestamp_part, signature_part = signature.split(',')
+        timestamp = timestamp_part.replace('t=', '')
+        expected_signature = signature_part.replace('v1=', '')
+        
+        signature_base = f"{timestamp}.{body}"
+        computed_signature = hmac.new(
+            secret.encode(),
+            signature_base.encode(),
+            hashlib.sha256
+        ).hexdigest()
+        
+        return hmac.compare_digest(computed_signature, expected_signature)
+
+    # In your webhook handler
+    @app.route('/webhook', methods=['POST'])
+    def webhook():
+        signature = request.headers.get('sim-signature')
+        body = json.dumps(request.json)
+        
+        if not verify_webhook_signature(body, signature, os.environ['WEBHOOK_SECRET']):
+            return 'Invalid signature', 401
+        
+        # Process the webhook...
+    ```
+  </Tab>
+</Tabs>
+
+### Retry Policy
+
+Failed webhook deliveries are retried with exponential backoff and jitter:
+
+- Maximum attempts: 5
+- Retry delays: 5 seconds, 15 seconds, 1 minute, 3 minutes, 10 minutes
+- Jitter: Up to 10% additional delay to prevent thundering herd
+- Only HTTP 5xx and 429 responses trigger retries
+- Deliveries timeout after 30 seconds
+
+<Callout type="info">
+  Webhook deliveries are processed asynchronously and don't affect workflow execution performance.
+</Callout>
+
+## Best Practices
+
+1. **Polling Strategy**: When polling for logs, use cursor-based pagination with `order=asc` and `startDate` to fetch new logs efficiently.
+
+2. **Webhook Security**: Always configure a webhook secret and verify signatures to ensure requests are from Sim.
+
+3. **Idempotency**: Use the `Idempotency-Key` header to detect and handle duplicate webhook deliveries.
+
+4. **Privacy**: By default, `finalOutput` and `traceSpans` are excluded from responses. Only enable these if you need the data and understand the privacy implications.
+
+5. **Rate Limiting**: Implement exponential backoff when you receive 429 responses. Check the `Retry-After` header for the recommended wait time.
+
+## Rate Limiting
+
+The API implements rate limiting to ensure fair usage:
+
+- **Free plan**: 10 requests per minute
+- **Pro plan**: 30 requests per minute
+- **Team plan**: 60 requests per minute
+- **Enterprise plan**: Custom limits
+
+Rate limit information is included in response headers:
+- `X-RateLimit-Limit`: Maximum requests per window
+- `X-RateLimit-Remaining`: Requests remaining in current window
+- `X-RateLimit-Reset`: ISO timestamp when the window resets
+
+## Example: Polling for New Logs
+
+```javascript
+let cursor = null;
+const workspaceId = 'YOUR_WORKSPACE_ID';
+const startDate = new Date().toISOString();
+
+async function pollLogs() {
+  const params = new URLSearchParams({
+    workspaceId,
+    startDate,
+    order: 'asc',
+    limit: '100'
+  });
+  
+  if (cursor) {
+    params.append('cursor', cursor);
+  }
+  
+  const response = await fetch(
+    `https://sim.ai/api/v1/logs?${params}`,
+    {
+      headers: {
+        'x-api-key': 'YOUR_API_KEY'
+      }
+    }
+  );
+  
+  if (response.ok) {
+    const data = await response.json();
+    
+    // Process new logs
+    for (const log of data.data) {
+      console.log(`New execution: ${log.executionId}`);
+    }
+    
+    // Update cursor for next poll
+    if (data.nextCursor) {
+      cursor = data.nextCursor;
+    }
+  }
+}
+
+// Poll every 30 seconds
+setInterval(pollLogs, 30000);
+```
+
+## Example: Processing Webhooks
+
+```javascript
+import express from 'express';
+import crypto from 'crypto';
+
+const app = express();
+app.use(express.json());
+
+app.post('/sim-webhook', (req, res) => {
+  // Verify signature
+  const signature = req.headers['sim-signature'];
+  const body = JSON.stringify(req.body);
+  
+  if (!verifyWebhookSignature(body, signature, process.env.WEBHOOK_SECRET)) {
+    return res.status(401).send('Invalid signature');
+  }
+  
+  // Check timestamp to prevent replay attacks
+  const timestamp = parseInt(req.headers['sim-timestamp']);
+  const fiveMinutesAgo = Date.now() - (5 * 60 * 1000);
+  
+  if (timestamp < fiveMinutesAgo) {
+    return res.status(401).send('Timestamp too old');
+  }
+  
+  // Process the webhook
+  const event = req.body;
+  
+  switch (event.type) {
+    case 'workflow.execution.completed':
+      const { workflowId, executionId, status, cost } = event.data;
+      
+      if (status === 'error') {
+        console.error(`Workflow ${workflowId} failed: ${executionId}`);
+        // Handle error...
+      } else {
+        console.log(`Workflow ${workflowId} completed: ${executionId}`);
+        console.log(`Cost: $${cost.total}`);
+        // Process successful execution...
+      }
+      break;
+  }
+  
+  // Return 200 to acknowledge receipt
+  res.status(200).send('OK');
+});
+
+app.listen(3000, () => {
+  console.log('Webhook server listening on port 3000');
+});
+```

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

@@ -1,248 +1,132 @@
 ---
 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 { Card, Cards } from 'fumadocs-ui/components/card'
 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'
+import { Image } from '@/components/ui/image'
+import { Video } from '@/components/ui/video'
 
-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.
+Understanding how workflows execute in Sim is key to building efficient and reliable automations. The execution engine automatically handles dependencies, concurrency, and data flow to ensure your workflows run smoothly and predictably.
 
-## Execution Flow
+## How Workflows Execute
 
-The execution engine runs workflows in layers, processing blocks based on their dependencies:
+Sim's execution engine processes workflows intelligently by analyzing dependencies and running blocks in the most efficient order possible.
 
-<Steps>
-  <Step>
-    <strong>Validation</strong>: Ensures the workflow has a starter block with no incoming connections and all blocks are properly connected.
-  </Step>
+### Concurrent Execution by Default
 
-  <Step>
-    <strong>Layer-based Execution</strong>: Identifies which blocks can execute next based on completed dependencies and executes them in parallel.
-  </Step>
+Multiple blocks run concurrently when they don't depend on each other. This parallel execution dramatically improves performance without requiring manual configuration.
 
-  <Step>
-    <strong>Path Updates</strong>: Router and Condition blocks update the active execution path, determining which blocks execute next.
-  </Step>
+<Image
+  src="/static/execution/concurrency.png"
+  alt="Multiple blocks running concurrently after the Start block"
+  width={800}
+  height={500}
+/>
 
-  <Step>
-    <strong>Iteration Processing</strong>: Loop and Parallel blocks manage iterations and create virtual instances for concurrent execution.
-  </Step>
+In this example, both the Customer Support and Deep Researcher agent blocks execute simultaneously after the Start block, maximizing efficiency.
 
-  <Step>
-    <strong>Result Collection</strong>: Outputs from the final blocks are collected and returned as the workflow result.
-  </Step>
-</Steps>
+### Automatic Output Combination
 
-## Block Types and Execution
+When blocks have multiple dependencies, the execution engine automatically waits for all dependencies to complete, then provides their combined outputs to the next block. No manual combining required.
 
-Different block types have different execution behaviors:
+<Image
+  src="/static/execution/combination.png"
+  alt="Function block automatically receiving outputs from multiple previous blocks"
+  width={800}
+  height={500}
+/>
 
-<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>
+The Function block receives outputs from both agent blocks as soon as they complete, allowing you to process the combined results.
 
-<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>
+### Smart Routing
+
+Workflows can branch in multiple directions using routing blocks. The execution engine supports both deterministic routing (with Condition blocks) and AI-powered routing (with Router blocks).
+
+<Image
+  src="/static/execution/routing.png"
+  alt="Workflow showing both conditional and router-based branching"
+  width={800}
+  height={500}
+/>
+
+This workflow demonstrates how execution can follow different paths based on conditions or AI decisions, with each path executing independently.
+
+## Block Types
+
+Sim provides different types of blocks that serve specific purposes in your workflows:
+
+<Cards>
+  <Card title="Triggers" href="/triggers">
+    **Starter blocks** initiate workflows and **Webhook blocks** respond to external events. Every workflow needs a trigger to begin execution.
   </Card>
-</Tab>
+  
+  <Card title="Processing Blocks" href="/blocks">
+    **Agent blocks** interact with AI models, **Function blocks** run custom code, and **API blocks** connect to external services. These blocks transform and process your data.
+  </Card>
+  
+  <Card title="Control Flow" href="/blocks">
+    **Router blocks** use AI to choose paths, **Condition blocks** branch based on logic, and **Loop/Parallel blocks** handle iterations and concurrency.
+  </Card>
+  
+  <Card title="Output & Response" href="/blocks">
+    **Response blocks** format final outputs for APIs and chat interfaces, returning structured results from your workflows.
+  </Card>
+</Cards>
 
-  <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>
+All blocks execute automatically based on their dependencies - you don't need to manually manage execution order or timing.
 
-## Execution Methods
+## Execution Triggers
 
-Sim Studio offers multiple ways to trigger workflow execution:
+Workflows can be triggered in several ways, depending on your use case:
 
-### Manual Execution
+### Manual Testing
+Click "Run" in the workflow editor to test your workflow during development. Perfect for debugging and validation.
 
-Run workflows on-demand through the Sim Studio interface by clicking the "Run" button. This is perfect for:
+### Scheduled Execution  
+Set up recurring executions using cron expressions. Great for regular data processing, reports, or maintenance tasks.
 
-- Testing during development
-- One-off tasks
-- Workflows that need human supervision
+### API Deployment
+Deploy workflows as HTTP endpoints that can be called programmatically from your applications.
 
-<ThemeImage
-  lightSrc="/static/light/manual-execution-light.png"
-  darkSrc="/static/dark/manual-execution-dark.png"
-  alt="Manual Execution"
-  width={600}
-  height={400}
-/>
+### Webhook Integration
+Respond to events from external services like GitHub, Stripe, or custom systems in real-time.
 
-### 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}
-/>
+### Chat Interface
+Create conversational interfaces hosted on custom subdomains for user-facing AI applications.
 
 <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.
+  Learn more about each trigger type in the [Triggers section](/triggers) of the documentation.
 </Callout>
 
-## Execution Context
+## Execution Monitoring
 
-Each workflow execution maintains a context that tracks:
+When workflows run, Sim provides real-time visibility into the execution process:
 
-- **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
+- **Live Block States**: See which blocks are currently executing, completed, or failed
+- **Execution Logs**: Detailed logs appear in real-time showing inputs, outputs, and any errors
+- **Performance Metrics**: Track execution time and costs for each block
+- **Path Visualization**: Understand which execution paths were taken through your workflow
 
-## Real-Time Monitoring
+<Callout type="info">
+  All execution details are captured and available for review even after workflows complete, helping with debugging and optimization.
+</Callout>
 
-Monitor your workflow execution in real-time:
+## Key Execution Principles
 
-- **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
+Understanding these core principles will help you build better workflows:
 
-These monitoring features help you understand workflow behavior and quickly identify any issues.
+1. **Dependency-Based Execution**: Blocks only run when all their dependencies have completed
+2. **Automatic Parallelization**: Independent blocks run concurrently without configuration
+3. **Smart Data Flow**: Outputs flow automatically to connected blocks
+4. **Error Handling**: Failed blocks stop their execution path but don't affect independent paths
+5. **State Persistence**: All block outputs and execution details are preserved for debugging
+
+## Next Steps
+
+Now that you understand execution basics, explore:
+- **[Block Types](/blocks)** - Learn about specific block capabilities
+- **[Logging](/execution/logging)** - Monitor workflow executions and debug issues
+- **[Cost Calculation](/execution/costs)** - Understand and optimize workflow costs
+- **[Triggers](/triggers)** - Set up different ways to run your workflows

apps/docs/content/docs/execution/costs.mdx

@@ -0,0 +1,182 @@
+---
+title: Cost Calculation
+---
+
+import { Accordion, Accordions } from 'fumadocs-ui/components/accordion'
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+Sim automatically calculates costs for all workflow executions, providing transparent pricing based on AI model usage and execution charges. Understanding these costs helps you optimize workflows and manage your budget effectively.
+
+## How Costs Are Calculated
+
+Every workflow execution includes two cost components:
+
+**Base Execution Charge**: $0.001 per execution
+
+**AI Model Usage**: Variable cost based on token consumption
+```javascript
+modelCost = (inputTokens × inputPrice + outputTokens × outputPrice) / 1,000,000
+totalCost = baseExecutionCharge + modelCost
+```
+
+<Callout type="info">
+  AI model prices are per million tokens. The calculation divides by 1,000,000 to get the actual cost. Workflows without AI blocks only incur the base execution charge.
+</Callout>
+
+## Model Breakdown in Logs
+
+For workflows using AI blocks, you can view detailed cost information in the logs:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/logs-cost.png"
+    alt="Model Breakdown"
+    width={600}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+The model breakdown shows:
+- **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
+
+## Pricing Options
+
+<Tabs items={['Hosted Models', 'Bring Your Own API Key']}>
+  <Tab>
+    **Hosted Models** - Sim 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 September 10, 2025. Check provider documentation for current pricing.
+</Callout>
+
+## Cost Optimization Strategies
+
+<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>
+  
+  <Accordion title="Caching and Reuse">
+    Store frequently used results in variables or files to avoid repeated AI model calls.
+  </Accordion>
+  
+  <Accordion title="Batch Processing">
+    Process multiple items in a single AI request rather than making individual calls.
+  </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
+
+### Programmatic Usage Tracking
+
+You can query your current usage and limits programmatically using the API:
+
+**Endpoint:**
+```text
+GET /api/users/me/usage-limits
+```
+
+**Authentication:**
+- Include your API key in the `X-API-Key` header
+
+**Example Request:**
+```bash
+curl -X GET -H "X-API-Key: YOUR_API_KEY" -H "Content-Type: application/json" https://sim.ai/api/users/me/usage-limits
+```
+
+**Example Response:**
+```json
+{
+  "success": true,
+  "rateLimit": {
+    "sync": { "isLimited": false, "limit": 10, "remaining": 10, "resetAt": "2025-09-08T22:51:55.999Z" },
+    "async": { "isLimited": false, "limit": 50, "remaining": 50, "resetAt": "2025-09-08T22:51:56.155Z" },
+    "authType": "api"
+  },
+  "usage": {
+    "currentPeriodCost": 12.34,
+    "limit": 100,
+    "plan": "pro"
+  }
+}
+```
+
+**Response Fields:**
+- `currentPeriodCost` reflects usage in the current billing period
+- `limit` is derived from individual limits (Free/Pro) or pooled organization limits (Team/Enterprise)
+- `plan` is the highest-priority active plan associated with your user
+
+## Plan Limits
+
+Different subscription plans have different usage limits:
+
+| Plan | Monthly Usage Limit | Rate Limits (per minute) |
+|------|-------------------|-------------------------|
+| **Free** | $10 | 5 sync, 10 async |
+| **Pro** | $100 | 10 sync, 50 async |
+| **Team** | $500 (pooled) | 50 sync, 100 async |
+| **Enterprise** | Custom | Custom |
+
+## Cost Management Best Practices
+
+1. **Monitor Regularly**: Check your usage dashboard frequently to avoid surprises
+2. **Set Budgets**: Use plan limits as guardrails for your spending
+3. **Optimize Workflows**: Review high-cost executions and optimize prompts or model selection
+4. **Use Appropriate Models**: Match model complexity to task requirements
+5. **Batch Similar Tasks**: Combine multiple requests when possible to reduce overhead
+
+## Next Steps
+
+- Review your current usage in [Settings → Subscription](https://sim.ai/settings/subscription)
+- Learn about [Logging](/execution/logging) to track execution details
+- Explore the [External API](/execution/api) for programmatic cost monitoring
+- Check out [workflow optimization techniques](/blocks) to reduce costs

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

@@ -1,12 +1,11 @@
 ---
 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.
+Sim's execution engine brings your workflows to life by processing blocks in the correct order, managing data flow, and handling errors gracefully, so you can understand exactly how workflows are executed in Sim.
 
 <Callout type="info">
   Every workflow execution follows a deterministic path based on your block connections and logic, ensuring predictable and reliable results.
@@ -20,8 +19,16 @@ Sim Studio's execution engine brings your workflows to life by processing blocks
     workflow
   </Card>
 
-  <Card title="Logging and Cost Calculation" href="/execution/advanced">
-    Understand workflow logs and how execution costs are calculated in Sim Studio
+  <Card title="Logging" href="/execution/logging">
+    Monitor workflow executions with comprehensive logging and real-time visibility
+  </Card>
+  
+  <Card title="Cost Calculation" href="/execution/costs">
+    Understand how workflow execution costs are calculated and optimized
+  </Card>
+  
+  <Card title="External API" href="/execution/api">
+    Access execution logs and set up webhooks programmatically via REST API
   </Card>
 </Cards>
 
@@ -56,15 +63,15 @@ Workflows can be executed through multiple channels:
 
 ### 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`
+When you deploy a workflow as an API, Sim:
+- Creates a unique HTTP endpoint: `https://sim.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 \
+curl -X POST https://sim.ai/api/workflows/your-workflow-id/execute \
   -H "X-API-Key: your-api-key" \
   -H "Content-Type: application/json" \
   -d '{"input": "your data here"}'
@@ -73,7 +80,7 @@ curl -X POST https://simstudio.ai/api/workflows/your-workflow-id/execute \
 ### Deploy as Chat
 
 Chat deployment creates a conversational interface for your workflow:
-- Hosted on a custom subdomain: `https://your-name.simstudio.ai`
+- Hosted on a custom subdomain: `https://your-name.sim.ai`
 - Optional authentication (public, password, or email-based)
 - Customizable UI with your branding
 - Streaming responses for real-time interaction
@@ -125,4 +132,4 @@ const result = await client.executeWorkflow('workflow-id', {
 
 ## 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.
+Start with [Execution Basics](/execution/basics) to understand how workflows run, then explore [Logging](/execution/logging) to monitor your executions and [Cost Calculation](/execution/costs) to optimize your spending.

apps/docs/content/docs/execution/logging.mdx

@@ -0,0 +1,150 @@
+---
+title: Logging
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { Image } from '@/components/ui/image'
+
+Sim provides comprehensive logging for all workflow executions, giving you complete visibility into how your workflows run, what data flows through them, and where issues might occur.
+
+## Logging System
+
+Sim offers two complementary logging interfaces to match different workflows and use cases:
+
+### Real-Time Console
+
+During manual or chat workflow execution, logs appear in real-time in the Console panel on the right side of the workflow editor:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/console.png"
+    alt="Real-time Console Panel"
+    width={400}
+    height={300}
+    className="my-6"
+  />
+</div>
+
+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 workflow executions—whether triggered manually, via API, Chat, Schedule, or Webhook—are logged to the dedicated Logs page:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/logs.png"
+    alt="Logs Page"
+    width={600}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+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:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/logs-sidebar.png"
+    alt="Logs Sidebar Details"
+    width={600}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+### 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
+
+## Workflow Snapshots
+
+For any logged execution, click "View Snapshot" to see the exact workflow state at execution time:
+
+<div className="flex justify-center">
+  <Image
+    src="/static/logs/logs-frozen-canvas.png"
+    alt="Workflow Snapshot"
+    width={600}
+    height={400}
+    className="my-6"
+  />
+</div>
+
+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>
+
+## Log Retention
+
+- **Free Plan**: 7 days of log retention
+- **Pro Plan**: 30 days of log retention
+- **Team Plan**: 90 days of log retention
+- **Enterprise Plan**: Custom retention periods available
+
+## Best Practices
+
+### For Development
+- Use the real-time console for immediate feedback during testing
+- Check block inputs and outputs to verify data flow
+- Use workflow snapshots to compare working vs. broken versions
+
+### For Production
+- Monitor the Logs page regularly for errors or performance issues
+- Set up filters to focus on specific workflows or time periods
+- Use live mode during critical deployments to watch executions in real-time
+
+### For Debugging
+- Always check the execution timeline to identify slow blocks
+- Compare inputs between working and failing executions
+- Use workflow snapshots to see the exact state when issues occurred
+
+## Next Steps
+
+- Learn about [Cost Calculation](/execution/costs) to understand workflow pricing
+- Explore the [External API](/execution/api) for programmatic log access
+- Set up [Webhook notifications](/execution/api#webhook-subscriptions) for real-time alerts

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

@@ -1,4 +1,5 @@
 {
   "title": "Execution",
-  "pages": ["basics", "advanced"]
+  "pages": ["basics", "logging", "costs", "api"],
+  "defaultOpen": false
 }

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

@@ -1,6 +1,5 @@
 ---
 title: Getting Started
-description: Build your first AI workflow in 5 minutes
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,7 +7,6 @@ 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,
@@ -23,11 +21,13 @@ import {
   PerplexityIcon,
   SlackIcon,
 } from '@/components/icons'
+import { Video } from '@/components/ui/video'
+import { Image } from '@/components/ui/image'
 
-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.
+This tutorial will guide you through building your first AI workflow in Sim. 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.
+  This tutorial takes about 10 minutes and covers the essential concepts of building workflows in Sim.
 </Callout>
 
 ## What We're Building
@@ -39,9 +39,8 @@ A people research agent that:
 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"
+<Image
+  src="/static/getting-started/started-1.png"
   alt="Getting Started Example"
   width={800}
   height={500}
@@ -51,7 +50,7 @@ A people research agent that:
 
 <Steps>
   <Step title="Create workflow and add AI agent">
-    Open Sim Studio and click "New Workflow" in the dashboard. Name it "Getting Started".
+    Open Sim 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.
     
@@ -63,7 +62,7 @@ A people research agent that:
     - **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>
+      <Video src="getting-started/started-2.mp4" width={700} height={450} />
     </div>
   </Step>
   
@@ -77,7 +76,7 @@ A people research agent that:
     - 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>
+      <Video src="getting-started/started-3.mp4" width={700} height={450} />
     </div>
   </Step>
   
@@ -92,7 +91,7 @@ A people research agent that:
     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>
+      <Video src="getting-started/started-4.mp4" width={700} height={450} />
     </div>
   </Step>
   
@@ -105,7 +104,7 @@ A people research agent that:
     - 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>
+      <Video src="getting-started/started-5.mp4" width={700} height={450} />
     </div>
   </Step>
   
@@ -120,7 +119,7 @@ A people research agent that:
     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>
+      <Video src="getting-started/started-6.mp4" width={700} height={450} />
     </div>
   </Step>
 </Steps>

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

@@ -1,94 +1,85 @@
 ---
 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'
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Image } from '@/components/ui/image'
 
-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.
+Sim is a visual workflow builder for AI applications that lets you build AI agent workflows visually. Create powerful AI agents, automation workflows, and data processing pipelines by connecting blocks on a canvas—no coding required.
 
-## What Makes Sim Studio Powerful
+<div className="flex justify-center">
+  <Image
+    src="/static/introduction.png"
+    alt="Sim visual workflow canvas"
+    width={700}
+    height={450}
+    className="my-6"
+  />
+</div>
 
-**Multi-Model AI Support** - Connect to OpenAI, Anthropic, Google, Groq, Cerebras, and local models through Ollama. Switch providers without rebuilding workflows.
+## What You Can Build
 
-**60+ Pre-Built Tools** - Gmail, Slack, Notion, Google Sheets, Airtable, Supabase, Pinecone, and more. Extensible architecture allows custom tool integration.
+**AI Assistants & Chatbots**
+Create intelligent agents that can search the web, access your calendar, send emails, and interact with your business tools.
 
-**Flexible Execution** - Run workflows via chat interface, REST API, webhooks, scheduled jobs, or trigger from external systems.
+**Business Process Automation**
+Automate repetitive tasks like data entry, report generation, customer support responses, and content creation.
 
-**Production Deployment** - Deploy as APIs, integrate with existing systems using our SDK, or embed as plugins. Built-in monitoring, logging, and error handling.
+**Data Processing & Analysis**
+Extract insights from documents, analyze datasets, generate reports, and sync data between systems.
 
-**Real-time Collaboration** - Work simultaneously with team members on the same workflow, like Google Docs for AI development.
+**API Integration Workflows**
+Connect multiple services into unified endpoints, orchestrate complex business logic, and handle event-driven automation.
 
-Connect multiple AI models, integrate with 60+ services, and deploy production-ready applications through an intuitive visual interface designed specifically for AI development.
+## How It Works
 
-## Core Building Blocks
+**Visual Canvas**
+Drag and drop blocks to build workflows. Connect AI models, databases, APIs, and business tools with simple point-and-click connections.
 
-**Processing Blocks**
+**Smart Blocks**
+Choose from processing blocks (AI agents, APIs, functions), logic blocks (conditions, loops, routers), and output blocks (responses, evaluators).
 
-- **Agent** - Execute AI model inference with any LLM provider
-- **API** - Connect to REST endpoints and external services  
-- **Function** - Run custom JavaScript for data processing
+**Multiple Triggers**
+Start workflows via chat interface, REST API, webhooks, scheduled jobs, or external events from services like Slack and GitHub.
 
-**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
+**Team Collaboration**
+Work simultaneously with team members on the same workflow with real-time editing and permissions management.
 
 ## Built-in Integrations
 
-**AI Models**: OpenAI, Anthropic, Google, Groq, Cerebras, Ollama
+Sim connects to 80+ services out of the box:
 
-**Communication**: Gmail, Slack, Telegram, WhatsApp, Microsoft Teams
+- **AI Models**: OpenAI, Anthropic, Google, Groq, Cerebras, local Ollama models
+- **Communication**: Gmail, Slack, Teams, Telegram, WhatsApp  
+- **Productivity**: Notion, Google Sheets, Airtable, Monday.com
+- **Development**: GitHub, Jira, Linear, browser automation
+- **Search & Web**: Google Search, Perplexity, Firecrawl, Exa AI
+- **Databases**: PostgreSQL, MySQL, Supabase, Pinecone, Qdrant
 
-**Data Sources**: Notion, Google Sheets, Airtable, Supabase, Pinecone
+Need something custom? Use our [MCP integration](/mcp) to connect any external service.
 
-**Web Services**: Firecrawl, Google Search, Exa AI, Perplexity
+## Deployment Options
 
-**Development**: GitHub, Jira, Linear, browser automation
+**Cloud-hosted**: Get started instantly at [sim.ai](https://sim.ai) with managed infrastructure, automatic scaling, and built-in monitoring.
 
-## Use Cases
+**Self-hosted**: Deploy on your own infrastructure using Docker, with support for local AI models via Ollama for complete data privacy.
 
-**AI Assistants** - Build chatbots with web search, calendar access, and email capabilities
+## Next Steps
 
-**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.
+Ready to build your first AI workflow?
 
 <Cards>
-  <Card title="Getting Started" href="/getting-started">
-    Build your first workflow
+  <Card title="Getting Started" href="/docs/getting-started">
+    Create your first workflow in 10 minutes
   </Card>
-  <Card title="Blocks" href="/blocks">
-    Learn about workflow components
+  <Card title="Workflow Blocks" href="/docs/blocks">
+    Learn about the building blocks
   </Card>
-  <Card title="Tools" href="/tools">
-    Explore integrations
+  <Card title="Tools & Integrations" href="/docs/tools">
+    Explore 60+ built-in integrations
+  </Card>
+  <Card title="Team Permissions" href="/docs/permissions">
+    Set up workspace roles and permissions
   </Card>
 </Cards>

apps/docs/content/docs/knowledgebase/index.mdx

@@ -0,0 +1,113 @@
+---
+title: Knowledgebase
+---
+
+import { Video } from '@/components/ui/video'
+import { Image } from '@/components/ui/image'
+
+The knowledgebase allows you to upload, process, and search through your documents with intelligent vector search and chunking. Documents of various types are automatically processed, embedded, and made searchable. Your documents are intelligently chunked, and you can view, edit, and search through them using natural language queries.
+
+## Upload and Processing
+
+Simply upload your documents to get started. Sim automatically processes them in the background, extracting text, creating embeddings, and breaking them into searchable chunks.
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="knowledgebase-1.mp4" width={700} height={450} />
+</div>
+
+The system handles the entire processing pipeline for you:
+
+1. **Text Extraction**: Content is extracted from your documents using specialized parsers for each file type
+2. **Intelligent Chunking**: Documents are broken into meaningful chunks with configurable size and overlap
+3. **Embedding Generation**: Vector embeddings are created for semantic search capabilities
+4. **Processing Status**: Track the progress as your documents are processed
+
+## Supported File Types
+
+Sim supports PDF, Word (DOC/DOCX), plain text (TXT), Markdown (MD), HTML, Excel (XLS/XLSX), PowerPoint (PPT/PPTX), and CSV files. Files can be up to 100MB each, with optimal performance for files under 50MB. You can upload multiple documents simultaneously, and PDF files include OCR processing for scanned documents.
+
+## Viewing and Editing Chunks
+
+Once your documents are processed, you can view and edit the individual chunks. This gives you full control over how your content is organized and searched.
+
+<Image src="/static/knowledgebase.png" alt="Document chunks view showing processed content" width={800} height={500} />
+
+### Chunk Configuration
+- **Default chunk size**: 1,024 characters
+- **Configurable range**: 100-4,000 characters per chunk
+- **Smart overlap**: 200 characters by default for context preservation
+- **Hierarchical splitting**: Respects document structure (sections, paragraphs, sentences)
+
+### Editing Capabilities
+- **Edit chunk content**: Modify the text content of individual chunks
+- **Adjust chunk boundaries**: Merge or split chunks as needed
+- **Add metadata**: Enhance chunks with additional context
+- **Bulk operations**: Manage multiple chunks efficiently
+
+## Advanced PDF Processing
+
+For PDF documents, Sim offers enhanced processing capabilities:
+
+### OCR Support
+When configured with Azure or [Mistral OCR](https://docs.mistral.ai/ocr/):
+- **Scanned document processing**: Extract text from image-based PDFs
+- **Mixed content handling**: Process PDFs with both text and images
+- **High accuracy**: Advanced AI models ensure accurate text extraction
+
+## Using The Knowledge Block in Workflows
+
+Once your documents are processed, you can use them in your AI workflows through the Knowledge block. This enables Retrieval-Augmented Generation (RAG), allowing your AI agents to access and reason over your document content to provide more accurate, contextual responses.
+
+<Image src="/static/knowledgebase-2.png" alt="Using Knowledge Block in Workflows" width={800} height={500} />
+
+### Knowledge Block Features
+- **Semantic search**: Find relevant content using natural language queries
+- **Context integration**: Automatically include relevant chunks in agent prompts
+- **Dynamic retrieval**: Search happens in real-time during workflow execution
+- **Relevance scoring**: Results ranked by semantic similarity
+
+### Integration Options
+- **System prompts**: Provide context to your AI agents
+- **Dynamic context**: Search and include relevant information during conversations
+- **Multi-document search**: Query across your entire knowledgebase
+- **Filtered search**: Combine with tags for precise content retrieval
+
+## Vector Search Technology
+
+Sim uses vector search powered by [pgvector](https://github.com/pgvector/pgvector) to understand the meaning and context of your content:
+
+### Semantic Understanding
+- **Contextual search**: Finds relevant content even when exact keywords don't match
+- **Concept-based retrieval**: Understands relationships between ideas
+- **Multi-language support**: Works across different languages
+- **Synonym recognition**: Finds related terms and concepts
+
+### Search Capabilities
+- **Natural language queries**: Ask questions in plain English
+- **Similarity search**: Find conceptually similar content
+- **Hybrid search**: Combines vector and traditional keyword search
+- **Configurable results**: Control the number and relevance threshold of results
+
+## Document Management
+
+### Organization Features
+- **Bulk upload**: Upload multiple files at once via the asynchronous API
+- **Processing status**: Real-time updates on document processing
+- **Search and filter**: Find documents quickly in large collections
+- **Metadata tracking**: Automatic capture of file information and processing details
+
+### Security and Privacy
+- **Secure storage**: Documents stored with enterprise-grade security
+- **Access control**: Workspace-based permissions
+- **Processing isolation**: Each workspace has isolated document processing
+- **Data retention**: Configure document retention policies
+
+## Getting Started
+
+1. **Navigate to your knowledgebase**: Access from your workspace sidebar
+2. **Upload documents**: Drag and drop or select files to upload
+3. **Monitor processing**: Watch as documents are processed and chunked
+4. **Explore chunks**: View and edit the processed content
+5. **Add to workflows**: Use the Knowledge block to integrate with your AI agents
+
+The knowledgebase transforms your static documents into an intelligent, searchable resource that your AI workflows can leverage for more informed and contextual responses.

apps/docs/content/docs/knowledgebase/meta.json

@@ -0,0 +1,5 @@
+{
+  "title": "Knowledgebase",
+  "pages": ["index", "tags"],
+  "defaultOpen": false
+}

apps/docs/content/docs/knowledgebase/tags.mdx

@@ -0,0 +1,108 @@
+---
+title: Tags and Filtering
+---
+
+import { Video } from '@/components/ui/video'
+
+Tags provide a powerful way to organize your documents and create precise filtering for your vector searches. By combining tag-based filtering with semantic search, you can retrieve exactly the content you need from your knowledgebase.
+
+## Adding Tags to Documents
+
+You can add custom tags to any document in your knowledgebase to organize and categorize your content for easier retrieval.
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="knowledgebase-tag.mp4" width={700} height={450} />
+</div>
+
+### Tag Management
+- **Custom tags**: Create your own tag system that fits your workflow
+- **Multiple tags per document**: Apply as many tags as needed to each document, there are 7 tag slots available per knowledgebase that are shared by all documents in the knowledgebase
+- **Tag organization**: Group related documents with consistent tagging
+
+### Tag Best Practices
+- **Consistent naming**: Use standardized tag names across your documents
+- **Descriptive tags**: Use clear, meaningful tag names
+- **Regular cleanup**: Remove unused or outdated tags periodically
+
+## Using Tags in Knowledge Blocks
+
+Tags become powerful when combined with the Knowledge block in your workflows. You can filter your searches to specific tagged content, ensuring your AI agents get the most relevant information.
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="knowledgebase-tag2.mp4" width={700} height={450} />
+</div>
+
+## Search Modes
+
+The Knowledge block supports three different search modes depending on what you provide:
+
+### 1. Tag-Only Search
+When you **only provide tags** (no search query):
+- **Direct retrieval**: Fetches all documents that have the specified tags
+- **No vector search**: Results are based purely on tag matching
+- **Fast performance**: Quick retrieval without semantic processing
+- **Exact matching**: Only documents with all specified tags are returned
+
+**Use case**: When you need all documents from a specific category or project
+
+### 2. Vector Search Only
+When you **only provide a search query** (no tags):
+- **Semantic search**: Finds content based on meaning and context
+- **Full knowledgebase**: Searches across all documents
+- **Relevance ranking**: Results ordered by semantic similarity
+- **Natural language**: Use questions or phrases to find relevant content
+
+**Use case**: When you need the most relevant content regardless of organization
+
+### 3. Combined Tag Filtering + Vector Search
+When you **provide both tags and a search query**:
+1. **First**: Filter documents to only those with the specified tags
+2. **Then**: Perform vector search within that filtered subset
+3. **Result**: Semantically relevant content from your tagged documents only
+
+**Use case**: When you need relevant content from a specific category or project
+
+### Search Configuration
+
+#### Tag Filtering
+- **Multiple tags**: Use multiple tags for OR logic (document must have one or more of the tags)
+- **Tag combinations**: Mix different tag types for precise filtering
+- **Case sensitivity**: Tag matching is case-insensitive
+- **Partial matching**: Exact tag name matching required
+
+#### Vector Search Parameters
+- **Query complexity**: Natural language questions work best
+- **Result limits**: Configure how many chunks to retrieve
+- **Relevance threshold**: Set minimum similarity scores
+- **Context window**: Adjust chunk size for your use case
+
+## Integration with Workflows
+
+### Knowledge Block Configuration
+1. **Select knowledgebase**: Choose which knowledgebase to search
+2. **Add tags**: Specify filtering tags (optional)
+3. **Enter query**: Add your search query (optional)
+4. **Configure results**: Set number of chunks to retrieve
+5. **Test search**: Preview results before using in workflow
+
+### Dynamic Tag Usage
+- **Variable tags**: Use workflow variables as tag values
+- **Conditional filtering**: Apply different tags based on workflow logic
+- **Context-aware search**: Adjust tags based on conversation context
+- **Multi-step filtering**: Refine searches through workflow steps
+
+### Performance Optimization
+- **Efficient filtering**: Tag filtering happens before vector search for better performance
+- **Caching**: Frequently used tag combinations are cached for speed
+- **Parallel processing**: Multiple tag searches can run simultaneously
+- **Resource management**: Automatic optimization of search resources
+
+## Getting Started with Tags
+
+1. **Plan your tag structure**: Decide on consistent naming conventions
+2. **Start tagging**: Add relevant tags to your existing documents
+3. **Test combinations**: Experiment with tag + search query combinations
+4. **Integrate into workflows**: Use the Knowledge block with your tagging strategy
+5. **Refine over time**: Adjust your tagging approach based on search results
+
+Tags transform your knowledgebase from a simple document store into a precisely organized, searchable intelligence system that your AI workflows can navigate with surgical precision.

apps/docs/content/docs/mcp/index.mdx

@@ -0,0 +1,140 @@
+---
+title: MCP (Model Context Protocol)
+---
+
+import { Video } from '@/components/ui/video'
+import { Callout } from 'fumadocs-ui/components/callout'
+
+The Model Context Protocol ([MCP](https://modelcontextprotocol.com/)) allows you to connect external tools and services using a standardized protocol, enabling you to integrate APIs and services directly into your workflows. With MCP, you can extend Sim's capabilities by adding custom integrations that work seamlessly with your agents and workflows.
+
+## What is MCP?
+
+MCP is an open standard that enables AI assistants to securely connect to external data sources and tools. It provides a standardized way to:
+
+- Connect to databases, APIs, and file systems
+- Access real-time data from external services
+- Execute custom tools and scripts
+- Maintain secure, controlled access to external resources
+
+## Adding MCP Servers
+
+MCP servers provide collections of tools that your agents can use. You can add MCP servers in two ways:
+
+### From Workspace Settings
+
+Configure MCP servers at the workspace level so all team members can use them:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp-1.mp4" width={700} height={450} />
+</div>
+
+1. Navigate to your workspace settings
+2. Go to the **MCP Servers** section
+3. Click **Add MCP Server**
+4. Enter the server configuration details
+5. Save the configuration
+
+<Callout type="info">
+MCP servers configured in workspace settings are available to all workspace members based on their permission levels.
+</Callout>
+
+### From Agent Configuration
+
+You can also add and configure MCP servers directly from within an agent block:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp-2.mp4" width={700} height={450} />
+</div>
+
+This is useful when you need to quickly set up a specific integration for a particular workflow.
+
+## Using MCP Tools in Agents
+
+Once MCP servers are configured, their tools become available within your agent blocks:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp-3.mp4" width={700} height={450} />
+</div>
+
+1. Open an **Agent** block
+2. In the **Tools** section, you'll see available MCP tools
+3. Select the tools you want the agent to use
+4. The agent can now access these tools during execution
+
+## Standalone MCP Tool Block
+
+For more granular control, you can use the dedicated MCP Tool block to execute specific MCP tools:
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="mcp-4.mp4" width={700} height={450} />
+</div>
+
+The MCP Tool block allows you to:
+- Execute any configured MCP tool directly
+- Pass specific parameters to the tool
+- Use the tool's output in subsequent workflow steps
+- Chain multiple MCP tools together
+
+### When to Use MCP Tool vs Agent
+
+**Use Agent with MCP tools when:**
+- You want the AI to decide which tools to use
+- You need complex reasoning about when and how to use tools
+- You want natural language interaction with the tools
+
+**Use MCP Tool block when:**
+- You need deterministic tool execution
+- You want to execute a specific tool with known parameters
+- You're building structured workflows with predictable steps
+
+## Permission Requirements
+
+MCP functionality requires specific workspace permissions:
+
+| Action | Required Permission |
+|--------|-------------------|
+| Configure MCP servers in settings | **Admin** |
+| Use MCP tools in agents | **Write** or **Admin** |
+| View available MCP tools | **Read**, **Write**, or **Admin** |
+| Execute MCP Tool blocks | **Write** or **Admin** |
+
+## Common Use Cases
+
+### Database Integration
+Connect to databases to query, insert, or update data within your workflows.
+
+### API Integrations
+Access external APIs and web services that don't have built-in Sim integrations.
+
+### File System Access
+Read, write, and manipulate files on local or remote file systems.
+
+### Custom Business Logic
+Execute custom scripts or tools specific to your organization's needs.
+
+### Real-time Data Access
+Fetch live data from external systems during workflow execution.
+
+## Security Considerations
+
+- MCP servers run with the permissions of the user who configured them
+- Always verify MCP server sources before installation
+- Use environment variables for sensitive configuration data
+- Review MCP server capabilities before granting access to agents
+
+## Troubleshooting
+
+### MCP Server Not Appearing
+- Verify the server configuration is correct
+- Check that you have the required permissions
+- Ensure the MCP server is running and accessible
+
+### Tool Execution Failures
+- Verify tool parameters are correctly formatted
+- Check MCP server logs for error messages
+- Ensure required authentication is configured
+
+### Permission Errors
+- Confirm your workspace permission level
+- Check if the MCP server requires additional authentication
+- Verify the server is properly configured for your workspace

apps/docs/content/docs/mcp/meta.json

@@ -0,0 +1,5 @@
+{
+  "title": "MCP",
+  "pages": ["index"],
+  "defaultOpen": false
+}

apps/docs/content/docs/meta.json

@@ -1,21 +1,25 @@
 {
-  "title": "Sim Studio Documentation",
+  "title": "Sim Documentation",
   "pages": [
-    "---Introduction---",
     "./introduction/index",
     "./getting-started/index",
-    "---Create---",
+    "---Building Workflows---",
+    "triggers",
     "blocks",
     "tools",
-    "---Connections---",
     "connections",
+    "mcp",
+    "copilot",
+    "knowledgebase",
+    "---Configuration---",
+    "variables",
     "---Execution---",
     "execution",
     "---Advanced---",
-    "./variables/index",
+    "permissions",
+    "yaml",
     "---SDKs---",
-    "./sdks/python",
-    "./sdks/typescript"
+    "sdks"
   ],
-  "defaultOpen": true
+  "defaultOpen": false
 }

apps/docs/content/docs/permissions/meta.json

@@ -0,0 +1,5 @@
+{
+  "title": "Permissions",
+  "pages": ["roles-and-permissions"],
+  "defaultOpen": false
+}

apps/docs/content/docs/permissions/roles-and-permissions.mdx

@@ -0,0 +1,161 @@
+---
+title: "Roles and Permissions"
+---
+
+import { Video } from '@/components/ui/video'
+
+When you invite team members to your organization or workspace, you'll need to choose what level of access to give them. This guide explains what each permission level allows users to do, helping you understand team roles and what access each permission level provides.
+
+## How to Invite Someone to a Workspace
+
+<div className="mx-auto w-full overflow-hidden rounded-lg">
+  <Video src="invitations.mp4" width={700} height={450} />
+</div>
+
+## Workspace Permission Levels
+
+When inviting someone to a workspace, you can assign one of three permission levels:
+
+| Permission | What They Can Do |
+|------------|------------------|
+| **Read** | View workflows, see execution results, but cannot make any changes |
+| **Write** | Create and edit workflows, run workflows, manage environment variables |
+| **Admin** | Everything Write can do, plus invite/remove users and manage workspace settings |
+
+## What Each Permission Level Can Do
+
+Here's a detailed breakdown of what users can do with each permission level:
+
+### Read Permission
+**Perfect for:** Stakeholders, observers, or team members who need visibility but shouldn't make changes
+
+**What they can do:**
+- View all workflows in the workspace
+- See workflow execution results and logs
+- Browse workflow configurations and settings
+- View environment variables (but not edit them)
+
+**What they cannot do:**
+- Create, edit, or delete workflows
+- Run or deploy workflows
+- Change any workspace settings
+- Invite other users
+
+### Write Permission  
+**Perfect for:** Developers, content creators, or team members actively working on automation
+
+**What they can do:**
+- Everything Read users can do, plus:
+- Create, edit, and delete workflows
+- Run and deploy workflows
+- Add, edit, and delete workspace environment variables
+- Use all available tools and integrations
+- Collaborate in real-time on workflow editing
+
+**What they cannot do:**
+- Invite or remove users from the workspace
+- Change workspace settings
+- Delete the workspace
+
+### Admin Permission
+**Perfect for:** Team leads, project managers, or technical leads who need to manage the workspace
+
+**What they can do:**
+- Everything Write users can do, plus:
+- Invite new users to the workspace with any permission level
+- Remove users from the workspace
+- Manage workspace settings and integrations
+- Configure external tool connections
+- Delete workflows created by other users
+
+**What they cannot do:**
+- Delete the workspace (only the workspace owner can do this)
+- Remove the workspace owner from the workspace
+
+---
+
+## Workspace Owner vs Admin
+
+Every workspace has one **Owner** (the person who created it) plus any number of **Admins**.
+
+### Workspace Owner
+- Has all Admin permissions
+- Can delete the workspace
+- Cannot be removed from the workspace
+- Can transfer ownership to another user
+
+### Workspace Admin  
+- Can do everything except delete the workspace or remove the owner
+- Can be removed from the workspace by the owner or other admins
+
+---
+
+## Common Scenarios
+
+### Adding a New Developer to Your Team
+1. **Organization level**: Invite them as an **Organization Member**
+2. **Workspace level**: Give them **Write** permission so they can create and edit workflows
+
+### Adding a Project Manager
+1. **Organization level**: Invite them as an **Organization Member** 
+2. **Workspace level**: Give them **Admin** permission so they can manage the team and see everything
+
+### Adding a Stakeholder or Client
+1. **Organization level**: Invite them as an **Organization Member**
+2. **Workspace level**: Give them **Read** permission so they can see progress but not make changes
+
+---
+
+## Environment Variables
+
+Users can create two types of environment variables:
+
+### Personal Environment Variables
+- Only visible to the individual user
+- Available in all workflows they run
+- Managed in user settings
+
+### Workspace Environment Variables
+- **Read permission**: Can see variable names and values
+- **Write/Admin permission**: Can add, edit, and delete variables
+- Available to all workspace members
+- If a personal variable has the same name as a workspace variable, the personal one takes priority
+
+---
+
+## Best Practices
+
+### Start with Minimal Permissions
+Give users the lowest permission level they need to do their job. You can always increase permissions later.
+
+### Use Organization Structure Wisely
+- Make trusted team leads **Organization Admins**
+- Most team members should be **Organization Members**
+- Reserve workspace **Admin** permissions for people who need to manage users
+
+### Review Permissions Regularly
+Periodically review who has access to what, especially when team members change roles or leave the company.
+
+### Environment Variable Security
+- Use personal environment variables for sensitive API keys
+- Use workspace environment variables for shared configuration
+- Regularly audit who has access to sensitive variables
+
+---
+
+## Organization Roles
+
+When inviting someone to your organization, you can assign one of two roles:
+
+### Organization Admin
+**What they can do:**
+- Invite and remove team members from the organization
+- Create new workspaces
+- Manage billing and subscription settings
+- Access all workspaces within the organization
+
+### Organization Member  
+**What they can do:**
+- Access workspaces they've been specifically invited to
+- View the list of organization members
+- Cannot invite new people or manage organization settings

apps/docs/content/docs/sdks/meta.json

@@ -0,0 +1,4 @@
+{
+  "title": "SDKs",
+  "pages": ["python", "typescript"]
+}

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

@@ -1,6 +1,5 @@
 ---
 title: Python SDK
-description: The official Python SDK for Sim Studio
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,7 +7,7 @@ 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.
+The official Python SDK for Sim allows you to execute workflows programmatically from your Python applications using the official Python SDK.
 
 <Callout type="info">
   The Python SDK supports Python 3.8+ and provides synchronous workflow execution. All workflow executions are currently synchronous.
@@ -32,7 +31,7 @@ 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
+    base_url="https://sim.ai"  # optional, defaults to https://sim.ai
 )
 
 # Execute a workflow
@@ -50,12 +49,12 @@ except Exception as error:
 #### Constructor
 
 ```python
-SimStudioClient(api_key: str, base_url: str = "https://simstudio.ai")
+SimStudioClient(api_key: str, base_url: str = "https://sim.ai")
 ```
 
 **Parameters:**
-- `api_key` (str): Your Sim Studio API key
-- `base_url` (str, optional): Base URL for the Sim Studio API
+- `api_key` (str): Your Sim API key
+- `base_url` (str, optional): Base URL for the Sim API
 
 #### Methods
 
@@ -353,7 +352,7 @@ Configure the client using environment variables:
     # Development configuration
     client = SimStudioClient(
         api_key=os.getenv("SIMSTUDIO_API_KEY"),
-        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://simstudio.ai")
+        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://sim.ai")
     )
     ```
   </Tab>
@@ -369,7 +368,7 @@ Configure the client using environment variables:
 
     client = SimStudioClient(
         api_key=api_key,
-        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://simstudio.ai")
+        base_url=os.getenv("SIMSTUDIO_BASE_URL", "https://sim.ai")
     )
     ```
   </Tab>
@@ -378,8 +377,8 @@ Configure the client using environment variables:
 ## 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 title="Log in to Sim">
+    Navigate to [Sim](https://sim.ai) and log in to your account.
   </Step>
   <Step title="Open your workflow">
     Navigate to the workflow you want to execute programmatically.

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

@@ -1,6 +1,5 @@
 ---
 title: TypeScript/JavaScript SDK
-description: The official TypeScript/JavaScript SDK for Sim Studio
 ---
 
 import { Callout } from 'fumadocs-ui/components/callout'
@@ -8,7 +7,7 @@ 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.
+The official TypeScript/JavaScript SDK for Sim provides full type safety and supports both Node.js and browser environments, allowing you to execute workflows programmatically from your Node.js applications, web applications, and other JavaScript environments. All workflow executions are currently synchronous.
 
 <Callout type="info">
   The TypeScript SDK provides full type safety and supports both Node.js and browser environments. All workflow executions are currently synchronous.
@@ -46,7 +45,7 @@ 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
+  baseUrl: 'https://sim.ai' // optional, defaults to https://sim.ai
 });
 
 // Execute a workflow
@@ -69,8 +68,8 @@ 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`)
+- `config.apiKey` (string): Your Sim API key
+- `config.baseUrl` (string, optional): Base URL for the Sim API (defaults to `https://sim.ai`)
 
 #### Methods
 
@@ -332,7 +331,7 @@ Configure the client using environment variables:
 
     const client = new SimStudioClient({
       apiKey,
-      baseUrl: process.env.SIMSTUDIO_BASE_URL || 'https://simstudio.ai'
+      baseUrl: process.env.SIMSTUDIO_BASE_URL || 'https://sim.ai'
     });
     ```
   </Tab>
@@ -429,7 +428,7 @@ 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'
+  baseUrl: 'https://sim.ai'
 });
 
 async function executeClientSideWorkflow() {
@@ -539,8 +538,8 @@ function WorkflowComponent() {
 ## 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 title="Log in to Sim">
+    Navigate to [Sim](https://sim.ai) and log in to your account.
   </Step>
   <Step title="Open your workflow">
     Navigate to the workflow you want to execute programmatically.

apps/docs/content/docs/tools/airtable.mdx

@@ -51,7 +51,7 @@ With Airtable, you can:
 - **Automate workflows**: Set up triggers and actions to automate repetitive tasks
 - **Integrate with other tools**: Connect with hundreds of other applications through native integrations and APIs
 
-In Sim Studio, the Airtable integration enables your agents to interact with your Airtable bases programmatically. This allows for seamless data operations like retrieving information, creating new records, and updating existing data - all within your agent workflows. Use Airtable as a dynamic data source or destination for your agents, enabling them to access and manipulate structured information as part of their decision-making and task execution processes.
+In Sim, the Airtable integration enables your agents to interact with your Airtable bases programmatically. This allows for seamless data operations like retrieving information, creating new records, and updating existing data - all within your agent workflows. Use Airtable as a dynamic data source or destination for your agents, enabling them to access and manipulate structured information as part of their decision-making and task execution processes.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -71,19 +71,16 @@ Read records from an Airtable table
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID of the table |
 | `maxRecords` | number | No | Maximum number of records to return |
-| `filterFormula` | string | No | Formula to filter records \(e.g.,  |
+| `filterFormula` | string | No | Formula to filter records \(e.g., "\(\{Field Name\} = \'Value\'\)"\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `records` | string |
-| `metadata` | string |
-| `totalRecords` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `records` | json | Array of retrieved Airtable records |
 
 ### `airtable_get_record`
 
@@ -93,17 +90,16 @@ Retrieve a single record from an Airtable table by its ID
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID or name of the table |
 | `recordId` | string | Yes | ID of the record to retrieve |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `record` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `record` | json | Retrieved Airtable record with id, createdTime, and fields |
+| `metadata` | json | Operation metadata including record count |
 
 ### `airtable_create_records`
 
@@ -113,16 +109,16 @@ Write new records to an Airtable table
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID or name of the table |
+| `records` | json | Yes | Array of records to create, each with a `fields` object |
+| `fields` | string | No | No description |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `records` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `records` | json | Array of created Airtable records |
 
 ### `airtable_update_record`
 
@@ -132,7 +128,6 @@ Update an existing record in an Airtable table by ID
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID or name of the table |
 | `recordId` | string | Yes | ID of the record to update |
@@ -140,11 +135,10 @@ Update an existing record in an Airtable table by ID
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `record` | string |
-| `metadata` | string |
-| `updatedFields` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `record` | json | Updated Airtable record with id, createdTime, and fields |
+| `metadata` | json | Operation metadata including record count and updated field names |
 
 ### `airtable_update_multiple_records`
 
@@ -154,39 +148,18 @@ Update multiple existing records in an Airtable table
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token |
 | `baseId` | string | Yes | ID of the Airtable base |
 | `tableId` | string | Yes | ID or name of the table |
+| `records` | json | Yes | Array of records to update, each with an `id` and a `fields` object |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `records` | string |
-| `metadata` | string |
-| `updatedRecordIds` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `records` | json | Array of updated Airtable records |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `records` | json | records output from the block |
-| `record` | json | record output from the block |
-| `metadata` | json | metadata output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/arxiv.mdx

@@ -0,0 +1,114 @@
+---
+title: ArXiv
+description: Search and retrieve academic papers from ArXiv
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="arxiv"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"  id='logomark' xmlns='http://www.w3.org/2000/svg' viewBox='0 0 17.732 24.269'>
+      <g id='tiny'>
+        <path
+          d='M573.549,280.916l2.266,2.738,6.674-7.84c.353-.47.52-.717.353-1.117a1.218,1.218,0,0,0-1.061-.748h0a.953.953,0,0,0-.712.262Z'
+          transform='translate(-566.984 -271.548)'
+          fill='#bdb9b4'
+        />
+        <path
+          d='M579.525,282.225l-10.606-10.174a1.413,1.413,0,0,0-.834-.5,1.09,1.09,0,0,0-1.027.66c-.167.4-.047.681.319,1.206l8.44,10.242h0l-6.282,7.716a1.336,1.336,0,0,0-.323,1.3,1.114,1.114,0,0,0,1.04.69A.992.992,0,0,0,571,293l8.519-7.92A1.924,1.924,0,0,0,579.525,282.225Z'
+          transform='translate(-566.984 -271.548)'
+          fill='#b31b1b'
+        />
+        <path
+          d='M584.32,293.912l-8.525-10.275,0,0L573.53,280.9l-1.389,1.254a2.063,2.063,0,0,0,0,2.965l10.812,10.419a.925.925,0,0,0,.742.282,1.039,1.039,0,0,0,.953-.667A1.261,1.261,0,0,0,584.32,293.912Z'
+          transform='translate(-566.984 -271.548)'
+          fill='#bdb9b4'
+        />
+      </g>
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[ArXiv](https://arxiv.org/) is a free, open-access repository of scientific research papers in fields such as physics, mathematics, computer science, quantitative biology, quantitative finance, statistics, electrical engineering, systems science, and economics. ArXiv provides a vast collection of preprints and published articles, making it a primary resource for researchers and practitioners worldwide.
+
+With ArXiv, you can:
+
+- **Search for academic papers**: Find research by keywords, author names, titles, categories, and more
+- **Retrieve paper metadata**: Access abstracts, author lists, publication dates, and other bibliographic information
+- **Download full-text PDFs**: Obtain the complete text of most papers for in-depth study
+- **Explore author contributions**: View all papers by a specific author
+- **Stay up-to-date**: Discover the latest submissions and trending topics in your field
+
+In Sim, the ArXiv integration enables your agents to programmatically search, retrieve, and analyze scientific papers from ArXiv. This allows you to automate literature reviews, build research assistants, or incorporate up-to-date scientific knowledge into your agentic workflows. Use ArXiv as a dynamic data source for research, discovery, and knowledge extraction within your Sim projects.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Search for academic papers, retrieve metadata, download papers, and access the vast collection of scientific research on ArXiv.
+
+
+
+## Tools
+
+### `arxiv_search`
+
+Search for academic papers on ArXiv by keywords, authors, titles, or other fields.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `searchQuery` | string | Yes | The search query to execute |
+| `searchField` | string | No | Field to search in: all, ti \(title\), au \(author\), abs \(abstract\), co \(comment\), jr \(journal\), cat \(category\), rn \(report number\) |
+| `maxResults` | number | No | Maximum number of results to return \(default: 10, max: 2000\) |
+| `sortBy` | string | No | Sort by: relevance, lastUpdatedDate, submittedDate \(default: relevance\) |
+| `sortOrder` | string | No | Sort order: ascending, descending \(default: descending\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `papers` | json | Array of papers matching the search query |
+
+### `arxiv_get_paper`
+
+Get detailed information about a specific ArXiv paper by its ID.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `paperId` | string | Yes | ArXiv paper ID \(e.g., "1706.03762"\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `paper` | json | Detailed information about the requested ArXiv paper |
+
+### `arxiv_get_author_papers`
+
+Search for papers by a specific author on ArXiv.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `authorName` | string | Yes | Author name to search for |
+| `maxResults` | number | No | Maximum number of results to return \(default: 10, max: 2000\) |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `authorPapers` | json | Array of papers authored by the specified author |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `arxiv`

apps/docs/content/docs/tools/browser_use.mdx

@@ -51,7 +51,7 @@ With BrowserUse, you can:
 - **Monitor task execution**: Watch browser tasks run in real-time with visual feedback
 - **Process results programmatically**: Receive structured output from web automation tasks
 
-In Sim Studio, the BrowserUse integration allows your agents to interact with the web as if they were human users. This enables scenarios like research, data collection, form submission, and web testing - all through simple natural language instructions. Your agents can gather information from websites, interact with web applications, and perform actions that would typically require manual browsing, expanding their capabilities to include the entire web as a resource.
+In Sim, the BrowserUse integration allows your agents to interact with the web as if they were human users. This enables scenarios like research, data collection, form submission, and web testing - all through simple natural language instructions. Your agents can gather information from websites, interact with web applications, and perform actions that would typically require manual browsing, expanding their capabilities to include the entire web as a resource.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -73,41 +73,22 @@ Runs a browser automation task using BrowserUse
 | --------- | ---- | -------- | ----------- |
 | `task` | string | Yes | What should the browser agent do |
 | `variables` | json | No | Optional variables to use as secrets \(format: \{key: value\}\) |
+| `format` | string | No | No description |
 | `save_browser_data` | boolean | No | Whether to save browser data |
 | `model` | string | No | LLM model to use \(default: gpt-4o\) |
 | `apiKey` | string | Yes | API key for BrowserUse API |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `id` | string |
-| `success` | string |
-| `output` | string |
-| `steps` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `id` | string | Task execution identifier |
+| `success` | boolean | Task completion status |
+| `output` | json | Task output data |
+| `steps` | json | Execution steps taken |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `task` | string | Yes | Task - Describe what the browser agent should do... |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `id` | string | id output from the block |
-| `success` | boolean | success output from the block |
-| `output` | any | output output from the block |
-| `steps` | json | steps output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/clay.mdx

@@ -174,13 +174,13 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Clay](https://www.clay.com/) is a data enrichment and workflow automation platform that helps teams streamline lead generation, research, and data operations through powerful integrations and flexible inputs.
 
-Learn how to use the Clay Tool in Sim Studio to seamlessly insert data into a Clay workbook through webhook triggers. This tutorial walks you through setting up a webhook, configuring data mapping, and automating real-time updates to your Clay workbooks. Perfect for streamlining lead generation and data enrichment directly from your workflow!
+Learn how to use the Clay Tool in Sim to seamlessly insert data into a Clay workbook through webhook triggers. This tutorial walks you through setting up a webhook, configuring data mapping, and automating real-time updates to your Clay workbooks. Perfect for streamlining lead generation and data enrichment directly from your workflow!
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/cx_75X5sI_s"
-  title="Clay Integration with Sim Studio"
+  title="Clay Integration with Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -188,11 +188,11 @@ Learn how to use the Clay Tool in Sim Studio to seamlessly insert data into a Cl
 
 With Clay, you can:
 
-- **Enrich agent outputs**: Automatically feed your Sim Studio agent data into Clay tables for structured tracking and analysis
-- **Trigger workflows via webhooks**: Use Clay’s webhook support to initiate Sim Studio agent tasks from within Clay
+- **Enrich agent outputs**: Automatically feed your Sim agent data into Clay tables for structured tracking and analysis
+- **Trigger workflows via webhooks**: Use Clay’s webhook support to initiate Sim agent tasks from within Clay
 - **Leverage data loops**: Seamlessly iterate over enriched data rows with agents that operate across dynamic datasets
 
-In Sim Studio, the Clay integration allows your agents to push structured data into Clay tables via webhooks. This makes it easy to collect, enrich, and manage dynamic outputs such as leads, research summaries, or action items—all in a collaborative, spreadsheet-like interface. Your agents can populate rows in real time, enabling asynchronous workflows where AI-generated insights are captured, reviewed, and used by your team. Whether you're automating research, enriching CRM data, or tracking operational outcomes, Clay becomes a living data layer that interacts intelligently with your agents. By connecting Sim Studio with Clay, you gain a powerful way to operationalize agent results, loop over datasets with precision, and maintain a clean, auditable record of AI-driven work.
+In Sim, the Clay integration allows your agents to push structured data into Clay tables via webhooks. This makes it easy to collect, enrich, and manage dynamic outputs such as leads, research summaries, or action items—all in a collaborative, spreadsheet-like interface. Your agents can populate rows in real time, enabling asynchronous workflows where AI-generated insights are captured, reviewed, and used by your team. Whether you're automating research, enriching CRM data, or tracking operational outcomes, Clay becomes a living data layer that interacts intelligently with your agents. By connecting Sim with Clay, you gain a powerful way to operationalize agent results, loop over datasets with precision, and maintain a clean, auditable record of AI-driven work.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -218,29 +218,13 @@ Populate Clay with data from a JSON file. Enables direct communication and notif
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | json | Clay populate operation results including response data from Clay webhook |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `authToken` | string | Yes | Auth Token - Enter your Clay Auth token |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `data` | any | data output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/confluence.mdx

@@ -37,7 +37,7 @@ With Confluence, you can:
 - **Integrate with other tools**: Connect with Jira, Trello, and other Atlassian products for seamless workflow integration
 - **Control access permissions**: Manage who can view, edit, or comment on specific content
 
-In Sim Studio, the Confluence integration enables your agents to access and leverage your organization's knowledge base. Agents can retrieve information from Confluence pages, search for specific content, and even update documentation when needed. This allows your workflows to incorporate the collective knowledge stored in your Confluence instance, making it possible to build agents that can reference internal documentation, follow established procedures, and maintain up-to-date information resources as part of their operations.
+In Sim, the Confluence integration enables your agents to access and leverage your organization's knowledge base. Agents can retrieve information from Confluence pages, search for specific content, and even update documentation when needed. This allows your workflows to incorporate the collective knowledge stored in your Confluence instance, making it possible to build agents that can reference internal documentation, follow established procedures, and maintain up-to-date information resources as part of their operations.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -57,19 +57,18 @@ Retrieve content from Confluence pages using the Confluence API.
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Confluence |
 | `domain` | string | Yes | Your Confluence domain \(e.g., yourcompany.atlassian.net\) |
 | `pageId` | string | Yes | Confluence page ID to retrieve |
 | `cloudId` | string | No | Confluence Cloud ID for the instance. If not provided, it will be fetched using the domain. |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `pageId` | string |
-| `content` | string |
-| `title` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `ts` | string | Timestamp of retrieval |
+| `pageId` | string | Confluence page ID |
+| `content` | string | Page content with HTML tags stripped |
+| `title` | string | Page title |
 
 ### `confluence_update`
 
@@ -79,7 +78,6 @@ Update a Confluence page using the Confluence API.
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Confluence |
 | `domain` | string | Yes | Your Confluence domain \(e.g., yourcompany.atlassian.net\) |
 | `pageId` | string | Yes | Confluence page ID to update |
 | `title` | string | No | New title for the page |
@@ -89,37 +87,15 @@ Update a Confluence page using the Confluence API.
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `pageId` | string |
-| `title` | string |
-| `body` | string |
-| `success` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `ts` | string | Timestamp of update |
+| `pageId` | string | Confluence page ID |
+| `title` | string | Updated page title |
+| `success` | boolean | Update operation success status |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `ts` | string | ts output from the block |
-| `pageId` | string | pageId output from the block |
-| `content` | string | content output from the block |
-| `title` | string | title output from the block |
-| `success` | boolean | success output from the block |
-
-
 ## Notes
 
 - Category: `tools`

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

@@ -39,11 +39,11 @@ With a Discord account or bot, you can:
 - **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.
+In Sim, 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.
+Discord components in Sim 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
 
@@ -78,9 +78,10 @@ Send a message to a Discord channel
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `data` | object | Discord message data |
 
 ### `discord_get_messages`
 
@@ -96,9 +97,10 @@ Retrieve messages from a Discord channel
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `messages` | array | Array of Discord messages with full metadata |
 
 ### `discord_get_server`
 
@@ -113,9 +115,10 @@ Retrieve information about a Discord server (guild)
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `data` | object | Discord server \(guild\) information |
 
 ### `discord_get_user`
 
@@ -130,30 +133,13 @@ Retrieve information about a Discord user
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `message` | string | Success or error message |
+| `data` | object | Discord user information |
 
 
 
-## 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`

apps/docs/content/docs/tools/elevenlabs.mdx

@@ -33,7 +33,7 @@ With ElevenLabs, you can:
 - **Control speech parameters**: Adjust stability, clarity, and emotional tone to fine-tune output
 - **Add realistic emotions**: Incorporate natural-sounding emotions like happiness, sadness, or excitement
 
-In Sim Studio, the ElevenLabs integration enables your agents to convert text to lifelike speech, enhancing the interactivity and engagement of your applications. This is particularly valuable for creating voice assistants, generating audio content, developing accessible applications, or building conversational interfaces that feel more human. The integration allows you to seamlessly incorporate ElevenLabs' advanced speech synthesis capabilities into your agent workflows, bridging the gap between text-based AI and natural human communication.
+In Sim, the ElevenLabs integration enables your agents to convert text to lifelike speech, enhancing the interactivity and engagement of your applications. This is particularly valuable for creating voice assistants, generating audio content, developing accessible applications, or building conversational interfaces that feel more human. The integration allows you to seamlessly incorporate ElevenLabs' advanced speech synthesis capabilities into your agent workflows, bridging the gap between text-based AI and natural human communication.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -60,29 +60,12 @@ Convert TTS using ElevenLabs voices
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `audioUrl` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `audioUrl` | string | The URL of the generated audio |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `text` | string | Yes | Text - Enter the text to convert to speech |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `audioUrl` | string | audioUrl output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/exa.mdx

@@ -26,7 +26,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Exa](https://exa.ai/) is an AI-powered search engine designed specifically for developers and researchers that provides highly relevant and up-to-date information from across the web. It combines advanced semantic search capabilities with AI understanding to deliver more accurate and contextually relevant results than traditional search engines.
+[Exa](https://exa.ai/) is an AI-powered search engine designed specifically for developers and researchers, providing highly relevant and up-to-date information from across the web. It combines advanced semantic search capabilities with AI understanding to deliver more accurate and contextually relevant results than traditional search engines.
 
 With Exa, you can:
 
@@ -35,14 +35,16 @@ With Exa, you can:
 - **Access up-to-date information**: Retrieve current information from across the web
 - **Find similar content**: Discover related resources based on content similarity
 - **Extract webpage contents**: Retrieve and process the full text of web pages
+- **Answer questions with citations**: Ask questions and receive direct answers with supporting sources
+- **Perform research tasks**: Automate multi-step research workflows to gather, synthesize, and summarize information
 
-In Sim Studio, the Exa integration allows your agents to search the web for information, retrieve content from specific URLs, and find similar resources - all programmatically through API calls. This enables your agents to access real-time information from the internet, enhancing their ability to provide accurate, current, and relevant responses. The integration is particularly valuable for research tasks, information gathering, content discovery, and answering questions that require up-to-date information from across the web.
+In Sim, the Exa integration allows your agents to search the web for information, retrieve content from specific URLs, find similar resources, answer questions with citations, and conduct research tasks—all programmatically through API calls. This enables your agents to access real-time information from the internet, enhancing their ability to provide accurate, current, and relevant responses. The integration is particularly valuable for research tasks, information gathering, content discovery, and answering questions that require up-to-date information from across the web.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Search the web, retrieve content, find similar links, and answer questions using Exa
+Search the web, retrieve content, find similar links, and answer questions using Exa's powerful AI search capabilities.
 
 
 
@@ -59,22 +61,14 @@ Search the web using Exa AI. Returns relevant search results with titles, URLs,
 | `query` | string | Yes | The search query to execute |
 | `numResults` | number | No | Number of results to return \(default: 10, max: 25\) |
 | `useAutoprompt` | boolean | No | Whether to use autoprompt to improve the query \(default: false\) |
-| `type` | string | No | Search type: neural, keyword, auto or magic \(default: auto\) |
+| `type` | string | No | Search type: neural, keyword, auto or fast \(default: auto\) |
 | `apiKey` | string | Yes | Exa AI API Key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `results` | string |
-| `url` | string |
-| `publishedDate` | string |
-| `author` | string |
-| `summary` | string |
-| `favicon` | string |
-| `image` | string |
-| `text` | string |
-| `score` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Search results with titles, URLs, and text snippets |
 
 ### `exa_get_contents`
 
@@ -91,12 +85,9 @@ Retrieve the contents of webpages using Exa AI. Returns the title, text content,
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `results` | string |
-| `title` | string |
-| `text` | string |
-| `summary` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Retrieved content from URLs with title, text, and summaries |
 
 ### `exa_find_similar_links`
 
@@ -113,12 +104,9 @@ Find webpages similar to a given URL using Exa AI. Returns a list of similar lin
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `similarLinks` | string |
-| `url` | string |
-| `text` | string |
-| `score` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `similarLinks` | array | Similar links found with titles, URLs, and text snippets |
 
 ### `exa_answer`
 
@@ -134,35 +122,30 @@ Get an AI-generated answer to a question with citations from the web using Exa A
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `query` | string |
-| `answer` | string |
-| `citations` | string |
-| `url` | string |
-| `text` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `answer` | string | AI-generated answer to the question |
+| `citations` | array | Sources and citations for the answer |
 
+### `exa_research`
 
+Perform comprehensive research using AI to generate detailed reports with citations
 
-## Block Configuration
+#### Input
 
-### Input
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `query` | string | Yes | Research query or topic |
+| `includeText` | boolean | No | Include full text content in results |
+| `apiKey` | string | Yes | Exa AI API Key |
 
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
+#### Output
 
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `research` | array | Comprehensive research findings with citations and summaries |
 
 
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `results` | json | results output from the block |
-| `similarLinks` | json | similarLinks output from the block |
-| `answer` | string | answer output from the block |
-| `citations` | json | citations output from the block |
-
 
 ## Notes
 

apps/docs/content/docs/tools/file.mdx

@@ -50,7 +50,7 @@ The File Parser tool is particularly useful for scenarios where your agents need
 
 ## Usage Instructions
 
-Upload and extract contents from structured file formats including PDFs, CSV spreadsheets, and Word documents (DOCX). Upload files directly. Specialized parsers extract text and metadata from each format. You can upload multiple files at once and access them individually or as a combined document.
+Upload and extract contents from structured file formats including PDFs, CSV spreadsheets, and Word documents (DOCX). You can either provide a URL to a file or upload files directly. Specialized parsers extract text and metadata from each format. You can upload multiple files at once and access them individually or as a combined document.
 
 
 
@@ -69,28 +69,13 @@ Parse one or more uploaded files or files from URLs (text, PDF, CSV, images, etc
 
 #### Output
 
-This tool does not produce any outputs.
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `files` | array | Array of parsed files |
+| `combinedContent` | string | Combined content of all parsed files |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `inputMethod` | string | No |  |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `files` | json | files output from the block |
-| `combinedContent` | string | combinedContent output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/firecrawl.mdx

@@ -34,9 +34,9 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Firecrawl](https://firecrawl.dev/) is a powerful web scraping and content extraction API that integrates seamlessly into Sim Studio, enabling developers to extract clean, structured content from any website. This integration provides a simple way to transform web pages into usable data formats like Markdown and HTML while preserving the essential content.
+[Firecrawl](https://firecrawl.dev/) is a powerful web scraping and content extraction API that integrates seamlessly into Sim, enabling developers to extract clean, structured content from any website. This integration provides a simple way to transform web pages into usable data formats like Markdown and HTML while preserving the essential content.
 
-With Firecrawl in Sim Studio, you can:
+With Firecrawl in Sim, you can:
 
 - **Extract clean content**: Remove ads, navigation elements, and other distractions to get just the main content
 - **Convert to structured formats**: Transform web pages into Markdown, HTML, or JSON
@@ -44,8 +44,16 @@ With Firecrawl in Sim Studio, you can:
 - **Handle JavaScript-heavy sites**: Process content from modern web applications that rely on JavaScript
 - **Filter content**: Focus on specific parts of a page using CSS selectors
 - **Process at scale**: Handle high-volume scraping needs with a reliable API
+- **Search the web**: Perform intelligent web searches and retrieve structured results
+- **Crawl entire sites**: Crawl multiple pages from a website and aggregate their content
 
-The Firecrawl integration allows your agents to access and process web content programmatically without leaving the Sim Studio environment. This enables scenarios like research, content aggregation, data extraction, and information analysis from across the web. Your agents can gather information from websites, extract structured data, and use that information to make decisions or generate insights - all without having to navigate the complexities of raw HTML parsing or browser automation. Simply configure the Firecrawl block with your API key, provide the target URL, and your agents can immediately begin working with web content in a clean, structured format.
+In Sim, the Firecrawl integration enables your agents to access and process web content programmatically as part of their workflows. Supported operations include:
+
+- **Scrape**: Extract structured content (Markdown, HTML, metadata) from a single web page.
+- **Search**: Search the web for information using Firecrawl's intelligent search capabilities.
+- **Crawl**: Crawl multiple pages from a website, returning structured content and metadata for each page.
+
+This allows your agents to gather information from websites, extract structured data, and use that information to make decisions or generate insights—all without having to navigate the complexities of raw HTML parsing or browser automation. Simply configure the Firecrawl block with your API key, select the operation (Scrape, Search, or Crawl), and provide the relevant parameters. Your agents can immediately begin working with web content in a clean, structured format.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -71,11 +79,11 @@ Extract structured content from web pages with comprehensive metadata support. C
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `markdown` | string |
-| `html` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `markdown` | string | Page content in markdown format |
+| `html` | string | Raw HTML content of the page |
+| `metadata` | object | Page metadata including SEO and Open Graph information |
 
 ### `firecrawl_search`
 
@@ -90,33 +98,30 @@ Search for information on the web using Firecrawl
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `warning` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | array | Search results data |
 
+### `firecrawl_crawl`
 
+Crawl entire websites and extract structured content from all accessible pages
 
-## Block Configuration
+#### Input
 
-### Input
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `url` | string | Yes | The website URL to crawl |
+| `limit` | number | No | Maximum number of pages to crawl \(default: 100\) |
+| `onlyMainContent` | boolean | No | Extract only main content from pages |
+| `apiKey` | string | Yes | Firecrawl API Key |
 
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `apiKey` | string | Yes |  |
+#### Output
 
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `pages` | array | Array of crawled pages with their content and metadata |
 
 
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `markdown` | string | markdown output from the block |
-| `html` | any | html output from the block |
-| `metadata` | json | metadata output from the block |
-| `data` | json | data output from the block |
-| `warning` | any | warning output from the block |
-
 
 ## Notes
 

apps/docs/content/docs/tools/generic_webhook.mdx

@@ -0,0 +1,32 @@
+---
+title: Webhook
+description: Receive webhooks from any service
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="generic_webhook"
+  color="#10B981"
+  icon={true}
+  iconSvg={`<svg className="block-icon"
+      
+      fill='currentColor'
+      
+      
+      viewBox='0 0 24 24'
+      xmlns='http://www.w3.org/2000/svg'
+    >
+      <path d='M17.974 7A4.967 4.967 0 0 0 18 6.5a5.5 5.5 0 1 0-8.672 4.491L7.18 15.114A2.428 2.428 0 0 0 6.496 15 2.5 2.5 0 1 0 9 17.496a2.36 2.36 0 0 0-.93-1.925l2.576-4.943-.41-.241A4.5 4.5 0 1 1 17 6.5a4.8 4.8 0 0 1-.022.452zM6.503 18.999a1.5 1.5 0 1 1 1.496-1.503A1.518 1.518 0 0 1 6.503 19zM18.5 12a5.735 5.735 0 0 0-1.453.157l-2.744-3.941A2.414 2.414 0 0 0 15 6.5a2.544 2.544 0 1 0-1.518 2.284l3.17 4.557.36-.13A4.267 4.267 0 0 1 18.5 13a4.5 4.5 0 1 1-.008 9h-.006a4.684 4.684 0 0 1-3.12-1.355l-.703.71A5.653 5.653 0 0 0 18.49 23h.011a5.5 5.5 0 0 0 0-11zM11 6.5A1.5 1.5 0 1 1 12.5 8 1.509 1.509 0 0 1 11 6.5zM18.5 20a2.5 2.5 0 1 0-2.447-3h-5.05l-.003.497A4.546 4.546 0 0 1 6.5 22 4.526 4.526 0 0 1 2 17.5a4.596 4.596 0 0 1 3.148-4.37l-.296-.954A5.606 5.606 0 0 0 1 17.5 5.532 5.532 0 0 0 6.5 23a5.573 5.573 0 0 0 5.478-5h4.08a2.487 2.487 0 0 0 2.442 2zm0-4a1.5 1.5 0 1 1-1.5 1.5 1.509 1.509 0 0 1 1.5-1.5z' />
+      <path fill='none' d='M0 0h24v24H0z' />
+    </svg>`}
+/>
+
+
+
+
+
+## Notes
+
+- Category: `triggers`
+- Type: `generic_webhook`

apps/docs/content/docs/tools/github.mdx

@@ -1,6 +1,6 @@
 ---
 title: GitHub
-description: Interact with GitHub
+description: Interact with GitHub or trigger workflows from GitHub events
 ---
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
@@ -29,13 +29,13 @@ With GitHub, you can:
 - **Manage projects**: Organize work with project boards, milestones, and task tracking
 - **Document code**: Create and maintain documentation with GitHub Pages and wikis
 
-In Sim Studio, the GitHub integration enables your agents to interact directly with GitHub repositories and workflows. This allows for powerful automation scenarios such as code review assistance, pull request management, issue tracking, and repository exploration. Your agents can fetch repository data, analyze code changes, post comments on pull requests, and perform other GitHub operations programmatically. This integration bridges the gap between your AI workflows and your development processes, enabling seamless collaboration between your agents and your development team.
+In Sim, the GitHub integration enables your agents to interact directly with GitHub repositories and workflows. This allows for powerful automation scenarios such as code review assistance, pull request management, issue tracking, and repository exploration. Your agents can fetch repository data, analyze code changes, post comments on pull requests, and perform other GitHub operations programmatically. This integration bridges the gap between your AI workflows and your development processes, enabling seamless collaboration between your agents and your development team.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Access GitHub repositories, pull requests, and comments through the GitHub API. Automate code reviews, PR management, and repository interactions within your workflow.
+Access GitHub repositories, pull requests, and comments through the GitHub API. Automate code reviews, PR management, and repository interactions within your workflow. Trigger workflows from GitHub events like push, pull requests, and issues.
 
 
 
@@ -56,24 +56,10 @@ Fetch PR details including diff and files changed
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `title` | string |
-| `state` | string |
-| `html_url` | string |
-| `diff_url` | string |
-| `created_at` | string |
-| `updated_at` | string |
-| `files` | string |
-| `additions` | string |
-| `deletions` | string |
-| `changes` | string |
-| `patch` | string |
-| `blob_url` | string |
-| `raw_url` | string |
-| `status` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Human-readable PR summary |
+| `metadata` | object | Detailed PR metadata including file changes |
 
 ### `github_comment`
 
@@ -97,17 +83,10 @@ Create comments on GitHub PRs
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `html_url` | string |
-| `created_at` | string |
-| `updated_at` | string |
-| `path` | string |
-| `line` | string |
-| `side` | string |
-| `commit_id` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Human-readable comment confirmation |
+| `metadata` | object | Comment metadata |
 
 ### `github_repo_info`
 
@@ -123,15 +102,10 @@ Retrieve comprehensive GitHub repository metadata including stars, forks, issues
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `description` | string |
-| `stars` | string |
-| `forks` | string |
-| `openIssues` | string |
-| `language` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Human-readable repository summary |
+| `metadata` | object | Repository metadata |
 
 ### `github_latest_commit`
 
@@ -143,41 +117,18 @@ Retrieve the latest commit from a GitHub repository
 | --------- | ---- | -------- | ----------- |
 | `owner` | string | Yes | Repository owner \(user or organization\) |
 | `repo` | string | Yes | Repository name |
-| `branch` | string | No | Branch name \(defaults to the repository |
+| `branch` | string | No | Branch name \(defaults to the repository's default branch\) |
 | `apiKey` | string | Yes | GitHub API token |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
-| `html_url` | string |
-| `commit_message` | string |
-| `author` | string |
-| `login` | string |
-| `avatar_url` | string |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Human-readable commit summary |
+| `metadata` | object | Commit metadata |
 
 
 
-## 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`

apps/docs/content/docs/tools/gmail.mdx

@@ -1,6 +1,6 @@
 ---
 title: Gmail
-description: Send Gmail
+description: Send Gmail or trigger workflows from Gmail events
 ---
 
 import { BlockInfoCard } from "@/components/ui/block-info-card"
@@ -45,13 +45,13 @@ With Gmail, you can:
 - **Access from anywhere**: Use Gmail across devices with synchronized content and settings
 - **Integrate with other services**: Connect with Google Calendar, Drive, and other productivity tools
 
-In Sim Studio, the Gmail integration enables your agents to send, read, and search emails programmatically. This allows for powerful automation scenarios such as sending notifications, processing incoming messages, extracting information from emails, and managing communication workflows. Your agents can compose and send personalized emails, search for specific messages using Gmail's query syntax, and extract content from emails to use in other parts of your workflow. Coming soon, agents will also be able to listen for new emails in real-time, enabling responsive workflows that can trigger actions based on incoming messages. This integration bridges the gap between your AI workflows and email communications, enabling seamless interaction with one of the world's most widely used communication platforms.
+In Sim, the Gmail integration enables your agents to send, read, and search emails programmatically. This allows for powerful automation scenarios such as sending notifications, processing incoming messages, extracting information from emails, and managing communication workflows. Your agents can compose and send personalized emails, search for specific messages using Gmail's query syntax, and extract content from emails to use in other parts of your workflow. Coming soon, agents will also be able to listen for new emails in real-time, enabling responsive workflows that can trigger actions based on incoming messages. This integration bridges the gap between your AI workflows and email communications, enabling seamless interaction with one of the world's most widely used communication platforms.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Integrate Gmail functionality to send email messages within your workflow. Automate email communications and process email content using OAuth authentication.
+Comprehensive Gmail integration with OAuth authentication. Send email messages, read email content, and trigger workflows from Gmail events like new emails and label changes.
 
 
 
@@ -65,19 +65,18 @@ Send emails using Gmail
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Gmail API |
 | `to` | string | Yes | Recipient email address |
 | `subject` | string | Yes | Email subject |
 | `body` | string | Yes | Email body content |
+| `cc` | string | No | CC recipients \(comma-separated\) |
+| `bcc` | string | No | BCC recipients \(comma-separated\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
-| `threadId` | string |
-| `labelIds` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Success message |
+| `metadata` | object | Email metadata |
 
 ### `gmail_draft`
 
@@ -87,20 +86,18 @@ Draft emails using Gmail
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Gmail API |
 | `to` | string | Yes | Recipient email address |
 | `subject` | string | Yes | Email subject |
 | `body` | string | Yes | Email body content |
+| `cc` | string | No | CC recipients \(comma-separated\) |
+| `bcc` | string | No | BCC recipients \(comma-separated\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
-| `message` | string |
-| `threadId` | string |
-| `labelIds` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Success message |
+| `metadata` | object | Draft metadata |
 
 ### `gmail_read`
 
@@ -110,18 +107,19 @@ Read emails from Gmail
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Gmail API |
 | `messageId` | string | No | ID of the message to read |
 | `folder` | string | No | Folder/label to read emails from |
 | `unreadOnly` | boolean | No | Only retrieve unread messages |
 | `maxResults` | number | No | Maximum number of messages to retrieve \(default: 1, max: 10\) |
+| `includeAttachments` | boolean | No | Download and include email attachments |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Text content of the email |
+| `metadata` | json | Metadata of the email |
+| `attachments` | file[] | Attachments of the email |
 
 ### `gmail_search`
 
@@ -131,37 +129,18 @@ Search emails in Gmail
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | Access token for Gmail API |
 | `query` | string | Yes | Search query for emails |
 | `maxResults` | number | No | Maximum number of results to return |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Search results summary |
+| `metadata` | object | Search metadata |
 
 
 
-## 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`

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

@@ -84,13 +84,13 @@ With Google Calendar, you can:
 - **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.
+In Sim, 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
+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' Google Calendar settings.
 
 
 
@@ -104,7 +104,6 @@ Create a new event in Google Calendar
 
 | 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 |
@@ -117,9 +116,10 @@ Create a new event in Google Calendar
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Event creation confirmation message |
+| `metadata` | json | Created event metadata including ID, status, and details |
 
 ### `google_calendar_list`
 
@@ -129,7 +129,6 @@ List events from Google Calendar
 
 | 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\) |
@@ -138,9 +137,10 @@ List events from Google Calendar
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Summary of found events count |
+| `metadata` | json | List of events with pagination tokens and event details |
 
 ### `google_calendar_get`
 
@@ -150,15 +150,15 @@ Get a specific event from Google Calendar
 
 | 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 |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Event retrieval confirmation message |
+| `metadata` | json | Event details including ID, status, times, and attendees |
 
 ### `google_calendar_quick_add`
 
@@ -168,17 +168,17 @@ Create events from natural language text
 
 | 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.,  |
+| `text` | string | Yes | Natural language text describing the event \(e.g., "Meeting with John tomorrow at 3pm"\) |
 | `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 |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Event creation confirmation message from natural language |
+| `metadata` | json | Created event metadata including parsed details |
 
 ### `google_calendar_invite`
 
@@ -188,7 +188,6 @@ Invite attendees to an existing Google Calendar event
 
 | 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 |
@@ -197,41 +196,13 @@ Invite attendees to an existing Google Calendar event
 
 #### 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 |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Attendee invitation confirmation message with email delivery status |
+| `metadata` | json | Updated event metadata including attendee list and details |
 
 
 
-## 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`

apps/docs/content/docs/tools/google_docs.mdx

@@ -29,37 +29,37 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Google Docs](https://docs.google.com) is a powerful cloud-based document creation and editing service that allows users to create, edit, and collaborate on documents in real-time. As part of Google's productivity suite, Google Docs offers a versatile platform for text documents with robust formatting, commenting, and sharing capabilities.
 
-Learn how to integrate the Google Docs "Read" tool in Sim Studio to effortlessly fetch data from your docs and to integrate into your workflows. This tutorial walks you through connecting Google Docs, setting up data reads, and using that information to automate processes in real-time. Perfect for syncing live data with your agents.
+Learn how to integrate the Google Docs "Read" tool in Sim to effortlessly fetch data from your docs and to integrate into your workflows. This tutorial walks you through connecting Google Docs, setting up data reads, and using that information to automate processes in real-time. Perfect for syncing live data with your agents.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/f41gy9rBHhE"
-  title="Use the Google Docs Read tool in Sim Studio"
+  title="Use the Google Docs Read tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Learn how to integrate the Google Docs "Update" tool in Sim Studio to effortlessly add content in your docs through your workflows. This tutorial walks you through connecting Google Docs, configuring data writes, and using that information to automate document updates seamlessly. Perfect for maintaining dynamic, real-time documentation with minimal effort.
+Learn how to integrate the Google Docs "Update" tool in Sim to effortlessly add content in your docs through your workflows. This tutorial walks you through connecting Google Docs, configuring data writes, and using that information to automate document updates seamlessly. Perfect for maintaining dynamic, real-time documentation with minimal effort.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/L64ROHS2ivA"
-  title="Use the Google Docs Update tool in Sim Studio"
+  title="Use the Google Docs Update tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Learn how to integrate the Google Docs "Create" tool in Sim Studio to effortlessly generate new documents through your workflows. This tutorial walks you through connecting Google Docs, setting up document creation, and using workflow data to populate content automatically. Perfect for streamlining document generation and enhancing productivity.
+Learn how to integrate the Google Docs "Create" tool in Sim to effortlessly generate new documents through your workflows. This tutorial walks you through connecting Google Docs, setting up document creation, and using workflow data to populate content automatically. Perfect for streamlining document generation and enhancing productivity.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/lWpHH4qddWk"
-  title="Use the Google Docs Create tool in Sim Studio"
+  title="Use the Google Docs Create tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -75,7 +75,7 @@ With Google Docs, you can:
 - **Work offline**: Continue working without internet connection with changes syncing when back online
 - **Integrate with other services**: Connect with Google Drive, Sheets, Slides, and third-party applications
 
-In Sim Studio, the Google Docs integration enables your agents to interact directly with document content programmatically. This allows for powerful automation scenarios such as document creation, content extraction, collaborative editing, and document management. Your agents can read existing documents to extract information, write to documents to update content, and create new documents from scratch. This integration bridges the gap between your AI workflows and document management, enabling seamless interaction with one of the world's most widely used document platforms. By connecting Sim Studio with Google Docs, you can automate document workflows, generate reports, extract insights from documents, and maintain documentation - all through your intelligent agents.
+In Sim, the Google Docs integration enables your agents to interact directly with document content programmatically. This allows for powerful automation scenarios such as document creation, content extraction, collaborative editing, and document management. Your agents can read existing documents to extract information, write to documents to update content, and create new documents from scratch. This integration bridges the gap between your AI workflows and document management, enabling seamless interaction with one of the world's most widely used document platforms. By connecting Sim with Google Docs, you can automate document workflows, generate reports, extract insights from documents, and maintain documentation - all through your intelligent agents.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -95,15 +95,14 @@ Read content from a Google Docs document
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Docs API |
 | `documentId` | string | Yes | The ID of the document to read |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | Extracted document text content |
+| `metadata` | json | Document metadata including ID, title, and URL |
 
 ### `google_docs_write`
 
@@ -113,16 +112,15 @@ Write or update content in a Google Docs document
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Docs API |
 | `documentId` | string | Yes | The ID of the document to write to |
 | `content` | string | Yes | The content to write to the document |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedContent` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `updatedContent` | boolean | Indicates if document content was updated successfully |
+| `metadata` | json | Updated document metadata including ID, title, and URL |
 
 ### `google_docs_create`
 
@@ -132,7 +130,6 @@ Create a new Google Docs document
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Docs API |
 | `title` | string | Yes | The title of the document to create |
 | `content` | string | No | The content of the document to create |
 | `folderSelector` | string | No | Select the folder to create the document in |
@@ -140,31 +137,12 @@ Create a new Google Docs document
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `metadata` | json | Created document metadata including ID, title, and URL |
 
 
 
-## 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`

apps/docs/content/docs/tools/google_drive.mdx

@@ -46,13 +46,13 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Google Drive](https://drive.google.com) is Google's cloud storage and file synchronization service that allows users to store files, synchronize files across devices, and share files with others. As a core component of Google's productivity ecosystem, Google Drive offers robust storage, organization, and collaboration capabilities.
 
-Learn how to integrate the Google Drive tool in Sim Studio to effortlessly pull information from your Drive through your workflows. This tutorial walks you through connecting Google Drive, setting up data retrieval, and using stored documents and files to enhance automation. Perfect for syncing important data with your agents in real-time.
+Learn how to integrate the Google Drive tool in Sim to effortlessly pull information from your Drive through your workflows. This tutorial walks you through connecting Google Drive, setting up data retrieval, and using stored documents and files to enhance automation. Perfect for syncing important data with your agents in real-time.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/cRoRr4b-EAs"
-  title="Use the Google Drive tool in Sim Studio"
+  title="Use the Google Drive tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -67,7 +67,7 @@ With Google Drive, you can:
 - **Access across devices**: Use Google Drive on desktop, mobile, and web platforms
 - **Integrate with other services**: Connect with Google Docs, Sheets, Slides, and third-party applications
 
-In Sim Studio, the Google Drive integration enables your agents to interact directly with your cloud storage programmatically. This allows for powerful automation scenarios such as file management, content organization, and document workflows. Your agents can upload new files to specific folders, download existing files to process their contents, and list folder contents to navigate your storage structure. This integration bridges the gap between your AI workflows and your document management system, enabling seamless file operations without manual intervention. By connecting Sim Studio with Google Drive, you can automate file-based workflows, manage documents intelligently, and incorporate cloud storage operations into your agent's capabilities.
+In Sim, the Google Drive integration enables your agents to interact directly with your cloud storage programmatically. This allows for powerful automation scenarios such as file management, content organization, and document workflows. Your agents can upload new files to specific folders, download existing files to process their contents, and list folder contents to navigate your storage structure. This integration bridges the gap between your AI workflows and your document management system, enabling seamless file operations without manual intervention. By connecting Sim with Google Drive, you can automate file-based workflows, manage documents intelligently, and incorporate cloud storage operations into your agent's capabilities.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -87,7 +87,6 @@ Upload a file to Google Drive
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Drive API |
 | `fileName` | string | Yes | The name of the file to upload |
 | `content` | string | Yes | The content of the file to upload |
 | `mimeType` | string | No | The MIME type of the file to upload |
@@ -96,17 +95,9 @@ Upload a file to Google Drive
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `file` | string |
-| `name` | string |
-| `mimeType` | string |
-| `webViewLink` | string |
-| `webContentLink` | string |
-| `size` | string |
-| `createdTime` | string |
-| `modifiedTime` | string |
-| `parents` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `file` | json | Uploaded file metadata including ID, name, and links |
 
 ### `google_drive_create_folder`
 
@@ -116,24 +107,15 @@ Create a new folder in Google Drive
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Drive API |
 | `fileName` | string | Yes | Name of the folder to create |
 | `folderSelector` | string | No | Select the parent folder to create the folder in |
 | `folderId` | string | No | ID of the parent folder \(internal use\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `file` | string |
-| `name` | string |
-| `mimeType` | string |
-| `webViewLink` | string |
-| `webContentLink` | string |
-| `size` | string |
-| `createdTime` | string |
-| `modifiedTime` | string |
-| `parents` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `file` | json | Created folder metadata including ID, name, and parent information |
 
 ### `google_drive_list`
 
@@ -143,7 +125,6 @@ List files and folders in Google Drive
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Drive API |
 | `folderSelector` | string | No | Select the folder to list files from |
 | `folderId` | string | No | The ID of the folder to list files from \(internal use\) |
 | `query` | string | No | A query to filter the files |
@@ -152,38 +133,12 @@ List files and folders in Google Drive
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `files` | string |
-| `name` | string |
-| `mimeType` | string |
-| `webViewLink` | string |
-| `webContentLink` | string |
-| `size` | string |
-| `createdTime` | string |
-| `modifiedTime` | string |
-| `parents` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `files` | json | Array of file metadata objects from the specified folder |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `file` | json | file output from the block |
-| `files` | json | files output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/google_search.mdx

@@ -32,13 +32,13 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Google Search](https://www.google.com) is the world's most widely used search engine, providing access to billions of web pages and information sources. Google Search uses sophisticated algorithms to deliver relevant search results based on user queries, making it an essential tool for finding information on the internet.
 
-Learn how to integrate the Google Search tool in Sim Studio to effortlessly fetch real-time search results through your workflows. This tutorial walks you through connecting Google Search, configuring search queries, and using live data to enhance automation. Perfect for powering your agents with up-to-date information and smarter decision-making.
+Learn how to integrate the Google Search tool in Sim to effortlessly fetch real-time search results through your workflows. This tutorial walks you through connecting Google Search, configuring search queries, and using live data to enhance automation. Perfect for powering your agents with up-to-date information and smarter decision-making.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/1B7hV9b5UMQ"
-  title="Use the Google Search tool in Sim Studio"
+  title="Use the Google Search tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -52,7 +52,7 @@ With Google Search, you can:
 - **Access knowledge graphs**: Get structured information about people, places, and things
 - **Utilize search features**: Take advantage of specialized search tools like calculators, unit converters, and more
 
-In Sim Studio, the Google Search integration enables your agents to search the web programmatically and incorporate search results into their workflows. This allows for powerful automation scenarios such as research, fact-checking, data gathering, and information synthesis. Your agents can formulate search queries, retrieve relevant results, and extract information from those results to make decisions or generate insights. This integration bridges the gap between your AI workflows and the vast information available on the web, enabling your agents to access up-to-date information from across the internet. By connecting Sim Studio with Google Search, you can create agents that stay informed with the latest information, verify facts, conduct research, and provide users with relevant web content - all without leaving your workflow.
+In Sim, the Google Search integration enables your agents to search the web programmatically and incorporate search results into their workflows. This allows for powerful automation scenarios such as research, fact-checking, data gathering, and information synthesis. Your agents can formulate search queries, retrieve relevant results, and extract information from those results to make decisions or generate insights. This integration bridges the gap between your AI workflows and the vast information available on the web, enabling your agents to access up-to-date information from across the internet. By connecting Sim with Google Search, you can create agents that stay informed with the latest information, verify facts, conduct research, and provide users with relevant web content - all without leaving your workflow.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -79,34 +79,12 @@ Search the web with the Custom Search API
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `items` | string |
-| `searchInformation` | string |
-| `searchTime` | string |
-| `formattedSearchTime` | string |
-| `formattedTotalResults` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `items` | array | Array of search results from Google |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `query` | string | Yes | Search Query - Enter your search query |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `items` | json | items output from the block |
-| `searchInformation` | json | searchInformation output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/google_sheets.mdx

@@ -32,49 +32,49 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 {/* MANUAL-CONTENT-START:intro */}
 [Google Sheets](https://sheets.google.com) is a powerful cloud-based spreadsheet application that allows users to create, edit, and collaborate on spreadsheets in real-time. As part of Google's productivity suite, Google Sheets offers a versatile platform for data organization, analysis, and visualization with robust formatting, formula, and sharing capabilities.
 
-Learn how to integrate the Google Sheets "Read" tool in Sim Studio to effortlessly fetch data from your spreadsheets to integrate into your workflows. This tutorial walks you through connecting Google Sheets, setting up data reads, and using that information to automate processes in real-time. Perfect for syncing live data with your agents.
+Learn how to integrate the Google Sheets "Read" tool in Sim to effortlessly fetch data from your spreadsheets to integrate into your workflows. This tutorial walks you through connecting Google Sheets, setting up data reads, and using that information to automate processes in real-time. Perfect for syncing live data with your agents.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/xxP7MZRuq_0"
-  title="Use the Google Sheets Read tool in Sim Studio"
+  title="Use the Google Sheets Read tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Discover how to use the Google Sheets "Write" tool in Sim Studio to automatically send data from your workflows to your Google Sheets. This tutorial covers setting up the integration, configuring write operations, and updating your sheets seamlessly as workflows execute. Perfect for maintaining real-time records without manual input.
+Discover how to use the Google Sheets "Write" tool in Sim to automatically send data from your workflows to your Google Sheets. This tutorial covers setting up the integration, configuring write operations, and updating your sheets seamlessly as workflows execute. Perfect for maintaining real-time records without manual input.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/cO86qTj7qeY"
-  title="Use the Google Sheets Write tool in Sim Studio"
+  title="Use the Google Sheets Write tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Explore how to leverage the Google Sheets "Update" tool in Sim Studio to modify existing entries in your spreadsheets based on workflow execution. This tutorial demonstrates setting up the update logic, mapping data fields, and synchronizing changes instantly. Perfect for keeping your data current and consistent.
+Explore how to leverage the Google Sheets "Update" tool in Sim to modify existing entries in your spreadsheets based on workflow execution. This tutorial demonstrates setting up the update logic, mapping data fields, and synchronizing changes instantly. Perfect for keeping your data current and consistent.
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/95by2fL9yn4"
-  title="Use the Google Sheets Update tool in Sim Studio"
+  title="Use the Google Sheets Update tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
 ></iframe>
 
-Learn how to use the Google Sheets "Append" tool in Sim Studio to effortlessly add new rows of data to your spreadsheets during workflow execution. This tutorial walks you through setting up the integration, configuring append actions, and ensuring smooth data growth. Perfect for expanding records without manual effort!
+Learn how to use the Google Sheets "Append" tool in Sim to effortlessly add new rows of data to your spreadsheets during workflow execution. This tutorial walks you through setting up the integration, configuring append actions, and ensuring smooth data growth. Perfect for expanding records without manual effort!
 
 <iframe
   width="100%"
   height="400"
   src="https://www.youtube.com/embed/8DgNvLBCsAo"
-  title="Use the Google Sheets Append tool in Sim Studio"
+  title="Use the Google Sheets Append tool in Sim"
   frameBorder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
   allowFullScreen
@@ -90,7 +90,7 @@ With Google Sheets, you can:
 - **Work offline**: Continue working without internet connection with changes syncing when back online
 - **Integrate with other services**: Connect with Google Drive, Forms, and third-party applications
 
-In Sim Studio, the Google Sheets integration enables your agents to interact directly with spreadsheet data programmatically. This allows for powerful automation scenarios such as data extraction, analysis, reporting, and management. Your agents can read existing spreadsheets to extract information, write to spreadsheets to update data, and create new spreadsheets from scratch. This integration bridges the gap between your AI workflows and data management, enabling seamless interaction with structured data. By connecting Sim Studio with Google Sheets, you can automate data workflows, generate reports, extract insights from data, and maintain up-to-date information - all through your intelligent agents. The integration supports various data formats and range specifications, making it flexible enough to handle diverse data management needs while maintaining the collaborative and accessible nature of Google Sheets.
+In Sim, the Google Sheets integration enables your agents to interact directly with spreadsheet data programmatically. This allows for powerful automation scenarios such as data extraction, analysis, reporting, and management. Your agents can read existing spreadsheets to extract information, write to spreadsheets to update data, and create new spreadsheets from scratch. This integration bridges the gap between your AI workflows and data management, enabling seamless interaction with structured data. By connecting Sim with Google Sheets, you can automate data workflows, generate reports, extract insights from data, and maintain up-to-date information - all through your intelligent agents. The integration supports various data formats and range specifications, making it flexible enough to handle diverse data management needs while maintaining the collaborative and accessible nature of Google Sheets.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -110,15 +110,15 @@ Read data from a Google Sheets spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Sheets 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 |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | json | Sheet data including range and cell values |
+| `metadata` | json | Spreadsheet metadata including ID and URL |
 
 ### `google_sheets_write`
 
@@ -128,7 +128,6 @@ Write data to a Google Sheets spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Sheets 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 |
@@ -137,15 +136,13 @@ Write data to a Google Sheets spreadsheet
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedRange` | string |
-| `updatedRows` | string |
-| `updatedColumns` | string |
-| `updatedCells` | string |
-| `metadata` | string |
-| `spreadsheetId` | string |
-| `spreadsheetUrl` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `updatedRange` | string | Range of cells that were updated |
+| `updatedRows` | number | Number of rows updated |
+| `updatedColumns` | number | Number of columns updated |
+| `updatedCells` | number | Number of cells updated |
+| `metadata` | json | Spreadsheet metadata including ID and URL |
 
 ### `google_sheets_update`
 
@@ -155,7 +152,6 @@ Update data in a Google Sheets spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Sheets API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet to update |
 | `range` | string | No | The range of cells to update |
 | `values` | array | Yes | The data to update in the spreadsheet |
@@ -164,15 +160,13 @@ Update data in a Google Sheets spreadsheet
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedRange` | string |
-| `updatedRows` | string |
-| `updatedColumns` | string |
-| `updatedCells` | string |
-| `metadata` | string |
-| `spreadsheetId` | string |
-| `spreadsheetUrl` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `updatedRange` | string | Range of cells that were updated |
+| `updatedRows` | number | Number of rows updated |
+| `updatedColumns` | number | Number of columns updated |
+| `updatedCells` | number | Number of cells updated |
+| `metadata` | json | Spreadsheet metadata including ID and URL |
 
 ### `google_sheets_append`
 
@@ -182,7 +176,6 @@ Append data to the end of a Google Sheets spreadsheet
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | The access token for the Google Sheets API |
 | `spreadsheetId` | string | Yes | The ID of the spreadsheet to append to |
 | `range` | string | No | The range of cells to append after |
 | `values` | array | Yes | The data to append to the spreadsheet |
@@ -192,35 +185,17 @@ Append data to the end of a Google Sheets spreadsheet
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `tableRange` | string | Range of the table where data was appended |
+| `updatedRange` | string | Range of cells that were updated |
+| `updatedRows` | number | Number of rows updated |
+| `updatedColumns` | number | Number of columns updated |
+| `updatedCells` | number | Number of cells updated |
+| `metadata` | json | Spreadsheet metadata including ID and URL |
 
 
 
-## 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 |
-| `tableRange` | string | tableRange output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/huggingface.mdx

@@ -60,7 +60,7 @@ Natural language processing: Process and analyze text with specialized NLP model
 Deploy at scale: Host and serve models for production applications
 Customize models: Fine-tune existing models for specific use cases
 
-In Sim Studio, the HuggingFace integration enables your agents to programmatically generate completions using the HuggingFace Inference API. This allows for powerful automation scenarios such as content generation, text analysis, code completion, and creative writing. Your agents can generate completions with natural language prompts, access specialized models for different tasks, and integrate AI-generated content into workflows. This integration bridges the gap between your AI workflows and machine learning capabilities, enabling seamless AI-powered automation with one of the world's most comprehensive ML platforms.
+In Sim, the HuggingFace integration enables your agents to programmatically generate completions using the HuggingFace Inference API. This allows for powerful automation scenarios such as content generation, text analysis, code completion, and creative writing. Your agents can generate completions with natural language prompts, access specialized models for different tasks, and integrate AI-generated content into workflows. This integration bridges the gap between your AI workflows and machine learning capabilities, enabling seamless AI-powered automation with one of the world's most comprehensive ML platforms.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -90,35 +90,13 @@ Generate completions using Hugging Face Inference API
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `model` | string |
-| `usage` | string |
-| `completion_tokens` | string |
-| `total_tokens` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Chat completion results |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `systemPrompt` | string | No | System Prompt - Enter system prompt to guide the model behavior... |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `content` | string | content output from the block |
-| `model` | string | model output from the block |
-| `usage` | json | usage output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/hunter.mdx

@@ -0,0 +1,211 @@
+---
+title: Hunter io
+description: Find and verify professional email addresses
+---
+
+import { BlockInfoCard } from "@/components/ui/block-info-card"
+
+<BlockInfoCard 
+  type="hunter"
+  color="#E0E0E0"
+  icon={true}
+  iconSvg={`<svg className="block-icon"
+      
+      
+      
+      viewBox='0 0 20 19'
+      fill='none'
+      xmlns='http://www.w3.org/2000/svg'
+    >
+      <path
+        d='M12.0671 8.43455C11.6625 8.55094 11.2164 8.55288 10.7992 8.53525C10.3141 8.51472 9.80024 8.45339 9.35223 8.25426C8.98359 8.09047 8.68787 7.79493 8.84262 7.36805C8.95175 7.06699 9.19361 6.79803 9.47319 6.64644C9.78751 6.4759 10.1329 6.50361 10.4474 6.65774C10.8005 6.83082 11.0942 7.11235 11.3604 7.3964C11.5 7.54536 11.6332 7.70002 11.7646 7.85617C11.8252 7.92801 12.2364 8.33865 12.0671 8.43455ZM18.7923 8.58131C18.17 8.43655 17.4348 8.4884 16.811 8.38867C15.8284 8.23146 14.3648 7.08576 13.5714 5.92122C13.0201 5.11202 12.757 4.28785 12.3356 3.28356C12.0415 2.58257 11.4001 0.365389 10.5032 1.40318C10.1339 1.83057 9.7204 3.23752 9.41837 3.2177C9.19467 3.26971 9.15818 2.83371 9.08739 2.64738C8.95886 2.30903 8.89071 1.9176 8.7185 1.59854C8.58086 1.34353 8.40014 1.03806 8.12337 0.91412C7.63027 0.660572 7.03575 1.42476 6.74072 2.33095C6.61457 2.81687 5.76653 3.75879 5.39721 3.9866C3.71684 5.02352 0.344233 6.11595 0.000262184 9.75358C-0.00114142 9.76867 0.000262182 9.81455 0.0573714 9.77323C0.459591 9.48197 5.02183 6.19605 2.09392 12.5476C0.300195 16.439 8.96062 18.917 9.40582 18.9271C9.46582 18.9284 9.46144 18.9011 9.46347 18.8832C10.1546 12.6724 16.9819 13.3262 18.5718 11.8387C20.1474 10.3649 20.1796 8.93816 18.7923 8.58131Z'
+        fill='#FA5320'
+      />
+    </svg>`}
+/>
+
+{/* MANUAL-CONTENT-START:intro */}
+[Hunter.io](https://hunter.io/) is a leading platform for finding and verifying professional email addresses, discovering companies, and enriching contact data. Hunter.io provides robust APIs for domain search, email finding, verification, and company discovery, making it an essential tool for sales, recruiting, and business development.
+
+With Hunter.io, you can:
+
+- **Find email addresses by domain:** Search for all publicly available email addresses associated with a specific company domain.
+- **Discover companies:** Use advanced filters and AI-powered search to find companies matching your criteria.
+- **Find a specific email address:** Locate the most likely email address for a person at a company using their name and domain.
+- **Verify email addresses:** Check the deliverability and validity of any email address.
+- **Enrich company data:** Retrieve detailed information about companies, including size, technologies used, and more.
+
+In Sim, the Hunter.io integration enables your agents to programmatically search for and verify email addresses, discover companies, and enrich contact data using Hunter.io’s API. This allows you to automate lead generation, contact enrichment, and email verification directly within your workflows. Your agents can leverage Hunter.io’s tools to streamline outreach, keep your CRM up-to-date, and power intelligent automation scenarios for sales, recruiting, and more.
+{/* MANUAL-CONTENT-END */}
+
+
+## Usage Instructions
+
+Search for email addresses, verify their deliverability, discover companies, and enrich contact data using Hunter.io's powerful email finding capabilities.
+
+
+
+## Tools
+
+### `hunter_discover`
+
+Returns companies matching a set of criteria using Hunter.io AI-powered search.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `query` | string | No | Natural language search query for companies |
+| `domain` | string | No | Company domain names to filter by |
+| `headcount` | string | No | Company size filter \(e.g., "1-10", "11-50"\) |
+| `company_type` | string | No | Type of organization |
+| `technology` | string | No | Technology used by companies |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Array of companies matching the search criteria, each containing domain, name, headcount, technologies, and email_count |
+
+### `hunter_domain_search`
+
+Returns all the email addresses found using one given domain name, with sources.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `domain` | string | Yes | Domain name to search for email addresses |
+| `limit` | number | No | Maximum email addresses to return \(default: 10\) |
+| `offset` | number | No | Number of email addresses to skip |
+| `type` | string | No | Filter for personal or generic emails |
+| `seniority` | string | No | Filter by seniority level: junior, senior, or executive |
+| `department` | string | No | Filter by specific departments \(e.g., sales, marketing\) |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `domain` | string | The searched domain name |
+| `disposable` | boolean | Whether the domain accepts disposable email addresses |
+| `webmail` | boolean | Whether the domain is a webmail provider |
+| `accept_all` | boolean | Whether the domain accepts all email addresses |
+| `pattern` | string | The email pattern used by the organization |
+| `organization` | string | The organization name |
+| `description` | string | Description of the organization |
+| `industry` | string | Industry of the organization |
+| `twitter` | string | Twitter profile of the organization |
+| `facebook` | string | Facebook profile of the organization |
+| `linkedin` | string | LinkedIn profile of the organization |
+| `instagram` | string | Instagram profile of the organization |
+| `youtube` | string | YouTube channel of the organization |
+| `technologies` | array | Array of technologies used by the organization |
+| `country` | string | Country where the organization is located |
+| `state` | string | State where the organization is located |
+| `city` | string | City where the organization is located |
+| `postal_code` | string | Postal code of the organization |
+| `street` | string | Street address of the organization |
+| `emails` | array | Array of email addresses found for the domain, each containing value, type, confidence, sources, and person details |
+
+### `hunter_email_finder`
+
+Finds the most likely email address for a person given their name and company domain.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `domain` | string | Yes | Company domain name |
+| `first_name` | string | Yes | Person's first name |
+| `last_name` | string | Yes | Person's last name |
+| `company` | string | No | Company name |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `email` | string | The found email address |
+| `score` | number | Confidence score for the found email address |
+| `sources` | array | Array of sources where the email was found, each containing domain, uri, extracted_on, last_seen_on, and still_on_page |
+| `verification` | object | Verification information containing date and status |
+
+### `hunter_email_verifier`
+
+Verifies the deliverability of an email address and provides detailed verification status.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `email` | string | Yes | The email address to verify |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `result` | string | Deliverability result: deliverable, undeliverable, or risky |
+| `score` | number | Confidence score for the verification result |
+| `email` | string | The verified email address |
+| `regexp` | boolean | Whether the email follows a valid regex pattern |
+| `gibberish` | boolean | Whether the email appears to be gibberish |
+| `disposable` | boolean | Whether the email is from a disposable email provider |
+| `webmail` | boolean | Whether the email is from a webmail provider |
+| `mx_records` | boolean | Whether MX records exist for the domain |
+| `smtp_server` | boolean | Whether the SMTP server is reachable |
+| `smtp_check` | boolean | Whether the SMTP check was successful |
+| `accept_all` | boolean | Whether the domain accepts all email addresses |
+| `block` | boolean | Whether the email is blocked |
+| `status` | string | Verification status: valid, invalid, accept_all, webmail, disposable, or unknown |
+| `sources` | array | Array of sources where the email was found |
+
+### `hunter_companies_find`
+
+Enriches company data using domain name.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `domain` | string | Yes | Domain to find company data for |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `person` | object | Person information \(undefined for companies_find tool\) |
+| `company` | object | Company information including name, domain, industry, size, country, linkedin, and twitter |
+
+### `hunter_email_count`
+
+Returns the total number of email addresses found for a domain or company.
+
+#### Input
+
+| Parameter | Type | Required | Description |
+| --------- | ---- | -------- | ----------- |
+| `domain` | string | No | Domain to count emails for \(required if company not provided\) |
+| `company` | string | No | Company name to count emails for \(required if domain not provided\) |
+| `type` | string | No | Filter for personal or generic emails only |
+| `apiKey` | string | Yes | Hunter.io API Key |
+
+#### Output
+
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `total` | number | Total number of email addresses found |
+| `personal_emails` | number | Number of personal email addresses found |
+| `generic_emails` | number | Number of generic email addresses found |
+| `department` | object | Breakdown of email addresses by department \(executive, it, finance, management, sales, legal, support, hr, marketing, communication\) |
+| `seniority` | object | Breakdown of email addresses by seniority level \(junior, senior, executive\) |
+
+
+
+## Notes
+
+- Category: `tools`
+- Type: `hunter`

apps/docs/content/docs/tools/image_generator.mdx

@@ -40,13 +40,13 @@ With DALL-E, you can:
 - **Visualize products**: Generate product mockups and design concepts
 - **Illustrate ideas**: Turn written concepts into visual illustrations
 
-In Sim Studio, the DALL-E integration enables your agents to generate images programmatically as part of their workflows. This allows for powerful automation scenarios such as content creation, visual design, and creative ideation. Your agents can formulate detailed prompts, generate corresponding images, and incorporate these visuals into their outputs or downstream processes. This integration bridges the gap between natural language processing and visual content creation, enabling your agents to communicate not just through text but also through compelling imagery. By connecting Sim Studio with DALL-E, you can create agents that produce visual content on demand, illustrate concepts, generate design assets, and enhance user experiences with rich visual elements - all without requiring human intervention in the creative process.
+In Sim, the DALL-E integration enables your agents to generate images programmatically as part of their workflows. This allows for powerful automation scenarios such as content creation, visual design, and creative ideation. Your agents can formulate detailed prompts, generate corresponding images, and incorporate these visuals into their outputs or downstream processes. This integration bridges the gap between natural language processing and visual content creation, enabling your agents to communicate not just through text but also through compelling imagery. By connecting Sim with DALL-E, you can create agents that produce visual content on demand, illustrate concepts, generate design assets, and enhance user experiences with rich visual elements - all without requiring human intervention in the creative process.
 {/* MANUAL-CONTENT-END */}
 
 
 ## Usage Instructions
 
-Create high-quality images using OpenAI
+Create high-quality images using OpenAI's image generation models. Configure resolution, quality, style, and other parameters to get exactly the image you need.
 
 
 
@@ -71,33 +71,13 @@ Generate images using OpenAI
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
-| `image` | string |
-| `metadata` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Generated image data |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `prompt` | string | Yes |  |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `content` | string | content output from the block |
-| `image` | string | image output from the block |
-| `metadata` | json | metadata output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/index.mdx

@@ -7,7 +7,7 @@ import { Card, Cards } from "fumadocs-ui/components/card";
 import { Step, Steps } from "fumadocs-ui/components/steps";
 import { Tab, Tabs } from "fumadocs-ui/components/tabs";
 
-Tools are powerful components in Sim Studio that allow your workflows to interact with external services, process data, and perform specialized tasks. They extend the capabilities of your agents and workflows by providing access to various APIs and services.
+Tools are powerful components in Sim that allow your workflows to interact with external services, process data, and perform specialized tasks. They extend the capabilities of your agents and workflows by providing access to various APIs and services.
 
 ## What is a Tool?
 
@@ -15,7 +15,7 @@ A tool is a specialized component that provides a specific functionality or inte
 
 ## Using Tools in Workflows
 
-There are two primary ways to use tools in your Sim Studio workflows:
+There are two primary ways to use tools in your Sim workflows:
 
 <Steps>
   <Step>
@@ -43,7 +43,7 @@ Each tool requires specific configuration to function properly. Common configura
 
 ## Available Tools
 
-Sim Studio provides a diverse collection of tools for various purposes, including:
+Sim provides a diverse collection of tools for various purposes, including:
 
 - **AI and Language Processing**: OpenAI, ElevenLabs, Translation services
 - **Search and Research**: Google Search, Tavily, Exa, Perplexity
@@ -64,3 +64,14 @@ Tools typically return structured data that can be processed by subsequent block
 - Status information
 
 Refer to each tool's specific documentation to understand its exact output format.
+
+## YAML Configuration
+
+For detailed YAML workflow configuration and syntax, see the [YAML Workflow Reference](/yaml) documentation. This includes comprehensive guides for:
+
+- **Block Reference Syntax**: How to connect and reference data between blocks
+- **Tool Configuration**: Using tools in both standalone blocks and agent configurations  
+- **Environment Variables**: Secure handling of API keys and credentials
+- **Complete Examples**: Real-world workflow patterns and configurations
+
+For specific tool parameters and configuration options, refer to each tool's individual documentation page.

apps/docs/content/docs/tools/jina.mdx

@@ -45,11 +45,11 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Jina AI](https://jina.ai/) is a powerful content extraction tool that seamlessly integrates with Sim Studio to transform web content into clean, readable text. This integration allows developers to easily incorporate web content processing capabilities into their agentic workflows.
+[Jina AI](https://jina.ai/) is a powerful content extraction tool that seamlessly integrates with Sim to transform web content into clean, readable text. This integration allows developers to easily incorporate web content processing capabilities into their agentic workflows.
 
 Jina AI Reader specializes in extracting the most relevant content from web pages, removing clutter, advertisements, and formatting issues to produce clean, structured text that's optimized for language models and other text processing tasks.
 
-With the Jina AI integration in Sim Studio, you can:
+With the Jina AI integration in Sim, you can:
 
 - **Extract clean content** from any web page by simply providing a URL
 - **Process complex web layouts** into structured, readable text
@@ -63,7 +63,7 @@ This integration is particularly valuable for building agents that need to gathe
 
 ## Usage Instructions
 
-Transform web content into clean, readable text using Jina AI
+Transform web content into clean, readable text using Jina AI's advanced extraction capabilities. Extract meaningful content from websites while preserving important information and optionally gathering links.
 
 
 
@@ -85,29 +85,12 @@ Extract and process web content into clean, LLM-friendly text using Jina AI Read
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `content` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `content` | string | The extracted content from the URL, processed into clean, LLM-friendly text |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `url` | string | Yes | URL - Enter URL to extract content from |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `content` | string | content output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/jira.mdx

@@ -37,7 +37,7 @@ Key features of Jira include:
 - Workflow Automation: Powerful automation rules to streamline repetitive tasks and processes
 - Advanced Search: JQL (Jira Query Language) for complex issue filtering and reporting
 
-In Sim Studio, the Jira 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 create, retrieve, and update Jira issues programmatically, facilitating automated project management tasks and ensuring that important information is properly tracked and documented. By connecting Sim Studio with Jira, you can build intelligent agents that maintain project visibility while automating routine project management tasks, enhancing team productivity and ensuring consistent project tracking.
+In Sim, the Jira 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 create, retrieve, and update Jira issues programmatically, facilitating automated project management tasks and ensuring that important information is properly tracked and documented. By connecting Sim with Jira, 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 */}
 
 
@@ -57,22 +57,17 @@ Retrieve detailed information about a specific Jira issue
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Jira |
 | `domain` | string | Yes | Your Jira domain \(e.g., yourcompany.atlassian.net\) |
-| `projectId` | string | No | Jira project ID to retrieve issues from. If not provided, all issues will be retrieved. |
+| `projectId` | string | No | Jira project ID \(optional; not required to retrieve a single issue\). |
 | `issueKey` | string | Yes | Jira issue key to retrieve \(e.g., PROJ-123\) |
 | `cloudId` | string | No | Jira Cloud ID for the instance. If not provided, it will be fetched using the domain. |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `issueKey` | string |
-| `summary` | string |
-| `description` | string |
-| `created` | string |
-| `updated` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Jira issue details with issue key, summary, description, created and updated timestamps |
 
 ### `jira_update`
 
@@ -82,7 +77,6 @@ Update a Jira issue
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Jira |
 | `domain` | string | Yes | Your Jira domain \(e.g., yourcompany.atlassian.net\) |
 | `projectId` | string | No | Jira project ID to update issues in. If not provided, all issues will be retrieved. |
 | `issueKey` | string | Yes | Jira issue key to update |
@@ -95,12 +89,10 @@ Update a Jira issue
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `issueKey` | string |
-| `summary` | string |
-| `success` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Updated Jira issue details with timestamp, issue key, summary, and success status |
 
 ### `jira_write`
 
@@ -110,7 +102,6 @@ Write a Jira issue
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Jira |
 | `domain` | string | Yes | Your Jira domain \(e.g., yourcompany.atlassian.net\) |
 | `projectId` | string | Yes | Project ID for the issue |
 | `summary` | string | Yes | Summary for the issue |
@@ -118,17 +109,14 @@ Write a Jira issue
 | `priority` | string | No | Priority for the issue |
 | `assignee` | string | No | Assignee for the issue |
 | `cloudId` | string | No | Jira Cloud ID for the instance. If not provided, it will be fetched using the domain. |
-| `issueType` | string | Yes | Type of issue to create \(e.g., Task, Story, Bug, Sub-task\) |
+| `issueType` | string | Yes | Type of issue to create \(e.g., Task, Story\) |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `ts` | string |
-| `issueKey` | string |
-| `summary` | string |
-| `success` | string |
-| `url` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | object | Created Jira issue details with timestamp, issue key, summary, success status, and URL |
 
 ### `jira_bulk_read`
 
@@ -138,43 +126,19 @@ Retrieve multiple Jira issues in bulk
 
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
-| `accessToken` | string | Yes | OAuth access token for Jira |
 | `domain` | string | Yes | Your Jira domain \(e.g., yourcompany.atlassian.net\) |
 | `projectId` | string | Yes | Jira project ID |
 | `cloudId` | string | No | Jira cloud ID |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `issues` | array |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Operation success status |
+| `output` | array | Array of Jira issues with summary, description, created and updated timestamps |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `ts` | string | ts output from the block |
-| `issueKey` | string | issueKey output from the block |
-| `summary` | string | summary output from the block |
-| `description` | string | description output from the block |
-| `created` | string | created output from the block |
-| `updated` | string | updated output from the block |
-| `success` | boolean | success output from the block |
-| `url` | string | url output from the block |
-
-
 ## Notes
 
 - Category: `tools`

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

@@ -31,7 +31,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* 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.
+Sim'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.
 
@@ -43,7 +43,7 @@ Key features of the Knowledge Base include:
 - 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.
+In Sim, 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 */}
 
 
@@ -57,31 +57,22 @@ Perform semantic vector search across knowledge bases, upload individual chunks
 
 ### `knowledge_search`
 
-Search for similar content in one or more knowledge bases using vector similarity
+Search for similar content in a knowledge base 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 |
+| `knowledgeBaseId` | string | Yes | ID of the knowledge base to search in |
+| `query` | string | No | Search query text \(optional when using tag filters\) |
 | `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 |
+| `tagFilters` | any | No | Array of tag filters with tagName and tagValue properties |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `results` | string |
-| `query` | string |
-| `totalResults` | string |
-| `cost` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `results` | array | Array of search results from the knowledge base |
 
 ### `knowledge_upload_chunk`
 
@@ -97,16 +88,9 @@ Upload a new chunk to a document in a knowledge base
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `chunkIndex` | string |
-| `content` | string |
-| `contentLength` | string |
-| `tokenCount` | string |
-| `enabled` | string |
-| `createdAt` | string |
-| `updatedAt` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | object | Information about the uploaded chunk |
 
 ### `knowledge_create_document`
 
@@ -126,35 +110,16 @@ Create a new document in a knowledge base
 | `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 |
+| `documentTagsData` | array | No | Structured tag data with names, types, and values |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | string |
-| `name` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | object | Information about the created document |
 
 
 
-## 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`

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

@@ -36,7 +36,7 @@ Key features of Linear include:
 - 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.
+In Sim, 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 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 */}
 
 
@@ -61,9 +61,9 @@ Fetch and filter issues from Linear
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `issues` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `issues` | array | Array of issues from the specified Linear team and project, each containing id, title, description, state, teamId, and projectId |
 
 ### `linear_create_issue`
 
@@ -80,35 +80,12 @@ Create a new issue in Linear
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `issue` | string |
-| `title` | string |
-| `description` | string |
-| `state` | string |
-| `teamId` | string |
-| `projectId` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `issue` | object | The created issue containing id, title, description, state, teamId, and projectId |
 
 
 
-## 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`

apps/docs/content/docs/tools/linkup.mdx

@@ -28,7 +28,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* MANUAL-CONTENT-START:intro */}
-[Linkup](https://linkup.so) is a powerful web search tool that integrates seamlessly with Sim Studio, allowing your AI agents to access up-to-date information from the web with proper source attribution.
+[Linkup](https://linkup.so) is a powerful web search tool that integrates seamlessly with Sim, allowing your AI agents to access up-to-date information from the web with proper source attribution.
 
 Linkup enhances your AI agents by providing them with the ability to search the web for current information. When integrated into your agent's toolkit:
 
@@ -58,37 +58,19 @@ Search the web for information using Linkup
 | Parameter | Type | Required | Description |
 | --------- | ---- | -------- | ----------- |
 | `q` | string | Yes | The search query |
-| `depth` | string | Yes | Search depth \(has to either be  |
-| `outputType` | string | Yes | Type of output to return \(has to either be  |
+| `depth` | string | Yes | Search depth \(has to either be "standard" or "deep"\) |
+| `outputType` | string | Yes | Type of output to return \(has to either be "sourcedAnswer" or "searchResults"\) |
 | `apiKey` | string | Yes | Enter your Linkup API key |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `answer` | string |
-| `sources` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `answer` | string | The sourced answer to the search query |
+| `sources` | array | Array of sources used to compile the answer, each containing name, url, and snippet |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `q` | string | Yes | Search Query - Enter your search query |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `answer` | string | answer output from the block |
-| `sources` | json | sources output from the block |
-
-
 ## Notes
 
 - Category: `tools`

apps/docs/content/docs/tools/mem0.mdx

@@ -38,7 +38,7 @@ With Mem0, you can:
 - **Implement long-term memory**: Create agents that learn and adapt over time
 - **Scale memory management**: Handle memory needs for multiple users and complex workflows
 
-In Sim Studio, the Mem0 integration enables your agents to maintain persistent memory across workflow executions. This allows for more natural, context-aware interactions where agents can recall past conversations, remember user preferences, and build upon previous interactions. By connecting Sim Studio with Mem0, you can create agents that feel more human-like in their ability to remember and learn from past experiences. The integration supports adding new memories, searching existing memories semantically, and retrieving specific memory records. This memory management capability is essential for building sophisticated agents that can maintain context over time, personalize interactions based on user history, and continuously improve their performance through accumulated knowledge.
+In Sim, the Mem0 integration enables your agents to maintain persistent memory across workflow executions. This allows for more natural, context-aware interactions where agents can recall past conversations, remember user preferences, and build upon previous interactions. By connecting Sim with Mem0, you can create agents that feel more human-like in their ability to remember and learn from past experiences. The integration supports adding new memories, searching existing memories semantically, and retrieving specific memory records. This memory management capability is essential for building sophisticated agents that can maintain context over time, personalize interactions based on user history, and continuously improve their performance through accumulated knowledge.
 {/* MANUAL-CONTENT-END */}
 
 
@@ -64,9 +64,10 @@ Add memories to Mem0 for persistent storage and retrieval
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `ids` | array | Array of memory IDs that were created |
+| `memories` | array | Array of memory objects that were created |
 
 ### `mem0_search_memories`
 
@@ -83,10 +84,10 @@ Search for memories in Mem0 using semantic search
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `searchResults` | string |
-| `ids` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `searchResults` | array | Array of search results with memory data, each containing id, data, and score |
+| `ids` | array | Array of memory IDs found in the search results |
 
 ### `mem0_get_memories`
 
@@ -105,32 +106,13 @@ Retrieve memories from Mem0 by ID or filter criteria
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
-| `ids` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `memories` | array | Array of retrieved memory objects |
+| `ids` | array | Array of memory IDs that were retrieved |
 
 
 
-## Block Configuration
-
-### Input
-
-| Parameter | Type | Required | Description | 
-| --------- | ---- | -------- | ----------- | 
-| `operation` | string | Yes | Operation |
-
-
-
-### Outputs
-
-| Output | Type | Description |
-| ------ | ---- | ----------- |
-| `ids` | any | ids output from the block |
-| `memories` | any | memories output from the block |
-| `searchResults` | any | searchResults output from the block |
-
-
 ## Notes
 
 - Category: `tools`

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

@@ -55,9 +55,11 @@ Add a new memory to the database or append to existing memory with the same ID.
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the memory was added successfully |
+| `memories` | array | Array of memory objects including the new or updated memory |
+| `error` | string | Error message if operation failed |
 
 ### `memory_get`
 
@@ -71,10 +73,12 @@ Retrieve a specific memory by its ID
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `memories` | string |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the memory was retrieved successfully |
+| `memories` | array | Array of memory data for the requested ID |
+| `message` | string | Success or error message |
+| `error` | string | Error message if operation failed |
 
 ### `memory_get_all`
 
@@ -87,10 +91,12 @@ Retrieve all memories from the database
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
-| `memories` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether all memories were retrieved successfully |
+| `memories` | array | Array of all memory objects with keys, types, and data |
+| `message` | string | Success or error message |
+| `error` | string | Error message if operation failed |
 
 ### `memory_delete`
 
@@ -104,30 +110,14 @@ Delete a specific memory by its ID
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `message` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `success` | boolean | Whether the memory was deleted successfully |
+| `message` | string | Success or error message |
+| `error` | string | Error message if operation failed |
 
 
 
-## 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`

apps/docs/content/docs/tools/meta.json

@@ -2,6 +2,7 @@
   "items": [
     "index",
     "airtable",
+    "arxiv",
     "browser_use",
     "clay",
     "confluence",
@@ -10,6 +11,7 @@
     "exa",
     "file",
     "firecrawl",
+    "generic_webhook",
     "github",
     "gmail",
     "google_calendar",
@@ -18,6 +20,7 @@
     "google_search",
     "google_sheets",
     "huggingface",
+    "hunter",
     "image_generator",
     "jina",
     "jira",
@@ -27,16 +30,25 @@
     "mem0",
     "memory",
     "microsoft_excel",
+    "microsoft_planner",
     "microsoft_teams",
     "mistral_parse",
+    "mongodb",
+    "mysql",
     "notion",
+    "onedrive",
     "openai",
     "outlook",
+    "parallel_ai",
     "perplexity",
     "pinecone",
+    "postgresql",
+    "qdrant",
     "reddit",
     "s3",
+    "schedule",
     "serper",
+    "sharepoint",
     "slack",
     "stagehand",
     "stagehand_agent",
@@ -49,8 +61,11 @@
     "typeform",
     "vision",
     "wealthbox",
+    "webhook",
     "whatsapp",
+    "wikipedia",
     "x",
     "youtube"
-  ]
+  ],
+  "defaultOpen": false
 }

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

@@ -78,7 +78,7 @@ import { BlockInfoCard } from "@/components/ui/block-info-card"
 />
 
 {/* 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.
+[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, you can programmatically read, write, and manipulate spreadsheet data to support your workflow automation needs.
 
 With Microsoft Excel integration, you can:
 
@@ -88,7 +88,7 @@ With Microsoft Excel integration, you can:
 - **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.
+In Sim, 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 */}
 
 
@@ -108,15 +108,14 @@ Read data from a Microsoft Excel spreadsheet
 
 | 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 |
+| `range` | string | No | The range of cells to read from. Accepts "SheetName!A1:B2" for explicit ranges or just "SheetName" to read the used range of that sheet. If omitted, reads the used range of the first sheet. |
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `data` | json |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `data` | object | Range data from the spreadsheet |
 
 ### `microsoft_excel_write`
 
@@ -126,7 +125,6 @@ Write data to a Microsoft Excel spreadsheet
 
 | 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 |
@@ -135,15 +133,13 @@ Write data to a Microsoft Excel spreadsheet
 
 #### Output
 
-| Parameter | Type |
-| --------- | ---- |
-| `updatedRange` | string |
-| `updatedRows` | string |
-| `updatedColumns` | string |
-| `updatedCells` | string |
-| `metadata` | string |
-| `spreadsheetId` | string |
-| `spreadsheetUrl` | string |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `updatedRange` | string | The range that was updated |
+| `updatedRows` | number | Number of rows that were updated |
+| `updatedColumns` | number | Number of columns that were updated |
+| `updatedCells` | number | Number of cells that were updated |
+| `metadata` | object | Spreadsheet metadata |
 
 ### `microsoft_excel_table_add`
 
@@ -153,43 +149,20 @@ Add new rows to a Microsoft Excel table
 
 | 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 |
+| Parameter | Type | Description |
+| --------- | ---- | ----------- |
+| `index` | number | Index of the first row that was added |
+| `values` | array | Array of rows that were added to the table |
+| `metadata` | object | Spreadsheet metadata |
 
 
 
-## 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`