Lint

.devcontainer/.bashrc

@@ -1,4 +1,4 @@
-# Sim Development Environment Bashrc
+# Sim Studio 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 specific aliases
+# Sim Studio specific aliases
 alias logs="cd /workspace/apps/sim && tail -f logs/*.log 2>/dev/null || echo 'No log files found'"
 alias sim-start="cd /workspace && bun run dev"
 alias sim-migrate="cd /workspace/apps/sim && bunx drizzle-kit push"
@@ -45,7 +45,7 @@ if [ -z "$SIM_WELCOME_SHOWN" ]; then
   
   echo ""
   echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-  echo "🚀 Welcome to Sim development environment!"
+  echo "🚀 Welcome to Sim Studio development environment!"
   echo ""
   echo "Available commands:"
   echo "  sim-start    - Start all apps in development mode"

.devcontainer/README.md

@@ -1,4 +1,4 @@
-# Sim Development Container
+# Sim Studio 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 Dev Environment",
+  "name": "Sim Studio 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:
-      - "${POSTGRES_PORT:-5432}:5432"
+      - "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 development environment..."
+echo "🔧 Setting up Sim Studio 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 Development Aliases
+# Additional Sim Studio Development Aliases
 alias migrate="cd /workspace/apps/sim && DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio bunx drizzle-kit push"
 alias generate="cd /workspace/apps/sim && bunx drizzle-kit generate"
 alias dev="cd /workspace && bun run dev"
@@ -104,7 +104,7 @@ unset SIM_WELCOME_SHOWN
 
 echo ""
 echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-echo "✅ Sim development environment setup complete!"
+echo "✅ Sim Studio 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
+# Code of Conduct - Sim Studio
 
 ## 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@sim.ai>.
+reported to the community leaders responsible for enforcement at <waleed@simstudio.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
+# Contributing to Sim Studio
 
-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.
+Thank you for your interest in contributing to Sim Studio! Our goal is to provide developers with a powerful, user-friendly platform for building, testing, and optimizing agentic workflows. We welcome contributions in all forms—from bug fixes and design improvements to brand-new features.
 
 > **Project Overview:**  
-> Sim is a monorepo using Turborepo, containing the main application (`apps/sim/`), documentation (`apps/docs/`), and shared packages (`packages/`). The main application is built with Next.js (app router), ReactFlow, Zustand, Shadcn, and Tailwind CSS. Please ensure your contributions follow our best practices for clarity, maintainability, and consistency.
+> Sim Studio is a monorepo 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.
 
 ---
 
@@ -15,6 +15,8 @@ Thank you for your interest in contributing to Sim! Our goal is to provide devel
 - [Commit Message Guidelines](#commit-message-guidelines)
 - [Local Development Setup](#local-development-setup)
 - [Adding New Blocks and Tools](#adding-new-blocks-and-tools)
+- [Local Storage Mode](#local-storage-mode)
+- [Standalone Build](#standalone-build)
 - [License](#license)
 - [Contributor License Agreement (CLA)](#contributor-license-agreement-cla)
 
@@ -55,7 +57,7 @@ We strive to keep our workflow as simple as possible. To contribute:
    ```
 
 7. **Create a Pull Request**  
-   Open a pull request against the `staging` branch on GitHub. Please provide a clear description of the changes and reference any relevant issues (e.g., `fixes #123`).
+   Open a pull request against the `main` branch on GitHub. Please provide a clear description of the changes and reference any relevant issues (e.g., `fixes #123`).
 
 ---
 
@@ -83,7 +85,7 @@ If you discover a bug or have a feature request, please open an issue in our Git
 Before creating a pull request:
 
 - **Ensure Your Branch Is Up-to-Date:**  
-  Rebase your branch onto the latest `staging` branch to prevent merge conflicts.
+  Rebase your branch onto the latest `main` branch to prevent merge conflicts.
 - **Follow the Guidelines:**  
   Make sure your changes are well-tested, follow our coding standards, and include relevant documentation if necessary.
 
@@ -130,7 +132,7 @@ To set up your local development environment:
 
 ### Option 1: Using NPM Package (Simplest)
 
-The easiest way to run Sim locally is using our NPM package:
+The easiest way to run Sim Studio locally is using our NPM package:
 
 ```bash
 npx simstudio
@@ -140,7 +142,7 @@ After running this command, open [http://localhost:3000/](http://localhost:3000/
 
 #### Options
 
-- `-p, --port <port>`: Specify the port to run Sim on (default: 3000)
+- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
 - `--no-pull`: Skip pulling the latest Docker images
 
 #### Requirements
@@ -154,7 +156,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
+# Start Sim Studio
 docker compose -f docker-compose.prod.yml up -d
 ```
 
@@ -162,19 +164,15 @@ Access the application at [http://localhost:3000/](http://localhost:3000/)
 
 #### Using Local Models
 
-To use local models with Sim:
+To use local models with Sim Studio:
 
-1. Install Ollama and pull models:
+1. Pull models using our helper script:
 
 ```bash
-# 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
+./apps/sim/scripts/ollama_docker.sh pull <model_name>
 ```
 
-2. Start Sim with local model support:
+2. Start Sim Studio with local model support:
 
 ```bash
 # With NVIDIA GPU support
@@ -211,14 +209,13 @@ Dev Containers provide a consistent and easy-to-use development environment:
 
 3. **Start Developing:**
 
-   - Run `bun run dev:full` in the terminal or use the `sim-start` alias
-   - This starts both the main application and the realtime socket server
+   - Run `bun run dev` in the terminal or use the `sim-start` alias
    - All dependencies and configurations are automatically set up
    - Your changes will be automatically hot-reloaded
 
 4. **GitHub Codespaces:**
    - This setup also works with GitHub Codespaces if you prefer development in the browser
-   - Just click "Code" → "Codespaces" → "Create codespace on staging"
+   - Just click "Code" → "Codespaces" → "Create codespace on main"
 
 ### Option 4: Manual Setup
 
@@ -249,11 +246,9 @@ If you prefer not to use Docker or Dev Containers:
 4. **Run the Development Server:**
 
    ```bash
-   bun run dev:full
+   bun run dev
    ```
 
-   This command starts both the main application and the realtime socket server required for full functionality.
-
 5. **Make Your Changes and Test Locally.**
 
 ### Email Template Development
@@ -280,7 +275,7 @@ When working on email templates, you can preview them using a local email previe
 
 ## Adding New Blocks and Tools
 
-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.
+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.
 
 ### Where to Add Your Code
 
@@ -305,8 +300,8 @@ In addition, you will need to update the registries:
 
    ```typescript:/apps/sim/blocks/blocks/pinecone.ts
    import { PineconeIcon } from '@/components/icons'
-   import type { BlockConfig } from '@/blocks/types'
-   import type { PineconeResponse } from '@/tools/pinecone/types'
+   import { PineconeResponse } from '@/tools/pinecone/types'
+   import { BlockConfig } from '../types'
 
    export const PineconeBlock: BlockConfig<PineconeResponse> = {
      type: 'pinecone',
@@ -317,58 +312,13 @@ 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: [
-       {
-         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,
-       },
+       // Block configuration options
      ],
-
-     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' },
-     },
    }
    ```
 
@@ -416,8 +366,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 '@/tools/types'
-   import { PineconeParams, PineconeResponse } from '@/tools/pinecone/types'
+   import { ToolConfig, ToolResponse } from '../types'
+   import { PineconeParams, PineconeResponse } from './types'
 
    export const fetchTool: ToolConfig<PineconeParams, PineconeResponse> = {
      id: 'pinecone_fetch', // Follow the {provider}_{tool_name} format
@@ -429,18 +379,7 @@ In addition, you will need to update the registries:
      provider: 'pinecone', // ID of the OAuth provider
 
      params: {
-       parameterName: {
-         type: 'string',
-         required: true,
-         visibility: 'user-or-llm', // Controls parameter visibility
-         description: 'Description of the parameter',
-       },
-       optionalParam: {
-         type: 'string',
-         required: false,
-         visibility: 'user-only',
-         description: 'Optional parameter only user can set',
-       },
+       // Tool parameters
      },
      request: {
        // Request configuration
@@ -448,6 +387,9 @@ In addition, you will need to update the registries:
      transformResponse: async (response: Response) => {
        // Transform response
      },
+     transformError: (error) => {
+       // Handle errors
+     },
    }
    ```
 
@@ -455,7 +397,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 '/@tools/pinecone'
+   import { fetchTool, generateEmbeddingsTool, searchTextTool } from './pinecone'
    // ... other imports
 
    export const tools: Record<string, ToolConfig> = {
@@ -487,57 +429,11 @@ Maintaining consistent naming across the codebase is critical for auto-generatio
 - **Tool Exports:** Should be named `{toolName}Tool` (e.g., `fetchTool`)
 - **Tool IDs:** Should follow the format `{provider}_{tool_name}` (e.g., `pinecone_fetch`)
 
-### Parameter Visibility System
-
-Sim implements a sophisticated parameter visibility system that controls how parameters are exposed to users and LLMs in agent workflows. Each parameter can have one of four visibility levels:
-
-| Visibility  | User Sees | LLM Sees | How It Gets Set                |
-|-------------|-----------|----------|--------------------------------|
-| `user-only` | ✅ Yes     | ❌ No     | User provides in UI            |
-| `user-or-llm` | ✅ Yes     | ✅ Yes    | User provides OR LLM generates |
-| `llm-only`  | ❌ No      | ✅ Yes    | LLM generates only             |
-| `hidden`    | ❌ No      | ❌ No     | Application injects at runtime |
-
-#### Visibility Guidelines
-
-- **`user-or-llm`**: Use for core parameters that can be provided by users or intelligently filled by the LLM (e.g., search queries, email subjects)
-- **`user-only`**: Use for configuration parameters, API keys, and settings that only users should control (e.g., number of results, authentication credentials)
-- **`llm-only`**: Use for computed values that the LLM should handle internally (e.g., dynamic calculations, contextual data)
-- **`hidden`**: Use for system-level parameters injected at runtime (e.g., OAuth tokens, internal identifiers)
-
-#### Example Implementation
-
-```typescript
-params: {
-  query: {
-    type: 'string',
-    required: true,
-    visibility: 'user-or-llm', // User can provide or LLM can generate
-    description: 'Search query to execute',
-  },
-  apiKey: {
-    type: 'string',
-    required: true,
-    visibility: 'user-only', // Only user provides this
-    description: 'API key for authentication',
-  },
-  internalId: {
-    type: 'string',
-    required: false,
-    visibility: 'hidden', // System provides this at runtime
-    description: 'Internal tracking identifier',
-  },
-}
-```
-
-This visibility system ensures clean user interfaces while maintaining full flexibility for LLM-driven workflows.
-
 ### Guidelines & Best Practices
 
-- **Code Style:** Follow the project's Biome configurations. Use meaningful variable names and small, focused functions.
+- **Code Style:** Follow the project's ESLint and Prettier configurations. Use meaningful variable names and small, focused functions.
 - **Documentation:** Clearly document the purpose, inputs, outputs, and any special behavior for your block/tool.
 - **Error Handling:** Implement robust error handling and provide user-friendly error messages.
-- **Parameter Visibility:** Always specify the appropriate visibility level for each parameter to ensure proper UI behavior and LLM integration.
 - **Testing:** Add unit or integration tests to verify your changes when possible.
 - **Commit Changes:** Update all related components and registries, and describe your changes in your pull request.
 
@@ -555,7 +451,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, Inc. ("The Licensor") a perpetual, irrevocable, worldwide, royalty-free, sublicensable right and license to:
+In addition, by submitting your contributions, you grant Sim Studio, 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.
@@ -567,4 +463,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. We truly appreciate your efforts and look forward to collaborating with you!
+Thank you for taking the time to contribute to Sim Studio. We truly appreciate your efforts and look forward to collaborating with you!

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,25 +1,42 @@
-## Summary
-Brief description of what this PR does and why.
+## Description
 
-Fixes #(issue)
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
 
-## Type of Change
-- [ ] Bug fix
-- [ ] New feature  
-- [ ] Breaking change
-- [ ] Documentation
-- [ ] Other: ___________
+Fixes # (issue)
 
-## Testing
-How has this been tested? What should reviewers focus on?
+## Type of change
 
-## Checklist
-- [ ] Code follows project style guidelines
-- [ ] Self-reviewed my changes
-- [ ] Tests added/updated and passing
-- [ ] No new warnings introduced
+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)
 - [ ] I confirm that I have read and agree to the terms outlined in the [Contributor License Agreement (CLA)](./CONTRIBUTING.md#contributor-license-agreement-cla)
 
-## Screenshots/Videos
-<!-- If applicable, add screenshots or videos to help explain your changes -->
-<!-- For UI changes, before/after screenshots are especially helpful -->
+## 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.

.github/SECURITY.md

@@ -8,11 +8,11 @@
 
 ## Reporting a Vulnerability
 
-We take the security of Sim seriously. If you believe you've found a security vulnerability, please follow these steps:
+We take the security of Sim Studio 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@sim.ai with details of the vulnerability.
+2. **Email us directly** at security@simstudio.ai with details of the vulnerability.
 
 3. **Include the following information** in your report:
 

.github/workflows/build.yml

@@ -2,47 +2,22 @@ name: Build and Publish Docker Image
 
 on:
   push:
-    branches: [main, staging]
+    branches: [main]
+    tags: ['v*']
 
 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
@@ -51,11 +26,14 @@ 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' && github.ref == 'refs/heads/main'
+        if: github.event_name != 'pull_request'
         uses: docker/login-action@v3
         with:
           registry: ghcr.io
@@ -68,84 +46,21 @@ jobs:
         with:
           images: ${{ matrix.image }}
           tags: |
-            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 }}
+            type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' }}
+            type=ref,event=pr
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+            type=semver,pattern={{major}}.{{minor}}.{{patch}}
+            type=sha,format=long
 
       - name: Build and push Docker image
         uses: docker/build-push-action@v6
         with:
           context: .
           file: ${{ matrix.dockerfile }}
-          platforms: ${{ matrix.platform }}
-          push: ${{ github.event_name != 'pull_request' && github.ref == 'refs/heads/main' }}
+          platforms: linux/amd64,linux/arm64
+          push: ${{ github.event_name != 'pull_request' }}
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
-          cache-from: type=gha,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
+          cache-from: type=gha
+          cache-to: type=gha,mode=max

.github/workflows/ci.yml

@@ -26,19 +26,19 @@ jobs:
           node-version: latest
 
       - name: Install dependencies
-        run: bun install --frozen-lockfile
+        run: bun install
 
       - name: Run tests with coverage
         env:
           NODE_OPTIONS: '--no-warnings'
-          NEXT_PUBLIC_APP_URL: 'https://www.sim.ai'
+          NEXT_PUBLIC_APP_URL: 'https://www.simstudio.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.sim.ai'
+          NEXT_PUBLIC_APP_URL: 'https://www.simstudio.ai'
           STRIPE_SECRET_KEY: 'dummy_key_for_ci_only'
           STRIPE_WEBHOOK_SECRET: 'dummy_secret_for_ci_only'
           RESEND_API_KEY: 'dummy_key_for_ci_only'
@@ -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 migrate
+        run: bunx drizzle-kit push

.github/workflows/docs-embeddings.yml

@@ -1,38 +0,0 @@
-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/i18n.yml

@@ -1,151 +0,0 @@
-name: 'Auto-translate Documentation'
-
-on:
-  push:
-    branches: [ staging ]
-    paths: 
-      - 'apps/docs/content/docs/en/**'
-      - 'apps/docs/i18n.json'
-  workflow_dispatch: # Allow manual triggers
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  translate:
-    runs-on: ubuntu-latest
-    if: github.actor != 'github-actions[bot]' # Prevent infinite loops
-    
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          fetch-depth: 0
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: latest
-
-      - name: Run Lingo.dev translations
-        env:
-          LINGODOTDEV_API_KEY: ${{ secrets.LINGODOTDEV_API_KEY }}
-        run: |
-          cd apps/docs
-          bunx lingo.dev@latest i18n
-      
-      - name: Check for translation changes
-        id: changes
-        run: |
-          cd apps/docs
-          git config --local user.email "action@github.com"
-          git config --local user.name "GitHub Action"
-          
-          if [ -n "$(git status --porcelain content/docs)" ]; then
-            echo "changes=true" >> $GITHUB_OUTPUT
-          else
-            echo "changes=false" >> $GITHUB_OUTPUT
-          fi
-      
-      - name: Create Pull Request with translations
-        if: steps.changes.outputs.changes == 'true'
-        uses: peter-evans/create-pull-request@v5
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          commit-message: "feat(i18n): update translations"
-          title: "🌐 Auto-update translations"
-          body: |
-            ## Summary
-            Automated translation updates triggered by changes to documentation.
-            
-            This PR was automatically created after content changes were made, updating translations for all supported languages using Lingo.dev AI translation engine.
-            
-            **Original trigger**: ${{ github.event.head_commit.message }}
-            **Commit**: ${{ github.sha }}
-            **Workflow**: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
-            
-            ## Type of Change
-            - [ ] Bug fix
-            - [ ] New feature  
-            - [ ] Breaking change
-            - [x] Documentation
-            - [ ] Other: ___________
-            
-            ## Testing
-            This PR includes automated translations for modified English documentation content:
-            - 🇪🇸 Spanish (es) translations
-            - 🇫🇷 French (fr) translations  
-            - 🇨🇳 Chinese (zh) translations
-            
-            **What reviewers should focus on:**
-            - Verify translated content accuracy and context
-            - Check that all links and references work correctly in translated versions
-            - Ensure formatting, code blocks, and structure are preserved
-            - Validate that technical terms are appropriately translated
-            
-            ## Checklist
-            - [x] Code follows project style guidelines (automated translation)
-            - [x] Self-reviewed my changes (automated process)
-            - [ ] Tests added/updated and passing
-            - [x] No new warnings introduced
-            - [x] I confirm that I have read and agree to the terms outlined in the [Contributor License Agreement (CLA)](./CONTRIBUTING.md#contributor-license-agreement-cla)
-            
-            ## Screenshots/Videos
-            <!-- Translation changes are text-based - no visual changes expected -->
-            <!-- Reviewers should check the documentation site renders correctly for all languages -->
-          branch: auto-translate/staging-merge-${{ github.run_id }}
-          base: staging
-          labels: |
-            i18n
-
-  verify-translations:
-    needs: translate
-    runs-on: ubuntu-latest
-    if: always() # Run even if translation fails
-    
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          ref: staging
-
-      - name: Setup Bun
-        uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: latest
-
-      - name: Install dependencies
-        run: |
-          cd apps/docs
-          bun install
-
-      - name: Build documentation to verify translations
-        run: |
-          cd apps/docs
-          bun run build
-
-      - name: Report translation status
-        run: |
-          cd apps/docs
-          echo "## Translation Status Report" >> $GITHUB_STEP_SUMMARY
-          echo "**Triggered by merge to staging branch**" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          
-          en_count=$(find content/docs/en -name "*.mdx" | wc -l)
-          es_count=$(find content/docs/es -name "*.mdx" 2>/dev/null | wc -l || echo 0)
-          fr_count=$(find content/docs/fr -name "*.mdx" 2>/dev/null | wc -l || echo 0)
-          zh_count=$(find content/docs/zh -name "*.mdx" 2>/dev/null | wc -l || echo 0)
-          
-          es_percentage=$((es_count * 100 / en_count))
-          fr_percentage=$((fr_count * 100 / en_count))
-          zh_percentage=$((zh_count * 100 / en_count))
-          
-          echo "### Coverage Statistics" >> $GITHUB_STEP_SUMMARY
-          echo "- **🇬🇧 English**: $en_count files (source)" >> $GITHUB_STEP_SUMMARY
-          echo "- **🇪🇸 Spanish**: $es_count/$en_count files ($es_percentage%)" >> $GITHUB_STEP_SUMMARY
-          echo "- **🇫🇷 French**: $fr_count/$en_count files ($fr_percentage%)" >> $GITHUB_STEP_SUMMARY
-          echo "- **🇨🇳 Chinese**: $zh_count/$en_count files ($zh_percentage%)" >> $GITHUB_STEP_SUMMARY
-          echo "" >> $GITHUB_STEP_SUMMARY
-          echo "🔄 **Auto-translation PR**: Check for new pull request with updated translations" >> $GITHUB_STEP_SUMMARY

.github/workflows/trigger-deploy.yml

@@ -1,44 +0,0 @@
-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,8 +65,4 @@ start-collector.sh
 .turbo
 
 # VSCode
-.vscode
-
-## Helm Chart Tests
-helm/sim/test
-i18n.cache
+.vscode

.husky/pre-commit

@@ -1 +1 @@
-bunx lint-staged
+bun lint

NOTICE

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

README.md

@@ -1,46 +1,50 @@
 <p align="center">
-  <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>
+  <img src="apps/sim/public/static/sim.png" alt="Sim Studio Logo" width="500"/>
 </p>
 
 <p align="center">
-  <img src="apps/sim/public/static/demo.gif" alt="Sim Demo" width="800"/>
+  <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>
 </p>
 
-## Quickstart
+<p align="center">
+  <strong>Sim Studio</strong> is a lightweight, user-friendly platform for building AI agent workflows.
+</p>
 
-### Cloud-hosted: [sim.ai](https://sim.ai)
+<p align="center">
+  <img src="apps/sim/public/static/demo.gif" alt="Sim Studio Demo" width="800"/>
+</p>
 
-<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>
+## Getting Started
 
-### Self-hosted: NPM Package
+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):
 
 ```bash
 npx simstudio
 ```
-→ http://localhost:3000
 
-#### Note
-Docker must be installed and running on your machine.
+After running these commands, open [http://localhost:3000/](http://localhost:3000/) in your browser.
 
 #### Options
 
-| Flag | Description |
-|------|-------------|
-| `-p, --port <port>` | Port to run Sim on (default `3000`) |
-| `--no-pull` | Skip pulling latest Docker images |
+- `-p, --port <port>`: Specify the port to run Sim Studio on (default: 3000)
+- `--no-pull`: Skip pulling the latest Docker images
 
-### Self-hosted: Docker Compose
+#### Requirements
+
+- Docker must be installed and running on your machine
+
+### Option 2: Docker Compose
 
 ```bash
 # Clone the repository
@@ -49,43 +53,42 @@ git clone https://github.com/simstudioai/sim.git
 # Navigate to the project directory
 cd sim
 
-# Start Sim
+# Start Sim Studio
 docker compose -f docker-compose.prod.yml up -d
 ```
 
 Access the application at [http://localhost:3000/](http://localhost:3000/)
 
-#### Using Local Models with Ollama
+#### Using Local Models
 
-Run Sim with local AI models using [Ollama](https://ollama.ai) - no external APIs required:
+To use local models with Sim Studio:
+
+1. Pull models using our helper script:
 
 ```bash
-# 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
+./apps/sim/scripts/ollama_docker.sh pull <model_name>
 ```
 
-Wait for the model to download, then visit [http://localhost:3000](http://localhost:3000). Add more models with:
+2. Start Sim Studio with local model support:
+
 ```bash
-docker compose -f docker-compose.ollama.yml exec ollama ollama pull llama3.1:8b
+# 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
 ```
 
-### Self-hosted: Dev Containers
+### Option 3: 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
 
-### 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.
+### Option 4: Manual Setup
 
 1. Clone and install dependencies:
 
@@ -95,71 +98,38 @@ cd sim
 bun install
 ```
 
-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:
+2. Set up environment:
 
 ```bash
 cd apps/sim
 cp .env.example .env  # Configure with required variables (DATABASE_URL, BETTER_AUTH_SECRET, BETTER_AUTH_URL)
 ```
 
-Update your `.env` file with the database URL:
-```bash
-DATABASE_URL="postgresql://postgres:your_password@localhost:5432/simstudio"
-```
-
-4. Set up the database:
+3. Set up the database:
 
 ```bash
-bunx drizzle-kit migrate 
+bunx drizzle-kit push
 ```
 
-5. Start the development servers:
+4. Start the development servers:
 
-**Recommended approach - run both servers together (from project root):**
+Next.js app:
 
-```bash
-bun run dev:full
-```
-
-This starts both the main Next.js application and the realtime socket server required for full functionality.
-
-**Alternative - run servers separately:**
-
-Next.js app (from project root):
 ```bash
 bun run dev
 ```
 
-Realtime socket server (from `apps/sim` directory in a separate terminal):
+Start the realtime server:
+
 ```bash
-cd apps/sim
 bun run dev:sockets
 ```
 
-## Copilot API Keys
+Run both together (recommended):
 
-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
+```bash
+bun run dev:full
+```
 
 ## Tech Stack
 
@@ -173,8 +143,6 @@ Copilot is a Sim-managed service. To use Copilot on a self-hosted instance:
 - **Docs**: [Fumadocs](https://fumadocs.vercel.app/)
 - **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
 
@@ -184,4 +152,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 Team</p>
+<p align="center">Made with ❤️ by the Sim Studio Team</p>

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

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

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

@@ -0,0 +1,58 @@
+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'
+
+export default async function Page(props: { params: Promise<{ slug?: string[] }> }) {
+  const params = await props.params
+  const page = source.getPage(params.slug)
+  if (!page) notFound()
+
+  const MDX = page.data.body
+
+  return (
+    <DocsPage
+      toc={page.data.toc}
+      full={page.data.full}
+      tableOfContent={{
+        style: 'clerk',
+        enabled: true,
+        header: <div className='mb-2 font-medium text-sm'>On this page</div>,
+        single: false,
+      }}
+      article={{
+        className: 'scroll-smooth max-sm:pb-16',
+      }}
+      tableOfContentPopover={{
+        style: 'clerk',
+        enabled: true,
+      }}
+      footer={{
+        enabled: false,
+      }}
+    >
+      <DocsTitle>{page.data.title}</DocsTitle>
+      <DocsDescription>{page.data.description}</DocsDescription>
+      <DocsBody>
+        <MDX components={mdxComponents} />
+      </DocsBody>
+    </DocsPage>
+  )
+}
+
+export async function generateStaticParams() {
+  return source.generateParams()
+}
+
+export async function generateMetadata(props: { params: Promise<{ slug?: string[] }> }) {
+  const params = await props.params
+  const page = source.getPage(params.slug)
+  if (!page) notFound()
+
+  return {
+    title: page.data.title,
+    description: page.data.description,
+  }
+}

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

@@ -0,0 +1,46 @@
+import type { ReactNode } from 'react'
+import { DocsLayout } from 'fumadocs-ui/layouts/docs'
+import { ExternalLink, GithubIcon } from 'lucide-react'
+import Link from 'next/link'
+import { source } from '@/lib/source'
+
+const GitHubLink = () => (
+  <div className='fixed right-4 bottom-4 z-50'>
+    <Link
+      href='https://github.com/simstudioai/sim'
+      target='_blank'
+      rel='noopener noreferrer'
+      className='flex h-8 w-8 items-center justify-center rounded-full border border-border bg-background transition-colors hover:bg-muted'
+    >
+      <GithubIcon className='h-4 w-4' />
+    </Link>
+  </div>
+)
+
+export default function Layout({ children }: { children: ReactNode }) {
+  return (
+    <>
+      <DocsLayout
+        tree={source.pageTree}
+        nav={{
+          title: <div className='flex items-center font-medium'>Sim Studio</div>,
+        }}
+        links={[
+          {
+            text: 'Visit Sim Studio',
+            url: 'https://simstudio.ai',
+            icon: <ExternalLink className='h-4 w-4' />,
+          },
+        ]}
+        sidebar={{
+          defaultOpenLevel: 1,
+          collapsible: true,
+          footer: null,
+        }}
+      >
+        {children}
+      </DocsLayout>
+      <GitHubLink />
+    </>
+  )
+}

apps/docs/app/[lang]/[[...slug]]/page.tsx

@@ -1,161 +0,0 @@
-import { findNeighbour } from 'fumadocs-core/server'
-import defaultMdxComponents from 'fumadocs-ui/mdx'
-import { DocsBody, DocsDescription, DocsPage, DocsTitle } from 'fumadocs-ui/page'
-import { ChevronLeft, ChevronRight } from 'lucide-react'
-import Link from 'next/link'
-import { notFound } from 'next/navigation'
-import { StructuredData } from '@/components/structured-data'
-import { source } from '@/lib/source'
-
-export const dynamic = 'force-dynamic'
-
-export default async function Page(props: { params: Promise<{ slug?: string[]; lang: string }> }) {
-  const params = await props.params
-  const page = source.getPage(params.slug, params.lang)
-  if (!page) notFound()
-
-  const MDX = page.data.body
-  const baseUrl = 'https://docs.sim.ai'
-
-  const pageTreeRecord = source.pageTree as Record<string, any>
-  const pageTree =
-    pageTreeRecord[params.lang] ?? pageTreeRecord.en ?? Object.values(pageTreeRecord)[0]
-  const neighbours = pageTree ? findNeighbour(pageTree, page.url) : null
-
-  const CustomFooter = () => (
-    <div className='mt-12 flex items-center justify-between border-border border-t py-8'>
-      {neighbours?.previous ? (
-        <Link
-          href={neighbours.previous.url}
-          className='group flex items-center gap-2 text-muted-foreground transition-colors hover:text-foreground'
-        >
-          <ChevronLeft className='group-hover:-translate-x-1 h-4 w-4 transition-transform' />
-          <span className='font-medium'>{neighbours.previous.name}</span>
-        </Link>
-      ) : (
-        <div />
-      )}
-
-      {neighbours?.next ? (
-        <Link
-          href={neighbours.next.url}
-          className='group flex items-center gap-2 text-muted-foreground transition-colors hover:text-foreground'
-        >
-          <span className='font-medium'>{neighbours.next.name}</span>
-          <ChevronRight className='h-4 w-4 transition-transform group-hover:translate-x-1' />
-        </Link>
-      ) : (
-        <div />
-      )}
-    </div>
-  )
-
-  return (
-    <>
-      <StructuredData
-        title={page.data.title}
-        description={page.data.description || ''}
-        url={`${baseUrl}${page.url}`}
-        lang={params.lang}
-      />
-      <DocsPage
-        toc={page.data.toc}
-        full={page.data.full}
-        tableOfContent={{
-          style: 'clerk',
-          enabled: true,
-          header: <div className='mb-2 font-medium text-sm'>On this page</div>,
-          single: false,
-        }}
-        article={{
-          className: 'scroll-smooth max-sm:pb-16',
-        }}
-        tableOfContentPopover={{
-          style: 'clerk',
-          enabled: true,
-        }}
-        footer={{
-          enabled: true,
-          component: <CustomFooter />,
-        }}
-      >
-        <DocsTitle>{page.data.title}</DocsTitle>
-        <DocsDescription>{page.data.description}</DocsDescription>
-        <DocsBody>
-          <MDX components={defaultMdxComponents} />
-        </DocsBody>
-      </DocsPage>
-    </>
-  )
-}
-
-export async function generateStaticParams() {
-  return source.generateParams()
-}
-
-export async function generateMetadata(props: {
-  params: Promise<{ slug?: string[]; lang: string }>
-}) {
-  const params = await props.params
-  const page = source.getPage(params.slug, params.lang)
-  if (!page) notFound()
-
-  const baseUrl = 'https://docs.sim.ai'
-  const fullUrl = `${baseUrl}${page.url}`
-
-  return {
-    title: page.data.title,
-    description:
-      page.data.description || 'Sim visual workflow builder for AI applications documentation',
-    keywords: [
-      'AI workflow builder',
-      'visual workflow editor',
-      'AI automation',
-      'workflow automation',
-      'AI agents',
-      'no-code AI',
-      'drag and drop workflows',
-      page.data.title?.toLowerCase().split(' '),
-    ]
-      .flat()
-      .filter(Boolean),
-    authors: [{ name: 'Sim Team' }],
-    category: 'Developer Tools',
-    openGraph: {
-      title: page.data.title,
-      description:
-        page.data.description || 'Sim visual workflow builder for AI applications documentation',
-      url: fullUrl,
-      siteName: 'Sim Documentation',
-      type: 'article',
-      locale: params.lang,
-      alternateLocale: ['en', 'fr', 'zh'].filter((lang) => lang !== params.lang),
-    },
-    twitter: {
-      card: 'summary',
-      title: page.data.title,
-      description:
-        page.data.description || 'Sim visual workflow builder for AI applications documentation',
-    },
-    robots: {
-      index: true,
-      follow: true,
-      googleBot: {
-        index: true,
-        follow: true,
-        'max-video-preview': -1,
-        'max-image-preview': 'large',
-        'max-snippet': -1,
-      },
-    },
-    canonical: fullUrl,
-    alternates: {
-      canonical: fullUrl,
-      languages: {
-        en: `${baseUrl}/en${page.url.replace(`/${params.lang}`, '')}`,
-        fr: `${baseUrl}/fr${page.url.replace(`/${params.lang}`, '')}`,
-        zh: `${baseUrl}/zh${page.url.replace(`/${params.lang}`, '')}`,
-      },
-    },
-  }
-}

apps/docs/app/[lang]/layout.tsx

@@ -1,99 +0,0 @@
-import type { ReactNode } from 'react'
-import { defineI18nUI } from 'fumadocs-ui/i18n'
-import { DocsLayout } from 'fumadocs-ui/layouts/docs'
-import { RootProvider } from 'fumadocs-ui/provider'
-import { ExternalLink, GithubIcon } from 'lucide-react'
-import { Inter } from 'next/font/google'
-import Image from 'next/image'
-import Link from 'next/link'
-import { LanguageDropdown } from '@/components/ui/language-dropdown'
-import { i18n } from '@/lib/i18n'
-import { source } from '@/lib/source'
-import '../global.css'
-import { Analytics } from '@vercel/analytics/next'
-
-const inter = Inter({
-  subsets: ['latin'],
-})
-
-const { provider } = defineI18nUI(i18n, {
-  translations: {
-    en: {
-      displayName: 'English',
-    },
-    es: {
-      displayName: 'Español',
-    },
-    fr: {
-      displayName: 'Français',
-    },
-    zh: {
-      displayName: '简体中文',
-    },
-  },
-})
-
-const GitHubLink = () => (
-  <div className='fixed right-4 bottom-4 z-50'>
-    <Link
-      href='https://github.com/simstudioai/sim'
-      target='_blank'
-      rel='noopener noreferrer'
-      className='flex h-8 w-8 items-center justify-center rounded-full border border-border bg-background transition-colors hover:bg-muted'
-    >
-      <GithubIcon className='h-4 w-4' />
-    </Link>
-  </div>
-)
-
-type LayoutProps = {
-  children: ReactNode
-  params: Promise<{ lang: string }>
-}
-
-export default async function Layout({ children, params }: LayoutProps) {
-  const { lang } = await params
-
-  return (
-    <html lang={lang} className={inter.className} suppressHydrationWarning>
-      <body className='flex min-h-screen flex-col'>
-        <RootProvider i18n={provider(lang)}>
-          <DocsLayout
-            tree={source.pageTree[lang]}
-            nav={{
-              title: (
-                <div className='flex items-center gap-3'>
-                  <Image
-                    src='/static/logo.png'
-                    alt='Sim'
-                    width={60}
-                    height={24}
-                    className='h-6 w-auto'
-                  />
-                  <LanguageDropdown />
-                </div>
-              ),
-            }}
-            links={[
-              {
-                text: 'Visit Sim',
-                url: 'https://sim.ai',
-                icon: <ExternalLink className='h-4 w-4' />,
-              },
-            ]}
-            sidebar={{
-              defaultOpenLevel: 0,
-              collapsible: true,
-              footer: null,
-              banner: null,
-            }}
-          >
-            {children}
-          </DocsLayout>
-          <GitHubLink />
-          <Analytics />
-        </RootProvider>
-      </body>
-    </html>
-  )
-}

apps/docs/app/global.css

@@ -1,153 +1,8 @@
 @import "tailwindcss";
 @import "fumadocs-ui/css/neutral.css";
 @import "fumadocs-ui/css/preset.css";
-
-@theme {
-  --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);
-  }
+  --color-fd-primary: #802fff; /* Purple from control-bar component */
 }
 
 /* Custom text highlighting styles */
@@ -160,26 +15,4 @@
   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}';
-@source '../content/**/*.{js,ts,jsx,tsx,mdx}';
-@source '../mdx-components.tsx';
 @source '../node_modules/fumadocs-ui/dist/**/*.js';

apps/docs/app/layout.tsx

@@ -1,32 +1,30 @@
 import type { ReactNode } from 'react'
+import { RootProvider } from 'fumadocs-ui/provider'
+import { Inter } from 'next/font/google'
+import './global.css'
+import { Analytics } from '@vercel/analytics/next'
 
-export default function RootLayout({ children }: { children: ReactNode }) {
-  return children
+const inter = Inter({
+  subsets: ['latin'],
+})
+
+export default function Layout({ children }: { children: ReactNode }) {
+  return (
+    <html lang='en' className={inter.className} suppressHydrationWarning>
+      <body className='flex min-h-screen flex-col'>
+        <RootProvider>
+          {children}
+          <Analytics />
+        </RootProvider>
+      </body>
+    </html>
+  )
 }
 
 export const metadata = {
-  metadataBase: new URL('https://docs.sim.ai'),
-  title: {
-    default: 'Sim Documentation - Visual Workflow Builder for AI Applications',
-    template: '%s',
-  },
+  title: 'Sim Studio',
   description:
-    'Comprehensive documentation for Sim - the visual workflow builder for AI applications. Create powerful AI agents, automation workflows, and data processing pipelines by connecting blocks on a canvas—no coding required.',
-  keywords: [
-    'AI workflow builder',
-    'visual workflow editor',
-    'AI automation',
-    'workflow automation',
-    'AI agents',
-    'no-code AI',
-    'drag and drop workflows',
-    'AI integrations',
-    'workflow canvas',
-    'AI development platform',
-  ],
-  authors: [{ name: 'Sim Team', url: 'https://sim.ai' }],
-  category: 'Developer Tools',
-  classification: 'Developer Documentation',
+    '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',
   icons: {
     icon: [
@@ -39,42 +37,6 @@ export const metadata = {
   appleWebApp: {
     capable: true,
     statusBarStyle: 'default',
-    title: 'Sim Docs',
-  },
-  openGraph: {
-    type: 'website',
-    locale: 'en_US',
-    alternateLocale: ['fr_FR', 'zh_CN'],
-    url: 'https://docs.sim.ai',
-    siteName: 'Sim Documentation',
-    title: 'Sim Documentation - Visual Workflow Builder for AI Applications',
-    description:
-      'Comprehensive documentation for Sim - the visual workflow builder for AI applications. Create powerful AI agents, automation workflows, and data processing pipelines.',
-  },
-  twitter: {
-    card: 'summary',
-    title: 'Sim Documentation - Visual Workflow Builder for AI Applications',
-    description:
-      'Comprehensive documentation for Sim - the visual workflow builder for AI applications.',
-    creator: '@sim_ai',
-  },
-  robots: {
-    index: true,
-    follow: true,
-    googleBot: {
-      index: true,
-      follow: true,
-      'max-video-preview': -1,
-      'max-image-preview': 'large',
-      'max-snippet': -1,
-    },
-  },
-  alternates: {
-    canonical: 'https://docs.sim.ai',
-    languages: {
-      en: '/en',
-      fr: '/fr',
-      zh: '/zh',
-    },
+    title: 'Sim Studio Docs',
   },
 }

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

@@ -1,6 +1,7 @@
 import { getLLMText } from '@/lib/llms'
 import { source } from '@/lib/source'
 
+// cached forever
 export const revalidate = false
 
 export async function GET() {

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

@@ -1,58 +0,0 @@
-export const revalidate = false
-
-export async function GET() {
-  const baseUrl = 'https://docs.sim.ai'
-
-  const robotsTxt = `# Robots.txt for Sim Documentation
-# Generated on ${new Date().toISOString()}
-
-User-agent: *
-Allow: /
-
-# Allow all well-behaved crawlers
-User-agent: Googlebot
-Allow: /
-
-User-agent: Bingbot
-Allow: /
-
-# AI and LLM crawlers
-User-agent: GPTBot
-Allow: /
-
-User-agent: ChatGPT-User
-Allow: /
-
-User-agent: CCBot
-Allow: /
-
-User-agent: anthropic-ai
-Allow: /
-
-User-agent: Claude-Web
-Allow: /
-
-# Disallow admin and internal paths (if any exist)
-Disallow: /.next/
-Disallow: /api/internal/
-Disallow: /_next/static/
-Disallow: /admin/
-
-# Allow but don't prioritize these
-Allow: /api/search
-Allow: /llms.txt
-Allow: /llms.mdx/
-
-# Sitemaps
-Sitemap: ${baseUrl}/sitemap.xml
-
-# Additional resources for AI indexing
-# See https://github.com/AnswerDotAI/llms-txt for more info
-# LLM-friendly content available at: ${baseUrl}/llms.txt`
-
-  return new Response(robotsTxt, {
-    headers: {
-      'Content-Type': 'text/plain',
-    },
-  })
-}

apps/docs/app/sitemap.xml/route.ts

@@ -1,54 +0,0 @@
-import { i18n } from '@/lib/i18n'
-import { source } from '@/lib/source'
-
-export const revalidate = false
-
-export async function GET() {
-  const baseUrl = 'https://docs.sim.ai'
-
-  const allPages = source.getPages()
-
-  const urls = allPages
-    .flatMap((page) => {
-      const urlWithoutLang = page.url.replace(/^\/[a-z]{2}\//, '/')
-
-      return i18n.languages.map((lang) => {
-        const url =
-          lang === i18n.defaultLanguage
-            ? `${baseUrl}${urlWithoutLang}`
-            : `${baseUrl}/${lang}${urlWithoutLang}`
-
-        return `  <url>
-    <loc>${url}</loc>
-    <lastmod>${new Date().toISOString().split('T')[0]}</lastmod>
-    <changefreq>weekly</changefreq>
-    <priority>${urlWithoutLang === '/introduction' ? '1.0' : '0.8'}</priority>
-    ${i18n.languages.length > 1 ? generateAlternateLinks(baseUrl, urlWithoutLang) : ''}
-  </url>`
-      })
-    })
-    .join('\n')
-
-  const sitemap = `<?xml version="1.0" encoding="UTF-8"?>
-<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml">
-${urls}
-</urlset>`
-
-  return new Response(sitemap, {
-    headers: {
-      'Content-Type': 'application/xml',
-    },
-  })
-}
-
-function generateAlternateLinks(baseUrl: string, urlWithoutLang: string): string {
-  return i18n.languages
-    .map((lang) => {
-      const url =
-        lang === i18n.defaultLanguage
-          ? `${baseUrl}${urlWithoutLang}`
-          : `${baseUrl}/${lang}${urlWithoutLang}`
-      return `    <xhtml:link rel="alternate" hreflang="${lang}" href="${url}" />`
-    })
-    .join('\n')
-}

apps/docs/components/icons.tsx

@@ -270,26 +270,3 @@ export const ResponseIcon = (props: SVGProps<SVGSVGElement>) => (
     <path d='m9 17-5-5 5-5' />
   </svg>
 )
-
-export const StarterIcon = (props: SVGProps<SVGSVGElement>) => (
-  <svg viewBox='0 0 24 24' fill='none' xmlns='http://www.w3.org/2000/svg' {...props}>
-    <path d='M8 5v14l11-7z' fill='currentColor' />
-  </svg>
-)
-
-export const LoopIcon = (props: SVGProps<SVGSVGElement>) => (
-  <svg viewBox='0 0 24 24' fill='none' xmlns='http://www.w3.org/2000/svg' {...props}>
-    <path
-      d='M4 12a8 8 0 018-8V2.5L16 6l-4 3.5V8a6 6 0 00-6 6 6 6 0 006 6 6 6 0 006-6h2a8 8 0 01-8 8 8 8 0 01-8-8z'
-      fill='currentColor'
-    />
-  </svg>
-)
-
-export const ParallelIcon = (props: SVGProps<SVGSVGElement>) => (
-  <svg viewBox='0 0 24 24' fill='none' xmlns='http://www.w3.org/2000/svg' {...props}>
-    <rect x='3' y='3' width='18' height='6' rx='1' stroke='currentColor' strokeWidth='2' />
-    <rect x='3' y='15' width='18' height='6' rx='1' stroke='currentColor' strokeWidth='2' />
-    <path d='M12 9v6' stroke='currentColor' strokeWidth='2' strokeLinecap='round' />
-  </svg>
-)

apps/docs/components/mdx-components.tsx

@@ -0,0 +1,10 @@
+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/structured-data.tsx

@@ -1,174 +0,0 @@
-import Script from 'next/script'
-
-interface StructuredDataProps {
-  title: string
-  description: string
-  url: string
-  lang: string
-  dateModified?: string
-  breadcrumb?: Array<{ name: string; url: string }>
-}
-
-export function StructuredData({
-  title,
-  description,
-  url,
-  lang,
-  dateModified,
-  breadcrumb,
-}: StructuredDataProps) {
-  const baseUrl = 'https://docs.sim.ai'
-
-  const articleStructuredData = {
-    '@context': 'https://schema.org',
-    '@type': 'TechArticle',
-    headline: title,
-    description: description,
-    url: url,
-    datePublished: dateModified || new Date().toISOString(),
-    dateModified: dateModified || new Date().toISOString(),
-    author: {
-      '@type': 'Organization',
-      name: 'Sim Team',
-      url: baseUrl,
-    },
-    publisher: {
-      '@type': 'Organization',
-      name: 'Sim',
-      url: baseUrl,
-      logo: {
-        '@type': 'ImageObject',
-        url: `${baseUrl}/static/logo.png`,
-      },
-    },
-    mainEntityOfPage: {
-      '@type': 'WebPage',
-      '@id': url,
-    },
-    inLanguage: lang,
-    isPartOf: {
-      '@type': 'WebSite',
-      name: 'Sim Documentation',
-      url: baseUrl,
-    },
-    potentialAction: {
-      '@type': 'ReadAction',
-      target: url,
-    },
-  }
-
-  const breadcrumbStructuredData = breadcrumb && {
-    '@context': 'https://schema.org',
-    '@type': 'BreadcrumbList',
-    itemListElement: breadcrumb.map((item, index) => ({
-      '@type': 'ListItem',
-      position: index + 1,
-      name: item.name,
-      item: item.url,
-    })),
-  }
-
-  const websiteStructuredData = url === baseUrl && {
-    '@context': 'https://schema.org',
-    '@type': 'WebSite',
-    name: 'Sim Documentation',
-    url: baseUrl,
-    description:
-      'Comprehensive documentation for Sim visual workflow builder for AI applications. Create powerful AI agents, automation workflows, and data processing pipelines.',
-    publisher: {
-      '@type': 'Organization',
-      name: 'Sim',
-      url: baseUrl,
-    },
-    potentialAction: {
-      '@type': 'SearchAction',
-      target: {
-        '@type': 'EntryPoint',
-        urlTemplate: `${baseUrl}/search?q={search_term_string}`,
-      },
-      'query-input': 'required name=search_term_string',
-    },
-    inLanguage: ['en', 'fr', 'zh'],
-  }
-
-  const faqStructuredData = title.toLowerCase().includes('faq') && {
-    '@context': 'https://schema.org',
-    '@type': 'FAQPage',
-    mainEntity: [],
-  }
-
-  const softwareStructuredData = {
-    '@context': 'https://schema.org',
-    '@type': 'SoftwareApplication',
-    name: 'Sim',
-    applicationCategory: 'DeveloperApplication',
-    operatingSystem: 'Any',
-    description:
-      'Visual workflow builder for AI applications. Create powerful AI agents, automation workflows, and data processing pipelines by connecting blocks on a canvas—no coding required.',
-    url: baseUrl,
-    author: {
-      '@type': 'Organization',
-      name: 'Sim Team',
-    },
-    offers: {
-      '@type': 'Offer',
-      category: 'Developer Tools',
-    },
-    featureList: [
-      'Visual workflow builder with drag-and-drop interface',
-      'AI agent creation and automation',
-      '80+ built-in integrations',
-      'Real-time team collaboration',
-      'Multiple deployment options',
-      'Custom integrations via MCP protocol',
-    ],
-  }
-
-  return (
-    <>
-      <Script
-        id='article-structured-data'
-        type='application/ld+json'
-        dangerouslySetInnerHTML={{
-          __html: JSON.stringify(articleStructuredData),
-        }}
-      />
-      {breadcrumbStructuredData && (
-        <Script
-          id='breadcrumb-structured-data'
-          type='application/ld+json'
-          dangerouslySetInnerHTML={{
-            __html: JSON.stringify(breadcrumbStructuredData),
-          }}
-        />
-      )}
-      {websiteStructuredData && (
-        <Script
-          id='website-structured-data'
-          type='application/ld+json'
-          dangerouslySetInnerHTML={{
-            __html: JSON.stringify(websiteStructuredData),
-          }}
-        />
-      )}
-      {faqStructuredData && (
-        <Script
-          id='faq-structured-data'
-          type='application/ld+json'
-          dangerouslySetInnerHTML={{
-            __html: JSON.stringify(faqStructuredData),
-          }}
-        />
-      )}
-      {url === baseUrl && (
-        <Script
-          id='software-structured-data'
-          type='application/ld+json'
-          dangerouslySetInnerHTML={{
-            __html: JSON.stringify(softwareStructuredData),
-          }}
-        />
-      )}
-    </>
-  )
-}

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

@@ -0,0 +1,163 @@
+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

@@ -0,0 +1,102 @@
+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

@@ -1,53 +0,0 @@
-'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',
-  enableLightbox = true,
-  alt = '',
-  src,
-  ...props
-}: ImageProps) {
-  const [isLightboxOpen, setIsLightboxOpen] = useState(false)
-
-  const handleImageClick = () => {
-    if (enableLightbox) {
-      setIsLightboxOpen(true)
-    }
-  }
-
-  return (
-    <>
-      <NextImage
-        className={cn(
-          'overflow-hidden rounded-xl border border-border object-cover shadow-sm',
-          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/language-dropdown.tsx

@@ -1,107 +0,0 @@
-'use client'
-
-import { useEffect, useState } from 'react'
-import { Check, ChevronDown } from 'lucide-react'
-import { useParams, usePathname } from 'next/navigation'
-
-const languages = {
-  en: { name: 'English', flag: '🇺🇸' },
-  es: { name: 'Español', flag: '🇪🇸' },
-  fr: { name: 'Français', flag: '🇫🇷' },
-  zh: { name: '简体中文', flag: '🇨🇳' },
-}
-
-export function LanguageDropdown() {
-  const [isOpen, setIsOpen] = useState(false)
-  const pathname = usePathname()
-  const params = useParams()
-
-  const [currentLang, setCurrentLang] = useState(() => {
-    const langFromParams = params?.lang as string
-    return langFromParams && Object.keys(languages).includes(langFromParams) ? langFromParams : 'en'
-  })
-
-  useEffect(() => {
-    const langFromParams = params?.lang as string
-
-    if (langFromParams && Object.keys(languages).includes(langFromParams)) {
-      if (langFromParams !== currentLang) {
-        setCurrentLang(langFromParams)
-      }
-    } else {
-      if (currentLang !== 'en') {
-        setCurrentLang('en')
-      }
-    }
-  }, [params, currentLang])
-
-  const handleLanguageChange = (locale: string) => {
-    if (locale === currentLang) {
-      setIsOpen(false)
-      return
-    }
-
-    setIsOpen(false)
-
-    const segments = pathname.split('/').filter(Boolean)
-
-    if (segments[0] && Object.keys(languages).includes(segments[0])) {
-      segments.shift()
-    }
-
-    let newPath = ''
-    if (locale === 'en') {
-      newPath = segments.length > 0 ? `/${segments.join('/')}` : '/introduction'
-    } else {
-      newPath = `/${locale}${segments.length > 0 ? `/${segments.join('/')}` : '/introduction'}`
-    }
-
-    window.location.href = newPath
-  }
-
-  return (
-    <div className='relative'>
-      <button
-        onClick={(e) => {
-          e.preventDefault()
-          e.stopPropagation()
-          setIsOpen(!isOpen)
-        }}
-        className='flex items-center gap-2 rounded-xl border border-border/20 bg-muted/50 px-3 py-2 text-sm backdrop-blur-sm transition-colors hover:bg-muted'
-      >
-        <span className='text-base'>{languages[currentLang as keyof typeof languages]?.flag}</span>
-        <span className='font-medium text-foreground'>
-          {languages[currentLang as keyof typeof languages]?.name}
-        </span>
-        <ChevronDown
-          className={`h-3 w-3 text-muted-foreground transition-transform ${isOpen ? 'rotate-180' : ''}`}
-        />
-      </button>
-
-      {isOpen && (
-        <>
-          <div className='fixed inset-0 z-10' onClick={() => setIsOpen(false)} />
-          <div className='absolute top-full left-0 z-20 mt-1 w-48 rounded-lg border border-border/50 bg-background/95 shadow-xl backdrop-blur-md'>
-            {Object.entries(languages).map(([code, lang]) => (
-              <button
-                key={code}
-                onClick={(e) => {
-                  e.preventDefault()
-                  e.stopPropagation()
-                  handleLanguageChange(code)
-                }}
-                className={`flex w-full items-center gap-3 px-3 py-2.5 text-sm transition-colors first:rounded-t-lg last:rounded-b-lg hover:bg-muted/80 ${
-                  currentLang === code ? 'bg-muted/60 font-medium text-primary' : 'text-foreground'
-                }`}
-              >
-                <span className='text-base'>{lang.flag}</span>
-                <span>{lang.name}</span>
-                {currentLang === code && <Check className='ml-auto h-4 w-4 text-primary' />}
-              </button>
-            ))}
-          </div>
-        </>
-      )}
-    </div>
-  )
-}

apps/docs/components/ui/lightbox.tsx

@@ -1,74 +0,0 @@
-'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

@@ -0,0 +1,48 @@
+'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

@@ -1,57 +0,0 @@
-'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

@@ -0,0 +1,212 @@
+---
+title: Agent
+description: Create powerful AI agents using any LLM provider
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The Agent block is a fundamental component in Sim Studio that allows you to create powerful AI agents using various LLM providers. These agents can process inputs based on customizable system prompts and utilize integrated tools to enhance their capabilities.
+
+<ThemeImage
+  lightSrc="/static/light/agent-light.png"
+  darkSrc="/static/dark/agent-dark.png"
+  alt="Agent Block"
+  width={300}
+  height={175}
+/>
+
+<Callout type="info">
+  Agent blocks serve as interfaces to Large Language Models, enabling your workflow to leverage
+  state-of-the-art AI capabilities.
+</Callout>
+
+## Overview
+
+The Agent block serves as an interface to Large Language Models (LLMs), enabling you to create agents that can:
+
+<Steps>
+  <Step>
+    <strong>Respond to user inputs</strong>: Generate natural language responses based on provided
+    inputs
+  </Step>
+  <Step>
+    <strong>Follow instructions</strong>: Adhere to specific instructions defined in the system
+    prompt
+  </Step>
+  <Step>
+    <strong>Use specialized tools</strong>: Interact with integrated tools to extend capabilities
+  </Step>
+  <Step>
+    <strong>Structure output</strong>: Generate responses in structured formats when needed
+  </Step>
+</Steps>
+
+## Configuration Options
+
+### System Prompt
+
+The system prompt defines the agent's behavior, capabilities, and limitations. It's the primary way to instruct the agent on how to respond to inputs.
+
+```markdown
+You are a helpful assistant that specializes in financial analysis.
+Always provide clear explanations and cite sources when possible.
+When responding to questions about investments, include risk disclaimers.
+```
+
+### User Prompt
+
+The user prompt or context is the specific input or question that the agent should respond to. This can be:
+
+- Directly provided in the block configuration
+- Connected from another block's output
+- Dynamically generated during workflow execution
+
+### Model Selection
+
+Choose from a variety of LLM providers:
+
+- OpenAI (GPT-4o, o1, o3, o4-mini, gpt-4.1)
+- Anthropic (Claude 3.7 Sonnet)
+- Google (Gemini 2.5 Pro, Gemini 2.0 Flash)
+- Groq, Cerebras
+- Ollama Local Models
+- And more
+
+### Temperature
+
+Control the creativity and randomness of responses:
+
+<Tabs items={['Low (0-0.3)', 'Medium (0.3-0.7)', 'High (0.7-2.0)']}>
+  <Tab>
+    <p>
+      More deterministic, focused responses. Best for factual tasks, customer support, and
+      situations where accuracy is critical.
+    </p>
+  </Tab>
+  <Tab>
+    <p>
+      Balanced creativity and focus. Suitable for general purpose applications that require both
+      accuracy and some creativity.
+    </p>
+  </Tab>
+  <Tab>
+    <p>
+      More creative, varied responses. Ideal for creative writing, brainstorming, and generating
+      diverse ideas.
+    </p>
+  </Tab>
+</Tabs>
+
+<p className="mt-4 text-sm text-gray-600 dark:text-gray-400">
+  The temperature range (0-1 or 0-2) varies depending on the selected model.
+</p>
+
+### API Key
+
+Your API key for the selected LLM provider. This is securely stored and used for authentication.
+
+### Tools
+
+Integrate specialized tools to enhance the agent's capabilities. You can add tools to your agent by:
+
+1. Clicking the Tools section in the Agent configuration
+2. Selecting from the tools dropdown menu
+3. Choosing an existing tool or creating a new one
+
+<ThemeImage
+  lightSrc="/static/light/tooldropdown-light.png"
+  darkSrc="/static/dark/tooldropdown-dark.png"
+  alt="Tools Dropdown"
+  width={150}
+  height={125}
+/>
+
+Available tools include:
+
+- **Confluence**: Access and query Confluence knowledge bases
+- **Evaluator**: Use evaluation metrics to assess content
+- **GitHub**: Interact with GitHub repositories and issues
+- **Gmail**: Process and respond to emails
+- **Firecrawl**: Web search and content retrieval
+- And many, many more pre-built integrations
+
+You can also create custom tools to meet specific requirements for your agent's capabilities.
+
+<Callout type="info">
+  Tools significantly expand what your agent can do, allowing it to access external systems,
+  retrieve information, and take actions beyond simple text generation.
+</Callout>
+
+### Response Format
+
+Define a structured format for the agent's response when needed, using JSON or other formats.
+
+## Inputs and Outputs
+
+<Tabs items={['Inputs', 'Outputs']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>User Prompt</strong>: The user's query or context for the agent
+      </li>
+      <li>
+        <strong>System Prompt</strong>: Instructions for the agent (optional)
+      </li>
+      <li>
+        <strong>Tools</strong>: Optional tool connections that the agent can use
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Content</strong>: The agent's response text
+      </li>
+      <li>
+        <strong>Model</strong>: The model used for generation
+      </li>
+      <li>
+        <strong>Tokens</strong>: Usage statistics (prompt, completion, total)
+      </li>
+      <li>
+        <strong>Tool Calls</strong>: Details of any tools used during processing
+      </li>
+      <li>
+        <strong>Cost</strong>: Cost of the response
+      </li>
+      <li>
+        <strong>Usage</strong>: Usage statistics (prompt, completion, total)
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Example Usage
+
+Here's an example of how an Agent block might be configured for a customer support workflow:
+
+```yaml
+# Example Agent Configuration
+systemPrompt: |
+  You are a customer support agent for TechCorp.
+  Always maintain a professional, friendly tone.
+  If you don't know an answer, direct the customer to email support@techcorp.com.
+  Never make up information about products or policies.
+
+model: OpenAI/gpt-4
+temperature: 0.2
+tools:
+  - ProductDatabase
+  - OrderHistory
+  - SupportTicketCreator
+```
+
+## Best Practices
+
+- **Be specific in system prompts**: Clearly define the agent's role, tone, and limitations. The more specific your instructions are, the better the agent will be able to fulfill its intended purpose.
+- **Choose the right temperature setting**: Use lower temperature settings (0-0.3) when accuracy is important, or increase temperature (0.7-2.0) for more creative or varied responses
+- **Combine with Evaluator blocks**: Use Evaluator blocks to assess agent responses and ensure quality. This allows you to create feedback loops and implement quality control measures.
+- **Leverage tools effectively**: Integrate tools that complement the agent's purpose and enhance its capabilities. Be selective about which tools you provide to avoid overwhelming the agent.

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

@@ -0,0 +1,128 @@
+---
+title: API
+description: Connect to external services through API endpoints
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The API block enables you to connect your workflow to external services through HTTP requests. It supports various methods like GET, POST, PUT, DELETE, and PATCH, allowing you to interact with virtually any API endpoint.
+
+<ThemeImage
+  lightSrc="/static/light/api-light.png"
+  darkSrc="/static/dark/api-dark.png"
+  alt="API Block"
+  width={300}
+  height={175}
+/>
+
+## Overview
+
+The API block enables you to:
+
+- Make HTTP requests to external services and APIs
+- Process and transform data from external sources
+- Send data to external systems
+- Integrate with third-party platforms and services
+- Create webhooks and callbacks
+
+## Configuration Options
+
+### URL
+
+The endpoint URL for the API request. This can be:
+
+- A static URL entered directly in the block
+- A dynamic URL connected from another block's output
+- A URL with path parameters
+
+### Method
+
+Select the HTTP method for your request:
+
+- **GET**: Retrieve data from the server
+- **POST**: Send data to the server to create a resource
+- **PUT**: Update an existing resource on the server
+- **DELETE**: Remove a resource from the server
+- **PATCH**: Partially update an existing resource
+
+### Query Parameters
+
+Define key-value pairs that will be appended to the URL as query parameters. For example:
+
+```
+Key: apiKey
+Value: your_api_key_here
+
+Key: limit
+Value: 10
+```
+
+These would be added to the URL as `?apiKey=your_api_key_here&limit=10`.
+
+### Headers
+
+Configure HTTP headers for your request. Common headers include:
+
+```
+Key: Content-Type
+Value: application/json
+
+Key: Authorization
+Value: Bearer your_token_here
+```
+
+### Request Body
+
+For methods that support a request body (POST, PUT, PATCH), you can define the data to send. The body can be:
+
+- JSON data entered directly in the block
+- Data connected from another block's output
+- Dynamically generated during workflow execution
+
+## Inputs and Outputs
+
+### Inputs
+
+- **URL**: The endpoint to send the request to
+- **Method**: The HTTP method to use
+- **Query Parameters**: Key-value pairs for URL parameters
+- **Headers**: HTTP headers for the request
+- **Body**: Data to send with the request (for applicable methods)
+
+### Outputs
+
+- **Status Code**: The HTTP status code returned by the server
+- **Response Body**: The data returned by the server
+- **Headers**: Response headers from the server
+- **Error**: Any error information if the request fails
+
+## Example Usage
+
+Here's an example of how an API block might be configured to fetch weather data:
+
+```yaml
+# Example API Configuration
+url: https://api.weatherapi.com/v1/current.json
+method: GET
+params:
+  - key: key
+    value: your_api_key_here
+  - key: q
+    value: London
+  - key: aqi
+    value: no
+headers:
+  - key: Accept
+    value: application/json
+```
+
+## Best Practices
+
+- **Use environment variables for sensitive data**: Don't hardcode API keys or credentials
+- **Handle errors gracefully**: Connect error handling logic for failed requests
+- **Validate responses**: Check status codes and response formats before processing data
+- **Respect rate limits**: Be mindful of API rate limits and implement appropriate throttling
+- **Cache responses when appropriate**: For frequently accessed data that doesn't change often

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

@@ -0,0 +1,191 @@
+---
+title: Condition
+description: Create conditional logic and branching in your workflows
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { File, Files, Folder } from 'fumadocs-ui/components/files'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The Condition block allows you to branch your workflow execution path based on boolean expressions. It evaluates conditions and routes the workflow accordingly, enabling you to create dynamic, responsive workflows with different execution paths.
+
+<ThemeImage
+  lightSrc="/static/light/condition-light.png"
+  darkSrc="/static/dark/condition-dark.png"
+  alt="Condition Block"
+  width={300}
+  height={175}
+/>
+
+<Callout>
+  Condition blocks enable deterministic decision-making without requiring an LLM, making them ideal
+  for straightforward branching logic.
+</Callout>
+
+## Overview
+
+The Condition block serves as a decision point in your workflow, enabling:
+
+<div className="my-6 grid grid-cols-1 gap-4 md:grid-cols-2">
+  <div className="rounded-lg border border-gray-200 p-4 dark:border-gray-800">
+    <h3 className="mb-2 text-lg font-medium">Branching Logic</h3>
+    <div className="text-sm text-gray-600 dark:text-gray-400">
+      Create different execution paths based on specific conditions
+    </div>
+  </div>
+
+  <div className="rounded-lg border border-gray-200 p-4 dark:border-gray-800">
+    <h3 className="mb-2 text-lg font-medium">Rule-Based Routing</h3>
+    <div className="text-sm text-gray-600 dark:text-gray-400">
+      Route workflows deterministically without needing an LLM
+    </div>
+  </div>
+
+  <div className="rounded-lg border border-gray-200 p-4 dark:border-gray-800">
+    <h3 className="mb-2 text-lg font-medium">Data-Driven Decisions</h3>
+    <div className="text-sm text-gray-600 dark:text-gray-400">
+      Create workflow paths based on structured data values
+    </div>
+  </div>
+
+  <div className="rounded-lg border border-gray-200 p-4 dark:border-gray-800">
+    <h3 className="mb-2 text-lg font-medium">If-Then-Else Logic</h3>
+    <div className="text-sm text-gray-600 dark:text-gray-400">
+      Implement conditional programming paradigms in your workflows
+    </div>
+  </div>
+</div>
+
+## How It Works
+
+The Condition block:
+
+<Steps>
+  <Step>
+    <strong>Evaluate Expression</strong>: Evaluates a boolean expression or condition
+  </Step>
+  <Step>
+    <strong>Determine Result</strong>: Determines whether the condition evaluates to true or false
+  </Step>
+  <Step>
+    <strong>Route Workflow</strong>: Routes the workflow to the appropriate path based on the result
+  </Step>
+  <Step>
+    <strong>Provide Context</strong>: Provides context about the decision made
+  </Step>
+</Steps>
+
+## Configuration Options
+
+### Conditions
+
+Define one or more conditions that will be evaluated. Each condition includes:
+
+- **Expression**: A JavaScript/TypeScript expression that evaluates to true or false
+- **Path**: The destination block to route to if the condition is true
+- **Description**: Optional explanation of what the condition checks
+
+You can create multiple conditions that are evaluated in order, with the first matching condition determining the execution path.
+
+### Condition Expression Format
+
+Conditions use JavaScript syntax and can reference input values from previous blocks.
+
+<Tabs items={['Score Threshold', 'Text Analysis', 'Multiple Conditions']}>
+  <Tab>
+    ```javascript
+    // Check if a score is above a threshold
+    input.score > 75
+    ```
+  </Tab>
+  <Tab>
+    ```javascript
+    // Check if a text contains specific keywords
+    input.text.includes('urgent') || input.text.includes('emergency')
+    ```
+  </Tab>
+  <Tab>
+    ```javascript
+    // Check multiple conditions
+    input.age >= 18 && input.country === 'US'
+    ```
+  </Tab>
+</Tabs>
+
+## Inputs and Outputs
+
+<Tabs items={['Inputs', 'Outputs']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Variables</strong>: Values from previous blocks that can be referenced in conditions
+      </li>
+      <li>
+        <strong>Conditions</strong>: Boolean expressions to evaluate
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Content</strong>: A description of the evaluation result
+      </li>
+      <li>
+        <strong>Condition Result</strong>: The boolean result of the condition evaluation
+      </li>
+      <li>
+        <strong>Selected Path</strong>: Details of the chosen routing destination
+      </li>
+      <li>
+        <strong>Selected Condition ID</strong>: Identifier of the condition that was matched
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Example Usage
+
+Here's an example of how a Condition block might be used in a customer satisfaction workflow:
+
+```yaml
+# Example Condition Configuration
+conditions:
+  - id: 'high_satisfaction'
+    expression: 'input.satisfactionScore >= 8'
+    description: 'Customer is highly satisfied'
+    path: 'positive_feedback_block'
+
+  - id: 'medium_satisfaction'
+    expression: 'input.satisfactionScore >= 5'
+    description: 'Customer is moderately satisfied'
+    path: 'neutral_feedback_block'
+
+  - id: 'default'
+    expression: 'true'
+    description: 'Customer is not satisfied'
+    path: 'improvement_feedback_block'
+```
+
+## Best Practices
+
+### Order conditions correctly
+
+Conditions are evaluated in order, so place more specific conditions before general ones. This ensures that more specific logic takes precedence over general fallbacks.
+
+### Include a default condition
+
+Add a catch-all condition (e.g., `true`) as the last condition to handle cases when no other conditions match. This prevents workflow execution from getting stuck.
+
+### Keep expressions simple
+
+Use clear, straightforward boolean expressions for better readability. Complex expressions can be difficult to debug and maintain.
+
+### Document your conditions
+
+Add descriptions to explain the purpose of each condition. This helps other team members understand the logic and makes maintenance easier.
+
+### Test edge cases
+
+Ensure your conditions handle boundary values correctly. Test with values at the edges of your condition ranges to verify correct behavior.

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

@@ -0,0 +1,128 @@
+---
+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'
+
+The Evaluator block allows you to assess the quality of content using customizable evaluation metrics. This is particularly useful for evaluating AI-generated text, ensuring outputs meet specific criteria, and building quality-control mechanisms into your workflows.
+
+<ThemeImage
+  lightSrc="/static/light/evaluator-light.png"
+  darkSrc="/static/dark/evaluator-dark.png"
+  alt="Evaluator Block"
+  width={300}
+  height={175}
+/>
+
+## Overview
+
+The Evaluator block utilizes LLMs to objectively evaluate content based on custom metrics you define. This is especially useful for:
+
+- Assessing the quality of AI-generated content
+- Evaluating responses against specific criteria
+- Creating scoring frameworks for different types of content
+- Building objective feedback loops in your workflows
+
+## Configuration Options
+
+### Evaluation Metrics
+
+Define custom metrics to evaluate content against. Each metric includes:
+
+- **Name**: A short identifier for the metric
+- **Description**: A detailed explanation of what the metric measures
+- **Range**: The numeric range for scoring (e.g., 1-5, 0-10)
+
+Example metrics:
+
+```
+Accuracy (1-5): How factually accurate is the content?
+Clarity (1-5): How clear and understandable is the content?
+Relevance (1-5): How relevant is the content to the original query?
+```
+
+### Content
+
+The content to be evaluated. This can be:
+
+- Directly provided in the block configuration
+- Connected from another block's output (typically an Agent block)
+- Dynamically generated during workflow execution
+
+### Model Selection
+
+Choose an LLM provider to perform the evaluation:
+
+- OpenAI (GPT-4o, o1, o3, , gpt-4.1)
+- Anthropic (Claude 3.7 Sonnet)
+- Google (Gemini 2.5 Pro, Gemini 2.0 Flash)
+- Groq, Cerebras
+- Ollama Local Models
+- And more
+
+The chosen model should have strong reasoning capabilities to provide accurate evaluations.
+
+### API Key
+
+Your API key for the selected LLM provider. This is securely stored and used for authentication.
+
+## How It Works
+
+1. The Evaluator block takes the provided content and your custom metrics
+2. It generates a specialized prompt that instructs the LLM to evaluate the content
+3. The prompt includes clear guidelines on how to score each metric
+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
+
+## 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
+```
+
+## Best Practices
+
+- **Use specific metric descriptions**: Clearly define what each metric measures to get more accurate evaluations
+- **Choose appropriate ranges**: Select scoring ranges that provide enough granularity without being overly complex
+- **Connect with Agent blocks**: Use Evaluator blocks to assess Agent block outputs and create feedback loops
+- **Use consistent metrics**: For comparative analysis, maintain consistent metrics across similar evaluations
+- **Combine multiple metrics**: Use several metrics to get a comprehensive evaluation

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

@@ -0,0 +1,137 @@
+---
+title: Function
+description: Execute custom JavaScript or TypeScript code in your workflows
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The Function block allows you to write and execute custom JavaScript or TypeScript code directly within your workflow. This powerful feature enables you to implement complex logic, data transformations, and integration with external libraries.
+
+<ThemeImage
+  lightSrc="/static/light/function-light.png"
+  darkSrc="/static/dark/function-dark.png"
+  alt="Function Block"
+  width={300}
+  height={175}
+/>
+
+## Overview
+
+The Function block brings the full power of JavaScript/TypeScript to your workflows, allowing for:
+
+- Custom data transformation and manipulation
+- Complex conditional logic
+- Mathematical calculations and algorithms
+- Integration with external libraries
+- Creation of reusable utility functions
+
+## How It Works
+
+The Function block:
+
+1. Takes your custom JavaScript/TypeScript code
+2. Executes it in a secure, isolated environment
+3. Processes any inputs provided from previous blocks
+4. Returns the result for use in subsequent blocks
+
+## Configuration Options
+
+### Code Editor
+
+A full-featured code editor where you can write your JavaScript/TypeScript code. The editor supports:
+
+- Syntax highlighting
+- Code completion
+- Error checking
+- Multiple lines of code
+
+### Inputs
+
+Your function can access inputs from previous blocks through an `input` object. For example:
+
+```javascript
+// Access data from a previous block
+const customerName = input.customerData.name;
+const orderTotal = input.orderData.total;
+
+// Process the data
+const discount = orderTotal > 100 ? 0.1 : 0;
+const finalPrice = orderTotal * (1 - discount);
+
+// Return the result
+return {
+  customerName,
+  originalTotal: orderTotal,
+  discount: discount * 100 + '%',
+  finalPrice
+};
+```
+
+## Safety and Limitations
+
+For security and performance reasons, function execution has certain limitations:
+
+- **Execution Time**: Functions have a maximum execution time to prevent infinite loops
+- **Memory Usage**: Memory is limited to prevent excessive resource usage
+- **Network Access**: Network calls are restricted to prevent unauthorized access
+- **Available APIs**: Only a subset of browser APIs are available
+
+## Inputs and Outputs
+
+### Inputs
+
+- **Code**: Your JavaScript/TypeScript code to execute
+- **Input Data**: Values from previous blocks that can be accessed in your code
+
+### Outputs
+
+- **Result**: The value returned by your function
+- **Standard Output**: Any console output from your function
+- **Execution Time**: The time taken to execute your function (in milliseconds)
+
+## Example Usage
+
+Here's an example of a Function block that processes customer data and calculates a loyalty score:
+
+```javascript
+// Example Function Block Code
+// Process customer data and calculate loyalty score
+
+// Access input from previous blocks
+const { purchaseHistory, accountAge, supportTickets } = input;
+
+// Calculate metrics
+const totalSpent = purchaseHistory.reduce((sum, purchase) => sum + purchase.amount, 0);
+const purchaseFrequency = purchaseHistory.length / (accountAge / 365);
+const ticketRatio = supportTickets.resolved / supportTickets.total;
+
+// Calculate loyalty score (0-100)
+const spendScore = Math.min(totalSpent / 1000 * 30, 30);
+const frequencyScore = Math.min(purchaseFrequency * 20, 40);
+const supportScore = ticketRatio * 30;
+
+const loyaltyScore = Math.round(spendScore + frequencyScore + supportScore);
+
+// Return results
+return {
+  customer: input.name,
+  loyaltyScore,
+  loyaltyTier: loyaltyScore >= 80 ? "Platinum" : loyaltyScore >= 60 ? "Gold" : loyaltyScore >= 40 ? "Silver" : "Bronze",
+  metrics: {
+    spendScore,
+    frequencyScore,
+    supportScore
+  }
+};
+```
+
+## Best Practices
+
+- **Keep functions focused**: Write functions that do one thing well
+- **Handle errors gracefully**: Use try/catch blocks to handle potential errors
+- **Document your code**: Add comments to explain complex logic
+- **Test edge cases**: Ensure your code handles unusual inputs correctly
+- **Optimize for performance**: Be mindful of computational complexity for large datasets

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

@@ -0,0 +1,54 @@
+---
+title: Blocks
+description: Building blocks for your agentic workflows
+---
+
+import { Card, Cards } from 'fumadocs-ui/components/card'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { BlockTypes } from '@/components/ui/block-types'
+
+Blocks are the fundamental building components of Sim Studio workflows. Each block has a specific purpose and can be connected to other blocks to create sophisticated workflows.
+
+## What is a Block?
+
+A block is a reusable, configurable component that performs a specific function within your workflow. Blocks have inputs and outputs that allow them to communicate with other blocks. They can process data, make decisions, interact with external systems, or perform computations.
+
+## Primary Block Types
+
+Sim Studio provides six powerful block types that form the foundation of any workflow. Each block is designed to handle specific aspects of your agentic applications, from AI-powered reasoning to conditional logic and external integrations.
+
+<BlockTypes />
+
+## Block Connections
+
+Blocks can be connected to form a directed graph representing your workflow. Each connection represents the flow of data from one block to another:
+
+<Steps>
+  <Step>
+    <strong>Outputs to Inputs</strong>: A block's outputs can be connected to another block's
+    inputs.
+  </Step>
+  <Step>
+    <strong>Multiple Connections</strong>: A block can have multiple incoming and outgoing
+    connections.
+  </Step>
+  <Step>
+    <strong>Conditional Flows</strong>: Some blocks (like Router and Condition) can have multiple
+    output paths based on conditions.
+  </Step>
+</Steps>
+
+## Block Configuration
+
+Each block type has its own configuration options allowing you to customize its behavior.
+
+### Common Configuration Options
+
+- **Input/output definitions**: Define how data flows in and out of the block
+- **Processing instructions**: Configure how the block processes its inputs
+- **API keys or authentication details**: Provide necessary credentials for external services
+- **Retry policies**: Configure how the block handles failures
+- **Error handling behavior**: Define how errors are managed and reported
+
+See the specific documentation for each block type to learn about its configuration options.

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

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

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

@@ -0,0 +1,188 @@
+---
+title: Response
+description: Send a structured response back to API calls
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The Response block is the final component in API-enabled workflows that transforms your workflow's variables into a structured HTTP response. This block serves as the endpoint that returns data, status codes, and headers back to API callers.
+
+<ThemeImage
+  lightSrc="/static/light/response-light.png"
+  darkSrc="/static/dark/response-dark.png"
+  alt="Response Block"
+  width={430}
+  height={784}
+/>
+
+<Callout type="info">
+  Response blocks are terminal blocks - they mark the end of a workflow execution and cannot have further connections.
+</Callout>
+
+## Overview
+
+The Response block serves as the final output mechanism for API workflows, enabling you to:
+
+<Steps>
+  <Step>
+    <strong>Return structured data</strong>: Transform workflow variables into JSON responses
+  </Step>
+  <Step>
+    <strong>Set HTTP status codes</strong>: Control the response status (200, 400, 500, etc.)
+  </Step>
+  <Step>
+    <strong>Configure headers</strong>: Add custom HTTP headers to the response
+  </Step>
+  <Step>
+    <strong>Reference variables</strong>: Use workflow variables dynamically in the response
+  </Step>
+</Steps>
+
+## Configuration Options
+
+### Response Data
+
+The response data is the main content that will be sent back to the API caller. This should be formatted as JSON and can include:
+
+- Static values
+- Dynamic references to workflow variables using the `<variable.name>` syntax
+- Nested objects and arrays
+- Any valid JSON structure
+
+### Status Code
+
+Set the HTTP status code for the response. Common status codes include:
+
+<Tabs items={['Success (2xx)', 'Client Error (4xx)', 'Server Error (5xx)']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li><strong>200</strong>: OK - Standard success response</li>
+      <li><strong>201</strong>: Created - Resource successfully created</li>
+      <li><strong>204</strong>: No Content - Success with no response body</li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li><strong>400</strong>: Bad Request - Invalid request parameters</li>
+      <li><strong>401</strong>: Unauthorized - Authentication required</li>
+      <li><strong>404</strong>: Not Found - Resource doesn't exist</li>
+      <li><strong>422</strong>: Unprocessable Entity - Validation errors</li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li><strong>500</strong>: Internal Server Error - Server-side error</li>
+      <li><strong>502</strong>: Bad Gateway - External service error</li>
+      <li><strong>503</strong>: Service Unavailable - Service temporarily down</li>
+    </ul>
+  </Tab>
+</Tabs>
+
+<p className="mt-4 text-sm text-gray-600 dark:text-gray-400">
+  Default status code is 200 if not specified.
+</p>
+
+### Response Headers
+
+Configure additional HTTP headers to include in the response.
+
+Headers are configured as key-value pairs:
+
+| Key | Value |
+|-----|-------|
+| Content-Type | application/json |
+| Cache-Control | no-cache |
+| X-API-Version | 1.0 |
+
+## Inputs and Outputs
+
+<Tabs items={['Inputs', 'Outputs']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>data</strong> (JSON, optional): The JSON data to send in the response body
+      </li>
+      <li>
+        <strong>status</strong> (number, optional): HTTP status code (default: 200)
+      </li>
+      <li>
+        <strong>headers</strong> (JSON, optional): Additional response headers
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>response</strong>: Complete response object containing:
+        <ul className="list-disc space-y-1 pl-6 mt-2">
+          <li><strong>data</strong>: The response body data</li>
+          <li><strong>status</strong>: HTTP status code</li>
+          <li><strong>headers</strong>: Response headers</li>
+        </ul>
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Variable References
+
+Use the `<variable.name>` syntax to dynamically insert workflow variables into your response:
+
+```json
+{
+  "user": {
+    "id": "<variable.userId>",
+    "name": "<variable.userName>",
+    "email": "<variable.userEmail>"
+  },
+  "query": "<variable.searchQuery>",
+  "results": "<variable.searchResults>",
+  "totalFound": "<variable.resultCount>",
+  "processingTime": "<variable.executionTime>ms"
+}
+```
+
+<Callout type="warning">
+  Variable names are case-sensitive and must match exactly with the variables available in your workflow.
+</Callout>
+
+## Example Usage
+
+Here's an example of how a Response block might be configured for a user search API:
+
+```yaml
+data: |
+  {
+    "success": true,
+    "data": {
+      "users": "<variable.searchResults>",
+      "pagination": {
+        "page": "<variable.currentPage>",
+        "limit": "<variable.pageSize>",
+        "total": "<variable.totalUsers>"
+      }
+    },
+    "query": {
+      "searchTerm": "<variable.searchTerm>",
+      "filters": "<variable.appliedFilters>"
+    },
+    "timestamp": "<variable.timestamp>"
+  }
+status: 200
+headers:
+  - key: X-Total-Count
+    value: <variable.totalUsers>
+  - key: Cache-Control
+    value: public, max-age=300
+```
+
+## Best Practices
+
+- **Use meaningful status codes**: Choose appropriate HTTP status codes that accurately reflect the outcome of the workflow
+- **Structure your responses consistently**: Maintain a consistent JSON structure across all your API endpoints for better developer experience
+- **Include relevant metadata**: Add timestamps and version information to help with debugging and monitoring
+- **Handle errors gracefully**: Use conditional logic in your workflow to set appropriate error responses with descriptive messages
+- **Validate variable references**: Ensure all referenced variables exist and contain the expected data types before the Response block executes

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

@@ -0,0 +1,120 @@
+---
+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 { ThemeImage } from '@/components/ui/theme-image'
+
+The Router block is a powerful component in Sim Studio that intelligently routes workflow execution based on content analysis, user input, or predefined conditions. It acts as a decision-making junction in your workflow, directing the flow to different paths based on various criteria.
+
+<ThemeImage
+  lightSrc="/static/light/router-light.png"
+  darkSrc="/static/dark/router-dark.png"
+  alt="Router Block"
+  width={300}
+  height={175}
+/>
+
+## Overview
+
+The Router block uses LLMs to analyze input content and determine the most appropriate next step in your workflow. This allows for:
+
+- Creating dynamic, adaptable workflows
+- Implementing complex decision trees
+- Routing user requests to specialized components
+- Building conversational systems that can handle diverse inputs
+
+## How It Works
+
+The Router block:
+
+1. Analyzes the input content using an LLM
+2. Evaluates the content against the available target blocks in your workflow
+3. Identifies the most appropriate destination based on the content's intent or requirements
+4. Routes the workflow execution to the selected block
+
+## Configuration Options
+
+### Content/Prompt
+
+The content or prompt that the Router will analyze to make routing decisions. This can be:
+
+- A direct user query or input
+- Output from a previous block
+- A system-generated message
+
+### Target Blocks
+
+The possible destination blocks that the Router can select from. The Router will automatically detect connected blocks, but you can also:
+
+- Customize the descriptions of target blocks to improve routing accuracy
+- Specify routing criteria for each target block
+- Exclude certain blocks from being considered as routing targets
+
+### Model Selection
+
+Choose an LLM provider to power the routing decision:
+
+- OpenAI (GPT-4o, o1, o3, o4-mini)
+- Anthropic (Claude 3.7 Sonnet)
+- Google (Gemini 2.5 Pro, Gemini 2.0 Flash)
+- Groq, Cerebras
+- Ollama Local Models
+- And more
+
+Select a model with strong reasoning capabilities for more accurate routing decisions.
+
+### API Key
+
+Your API key for the selected LLM provider. This is securely stored and used for authentication.
+
+## Inputs and Outputs
+
+### Inputs
+
+- **Content/Prompt**: The text to analyze for routing decisions
+- **Target Blocks**: Connected blocks that are potential routing destinations
+- **Model Settings**: LLM provider and parameters
+
+### Outputs
+
+- **Content**: A summary of the routing decision
+- **Model**: The model used for decision-making
+- **Tokens**: Usage statistics
+- **Selected Path**: Details of the chosen routing destination, including:
+  - Block ID
+  - Block Type
+  - Block Title
+
+## Example Usage
+
+Here's an example of how a Router block might be used in a customer support workflow:
+
+```yaml
+# Example Router Configuration
+prompt: |
+  Analyze the user query and route to the most appropriate department.
+  Choose ONE destination based on the query content and intent.
+
+model: OpenAI/gpt-4
+```
+
+In this example, the Router might be connected to:
+
+- A product support block
+- A billing inquiries block
+- A technical support block
+- A general inquiries block
+
+Based on the user's query, the Router would analyze the content and direct it to the most appropriate specialized support block.
+
+## Best Practices
+
+- **Provide clear descriptions for target blocks**: Help the Router understand when to select each destination
+- **Use specific routing criteria**: Define clear conditions for selecting each path
+- **Consider fallback paths**: Connect a default destination for when no specific path is appropriate
+- **Test with diverse inputs**: Ensure the Router handles various input types correctly
+- **Review routing decisions**: Monitor the Router's performance and refine as needed

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

@@ -0,0 +1,231 @@
+---
+title: Workflow
+description: Execute other workflows as reusable components within your current workflow
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+import { Step, Steps } from 'fumadocs-ui/components/steps'
+import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
+import { ThemeImage } from '@/components/ui/theme-image'
+
+The Workflow block allows you to execute other workflows as reusable components within your current workflow. This powerful feature enables modular design, code reuse, and the creation of complex nested workflows that can be composed from smaller, focused workflows.
+
+<ThemeImage
+  lightSrc="/static/light/workflow-light.png"
+  darkSrc="/static/dark/workflow-dark.png"
+  alt="Workflow Block"
+  width={300}
+  height={175}
+/>
+
+<Callout type="info">
+  Workflow blocks enable modular design by allowing you to compose complex workflows from smaller, reusable components.
+</Callout>
+
+## Overview
+
+The Workflow block serves as a bridge between workflows, enabling you to:
+
+<Steps>
+  <Step>
+    <strong>Reuse existing workflows</strong>: Execute previously created workflows as components within new workflows
+  </Step>
+  <Step>
+    <strong>Create modular designs</strong>: Break down complex processes into smaller, manageable workflows
+  </Step>
+  <Step>
+    <strong>Maintain separation of concerns</strong>: Keep different business logic isolated in separate workflows
+  </Step>
+  <Step>
+    <strong>Enable team collaboration</strong>: Share and reuse workflows across different projects and team members
+  </Step>
+</Steps>
+
+## How It Works
+
+The Workflow block:
+
+1. Takes a reference to another workflow in your workspace
+2. Passes input data from the current workflow to the child workflow
+3. Executes the child workflow in an isolated context
+4. Returns the results back to the parent workflow for further processing
+
+## Configuration Options
+
+### Workflow Selection
+
+Choose which workflow to execute from a dropdown list of available workflows in your workspace. The list includes:
+
+- All workflows you have access to in the current workspace
+- Workflows shared with you by other team members
+- Both enabled and disabled workflows (though only enabled workflows can be executed)
+
+### Input Data
+
+Define the data to pass to the child workflow:
+
+- **Single Variable Input**: Select a variable or block output to pass to the child workflow
+- **Variable References**: Use `<variable.name>` to reference workflow variables
+- **Block References**: Use `<blockName.field>` to reference outputs from previous blocks
+- **Automatic Mapping**: The selected data is automatically available as `start.input` in the child workflow
+- **Optional**: The input field is optional - child workflows can run without input data
+- **Type Preservation**: Variable types (strings, numbers, objects, etc.) are preserved when passed to the child workflow
+
+### Examples of Input References
+
+- `<variable.customerData>` - Pass a workflow variable
+- `<dataProcessor.result>` - Pass the result from a previous block
+- `<start.input>` - Pass the original workflow input
+- `<apiCall.data.user>` - Pass a specific field from an API response
+
+### Execution Context
+
+The child workflow executes with:
+
+- Its own isolated execution context
+- Access to the same workspace resources (API keys, environment variables)
+- Proper workspace membership and permission checks
+- Independent logging and monitoring
+
+## Safety and Limitations
+
+To prevent infinite recursion and ensure system stability, the Workflow block includes several safety mechanisms:
+
+<Callout type="warning">
+  **Cycle Detection**: The system automatically detects and prevents circular dependencies between workflows to avoid infinite loops.
+</Callout>
+
+- **Maximum Depth Limit**: Nested workflows are limited to a maximum depth of 10 levels
+- **Cycle Detection**: Automatic detection and prevention of circular workflow dependencies
+- **Timeout Protection**: Child workflows inherit timeout settings to prevent indefinite execution
+- **Resource Limits**: Memory and execution time limits apply to prevent resource exhaustion
+
+## Inputs and Outputs
+
+<Tabs items={['Inputs', 'Outputs']}>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Workflow ID</strong>: The identifier of the workflow to execute
+      </li>
+      <li>
+        <strong>Input Variable</strong>: Variable or block reference to pass to the child workflow (e.g., `<variable.name>` or `<block.field>`)
+      </li>
+    </ul>
+  </Tab>
+  <Tab>
+    <ul className="list-disc space-y-2 pl-6">
+      <li>
+        <strong>Response</strong>: The complete output from the child workflow execution
+      </li>
+      <li>
+        <strong>Child Workflow Name</strong>: The name of the executed child workflow
+      </li>
+      <li>
+        <strong>Success Status</strong>: Boolean indicating whether the child workflow completed successfully
+      </li>
+      <li>
+        <strong>Error Information</strong>: Details about any errors that occurred during execution
+      </li>
+      <li>
+        <strong>Execution Metadata</strong>: Information about execution time, resource usage, and performance
+      </li>
+    </ul>
+  </Tab>
+</Tabs>
+
+## Example Usage
+
+Here's an example of how a Workflow block might be used to create a modular customer onboarding process:
+
+### Parent Workflow: Customer Onboarding
+```yaml
+# Main customer onboarding workflow
+blocks:
+  - type: workflow
+    name: "Validate Customer Data"
+    workflowId: "customer-validation-workflow"
+    input: "<variable.newCustomer>"
+  
+  - type: workflow
+    name: "Setup Customer Account"
+    workflowId: "account-setup-workflow"
+    input: "<Validate Customer Data.result>"
+  
+  - type: workflow
+    name: "Send Welcome Email"
+    workflowId: "welcome-email-workflow"
+    input: "<Setup Customer Account.result.accountDetails>"
+```
+
+### Child Workflow: Customer Validation
+```yaml
+# Reusable customer validation workflow
+# Access the input data using: start.input
+blocks:
+  - type: function
+    name: "Validate Email"
+    code: |
+      const customerData = start.input;
+      const emailRegex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
+      return emailRegex.test(customerData.email);
+  
+  - type: api
+    name: "Check Credit Score"
+    url: "https://api.creditcheck.com/score"
+    method: "POST"
+    body: "<start.input>"
+```
+
+### Variable Reference Examples
+
+```yaml
+# Using workflow variables
+input: "<variable.customerInfo>"
+
+# Using block outputs
+  input: "<dataProcessor.cleanedData>"
+
+# Using nested object properties
+  input: "<apiCall.data.user.profile>"
+
+# Using array elements (if supported by the resolver)
+  input: "<listProcessor.items[0]>"
+```
+
+## Access Control and Permissions
+
+The Workflow block respects workspace permissions and access controls:
+
+- **Workspace Membership**: Only workflows within the same workspace can be executed
+- **Permission Inheritance**: Child workflows inherit the execution permissions of the parent workflow
+- **API Key Access**: Child workflows have access to the same API keys and environment variables as the parent
+- **User Context**: The execution maintains the original user context for audit and logging purposes
+
+## Best Practices
+
+- **Keep workflows focused**: Design child workflows to handle specific, well-defined tasks
+- **Minimize nesting depth**: Avoid deeply nested workflow hierarchies for better maintainability
+- **Handle errors gracefully**: Implement proper error handling for child workflow failures
+- **Document dependencies**: Clearly document which workflows depend on others
+- **Version control**: Consider versioning strategies for workflows that are used as components
+- **Test independently**: Ensure child workflows can be tested and validated independently
+- **Monitor performance**: Be aware that nested workflows can impact overall execution time
+
+## Common Patterns
+
+### Microservice Architecture
+Break down complex business processes into smaller, focused workflows that can be developed and maintained independently.
+
+### Reusable Components
+Create library workflows for common operations like data validation, email sending, or API integrations that can be reused across multiple projects.
+
+### Conditional Execution
+Use workflow blocks within conditional logic to execute different business processes based on runtime conditions.
+
+### Parallel Processing
+Combine workflow blocks with parallel execution to run multiple child workflows simultaneously for improved performance.
+
+<Callout type="tip">
+  When designing modular workflows, think of each workflow as a function with clear inputs, outputs, and a single responsibility.
+</Callout> 

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

@@ -0,0 +1,190 @@
+---
+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

@@ -0,0 +1,76 @@
+---
+title: Connection Basics
+description: Learn how connections work in Sim Studio
+---
+
+import { Callout } from 'fumadocs-ui/components/callout'
+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.
+
+<Callout type="info">
+  Each connection represents a directed relationship where data flows from a source block's output
+  to a destination block's input.
+</Callout>
+
+### Creating Connections
+
+<Steps>
+  <Step>
+    <strong>Select Source Block</strong>: Click on the output port of the block you want to connect
+    from
+  </Step>
+  <Step>
+    <strong>Draw Connection</strong>: Drag to the input port of the destination block
+  </Step>
+  <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
+
+The flow of data through connections follows these principles:
+
+1. **Directional Flow**: Data always flows from outputs to inputs
+2. **Execution Order**: Blocks execute in order based on their connections
+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

@@ -0,0 +1,208 @@
+---
+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,11 +1,12 @@
 ---
 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, 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.
+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.
 
 <Callout type="info">
   Understanding these data structures is essential for effectively using connection tags and
@@ -70,6 +71,7 @@ Different block types produce different output structures. Here's what you can e
     {
       "result": "Function return value",
       "stdout": "Console output",
+      "executionTime": 45
     }
     ```
 
@@ -77,13 +79,14 @@ Different block types produce different output structures. Here's what you can e
 
     - **result**: The return value of the function (can be any type)
     - **stdout**: Console output captured during function execution
+    - **executionTime**: Time taken to execute the function (in milliseconds)
 
   </Tab>
   <Tab>
     ```json
     {
       "content": "Evaluation summary",
-      "model": "gpt-5",
+      "model": "gpt-4o",
       "tokens": {
         "prompt": 120,
         "completion": 85,
@@ -179,7 +182,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:
 
 ```
-<blockName.path.to.nested.data>
+<blockId.path.to.nested.data>
 ```
 
 For example:

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

@@ -6,7 +6,6 @@ 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,13 +14,13 @@ Connections are the pathways that allow data to flow between blocks in your work
   data moves through your system and how blocks interact with each other.
 </Callout>
 
-<div className="mx-auto w-full overflow-hidden rounded-lg">
-  <Video src="connections.mp4" />
+<div>
+  <video autoPlay loop muted playsInline className="w-full" src="/connections.mp4"></video>
 </div>
 
 ## Connection Types
 
-Sim supports different types of connections that enable various workflow patterns:
+Sim Studio 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

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

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, providing an easy way to reference data between blocks and outputs from previous blocks in your workflow.
+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.
 
-<div className="mx-auto w-full overflow-hidden rounded-lg">
-  <Video src="connections.mp4" />
+<div>
+  <video autoPlay loop muted playsInline className="w-full" src="/connections.mp4"></video>
 </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:
 
 ```
-<blockName.path.to.data>
+<blockId.path.to.data>
 ```
 
 Where:
 
-- `blockName` is the name of the source block
+- `blockId` is the identifier of the source block
 - `path.to.data` is the path to the specific data field
 
 For example:

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

@@ -1,306 +0,0 @@
----
-title: Agent
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-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.
-
-<div className="flex justify-center">
-  <Image
-    src="/static/blocks/agent.png"
-    alt="Agent Block Configuration"
-    width={500}
-    height={400}
-    className="my-6"
-  />
-</div>
-
-## Overview
-
-The Agent block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Process natural language</strong>: Analyze user input and generate contextual responses
-  </Step>
-  <Step>
-    <strong>Execute AI-powered tasks</strong>: Perform content analysis, generation, and decision-making
-  </Step>
-  <Step>
-    <strong>Call external tools</strong>: Access APIs, databases, and services during processing
-  </Step>
-  <Step>
-    <strong>Generate structured output</strong>: Return JSON data that matches your schema requirements
-  </Step>
-</Steps> 
-
-## Configuration Options
-
-### System Prompt
-
-The system prompt establishes the agent's operational parameters and behavioral constraints. This configuration defines the agent's role, response methodology, and processing boundaries for all incoming requests.
-
-```markdown
-You are a helpful assistant that specializes in financial analysis.
-Always provide clear explanations and cite sources when possible.
-When responding to questions about investments, include risk disclaimers.
-```
-
-### User Prompt
-
-The user prompt represents the primary input data for inference processing. This parameter accepts natural language text or structured data that the agent will analyze and respond to. Input sources include:
-
-- **Static Configuration**: Direct text input specified in the block configuration
-- **Dynamic Input**: Data passed from upstream blocks through connection interfaces
-- **Runtime Generation**: Programmatically generated content during workflow execution
-
-### Model Selection
-
-The Agent block supports multiple LLM providers through a unified inference interface. Available models include:
-
-**OpenAI Models**: GPT-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 src="models.mp4" width={500} height={350} />
-</div>
-
-### Temperature
-
-Control the creativity and randomness of responses:
-
-<Tabs items={['Low (0-0.3)', 'Medium (0.3-0.7)', 'High (0.7-2.0)']}>
-  <Tab>
-    More deterministic, focused responses. Best for factual tasks, customer support, and
-    situations where accuracy is critical.
-  </Tab>
-  <Tab>
-    Balanced creativity and focus. Suitable for general purpose applications that require both
-    accuracy and some creativity.
-  </Tab>
-  <Tab>
-    More creative, varied responses. Ideal for creative writing, brainstorming, and generating
-    diverse ideas.
-  </Tab>
-</Tabs>
-
-<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.
-</div>
-
-### API Key
-
-Your API key for the selected LLM provider. This is securely stored and used for authentication.
-
-### Tools
-
-Tools extend the agent's capabilities through external API integrations and service connections. The tool system enables function calling, allowing the agent to execute operations beyond text generation.
-
-**Tool Integration Process**:
-1. Access the Tools configuration section within the Agent block
-2. Select from 60+ pre-built integrations or define custom functions
-3. Configure authentication parameters and operational constraints
-
-<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
-  <Video src="tools.mp4" width={500} height={350} />
-</div>
-
-**Available Tool Categories**:
-- **Communication**: Gmail, Slack, Telegram, WhatsApp, Microsoft Teams
-- **Data Sources**: Notion, Google Sheets, Airtable, Supabase, Pinecone
-- **Web Services**: Firecrawl, Google Search, Exa AI, browser automation
-- **Development**: GitHub, Jira, Linear repository and issue management
-- **AI Services**: OpenAI, Perplexity, Hugging Face, ElevenLabs
-
-**Tool Execution Control**:
-- **Auto**: Model determines tool invocation based on context and necessity
-- **Required**: Tool must be called during every inference request
-- **None**: Tool definition available but excluded from model context
-
-<div className="mx-auto w-3/5 overflow-hidden rounded-lg">
-  <Video src="granular-tool-control.mp4" width={500} height={350} />
-</div>
-
-### Response Format
-
-The Response Format parameter enforces structured output generation through JSON Schema validation. This ensures consistent, machine-readable responses that conform to predefined data structures:
-
-```json
-{
-  "name": "user_analysis",
-  "schema": {
-    "type": "object",
-    "properties": {
-      "sentiment": {
-        "type": "string",
-        "enum": ["positive", "negative", "neutral"]
-      },
-      "confidence": {
-        "type": "number",
-        "minimum": 0,
-        "maximum": 1
-      }
-    },
-    "required": ["sentiment", "confidence"]
-  }
-}
-```
-
-This configuration constrains the model's output to comply with the specified schema, preventing free-form text responses and ensuring structured data generation.
-
-### Accessing Results
-
-After an agent completes, you can access its outputs:
-
-- **`<agent.content>`**: The agent's response text or structured data
-- **`<agent.tokens>`**: Token usage statistics (prompt, completion, total)
-- **`<agent.tool_calls>`**: Details of any tools the agent used during execution
-- **`<agent.cost>`**: Estimated cost of the API call (if available)
-
-## Advanced Features
-
-### Memory + Agent: Conversation History
-
-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.
-
-- 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}}
-```
-
-See the `Memory` block reference for details: [/tools/memory](/tools/memory).
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>System Prompt</strong>: Instructions defining agent behavior and role
-      </li>
-      <li>
-        <strong>User Prompt</strong>: Input text or data to process
-      </li>
-      <li>
-        <strong>Model</strong>: AI model selection (OpenAI, Anthropic, Google, etc.)
-      </li>
-      <li>
-        <strong>Temperature</strong>: Response randomness control (0-2)
-      </li>
-      <li>
-        <strong>Tools</strong>: Array of available tools for function calling
-      </li>
-      <li>
-        <strong>Response Format</strong>: JSON Schema for structured output
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>agent.content</strong>: Agent's response text or structured data
-      </li>
-      <li>
-        <strong>agent.tokens</strong>: Token usage statistics object
-      </li>
-      <li>
-        <strong>agent.tool_calls</strong>: Array of tool execution details
-      </li>
-      <li>
-        <strong>agent.cost</strong>: Estimated API call cost (if available)
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Content</strong>: Primary response output from the agent
-      </li>
-      <li>
-        <strong>Metadata</strong>: Usage statistics and execution details
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the agent
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Customer Support Automation
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Handle customer inquiries with database access</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>User submits 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>
-
-### Multi-Model Content Analysis
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Analyze content with different AI models</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Function block processes uploaded document</li>
-    <li>Agent with GPT-4o performs technical analysis</li>
-    <li>Agent with Claude analyzes sentiment and tone</li>
-    <li>Function block combines results for final report</li>
-  </ol>
-</div>
-
-### Tool-Powered Research Assistant
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Research assistant with web search and document access</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>User query received via input</li>
-    <li>Agent searches web using Google Search tool</li>
-    <li>Agent accesses Notion database for internal docs</li>
-    <li>Agent compiles comprehensive research report</li>
-  </ol>
-</div>
-
-## Best Practices
-
-- **Be specific in system prompts**: Clearly define the agent's role, tone, and limitations. The more specific your instructions are, the better the agent will be able to fulfill its intended purpose.
-- **Choose the right temperature setting**: Use lower temperature settings (0-0.3) when accuracy is important, or increase temperature (0.7-2.0) for more creative or varied responses
-- **Leverage tools effectively**: Integrate tools that complement the agent's purpose and enhance its capabilities. Be selective about which tools you provide to avoid overwhelming the agent. For tasks with little overlap, use another Agent block for the best results.

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

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

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

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

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

@@ -1,199 +0,0 @@
----
-title: Evaluator
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { Image } from '@/components/ui/image'
-import { Video } from '@/components/ui/video'
-
-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.
-
-<div className="flex justify-center">
-  <Image
-    src="/static/blocks/evaluator.png"
-    alt="Evaluator Block Configuration"
-    width={500}
-    height={400}
-    className="my-6"
-  />
-</div>
-
-## Overview
-
-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
-
-### Evaluation Metrics
-
-Define custom metrics to evaluate content against. Each metric includes:
-
-- **Name**: A short identifier for the metric
-- **Description**: A detailed explanation of what the metric measures
-- **Range**: The numeric range for scoring (e.g., 1-5, 0-10)
-
-Example metrics:
-
-```
-Accuracy (1-5): How factually accurate is the content?
-Clarity (1-5): How clear and understandable is the content?
-Relevance (1-5): How relevant is the content to the original query?
-```
-
-### Content
-
-The content to be evaluated. This can be:
-
-- Directly provided in the block configuration
-- Connected from another block's output (typically an Agent block)
-- Dynamically generated during workflow execution
-
-### Model Selection
-
-Choose an AI model to perform the evaluation:
-
-**OpenAI**: GPT-4o, o1, o3, o4-mini, gpt-4.1
-**Anthropic**: Claude 3.7 Sonnet
-**Google**: Gemini 2.5 Pro, Gemini 2.0 Flash
-**Other Providers**: Groq, Cerebras, xAI, DeepSeek
-**Local Models**: Any model running on Ollama
-
-<div className="w-full max-w-2xl mx-auto overflow-hidden rounded-lg">
-  <Video 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.
-
-### API Key
-
-Your API key for the selected LLM provider. This is securely stored and used for authentication.
-
-## How It Works
-
-1. The Evaluator block takes the provided content and your custom metrics
-2. It generates a specialized prompt that instructs the LLM to evaluate the content
-3. The prompt includes clear guidelines on how to score each metric
-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
-
-<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
-
-- **Use specific metric descriptions**: Clearly define what each metric measures to get more accurate evaluations
-- **Choose appropriate ranges**: Select scoring ranges that provide enough granularity without being overly complex
-- **Connect with Agent blocks**: Use Evaluator blocks to assess Agent block outputs and create feedback loops
-- **Use consistent metrics**: For comparative analysis, maintain consistent metrics across similar evaluations
-- **Combine multiple metrics**: Use several metrics to get a comprehensive evaluation

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

@@ -1,156 +0,0 @@
----
-title: Function
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { Image } from '@/components/ui/image'
-
-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.
-
-<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
-
-The Function block enables you to:
-
-<Steps>
-  <Step>
-    <strong>Transform data</strong>: Convert formats, parse text, manipulate arrays and objects
-  </Step>
-  <Step>
-    <strong>Perform calculations</strong>: Math operations, statistics, financial calculations
-  </Step>
-  <Step>
-    <strong>Implement custom logic</strong>: Complex conditionals, loops, and algorithms
-  </Step>
-  <Step>
-    <strong>Process external data</strong>: Parse responses, format requests, handle authentication
-  </Step>
-</Steps>
-
-## How It Works
-
-The Function block runs your code in a secure, isolated environment:
-
-1. **Receive Input**: Access data from previous blocks via the `input` object
-2. **Execute Code**: Run your JavaScript/Python code 
-3. **Return Results**: Use `return` to pass data to the next block
-4. **Handle Errors**: Built-in error handling and logging
-
-## Remote Execution (E2B)
-
-  - **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']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Code</strong>: Your JavaScript/Python code to execute
-      </li>
-      <li>
-        <strong>Timeout</strong>: Maximum execution time (defaults to 30 seconds)
-      </li>
-      <li>
-        <strong>Input Data</strong>: All connected block outputs available via variables
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>function.result</strong>: The value returned from your function
-      </li>
-      <li>
-        <strong>function.stdout</strong>: Console.log() output from your code
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Data Processing Pipeline
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Transform API response into structured data</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>API block fetches raw customer data</li>
-    <li>Function block processes and validates data</li>
-    <li>Function block calculates derived metrics</li>
-    <li>Response block returns formatted results</li>
-  </ol>
-</div>
-
-### Business Logic Implementation
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Calculate loyalty scores and tiers</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Agent retrieves customer purchase history</li>
-    <li>Function block calculates loyalty metrics</li>
-    <li>Function block determines customer tier</li>
-    <li>Condition block routes based on tier level</li>
-  </ol>
-</div>
-
-### Data Validation and Sanitization
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Validate and clean user input</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>User input received from form submission</li>
-    <li>Function block validates email format and phone numbers</li>
-    <li>Function block sanitizes and normalizes data</li>
-    <li>API block saves validated data to database</li>
-  </ol>
-</div>
-
-### Example: Loyalty Score Calculator
-
-```javascript title="loyalty-calculator.js"
-// Process customer data and calculate loyalty score
-const { purchaseHistory, accountAge, supportTickets } = <agent>;
-
-// Calculate metrics
-const totalSpent = purchaseHistory.reduce((sum, purchase) => sum + purchase.amount, 0);
-const purchaseFrequency = purchaseHistory.length / (accountAge / 365);
-const ticketRatio = supportTickets.resolved / supportTickets.total;
-
-// Calculate loyalty score (0-100)
-const spendScore = Math.min(totalSpent / 1000 * 30, 30);
-const frequencyScore = Math.min(purchaseFrequency * 20, 40);
-const supportScore = ticketRatio * 30;
-
-const loyaltyScore = Math.round(spendScore + frequencyScore + supportScore);
-
-return {
-  customer: <agent.name>,
-  loyaltyScore,
-  loyaltyTier: loyaltyScore >= 80 ? "Platinum" : loyaltyScore >= 60 ? "Gold" : "Silver",
-  metrics: { spendScore, frequencyScore, supportScore }
-};
-```
-
-## Best Practices
-
-- **Keep functions focused**: Write functions that do one thing well to improve maintainability and debugging
-- **Handle errors gracefully**: Use try/catch blocks to handle potential errors and provide meaningful error messages
-- **Test edge cases**: Ensure your code handles unusual inputs, null values, and boundary conditions correctly
-- **Optimize for performance**: Be mindful of computational complexity and memory usage for large datasets
-- **Use console.log() for debugging**: Leverage stdout output to debug and monitor function execution

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

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

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

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

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

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

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

@@ -1,247 +0,0 @@
----
-title: Response
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Tab, Tabs } from 'fumadocs-ui/components/tabs'
-import { Image } from '@/components/ui/image'
-
-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.
-
-<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
-
-## Two Ways to Build Responses
-
-### Builder Mode (Recommended)
-Visual interface for building response structure:
-- Drag and drop fields
-- Reference workflow variables easily
-- Visual preview of response structure
-
-### Editor Mode (Advanced)
-Write JSON directly:
-- Full control over response format
-- Support for complex nested structures
-- Use `<variable.name>` syntax for dynamic values
-
-## Configuration Options
-
-### Response Data
-
-The response data is the main content that will be sent back to the API caller. This should be formatted as JSON and can include:
-
-- Static values
-- Dynamic references to workflow variables using the `<variable.name>` syntax
-- Nested objects and arrays
-- Any valid JSON structure
-
-### Status Code
-
-Set the HTTP status code for the response. Common status codes include:
-
-<Tabs items={['Success (2xx)', 'Client Error (4xx)', 'Server Error (5xx)']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>200</strong>: OK - Standard success response</li>
-      <li><strong>201</strong>: Created - Resource successfully created</li>
-      <li><strong>204</strong>: No Content - Success with no response body</li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>400</strong>: Bad Request - Invalid request parameters</li>
-      <li><strong>401</strong>: Unauthorized - Authentication required</li>
-      <li><strong>404</strong>: Not Found - Resource doesn't exist</li>
-      <li><strong>422</strong>: Unprocessable Entity - Validation errors</li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li><strong>500</strong>: Internal Server Error - Server-side error</li>
-      <li><strong>502</strong>: Bad Gateway - External service error</li>
-      <li><strong>503</strong>: Service Unavailable - Service temporarily down</li>
-    </ul>
-  </Tab>
-</Tabs>
-
-<div className="mt-4 text-sm text-gray-600 dark:text-gray-400">
-  Default status code is 200 if not specified.
-</div>
-
-### Response Headers
-
-Configure additional HTTP headers to include in the response.
-
-Headers are configured as key-value pairs:
-
-| Key | Value |
-|-----|-------|
-| Content-Type | application/json |
-| Cache-Control | no-cache |
-| X-API-Version | 1.0 |
-
-## 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={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Response Data</strong>: JSON structure for response body
-      </li>
-      <li>
-        <strong>Status Code</strong>: HTTP status code (default: 200)
-      </li>
-      <li>
-        <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>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>
-
-## Variable References
-
-Use the `<variable.name>` syntax to dynamically insert workflow variables into your response:
-
-```json
-{
-  "user": {
-    "id": "<variable.userId>",
-    "name": "<variable.userName>",
-    "email": "<variable.userEmail>"
-  },
-  "query": "<variable.searchQuery>",
-  "results": "<variable.searchResults>",
-  "totalFound": "<variable.resultCount>",
-  "processingTime": "<variable.executionTime>ms"
-}
-```
-
-<Callout type="warning">
-  Variable names are case-sensitive and must match exactly with the variables available in your workflow.
-</Callout>
-
-## Best Practices
-
-- **Use meaningful status codes**: Choose appropriate HTTP status codes that accurately reflect the outcome of the workflow
-- **Structure your responses consistently**: Maintain a consistent JSON structure across all your API endpoints for better developer experience
-- **Include relevant metadata**: Add timestamps and version information to help with debugging and monitoring
-- **Handle errors gracefully**: Use conditional logic in your workflow to set appropriate error responses with descriptive messages
-- **Validate variable references**: Ensure all referenced variables exist and contain the expected data types before the Response block executes
-

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

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

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

@@ -1,169 +0,0 @@
----
-title: 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 { Image } from '@/components/ui/image'
-
-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.
-
-<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.
-</Callout>
-
-## Overview
-
-The Workflow block serves as a bridge between workflows, enabling you to:
-
-<Steps>
-  <Step>
-    <strong>Reuse existing workflows</strong>: Execute previously created workflows as components within new workflows
-  </Step>
-  <Step>
-    <strong>Create modular designs</strong>: Break down complex processes into smaller, manageable workflows
-  </Step>
-  <Step>
-    <strong>Maintain separation of concerns</strong>: Keep different business logic isolated in separate workflows
-  </Step>
-  <Step>
-    <strong>Enable team collaboration</strong>: Share and reuse workflows across different projects and team members
-  </Step>
-</Steps>
-
-## How It Works
-
-The Workflow block:
-
-1. Takes a reference to another workflow in your workspace
-2. Passes input data from the current workflow to the child workflow (available via start.input)
-3. Executes the child workflow in an isolated context
-4. Returns the result back to the parent workflow for further processing
-
-## Configuration Options
-
-### Workflow Selection
-
-Choose which workflow to execute from a dropdown list of available workflows in your workspace. The list includes:
-
-- All workflows you have access to in the current workspace
-- Workflows shared with you by other team members
-- Both enabled and disabled workflows (though only enabled workflows can be executed)
-
-
-### Execution Context
-
-The child workflow executes with:
-
-- Its own isolated execution context
-- Access to the same workspace resources (API keys, environment variables)
-- Proper workspace membership and permission checks
-- 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>
-
-## Inputs and Outputs
-
-<Tabs items={['Configuration', 'Variables', 'Results']}>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Workflow Selection</strong>: Choose which workflow to execute
-      </li>
-      <li>
-        <strong>Input Data</strong>: Variable or block reference to pass to child workflow
-      </li>
-      <li>
-        <strong>Execution Context</strong>: Isolated environment with workspace resources
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>workflow.success</strong>: Boolean indicating completion status
-      </li>
-      <li>
-        <strong>workflow.childWorkflowName</strong>: Name of executed child workflow
-      </li>
-      <li>
-        <strong>workflow.result</strong>: Result returned by the child workflow
-      </li>
-      <li>
-        <strong>workflow.error</strong>: Error details if workflow failed
-      </li>
-    </ul>
-  </Tab>
-  <Tab>
-    <ul className="list-disc space-y-2 pl-6">
-      <li>
-        <strong>Workflow Response</strong>: Primary output from child workflow
-      </li>
-      <li>
-        <strong>Execution Status</strong>: Success status and error information
-      </li>
-      <li>
-        <strong>Access</strong>: Available in blocks after the workflow
-      </li>
-    </ul>
-  </Tab>
-</Tabs>
-
-## Example Use Cases
-
-### Modular Customer Onboarding
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Break down complex onboarding into reusable components</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Main workflow receives customer data</li>
-    <li>Workflow block executes validation workflow</li>
-    <li>Workflow block executes account setup workflow</li>
-    <li>Workflow block executes welcome email workflow</li>
-  </ol>
-</div>
-
-### Microservice Architecture
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Create independent service workflows</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Payment processing workflow handles transactions</li>
-    <li>Inventory management workflow updates stock</li>
-    <li>Notification workflow sends confirmations</li>
-    <li>Main workflow orchestrates all services</li>
-  </ol>
-</div>
-
-### Conditional Processing
-
-<div className="mb-4 rounded-md border p-4">
-  <h4 className="font-medium">Scenario: Execute different workflows based on conditions</h4>
-  <ol className="list-decimal pl-5 text-sm">
-    <li>Condition block evaluates user type</li>
-    <li>Enterprise users → Complex approval workflow</li>
-    <li>Standard users → Simple approval workflow</li>
-    <li>Free users → Basic processing workflow</li>
-  </ol>
-</div>
-
-## 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
-- **Test independently**: Ensure child workflows can be tested and validated independently from parent workflows
-- **Use semantic naming**: Give workflows descriptive names that clearly indicate their purpose and functionality

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

@@ -1,44 +0,0 @@
----
-title: Connection Basics
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-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. 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
-  to a destination block's input.
-</Callout>
-
-### Creating Connections
-
-<Steps>
-  <Step>
-    <strong>Select Source Block</strong>: Click on the output port of the block you want to connect
-    from
-  </Step>
-  <Step>
-    <strong>Draw Connection</strong>: Drag to the input port of the destination block
-  </Step>
-  <Step>
-    <strong>Confirm Connection</strong>: Release to create the connection
-  </Step>
-</Steps>
-
-### Connection Flow
-
-The flow of data through connections follows these principles:
-
-1. **Directional Flow**: Data always flows from outputs to inputs
-2. **Execution Order**: Blocks execute in order based on their connections
-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
-
-<Callout type="warning">
-  Deleting a connection will immediately stop data flow between the blocks. Make sure this is
-  intended before removing connections.
-</Callout>

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

@@ -1,162 +0,0 @@
----
-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/en/execution/api.mdx

@@ -1,536 +0,0 @@
----
-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/en/execution/basics.mdx

@@ -1,132 +0,0 @@
----
-title: Execution Basics
----
-
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Card, Cards } from 'fumadocs-ui/components/card'
-import { Step, Steps } from 'fumadocs-ui/components/steps'
-import { Image } from '@/components/ui/image'
-import { Video } from '@/components/ui/video'
-
-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.
-
-## How Workflows Execute
-
-Sim's execution engine processes workflows intelligently by analyzing dependencies and running blocks in the most efficient order possible.
-
-### Concurrent Execution by Default
-
-Multiple blocks run concurrently when they don't depend on each other. This parallel execution dramatically improves performance without requiring manual configuration.
-
-<Image
-  src="/static/execution/concurrency.png"
-  alt="Multiple blocks running concurrently after the Start block"
-  width={800}
-  height={500}
-/>
-
-In this example, both the Customer Support and Deep Researcher agent blocks execute simultaneously after the Start block, maximizing efficiency.
-
-### Automatic Output Combination
-
-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.
-
-<Image
-  src="/static/execution/combination.png"
-  alt="Function block automatically receiving outputs from multiple previous blocks"
-  width={800}
-  height={500}
-/>
-
-The Function block receives outputs from both agent blocks as soon as they complete, allowing you to process the combined results.
-
-### 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>
-  
-  <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>
-
-All blocks execute automatically based on their dependencies - you don't need to manually manage execution order or timing.
-
-## Execution Triggers
-
-Workflows can be triggered in several ways, depending on your use case:
-
-### Manual Testing
-Click "Run" in the workflow editor to test your workflow during development. Perfect for debugging and validation.
-
-### Scheduled Execution  
-Set up recurring executions using cron expressions. Great for regular data processing, reports, or maintenance tasks.
-
-### API Deployment
-Deploy workflows as HTTP endpoints that can be called programmatically from your applications.
-
-### Webhook Integration
-Respond to events from external services like GitHub, Stripe, or custom systems in real-time.
-
-### Chat Interface
-Create conversational interfaces hosted on custom subdomains for user-facing AI applications.
-
-<Callout type="info">
-  Learn more about each trigger type in the [Triggers section](/triggers) of the documentation.
-</Callout>
-
-## Execution Monitoring
-
-When workflows run, Sim provides real-time visibility into the execution process:
-
-- **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
-
-<Callout type="info">
-  All execution details are captured and available for review even after workflows complete, helping with debugging and optimization.
-</Callout>
-
-## Key Execution Principles
-
-Understanding these core principles will help you build better workflows:
-
-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/en/execution/costs.mdx

@@ -1,182 +0,0 @@
----
-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/en/execution/index.mdx

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

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

@@ -1,150 +0,0 @@
----
-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/en/getting-started/index.mdx

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

apps/docs/content/docs/en/index.mdx

@@ -1,60 +0,0 @@
----
-title: Documentation
----
-
-import { Card, Cards } from 'fumadocs-ui/components/card'
-
-# Sim Documentation
-
-Welcome to Sim, a visual workflow builder for AI applications. Build powerful AI agents, automation workflows, and data processing pipelines by connecting blocks on a canvas.
-
-## Quick Start
-
-<Cards>
-  <Card title="Introduction" href="/introduction">
-    Learn what you can build with Sim
-  </Card>
-  <Card title="Getting Started" href="/getting-started">
-    Create your first workflow in 10 minutes
-  </Card>
-  <Card title="Workflow Blocks" href="/blocks">
-    Learn about the building blocks
-  </Card>
-  <Card title="Tools & Integrations" href="/tools">
-    Explore 80+ built-in integrations
-  </Card>
-</Cards>
-
-## Core Concepts
-
-<Cards>
-  <Card title="Connections" href="/connections">
-    Understand how data flows between blocks
-  </Card>
-  <Card title="Variables" href="/variables">
-    Work with workflow and environment variables
-  </Card>
-  <Card title="Execution" href="/execution">
-    Monitor workflow runs and manage costs
-  </Card>
-  <Card title="Triggers" href="/triggers">
-    Start workflows via API, webhooks, or schedules
-  </Card>
-</Cards>
-
-## Advanced Features
-
-<Cards>
-  <Card title="Team Management" href="/permissions/roles-and-permissions">
-    Set up workspace roles and permissions
-  </Card>
-  <Card title="YAML Configuration" href="/yaml">
-    Define workflows as code
-  </Card>
-  <Card title="MCP Integration" href="/mcp">
-    Connect external services with Model Context Protocol
-  </Card>
-  <Card title="SDKs" href="/sdks">
-    Integrate Sim into your applications
-  </Card>
-</Cards>

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

@@ -1,85 +0,0 @@
----
-title: Introduction
----
-
-import { Card, Cards } from 'fumadocs-ui/components/card'
-import { Callout } from 'fumadocs-ui/components/callout'
-import { Image } from '@/components/ui/image'
-
-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.
-
-<div className="flex justify-center">
-  <Image
-    src="/static/introduction.png"
-    alt="Sim visual workflow canvas"
-    width={700}
-    height={450}
-    className="my-6"
-  />
-</div>
-
-## What You Can Build
-
-**AI Assistants & Chatbots**
-Create intelligent agents that can search the web, access your calendar, send emails, and interact with your business tools.
-
-**Business Process Automation**
-Automate repetitive tasks like data entry, report generation, customer support responses, and content creation.
-
-**Data Processing & Analysis**
-Extract insights from documents, analyze datasets, generate reports, and sync data between systems.
-
-**API Integration Workflows**
-Connect multiple services into unified endpoints, orchestrate complex business logic, and handle event-driven automation.
-
-## How It Works
-
-**Visual Canvas**
-Drag and drop blocks to build workflows. Connect AI models, databases, APIs, and business tools with simple point-and-click connections.
-
-**Smart Blocks**
-Choose from processing blocks (AI agents, APIs, functions), logic blocks (conditions, loops, routers), and output blocks (responses, evaluators).
-
-**Multiple Triggers**
-Start workflows via chat interface, REST API, webhooks, scheduled jobs, or external events from services like Slack and GitHub.
-
-**Team Collaboration**
-Work simultaneously with team members on the same workflow with real-time editing and permissions management.
-
-## Built-in Integrations
-
-Sim connects to 80+ services out of the box:
-
-- **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
-
-Need something custom? Use our [MCP integration](/mcp) to connect any external service.
-
-## Deployment Options
-
-**Cloud-hosted**: Get started instantly at [sim.ai](https://sim.ai) with managed infrastructure, automatic scaling, and built-in monitoring.
-
-**Self-hosted**: Deploy on your own infrastructure using Docker, with support for local AI models via Ollama for complete data privacy.
-
-## Next Steps
-
-Ready to build your first AI workflow?
-
-<Cards>
-  <Card title="Getting Started" href="/getting-started">
-    Create your first workflow in 10 minutes
-  </Card>
-  <Card title="Workflow Blocks" href="/blocks">
-    Learn about the building blocks
-  </Card>
-  <Card title="Tools & Integrations" href="/tools">
-    Explore 60+ built-in integrations
-  </Card>
-  <Card title="Team Permissions" href="/permissions/roles-and-permissions">
-    Set up workspace roles and permissions
-  </Card>
-</Cards>

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

@@ -1,113 +0,0 @@
----
-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/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/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/en/knowledgebase/tags.mdx

@@ -1,108 +0,0 @@
----
-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/en/mcp/index.mdx

@@ -1,140 +0,0 @@
----
-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/en/meta.json

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

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

@@ -1,161 +0,0 @@
----
-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/en/tools/arxiv.mdx

@@ -1,114 +0,0 @@
----
-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
-
-Integrates ArXiv into the workflow. Can search for papers, get paper details, and get author papers. Does not require OAuth or an API key.
-
-
-
-## 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/en/tools/generic_webhook.mdx

@@ -1,32 +0,0 @@
----
-title: Webhook
-description: Receive webhooks from any service by configuring a custom webhook.
----
-
-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/en/tools/google_forms.mdx

@@ -1,86 +0,0 @@
----
-title: Google Forms
-description: Read responses from a Google Form
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="google_forms"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"  xmlns='http://www.w3.org/2000/svg' viewBox='0 0 48 65' fill='none'>
-      <path
-        d='M29.583 0H4.438C1.997 0 0 1.997 0 4.438v56.208C0 63.086 1.997 65.083 4.438 65.083h38.458c2.44 0 4.437-1.997 4.437-4.437V17.75L36.979 10.354 29.583 0Z'
-        fill='#673AB7'
-      />
-      <path
-        d='M29.583 0v10.354c0 2.45 1.986 4.438 4.438 4.438h13.312L36.979 10.354 29.583 0Z'
-        fill='#B39DDB'
-      />
-      <path
-        d='M19.229 50.292h16.271v-2.959H19.229v2.959Zm0-17.75v2.958h16.271v-2.958H19.229Zm-3.698 1.479c0 1.224-0.995 2.219-2.219 2.219s-2.219-0.995-2.219-2.219c0-1.224 0.995-2.219 2.219-2.219s2.219 0.995 2.219 2.219Zm0 7.396c0 1.224-0.995 2.219-2.219 2.219s-2.219-0.995-2.219-2.219c0-1.224 0.995-2.219 2.219-2.219s2.219 0.995 2.219 2.219Zm0 7.396c0 1.224-0.995 2.219-2.219 2.219s-2.219-0.995-2.219-2.219c0-1.224 0.995-2.219 2.219-2.219s2.219 0.995 2.219 2.219Zm3.698-5.917h16.271v-2.959H19.229v2.959Z'
-        fill='#F1F1F1'
-      />
-      <defs>
-        <linearGradient
-          id='gf-gradient'
-          x1='30.881'
-          y1='16.452'
-          x2='47.333'
-          y2='32.9'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop stopColor='#9575CD' />
-          <stop offset='1' stopColor='#7E57C2' />
-        </linearGradient>
-      </defs>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Google Forms](https://forms.google.com) is Google's online survey and form tool that allows users to create forms, collect responses, and analyze results. As part of Google's productivity suite, Google Forms makes it easy to gather information, feedback, and data from users.
-
-Learn how to integrate the Google Forms tool in Sim to automatically read and process form responses in your workflows. This tutorial walks you through connecting Google Forms, retrieving responses, and using collected data to power automation. Perfect for syncing survey results, registrations, or feedback with your agents in real-time.
-
-With Google Forms, you can:
-
-- **Create surveys and forms**: Design custom forms for feedback, registration, quizzes, and more
-- **Collect responses automatically**: Gather data from users in real-time
-- **Analyze results**: View responses in Google Forms or export to Google Sheets for further analysis
-- **Collaborate easily**: Share forms and work with others to build and review questions
-- **Integrate with other Google services**: Connect with Google Sheets, Drive, and more
-
-In Sim, the Google Forms integration enables your agents to programmatically access form responses. This allows for powerful automation scenarios such as processing survey data, triggering workflows based on new submissions, and syncing form results with other tools. Your agents can fetch all responses for a form, retrieve a specific response, and use the data to drive intelligent automation. By connecting Sim with Google Forms, you can automate data collection, streamline feedback processing, and incorporate form responses into your agent's capabilities.
-{/* MANUAL-CONTENT-END */}
-
-## Usage Instructions
-
-Integrate Google Forms into your workflow. Provide a Form ID to list responses, or specify a Response ID to fetch a single response. Requires OAuth.
-
-
-
-## Tools
-
-### `google_forms_get_responses`
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| formId | string | Yes | The ID of the Google Form |
-| responseId | string | No | If provided, returns this specific response |
-| pageSize | number | No | Max responses to return (service may return fewer). Defaults to 5000 |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `data` | json | Response or list of responses |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `google_forms`

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

@@ -1,211 +0,0 @@
----
-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
-
-Integrate Hunter into the workflow. Can search domains, find email addresses, verify email addresses, discover companies, find companies, and count email addresses. Requires API Key.
-
-
-
-## 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/en/tools/linkup.mdx

@@ -1,77 +0,0 @@
----
-title: Linkup
-description: Search the web with Linkup
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="linkup"
-  color="#D6D3C7"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      viewBox='0 0 24 24'
-      
-      
-      fill='none'
-    >
-      <path
-        d='M20.2 14.1c-.4-.3-1.6-.4-2.9-.2.5-1.4 1.3-3.9.1-5-.6-.5-1.5-.7-2.6-.5-.3 0-.6.1-1 .2-1.1-1.6-2.4-2.5-3.8-2.5-1.6 0-3.1 1-4.1 2.9-1.2 2.1-1.9 5.1-1.9 8.8v.03l.4.3c3-.9 7.5-2.3 10.7-2.9 0 .9.1 1.9.1 2.8v.03l.4.3c.1 0 5.4-1.7 5.3-3.3 0-.2-.1-.5-.3-.7zM19.9 14.7c.03.4-1.7 1.4-4 2.3.5-.7 1-1.6 1.3-2.5 1.4-.1 2.4-.1 2.7.2zM16.4 14.6c-.3.7-.7 1.4-1.2 2-.02-.6-.1-1.2-.2-1.8.4-.1.9-.1 1.4-.2zM16.5 9.4c.8.7.9 2.4.1 5.1-.5.1-1 .1-1.5.2-.3-2-.9-3.8-1.7-5.3.3-.1.6-.2.8-.2.9-.1 1.7.05 2.3.2zM9.5 6.8c1.2 0 2.3.7 3.2 2.1-2.8 1.1-5.9 3.4-8.4 7.8.2-5.1 1.9-9.9 5.2-9.9zM4.7 17c3.4-4.9 6.4-6.8 8.4-7.8.7 1.3 1.2 2.9 1.5 4.8-3.2.6-7.3 1.8-9.9 3z'
-        fill='currentColor'
-        stroke='currentColor'
-        strokeWidth='0.5'
-        strokeLinejoin='round'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[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:
-
-- **Real-time Information Access**: Agents can retrieve the latest information from the web, keeping responses current and relevant.
-- **Source Attribution**: All information comes with proper citations, ensuring transparency and credibility.
-- **Simple Implementation**: Add Linkup to your agents toolset with minimal configuration.
-- **Contextual Awareness**: Agents can use web information while maintaining their personality and conversational style.
-
-To implement Linkup in your agent, simply add the tool to your agent's configuration. Your agent will then be able to search the web whenever they need to answer questions requiring current information.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Linkup into the workflow. Can search the web. Requires API Key.
-
-
-
-## Tools
-
-### `linkup_search`
-
-Search the web for information using Linkup
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `q` | string | Yes | The search query |
-| `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 | 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 |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `linkup`

apps/docs/content/docs/en/tools/mail.mdx

@@ -1,70 +0,0 @@
----
-title: Mail
-description: Send emails using the internal mail service
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="mail"
-  color="#181C1E"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      
-      
-      viewBox='0 0 30 24'
-      fill='none'
-      xmlns='http://www.w3.org/2000/svg'
-    >
-      <path
-        d='M2.35742 5.83288L11.7674 12.1071C13.0656 12.9712 13.7141 13.404 14.4151 13.5725C15.0352 13.7208 15.681 13.7208 16.2998 13.5725C17.0008 13.404 17.6492 12.9712 18.9475 12.1071L28.3574 5.83288M8.82844 21.7219H21.8864C24.1513 21.7219 25.2837 21.7219 26.1492 21.2811C26.9097 20.8931 27.5278 20.2744 27.9152 19.5137C28.3574 18.6482 28.3574 17.5158 28.3574 15.2509V7.97102C28.3574 5.70616 28.3574 4.57373 27.9166 3.70823C27.5288 2.94727 26.9102 2.32858 26.1492 1.94084C25.2837 1.5 24.1513 1.5 21.8864 1.5H8.82844C6.56358 1.5 5.43115 1.5 4.56566 1.94084C3.80519 2.32881 3.187 2.94747 2.79961 3.70823C2.35742 4.57373 2.35742 5.70616 2.35742 7.97102V15.2509C2.35742 17.5158 2.35742 18.6482 2.79826 19.5137C3.186 20.2747 3.80469 20.8933 4.56566 21.2811C5.43115 21.7219 6.56358 21.7219 8.82844 21.7219Z'
-        stroke='currentColor'
-        strokeWidth='2.5'
-        strokeLinecap='round'
-        strokeLinejoin='round'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-The Mail block allows you to send emails directly from your workflows using Sim's own mail sending infrastructure powered by [Resend](https://resend.com/). This integration enables you to programmatically deliver notifications, alerts, and other important information to users' email addresses without requiring any external configuration or OAuth.
-
-Our internal mail service is designed for reliability and ease of use, making it ideal for automating communications and ensuring your messages reach recipients efficiently.
-{/* MANUAL-CONTENT-END */}
-
-## Usage Instructions
-
-Send emails directly using the internal mail service. Uses MAIL_BLOCK_FROM_ADDRESS if configured, otherwise falls back to FROM_EMAIL_ADDRESS. No external configuration or OAuth required. Perfect for sending notifications, alerts, or general purpose emails from your workflows. Supports HTML formatting.
-
-
-
-## Tools
-
-### `mail_send`
-
-Send an email using the internal mail service without requiring OAuth or external configuration
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `to` | string | Yes | Recipient email address |
-| `subject` | string | Yes | Email subject |
-| `body` | string | Yes | Email body content |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the email was sent successfully |
-| `to` | string | Recipient email address |
-| `subject` | string | Email subject |
-| `body` | string | Email body content |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `mail`

apps/docs/content/docs/en/tools/mcp.mdx

@@ -1,40 +0,0 @@
----
-title: MCP Tool
-description: Execute tools from Model Context Protocol (MCP) servers
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="mcp"
-  color="#181C1E"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      viewBox='0 0 24 24'
-      fill='none'
-      stroke='currentColor'
-      strokeWidth='2'
-      strokeLinecap='round'
-      strokeLinejoin='round'
-    >
-      <rect   x='2' y='2' rx='2' ry='2' />
-      <rect   x='2' y='14' rx='2' ry='2' />
-      <line x1='6' x2='6.01' y1='6' y2='6' />
-      <line x1='6' x2='6.01' y1='18' y2='18' />
-    </svg>`}
-/>
-
-## Usage Instructions
-
-Integrate MCP into the workflow. Can execute tools from MCP servers. Requires MCP servers in workspace settings.
-
-
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `mcp`

apps/docs/content/docs/en/tools/microsoft_planner.mdx

@@ -1,178 +0,0 @@
----
-title: Microsoft Planner
-description: Read and create tasks in Microsoft Planner
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="microsoft_planner"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"  fill='currentColor' viewBox='-1 -1 27 27' xmlns='http://www.w3.org/2000/svg'>
-      <defs>
-        <linearGradient
-          id='paint0_linear_3984_11038'
-          x1='6.38724'
-          y1='3.74167'
-          x2='2.15779'
-          y2='12.777'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop stopColor='#8752E0' />
-          <stop offset='1' stopColor='#541278' />
-        </linearGradient>
-        <linearGradient
-          id='paint1_linear_3984_11038'
-          x1='8.38032'
-          y1='11.0696'
-          x2='4.94062'
-          y2='7.69244'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop offset='0.12172' stopColor='#3D0D59' />
-          <stop offset='1' stopColor='#7034B0' stopOpacity='0' />
-        </linearGradient>
-        <linearGradient
-          id='paint2_linear_3984_11038'
-          x1='18.3701'
-          y1='-3.33385e-05'
-          x2='9.85717'
-          y2='20.4192'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop stopColor='#DB45E0' />
-          <stop offset='1' stopColor='#6C0F71' />
-        </linearGradient>
-        <linearGradient
-          id='paint3_linear_3984_11038'
-          x1='18.3701'
-          y1='-3.33385e-05'
-          x2='9.85717'
-          y2='20.4192'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop stopColor='#DB45E0' />
-          <stop offset='0.677403' stopColor='#A829AE' />
-          <stop offset='1' stopColor='#8F28B3' />
-        </linearGradient>
-        <linearGradient
-          id='paint4_linear_3984_11038'
-          x1='18.0002'
-          y1='7.49958'
-          x2='14.0004'
-          y2='23.9988'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop stopColor='#3DCBFF' />
-          <stop offset='1' stopColor='#00479E' />
-        </linearGradient>
-        <linearGradient
-          id='paint5_linear_3984_11038'
-          x1='18.2164'
-          y1='7.92626'
-          x2='10.5237'
-          y2='22.9363'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop stopColor='#3DCBFF' />
-          <stop offset='1' stopColor='#4A40D4' />
-        </linearGradient>
-      </defs>
-      <path
-        d='M8.25809 15.7412C7.22488 16.7744 5.54971 16.7744 4.5165 15.7412L0.774909 11.9996C-0.258303 10.9664 -0.258303 9.29129 0.774908 8.25809L4.5165 4.51655C5.54971 3.48335 7.22488 3.48335 8.25809 4.51655L11.9997 8.2581C13.0329 9.29129 13.0329 10.9664 11.9997 11.9996L8.25809 15.7412Z'
-        fill='url(#paint0_linear_3984_11038)'
-      />
-      <path
-        d='M8.25809 15.7412C7.22488 16.7744 5.54971 16.7744 4.5165 15.7412L0.774909 11.9996C-0.258303 10.9664 -0.258303 9.29129 0.774908 8.25809L4.5165 4.51655C5.54971 3.48335 7.22488 3.48335 8.25809 4.51655L11.9997 8.2581C13.0329 9.29129 13.0329 10.9664 11.9997 11.9996L8.25809 15.7412Z'
-        fill='url(#paint1_linear_3984_11038)'
-      />
-      <path
-        d='M0.774857 11.9999C1.80809 13.0331 3.48331 13.0331 4.51655 11.9999L15.7417 0.774926C16.7749 -0.258304 18.4501 -0.258309 19.4834 0.774914L23.225 4.51655C24.2583 5.54977 24.2583 7.22496 23.225 8.25819L11.9999 19.4832C10.9667 20.5164 9.29146 20.5164 8.25822 19.4832L0.774857 11.9999Z'
-        fill='url(#paint2_linear_3984_11038)'
-      />
-      <path
-        d='M0.774857 11.9999C1.80809 13.0331 3.48331 13.0331 4.51655 11.9999L15.7417 0.774926C16.7749 -0.258304 18.4501 -0.258309 19.4834 0.774914L23.225 4.51655C24.2583 5.54977 24.2583 7.22496 23.225 8.25819L11.9999 19.4832C10.9667 20.5164 9.29146 20.5164 8.25822 19.4832L0.774857 11.9999Z'
-        fill='url(#paint3_linear_3984_11038)'
-      />
-      <path
-        d='M4.51642 15.7413C5.54966 16.7746 7.22487 16.7746 8.25812 15.7413L15.7415 8.25803C16.7748 7.2248 18.45 7.2248 19.4832 8.25803L23.2249 11.9997C24.2582 13.0329 24.2582 14.7081 23.2249 15.7413L15.7415 23.2246C14.7083 24.2579 13.033 24.2579 11.9998 23.2246L4.51642 15.7413Z'
-        fill='url(#paint4_linear_3984_11038)'
-      />
-      <path
-        d='M4.51642 15.7413C5.54966 16.7746 7.22487 16.7746 8.25812 15.7413L15.7415 8.25803C16.7748 7.2248 18.45 7.2248 19.4832 8.25803L23.2249 11.9997C24.2582 13.0329 24.2582 14.7081 23.2249 15.7413L15.7415 23.2246C14.7083 24.2579 13.033 24.2579 11.9998 23.2246L4.51642 15.7413Z'
-        fill='url(#paint5_linear_3984_11038)'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Microsoft Planner](https://www.microsoft.com/en-us/microsoft-365/planner) is a task management tool that helps teams organize work visually using boards, tasks, and buckets. Integrated with Microsoft 365, it offers a simple, intuitive way to manage team projects, assign responsibilities, and track progress.
-
-With Microsoft Planner, you can:
-
-- **Create and manage tasks**: Add new tasks with due dates, priorities, and assigned users
-- **Organize with buckets**: Group tasks by phase, status, or category to reflect your team’s workflow
-- **Visualize project status**: Use boards, charts, and filters to monitor workload and track progress
-- **Stay integrated with Microsoft 365**: Seamlessly connect tasks with Teams, Outlook, and other Microsoft tools
-
-In Sim, the Microsoft Planner integration allows your agents to programmatically create, read, and manage tasks as part of their workflows. Agents can generate new tasks based on incoming requests, retrieve task details to drive decisions, and track status across projects — all without human intervention. Whether you're building workflows for client onboarding, internal project tracking, or follow-up task generation, integrating Microsoft Planner with Sim gives your agents a structured way to coordinate work, automate task creation, and keep teams aligned.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Microsoft Planner into the workflow. Can read and create tasks. Requires OAuth.
-
-
-
-## Tools
-
-### `microsoft_planner_read_task`
-
-Read tasks from Microsoft Planner - get all user tasks or all tasks from a specific plan
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `planId` | string | No | The ID of the plan to get tasks from \(if not provided, gets all user tasks\) |
-| `taskId` | string | No | The ID of the task to get |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether tasks were retrieved successfully |
-| `tasks` | array | Array of task objects with filtered properties |
-| `metadata` | object | Metadata including planId, userId, and planUrl |
-
-### `microsoft_planner_create_task`
-
-Create a new task in Microsoft Planner
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `planId` | string | Yes | The ID of the plan where the task will be created |
-| `title` | string | Yes | The title of the task |
-| `description` | string | No | The description of the task |
-| `dueDateTime` | string | No | The due date and time for the task \(ISO 8601 format\) |
-| `assigneeUserId` | string | No | The user ID to assign the task to |
-| `bucketId` | string | No | The bucket ID to place the task in |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the task was created successfully |
-| `task` | object | The created task object with all properties |
-| `metadata` | object | Metadata including planId, taskId, and taskUrl |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `microsoft_planner`

apps/docs/content/docs/en/tools/mongodb.mdx

@@ -1,264 +0,0 @@
----
-title: MongoDB
-description: Connect to MongoDB database
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="mongodb"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"  xmlns='http://www.w3.org/2000/svg' viewBox='0 0 128 128'>
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='currentColor'
-        d='M88.038 42.812c1.605 4.643 2.761 9.383 3.141 14.296.472 6.095.256 12.147-1.029 18.142-.035.165-.109.32-.164.48-.403.001-.814-.049-1.208.012-3.329.523-6.655 1.065-9.981 1.604-3.438.557-6.881 1.092-10.313 1.687-1.216.21-2.721-.041-3.212 1.641-.014.046-.154.054-.235.08l.166-10.051-.169-24.252 1.602-.275c2.62-.429 5.24-.864 7.862-1.281 3.129-.497 6.261-.98 9.392-1.465 1.381-.215 2.764-.412 4.148-.618z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#45A538'
-        d='M61.729 110.054c-1.69-1.453-3.439-2.842-5.059-4.37-8.717-8.222-15.093-17.899-18.233-29.566-.865-3.211-1.442-6.474-1.627-9.792-.13-2.322-.318-4.665-.154-6.975.437-6.144 1.325-12.229 3.127-18.147l.099-.138c.175.233.427.439.516.702 1.759 5.18 3.505 10.364 5.242 15.551 5.458 16.3 10.909 32.604 16.376 48.9.107.318.384.579.583.866l-.87 2.969z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#46A037'
-        d='M88.038 42.812c-1.384.206-2.768.403-4.149.616-3.131.485-6.263.968-9.392 1.465-2.622.417-5.242.852-7.862 1.281l-1.602.275-.012-1.045c-.053-.859-.144-1.717-.154-2.576-.069-5.478-.112-10.956-.18-16.434-.042-3.429-.105-6.857-.175-10.285-.043-2.13-.089-4.261-.185-6.388-.052-1.143-.236-2.28-.311-3.423-.042-.657.016-1.319.029-1.979.817 1.583 1.616 3.178 2.456 4.749 1.327 2.484 3.441 4.314 5.344 6.311 7.523 7.892 12.864 17.068 16.193 27.433z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#409433'
-        d='M65.036 80.753c.081-.026.222-.034.235-.08.491-1.682 1.996-1.431 3.212-1.641 3.432-.594 6.875-1.13 10.313-1.687 3.326-.539 6.652-1.081 9.981-1.604.394-.062.805-.011 1.208-.012-.622 2.22-1.112 4.488-1.901 6.647-.896 2.449-1.98 4.839-3.131 7.182a49.142 49.142 0 01-6.353 9.763c-1.919 2.308-4.058 4.441-6.202 6.548-1.185 1.165-2.582 2.114-3.882 3.161l-.337-.23-1.214-1.038-1.256-2.753a41.402 41.402 0 01-1.394-9.838l.023-.561.171-2.426c.057-.828.133-1.655.168-2.485.129-2.982.241-5.964.359-8.946z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#4FAA41'
-        d='M65.036 80.753c-.118 2.982-.23 5.964-.357 8.947-.035.83-.111 1.657-.168 2.485l-.765.289c-1.699-5.002-3.399-9.951-5.062-14.913-2.75-8.209-5.467-16.431-8.213-24.642a4498.887 4498.887 0 00-6.7-19.867c-.105-.31-.407-.552-.617-.826l4.896-9.002c.168.292.39.565.496.879a6167.476 6167.476 0 016.768 20.118c2.916 8.73 5.814 17.467 8.728 26.198.116.349.308.671.491 1.062l.67-.78-.167 10.052z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#4AA73C'
-        d='M43.155 32.227c.21.274.511.516.617.826a4498.887 4498.887 0 016.7 19.867c2.746 8.211 5.463 16.433 8.213 24.642 1.662 4.961 3.362 9.911 5.062 14.913l.765-.289-.171 2.426-.155.559c-.266 2.656-.49 5.318-.814 7.968-.163 1.328-.509 2.632-.772 3.947-.198-.287-.476-.548-.583-.866-5.467-16.297-10.918-32.6-16.376-48.9a3888.972 3888.972 0 00-5.242-15.551c-.089-.263-.34-.469-.516-.702l3.272-8.84z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#57AE47'
-        d='M65.202 70.702l-.67.78c-.183-.391-.375-.714-.491-1.062-2.913-8.731-5.812-17.468-8.728-26.198a6167.476 6167.476 0 00-6.768-20.118c-.105-.314-.327-.588-.496-.879l6.055-7.965c.191.255.463.482.562.769 1.681 4.921 3.347 9.848 5.003 14.778 1.547 4.604 3.071 9.215 4.636 13.813.105.308.47.526.714.786l.012 1.045c.058 8.082.115 16.167.171 24.251z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#60B24F'
-        d='M65.021 45.404c-.244-.26-.609-.478-.714-.786-1.565-4.598-3.089-9.209-4.636-13.813-1.656-4.93-3.322-9.856-5.003-14.778-.099-.287-.371-.514-.562-.769 1.969-1.928 3.877-3.925 5.925-5.764 1.821-1.634 3.285-3.386 3.352-5.968.003-.107.059-.214.145-.514l.519 1.306c-.013.661-.072 1.322-.029 1.979.075 1.143.259 2.28.311 3.423.096 2.127.142 4.258.185 6.388.069 3.428.132 6.856.175 10.285.067 5.478.111 10.956.18 16.434.008.861.098 1.718.152 2.577z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#A9AA88'
-        d='M62.598 107.085c.263-1.315.609-2.62.772-3.947.325-2.649.548-5.312.814-7.968l.066-.01.066.011a41.402 41.402 0 001.394 9.838c-.176.232-.425.439-.518.701-.727 2.05-1.412 4.116-2.143 6.166-.1.28-.378.498-.574.744l-.747-2.566.87-2.969z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#B6B598'
-        d='M62.476 112.621c.196-.246.475-.464.574-.744.731-2.05 1.417-4.115 2.143-6.166.093-.262.341-.469.518-.701l1.255 2.754c-.248.352-.59.669-.728 1.061l-2.404 7.059c-.099.283-.437.483-.663.722l-.695-3.985z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#C2C1A7'
-        d='M63.171 116.605c.227-.238.564-.439.663-.722l2.404-7.059c.137-.391.48-.709.728-1.061l1.215 1.037c-.587.58-.913 1.25-.717 2.097l-.369 1.208c-.168.207-.411.387-.494.624-.839 2.403-1.64 4.819-2.485 7.222-.107.305-.404.544-.614.812-.109-1.387-.22-2.771-.331-4.158z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#CECDB7'
-        d='M63.503 120.763c.209-.269.506-.508.614-.812.845-2.402 1.646-4.818 2.485-7.222.083-.236.325-.417.494-.624l-.509 5.545c-.136.157-.333.294-.398.477-.575 1.614-1.117 3.24-1.694 4.854-.119.333-.347.627-.525.938-.158-.207-.441-.407-.454-.623-.051-.841-.016-1.688-.013-2.533z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#DBDAC7'
-        d='M63.969 123.919c.178-.312.406-.606.525-.938.578-1.613 1.119-3.239 1.694-4.854.065-.183.263-.319.398-.477l.012 3.64-1.218 3.124-1.411-.495z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#EBE9DC'
-        d='M65.38 124.415l1.218-3.124.251 3.696-1.469-.572z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#CECDB7'
-        d='M67.464 110.898c-.196-.847.129-1.518.717-2.097l.337.23-1.054 1.867z'
-      />
-      <path
-        fillRule='evenodd'
-        clipRule='evenodd'
-        fill='#4FAA41'
-        d='M64.316 95.172l-.066-.011-.066.01.155-.559-.023.56z'
-      />
-    </svg>`}
-/>
-
-## Usage Instructions
-
-Integrate MongoDB into the workflow. Can find, insert, update, delete, and aggregate data.
-
-
-
-## Tools
-
-### `mongodb_query`
-
-Execute find operation on MongoDB collection
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MongoDB server hostname or IP address |
-| `port` | number | Yes | MongoDB server port \(default: 27017\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | No | MongoDB username |
-| `password` | string | No | MongoDB password |
-| `authSource` | string | No | Authentication database |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `collection` | string | Yes | Collection name to query |
-| `query` | string | No | MongoDB query filter as JSON string |
-| `limit` | number | No | Maximum number of documents to return |
-| `sort` | string | No | Sort criteria as JSON string |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `documents` | array | Array of documents returned from the query |
-| `documentCount` | number | Number of documents returned |
-
-### `mongodb_insert`
-
-Insert documents into MongoDB collection
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MongoDB server hostname or IP address |
-| `port` | number | Yes | MongoDB server port \(default: 27017\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | No | MongoDB username |
-| `password` | string | No | MongoDB password |
-| `authSource` | string | No | Authentication database |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `collection` | string | Yes | Collection name to insert into |
-| `documents` | array | Yes | Array of documents to insert |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `documentCount` | number | Number of documents inserted |
-| `insertedId` | string | ID of inserted document \(single insert\) |
-| `insertedIds` | array | Array of inserted document IDs \(multiple insert\) |
-
-### `mongodb_update`
-
-Update documents in MongoDB collection
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MongoDB server hostname or IP address |
-| `port` | number | Yes | MongoDB server port \(default: 27017\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | No | MongoDB username |
-| `password` | string | No | MongoDB password |
-| `authSource` | string | No | Authentication database |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `collection` | string | Yes | Collection name to update |
-| `filter` | string | Yes | Filter criteria as JSON string |
-| `update` | string | Yes | Update operations as JSON string |
-| `upsert` | boolean | No | Create document if not found |
-| `multi` | boolean | No | Update multiple documents |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `matchedCount` | number | Number of documents matched by filter |
-| `modifiedCount` | number | Number of documents modified |
-| `documentCount` | number | Total number of documents affected |
-| `insertedId` | string | ID of inserted document \(if upsert\) |
-
-### `mongodb_delete`
-
-Delete documents from MongoDB collection
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MongoDB server hostname or IP address |
-| `port` | number | Yes | MongoDB server port \(default: 27017\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | No | MongoDB username |
-| `password` | string | No | MongoDB password |
-| `authSource` | string | No | Authentication database |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `collection` | string | Yes | Collection name to delete from |
-| `filter` | string | Yes | Filter criteria as JSON string |
-| `multi` | boolean | No | Delete multiple documents |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `deletedCount` | number | Number of documents deleted |
-| `documentCount` | number | Total number of documents affected |
-
-### `mongodb_execute`
-
-Execute MongoDB aggregation pipeline
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MongoDB server hostname or IP address |
-| `port` | number | Yes | MongoDB server port \(default: 27017\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | No | MongoDB username |
-| `password` | string | No | MongoDB password |
-| `authSource` | string | No | Authentication database |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `collection` | string | Yes | Collection name to execute pipeline on |
-| `pipeline` | string | Yes | Aggregation pipeline as JSON string |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `documents` | array | Array of documents returned from aggregation |
-| `documentCount` | number | Number of documents returned |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `mongodb`

apps/docs/content/docs/en/tools/mysql.mdx

@@ -1,180 +0,0 @@
----
-title: MySQL
-description: Connect to MySQL database
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="mysql"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      
-      
-      viewBox='0 0 25.6 25.6'
-    >
-      <path
-        d='M179.076 94.886c-3.568-.1-6.336.268-8.656 1.25-.668.27-1.74.27-1.828 1.116.357.355.4.936.713 1.428.535.893 1.473 2.096 2.32 2.72l2.855 2.053c1.74 1.07 3.703 1.695 5.398 2.766.982.625 1.963 1.428 2.945 2.098.5.357.803.938 1.428 1.16v-.135c-.312-.4-.402-.98-.713-1.428l-1.34-1.293c-1.293-1.74-2.9-3.258-4.64-4.506-1.428-.982-4.55-2.32-5.13-3.97l-.088-.1c.98-.1 2.14-.447 3.078-.715 1.518-.4 2.9-.312 4.46-.713l2.143-.625v-.4c-.803-.803-1.383-1.874-2.23-2.632-2.275-1.963-4.775-3.882-7.363-5.488-1.383-.892-3.168-1.473-4.64-2.23-.537-.268-1.428-.402-1.74-.848-.805-.98-1.25-2.275-1.83-3.436l-3.658-7.763c-.803-1.74-1.295-3.48-2.275-5.086-4.596-7.585-9.594-12.18-17.268-16.687-1.65-.937-3.613-1.34-5.7-1.83l-3.346-.18c-.715-.312-1.428-1.16-2.053-1.562-2.543-1.606-9.102-5.086-10.977-.5-1.205 2.9 1.785 5.755 2.8 7.228.76 1.026 1.74 2.186 2.277 3.346.3.758.4 1.562.713 2.365.713 1.963 1.383 4.15 2.32 5.98.5.937 1.025 1.92 1.65 2.767.357.5.982.714 1.115 1.517-.625.893-.668 2.23-1.025 3.347-1.607 5.042-.982 11.288 1.293 15 .715 1.115 2.4 3.57 4.686 2.632 2.008-.803 1.56-3.346 2.14-5.577.135-.535.045-.892.312-1.25v.1l1.83 3.703c1.383 2.186 3.793 4.462 5.8 5.98 1.07.803 1.918 2.187 3.256 2.677v-.135h-.088c-.268-.4-.67-.58-1.027-.892-.803-.803-1.695-1.785-2.32-2.677-1.873-2.498-3.523-5.265-4.996-8.12-.715-1.383-1.34-2.9-1.918-4.283-.27-.536-.27-1.34-.715-1.606-.67.98-1.65 1.83-2.143 3.034-.848 1.918-.936 4.283-1.248 6.737-.18.045-.1 0-.18.1-1.426-.356-1.918-1.83-2.453-3.078-1.338-3.168-1.562-8.254-.402-11.913.312-.937 1.652-3.882 1.117-4.774-.27-.848-1.16-1.338-1.652-2.008-.58-.848-1.203-1.918-1.605-2.855-1.07-2.5-1.605-5.265-2.766-7.764-.537-1.16-1.473-2.365-2.232-3.435-.848-1.205-1.783-2.053-2.453-3.48-.223-.5-.535-1.294-.178-1.83.088-.357.268-.5.623-.58.58-.5 2.232.134 2.812.4 1.65.67 3.033 1.294 4.416 2.23.625.446 1.295 1.294 2.098 1.518h.938c1.428.312 3.033.1 4.37.5 2.365.76 4.506 1.874 6.426 3.08 5.844 3.703 10.664 8.968 13.92 15.26.535 1.026.758 1.963 1.25 3.034.938 2.187 2.098 4.417 3.033 6.56.938 2.097 1.83 4.24 3.168 5.98.67.937 3.346 1.427 4.55 1.918.893.4 2.275.76 3.08 1.25 1.516.937 3.033 2.008 4.46 3.034.713.534 2.945 1.65 3.078 2.54zm-45.5-38.772a7.09 7.09 0 0 0-1.828.223v.1h.088c.357.714.982 1.205 1.428 1.83l1.027 2.142.088-.1c.625-.446.938-1.16.938-2.23-.268-.312-.312-.625-.535-.937-.268-.446-.848-.67-1.206-1.026z'
-        transform='matrix(.390229 0 0 .38781 -46.300037 -16.856717)'
-        fillRule='evenodd'
-        fill='#00678c'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-The [MySQL](https://www.mysql.com/) tool enables you to connect to any MySQL database and perform a wide range of database operations directly within your agentic workflows. With secure connection handling and flexible configuration, you can easily manage and interact with your data.
-
-With the MySQL tool, you can:
-
-- **Query data**: Execute SELECT queries to retrieve data from your MySQL tables using the `mysql_query` operation.
-- **Insert records**: Add new rows to your tables with the `mysql_insert` operation by specifying the table and data to insert.
-- **Update records**: Modify existing data in your tables using the `mysql_update` operation, providing the table, new data, and WHERE conditions.
-- **Delete records**: Remove rows from your tables with the `mysql_delete` operation, specifying the table and WHERE conditions.
-- **Execute raw SQL**: Run any custom SQL command using the `mysql_execute` operation for advanced use cases.
-
-The MySQL tool is ideal for scenarios where your agents need to interact with structured data—such as automating reporting, syncing data between systems, or powering data-driven workflows. It streamlines database access, making it easy to read, write, and manage your MySQL data programmatically.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate MySQL into the workflow. Can query, insert, update, delete, and execute raw SQL.
-
-
-
-## Tools
-
-### `mysql_query`
-
-Execute SELECT query on MySQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MySQL server hostname or IP address |
-| `port` | number | Yes | MySQL server port \(default: 3306\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `query` | string | Yes | SQL SELECT query to execute |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Array of rows returned from the query |
-| `rowCount` | number | Number of rows returned |
-
-### `mysql_insert`
-
-Insert new record into MySQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MySQL server hostname or IP address |
-| `port` | number | Yes | MySQL server port \(default: 3306\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `table` | string | Yes | Table name to insert into |
-| `data` | object | Yes | Data to insert as key-value pairs |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Array of inserted rows |
-| `rowCount` | number | Number of rows inserted |
-
-### `mysql_update`
-
-Update existing records in MySQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MySQL server hostname or IP address |
-| `port` | number | Yes | MySQL server port \(default: 3306\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `table` | string | Yes | Table name to update |
-| `data` | object | Yes | Data to update as key-value pairs |
-| `where` | string | Yes | WHERE clause condition \(without WHERE keyword\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Array of updated rows |
-| `rowCount` | number | Number of rows updated |
-
-### `mysql_delete`
-
-Delete records from MySQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MySQL server hostname or IP address |
-| `port` | number | Yes | MySQL server port \(default: 3306\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `table` | string | Yes | Table name to delete from |
-| `where` | string | Yes | WHERE clause condition \(without WHERE keyword\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Array of deleted rows |
-| `rowCount` | number | Number of rows deleted |
-
-### `mysql_execute`
-
-Execute raw SQL query on MySQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | MySQL server hostname or IP address |
-| `port` | number | Yes | MySQL server port \(default: 3306\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `query` | string | Yes | Raw SQL query to execute |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Array of rows returned from the query |
-| `rowCount` | number | Number of rows affected |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `mysql`

apps/docs/content/docs/en/tools/onedrive.mdx

@@ -1,125 +0,0 @@
----
-title: OneDrive
-description: Create, upload, and list files
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="onedrive"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"  fill='currentColor' viewBox='0 0 32 32' xmlns='http://www.w3.org/2000/svg'>
-      <g>
-        <path
-          d='M12.20245,11.19292l.00031-.0011,6.71765,4.02379,4.00293-1.68451.00018.00068A6.4768,6.4768,0,0,1,25.5,13c.14764,0,.29358.0067.43878.01639a10.00075,10.00075,0,0,0-18.041-3.01381C7.932,10.00215,7.9657,10,8,10A7.96073,7.96073,0,0,1,12.20245,11.19292Z'
-          fill='#0364b8'
-        />
-        <path
-          d='M12.20276,11.19182l-.00031.0011A7.96073,7.96073,0,0,0,8,10c-.0343,0-.06805.00215-.10223.00258A7.99676,7.99676,0,0,0,1.43732,22.57277l5.924-2.49292,2.63342-1.10819,5.86353-2.46746,3.06213-1.28859Z'
-          fill='#0078d4'
-        />
-        <path
-          d='M25.93878,13.01639C25.79358,13.0067,25.64764,13,25.5,13a6.4768,6.4768,0,0,0-2.57648.53178l-.00018-.00068-4.00293,1.68451,1.16077.69528L23.88611,18.19l1.66009.99438,5.67633,3.40007a6.5002,6.5002,0,0,0-5.28375-9.56805Z'
-          fill='#1490df'
-        />
-        <path
-          d='M25.5462,19.18437,23.88611,18.19l-3.80493-2.2791-1.16077-.69528L15.85828,16.5042,9.99475,18.97166,7.36133,20.07985l-5.924,2.49292A7.98889,7.98889,0,0,0,8,26H25.5a6.49837,6.49837,0,0,0,5.72253-3.41556Z'
-          fill='#28a8ea'
-        />
-      </g>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[OneDrive](https://onedrive.live.com) is Microsoft’s cloud storage and file synchronization service that allows users to securely store, access, and share files across devices. Integrated deeply into the Microsoft 365 ecosystem, OneDrive supports seamless collaboration, version control, and real-time access to content across teams and organizations.
-
-Learn how to integrate the OneDrive tool in Sim to automatically pull, manage, and organize your cloud files within your workflows. This tutorial walks you through connecting OneDrive, setting up file access, and using stored content to power automation. Ideal for syncing essential documents and media with your agents in real time.
-
-With OneDrive, you can:
-
-- **Store files securely in the cloud**: Upload and access documents, images, and other files from any device
-- **Organize your content**: Create structured folders and manage file versions with ease
-- **Collaborate in real time**: Share files, edit them simultaneously with others, and track changes
-- **Access across devices**: Use OneDrive from desktop, mobile, and web platforms
-- **Integrate with Microsoft 365**: Work seamlessly with Word, Excel, PowerPoint, and Teams
-- **Control permissions**: Share files and folders with custom access settings and expiration controls
-
-In Sim, the OneDrive integration enables your agents to directly interact with your cloud storage. Agents can upload new files to specific folders, retrieve and read existing files, and list folder contents to dynamically organize and access information. This integration allows your agents to incorporate file operations into intelligent workflows — automating document intake, content analysis, and structured storage management. By connecting Sim with OneDrive, you empower your agents to manage and use cloud documents programmatically, eliminating manual steps and enhancing automation with secure, real-time file access.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate OneDrive into the workflow. Can create, upload, and list files. Requires OAuth.
-
-
-
-## Tools
-
-### `onedrive_upload`
-
-Upload a file to OneDrive
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `fileName` | string | Yes | The name of the file to upload |
-| `content` | string | Yes | The content of the file to upload |
-| `folderSelector` | string | No | Select the folder to upload the file to |
-| `manualFolderId` | string | No | Manually entered folder ID \(advanced mode\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the file was uploaded successfully |
-| `file` | object | The uploaded file object with metadata including id, name, webViewLink, webContentLink, and timestamps |
-
-### `onedrive_create_folder`
-
-Create a new folder in OneDrive
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `folderName` | string | Yes | Name of the folder to create |
-| `folderSelector` | string | No | Select the parent folder to create the folder in |
-| `manualFolderId` | string | No | Manually entered parent folder ID \(advanced mode\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the folder was created successfully |
-| `file` | object | The created folder object with metadata including id, name, webViewLink, and timestamps |
-
-### `onedrive_list`
-
-List files and folders in OneDrive
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `folderSelector` | string | No | Select the folder to list files from |
-| `manualFolderId` | string | No | The manually entered folder ID \(advanced mode\) |
-| `query` | string | No | A query to filter the files |
-| `pageSize` | number | No | The number of files to return |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether files were listed successfully |
-| `files` | array | Array of file and folder objects with metadata |
-| `nextPageToken` | string | Token for retrieving the next page of results \(optional\) |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `onedrive`

apps/docs/content/docs/en/tools/parallel_ai.mdx

@@ -1,106 +0,0 @@
----
-title: Parallel AI
-description: Search with Parallel AI
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="parallel_ai"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      fill='currentColor'
-      
-      
-      viewBox='0 0 271 270'
-      xmlns='http://www.w3.org/2000/svg'
-    >
-      <path
-        d='M267.804 105.65H193.828C194.026 106.814 194.187 107.996 194.349 109.178H76.6703C76.4546 110.736 76.2388 112.312 76.0591 113.87H1.63342C1.27387 116.198 0.950289 118.543 0.698608 120.925H75.3759C75.2501 122.483 75.1602 124.059 75.0703 125.617H195.949C196.003 126.781 196.057 127.962 196.093 129.144H270.68V125.384C270.195 118.651 269.242 112.061 267.804 105.65Z'
-        fill='#1D1C1A'
-      />
-      <path
-        d='M195.949 144.401H75.0703C75.1422 145.977 75.2501 147.535 75.3759 149.093H0.698608C0.950289 151.457 1.2559 153.802 1.63342 156.148H76.0591C76.2388 157.724 76.4366 159.282 76.6703 160.84H194.349C194.187 162.022 194.008 163.186 193.828 164.367H267.804C269.242 157.957 270.195 151.367 270.68 144.634V140.874H196.093C196.057 142.055 196.003 143.219 195.949 144.401Z'
-        fill='#1D1C1A'
-      />
-      <path
-        d='M190.628 179.642H80.3559C80.7514 181.218 81.1828 182.776 81.6143 184.334H9.30994C10.2448 186.715 11.2515 189.061 12.3121 191.389H83.7536C84.2749 192.965 84.7962 194.523 85.3535 196.08H185.594C185.163 197.262 184.732 198.426 184.282 199.608H254.519C258.6 192.177 261.98 184.316 264.604 176.114H191.455C191.185 177.296 190.898 178.46 190.61 179.642H190.628Z'
-        fill='#1D1C1A'
-      />
-      <path
-        d='M177.666 214.883H93.3352C94.1082 216.458 94.9172 218.034 95.7441 219.574H29.8756C31.8351 221.992 33.8666 224.337 35.9699 226.63H99.6632C100.598 228.205 101.551 229.781 102.522 231.321H168.498C167.761 232.503 167.006 233.685 166.233 234.849H226.762C234.474 227.847 241.36 219.95 247.292 211.355H179.356C178.799 212.537 178.26 213.719 177.684 214.883H177.666Z'
-        fill='#1D1C1A'
-      />
-      <path
-        d='M154.943 250.106H116.058C117.371 251.699 118.701 253.257 120.067 254.797H73.021C91.6094 264.431 112.715 269.946 135.096 270C135.24 270 135.366 270 135.492 270C135.618 270 135.761 270 135.887 270C164.04 269.911 190.178 261.28 211.805 246.56H157.748C156.813 247.742 155.878 248.924 154.925 250.088L154.943 250.106Z'
-        fill='#1D1C1A'
-      />
-      <path
-        d='M116.059 19.9124H154.943C155.896 21.0764 156.831 22.2582 157.766 23.4401H211.823C190.179 8.72065 164.058 0.0895344 135.906 0C135.762 0 135.636 0 135.51 0C135.384 0 135.24 0 135.115 0C112.715 0.0716275 91.6277 5.56904 73.0393 15.2029H120.086C118.719 16.7429 117.389 18.3187 116.077 19.8945L116.059 19.9124Z'
-        fill='#1D1C1A'
-      />
-      <path
-        d='M93.3356 55.1532H177.667C178.242 56.3171 178.799 57.499 179.339 58.6808H247.274C241.342 50.0855 234.457 42.1886 226.744 35.187H166.215C166.988 36.351 167.743 37.5328 168.48 38.7147H102.504C101.533 40.2726 100.58 41.8305 99.6456 43.4063H35.9523C33.831 45.6804 31.7996 48.0262 29.858 50.4616H95.7265C94.8996 52.0195 94.1086 53.5774 93.3176 55.1532H93.3356Z'
-        fill='#1D1C1A'
-      />
-      <path
-        d='M80.3736 90.3758H190.646C190.933 91.5398 191.221 92.7216 191.491 93.9035H264.64C262.015 85.7021 258.636 77.841 254.555 70.4097H184.318C184.767 71.5736 185.199 72.7555 185.63 73.9373H85.3893C84.832 75.4952 84.2927 77.0531 83.7893 78.6289H12.3479C11.2872 80.9389 10.2805 83.2847 9.3457 85.6842H81.65C81.2186 87.2421 80.7871 88.8 80.3916 90.3758H80.3736Z'
-        fill='#1D1C1A'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Parallel AI](https://parallel.ai/) is an advanced web search and content extraction platform designed to deliver comprehensive, high-quality results for any query. By leveraging intelligent processing and large-scale data extraction, Parallel AI enables users and agents to access, analyze, and synthesize information from across the web with speed and accuracy.
-
-With Parallel AI, you can:
-
-- **Search the web intelligently**: Retrieve relevant, up-to-date information from a wide range of sources  
-- **Extract and summarize content**: Get concise, meaningful excerpts from web pages and documents  
-- **Customize search objectives**: Tailor queries to specific needs or questions for targeted results  
-- **Process results at scale**: Handle large volumes of search results with advanced processing options  
-- **Integrate with workflows**: Use Parallel AI within Sim to automate research, content gathering, and knowledge extraction  
-- **Control output granularity**: Specify the number of results and the amount of content per result  
-- **Secure API access**: Protect your searches and data with API key authentication
-
-In Sim, the Parallel AI integration empowers your agents to perform web searches and extract content programmatically. This enables powerful automation scenarios such as real-time research, competitive analysis, content monitoring, and knowledge base creation. By connecting Sim with Parallel AI, you unlock the ability for agents to gather, process, and utilize web data as part of your automated workflows.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Parallel AI into the workflow. Can search the web. Requires API Key.
-
-
-
-## Tools
-
-### `parallel_search`
-
-Search the web using Parallel AI. Provides comprehensive search results with intelligent processing and content extraction.
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `objective` | string | Yes | The search objective or question to answer |
-| `search_queries` | string | No | Optional comma-separated list of search queries to execute |
-| `processor` | string | No | Processing method: base or pro \(default: base\) |
-| `max_results` | number | No | Maximum number of results to return \(default: 5\) |
-| `max_chars_per_result` | number | No | Maximum characters per result \(default: 1500\) |
-| `apiKey` | string | Yes | Parallel AI API Key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `results` | array | Search results with excerpts from relevant pages |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `parallel_ai`

apps/docs/content/docs/en/tools/postgresql.mdx

@@ -1,188 +0,0 @@
----
-title: PostgreSQL
-description: Connect to PostgreSQL database
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="postgresql"
-  color="#336791"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      
-      
-      viewBox='-4 0 264 264'
-      xmlns='http://www.w3.org/2000/svg'
-      preserveAspectRatio='xMinYMin meet'
-    >
-      <path d='M255.008 158.086c-1.535-4.649-5.556-7.887-10.756-8.664-2.452-.366-5.26-.21-8.583.475-5.792 1.195-10.089 1.65-13.225 1.738 11.837-19.985 21.462-42.775 27.003-64.228 8.96-34.689 4.172-50.492-1.423-57.64C233.217 10.847 211.614.683 185.552.372c-13.903-.17-26.108 2.575-32.475 4.549-5.928-1.046-12.302-1.63-18.99-1.738-12.537-.2-23.614 2.533-33.079 8.15-5.24-1.772-13.65-4.27-23.362-5.864-22.842-3.75-41.252-.828-54.718 8.685C6.622 25.672-.937 45.684.461 73.634c.444 8.874 5.408 35.874 13.224 61.48 4.492 14.718 9.282 26.94 14.237 36.33 7.027 13.315 14.546 21.156 22.987 23.972 4.731 1.576 13.327 2.68 22.368-4.85 1.146 1.388 2.675 2.767 4.704 4.048 2.577 1.625 5.728 2.953 8.875 3.74 11.341 2.835 21.964 2.126 31.027-1.848.056 1.612.099 3.152.135 4.482.06 2.157.12 4.272.199 6.25.537 13.374 1.447 23.773 4.143 31.049.148.4.347 1.01.557 1.657 1.345 4.118 3.594 11.012 9.316 16.411 5.925 5.593 13.092 7.308 19.656 7.308 3.292 0 6.433-.432 9.188-1.022 9.82-2.105 20.973-5.311 29.041-16.799 7.628-10.86 11.336-27.217 12.007-52.99.087-.729.167-1.425.244-2.088l.16-1.362 1.797.158.463.031c10.002.456 22.232-1.665 29.743-5.154 5.935-2.754 24.954-12.795 20.476-26.351' />
-      <path
-        d='M237.906 160.722c-29.74 6.135-31.785-3.934-31.785-3.934 31.4-46.593 44.527-105.736 33.2-120.211-30.904-39.485-84.399-20.811-85.292-20.327l-.287.052c-5.876-1.22-12.451-1.946-19.842-2.067-13.456-.22-23.664 3.528-31.41 9.402 0 0-95.43-39.314-90.991 49.444.944 18.882 27.064 142.873 58.218 105.422 11.387-13.695 22.39-25.274 22.39-25.274 5.464 3.63 12.006 5.482 18.864 4.817l.533-.452c-.166 1.7-.09 3.363.213 5.332-8.026 8.967-5.667 10.541-21.711 13.844-16.235 3.346-6.698 9.302-.471 10.86 7.549 1.887 25.013 4.561 36.813-11.958l-.47 1.885c3.144 2.519 5.352 16.383 4.982 28.952-.37 12.568-.617 21.197 1.86 27.937 2.479 6.74 4.948 21.905 26.04 17.386 17.623-3.777 26.756-13.564 28.027-29.89.901-11.606 2.942-9.89 3.07-20.267l1.637-4.912c1.887-15.733.3-20.809 11.157-18.448l2.64.232c7.99.363 18.45-1.286 24.589-4.139 13.218-6.134 21.058-16.377 8.024-13.686h.002'
-        fill='#336791'
-      />
-      <path
-        d='M108.076 81.525c-2.68-.373-5.107-.028-6.335.902-.69.523-.904 1.129-.962 1.546-.154 1.105.62 2.327 1.096 2.957 1.346 1.784 3.312 3.01 5.258 3.28.282.04.563.058.842.058 3.245 0 6.196-2.527 6.456-4.392.325-2.336-3.066-3.893-6.355-4.35M196.86 81.599c-.256-1.831-3.514-2.353-6.606-1.923-3.088.43-6.082 1.824-5.832 3.659.2 1.427 2.777 3.863 5.827 3.863.258 0 .518-.017.78-.054 2.036-.282 3.53-1.575 4.24-2.32 1.08-1.136 1.706-2.402 1.591-3.225'
-        fill='#FFF'
-      />
-      <path
-        d='M247.802 160.025c-1.134-3.429-4.784-4.532-10.848-3.28-18.005 3.716-24.453 1.142-26.57-.417 13.995-21.32 25.508-47.092 31.719-71.137 2.942-11.39 4.567-21.968 4.7-30.59.147-9.463-1.465-16.417-4.789-20.665-13.402-17.125-33.072-26.311-56.882-26.563-16.369-.184-30.199 4.005-32.88 5.183-5.646-1.404-11.801-2.266-18.502-2.376-12.288-.199-22.91 2.743-31.704 8.74-3.82-1.422-13.692-4.811-25.765-6.756-20.872-3.36-37.458-.814-49.294 7.571-14.123 10.006-20.643 27.892-19.38 53.16.425 8.501 5.269 34.653 12.913 59.698 10.062 32.964 21 51.625 32.508 55.464 1.347.449 2.9.763 4.613.763 4.198 0 9.345-1.892 14.7-8.33a529.832 529.832 0 0 1 20.261-22.926c4.524 2.428 9.494 3.784 14.577 3.92.01.133.023.266.035.398a117.66 117.66 0 0 0-2.57 3.175c-3.522 4.471-4.255 5.402-15.592 7.736-3.225.666-11.79 2.431-11.916 8.435-.136 6.56 10.125 9.315 11.294 9.607 4.074 1.02 7.999 1.523 11.742 1.523 9.103 0 17.114-2.992 23.516-8.781-.197 23.386.778 46.43 3.586 53.451 2.3 5.748 7.918 19.795 25.664 19.794 2.604 0 5.47-.303 8.623-.979 18.521-3.97 26.564-12.156 29.675-30.203 1.665-9.645 4.522-32.676 5.866-45.03 2.836.885 6.487 1.29 10.434 1.289 8.232 0 17.731-1.749 23.688-4.514 6.692-3.108 18.768-10.734 16.578-17.36zm-44.106-83.48c-.061 3.647-.563 6.958-1.095 10.414-.573 3.717-1.165 7.56-1.314 12.225-.147 4.54.42 9.26.968 13.825 1.108 9.22 2.245 18.712-2.156 28.078a36.508 36.508 0 0 1-1.95-4.009c-.547-1.326-1.735-3.456-3.38-6.404-6.399-11.476-21.384-38.35-13.713-49.316 2.285-3.264 8.084-6.62 22.64-4.813zm-17.644-61.787c21.334.471 38.21 8.452 50.158 23.72 9.164 11.711-.927 64.998-30.14 110.969a171.33 171.33 0 0 0-.886-1.117l-.37-.462c7.549-12.467 6.073-24.802 4.759-35.738-.54-4.488-1.05-8.727-.92-12.709.134-4.22.692-7.84 1.232-11.34.663-4.313 1.338-8.776 1.152-14.037.139-.552.195-1.204.122-1.978-.475-5.045-6.235-20.144-17.975-33.81-6.422-7.475-15.787-15.84-28.574-21.482 5.5-1.14 13.021-2.203 21.442-2.016zM66.674 175.778c-5.9 7.094-9.974 5.734-11.314 5.288-8.73-2.912-18.86-21.364-27.791-50.624-7.728-25.318-12.244-50.777-12.602-57.916-1.128-22.578 4.345-38.313 16.268-46.769 19.404-13.76 51.306-5.524 64.125-1.347-.184.182-.376.352-.558.537-21.036 21.244-20.537 57.54-20.485 59.759-.002.856.07 2.068.168 3.735.362 6.105 1.036 17.467-.764 30.334-1.672 11.957 2.014 23.66 10.111 32.109a36.275 36.275 0 0 0 2.617 2.468c-3.604 3.86-11.437 12.396-19.775 22.426zm22.479-29.993c-6.526-6.81-9.49-16.282-8.133-25.99 1.9-13.592 1.199-25.43.822-31.79-.053-.89-.1-1.67-.127-2.285 3.073-2.725 17.314-10.355 27.47-8.028 4.634 1.061 7.458 4.217 8.632 9.645 6.076 28.103.804 39.816-3.432 49.229-.873 1.939-1.698 3.772-2.402 5.668l-.546 1.466c-1.382 3.706-2.668 7.152-3.465 10.424-6.938-.02-13.687-2.984-18.819-8.34zm1.065 37.9c-2.026-.506-3.848-1.385-4.917-2.114.893-.42 2.482-.992 5.238-1.56 13.337-2.745 15.397-4.683 19.895-10.394 1.031-1.31 2.2-2.794 3.819-4.602l.002-.002c2.411-2.7 3.514-2.242 5.514-1.412 1.621.67 3.2 2.702 3.84 4.938.303 1.056.643 3.06-.47 4.62-9.396 13.156-23.088 12.987-32.921 10.526zm69.799 64.952c-16.316 3.496-22.093-4.829-25.9-14.346-2.457-6.144-3.665-33.85-2.808-64.447.011-.407-.047-.8-.159-1.17a15.444 15.444 0 0 0-.456-2.162c-1.274-4.452-4.379-8.176-8.104-9.72-1.48-.613-4.196-1.738-7.46-.903.696-2.868 1.903-6.107 3.212-9.614l.549-1.475c.618-1.663 1.394-3.386 2.214-5.21 4.433-9.848 10.504-23.337 3.915-53.81-2.468-11.414-10.71-16.988-23.204-15.693-7.49.775-14.343 3.797-17.761 5.53-.735.372-1.407.732-2.035 1.082.954-11.5 4.558-32.992 18.04-46.59 8.489-8.56 19.794-12.788 33.568-12.56 27.14.444 44.544 14.372 54.366 25.979 8.464 10.001 13.047 20.076 14.876 25.51-13.755-1.399-23.11 1.316-27.852 8.096-10.317 14.748 5.644 43.372 13.315 57.129 1.407 2.521 2.621 4.7 3.003 5.626 2.498 6.054 5.732 10.096 8.093 13.046.724.904 1.426 1.781 1.96 2.547-4.166 1.201-11.649 3.976-10.967 17.847-.55 6.96-4.461 39.546-6.448 51.059-2.623 15.21-8.22 20.875-23.957 24.25zm68.104-77.936c-4.26 1.977-11.389 3.46-18.161 3.779-7.48.35-11.288-.838-12.184-1.569-.42-8.644 2.797-9.547 6.202-10.503.535-.15 1.057-.297 1.561-.473.313.255.656.508 1.032.756 6.012 3.968 16.735 4.396 31.874 1.271l.166-.033c-2.042 1.909-5.536 4.471-10.49 6.772z'
-        fill='#FFF'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-The [PostgreSQL](https://www.postgresql.org/) tool enables you to connect to any PostgreSQL database and perform a wide range of database operations directly within your agentic workflows. With secure connection handling and flexible configuration, you can easily manage and interact with your data.
-
-With the PostgreSQL tool, you can:
-
-- **Query data**: Execute SELECT queries to retrieve data from your PostgreSQL tables using the `postgresql_query` operation.
-- **Insert records**: Add new rows to your tables with the `postgresql_insert` operation by specifying the table and data to insert.
-- **Update records**: Modify existing data in your tables using the `postgresql_update` operation, providing the table, new data, and WHERE conditions.
-- **Delete records**: Remove rows from your tables with the `postgresql_delete` operation, specifying the table and WHERE conditions.
-- **Execute raw SQL**: Run any custom SQL command using the `postgresql_execute` operation for advanced use cases.
-
-The PostgreSQL tool is ideal for scenarios where your agents need to interact with structured data—such as automating reporting, syncing data between systems, or powering data-driven workflows. It streamlines database access, making it easy to read, write, and manage your PostgreSQL data programmatically.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate PostgreSQL into the workflow. Can query, insert, update, delete, and execute raw SQL.
-
-
-
-## Tools
-
-### `postgresql_query`
-
-Execute a SELECT query on PostgreSQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | PostgreSQL server hostname or IP address |
-| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `query` | string | Yes | SQL SELECT query to execute |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Array of rows returned from the query |
-| `rowCount` | number | Number of rows returned |
-
-### `postgresql_insert`
-
-Insert data into PostgreSQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | PostgreSQL server hostname or IP address |
-| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `table` | string | Yes | Table name to insert data into |
-| `data` | object | Yes | Data object to insert \(key-value pairs\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Inserted data \(if RETURNING clause used\) |
-| `rowCount` | number | Number of rows inserted |
-
-### `postgresql_update`
-
-Update data in PostgreSQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | PostgreSQL server hostname or IP address |
-| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `table` | string | Yes | Table name to update data in |
-| `data` | object | Yes | Data object with fields to update \(key-value pairs\) |
-| `where` | string | Yes | WHERE clause condition \(without WHERE keyword\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Updated data \(if RETURNING clause used\) |
-| `rowCount` | number | Number of rows updated |
-
-### `postgresql_delete`
-
-Delete data from PostgreSQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | PostgreSQL server hostname or IP address |
-| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `table` | string | Yes | Table name to delete data from |
-| `where` | string | Yes | WHERE clause condition \(without WHERE keyword\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Deleted data \(if RETURNING clause used\) |
-| `rowCount` | number | Number of rows deleted |
-
-### `postgresql_execute`
-
-Execute raw SQL query on PostgreSQL database
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `host` | string | Yes | PostgreSQL server hostname or IP address |
-| `port` | number | Yes | PostgreSQL server port \(default: 5432\) |
-| `database` | string | Yes | Database name to connect to |
-| `username` | string | Yes | Database username |
-| `password` | string | Yes | Database password |
-| `ssl` | string | No | SSL connection mode \(disabled, required, preferred\) |
-| `query` | string | Yes | Raw SQL query to execute |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `rows` | array | Array of rows returned from the query |
-| `rowCount` | number | Number of rows affected |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `postgresql`

apps/docs/content/docs/en/tools/qdrant.mdx

@@ -1,183 +0,0 @@
----
-title: Qdrant
-description: Use Qdrant vector database
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="qdrant"
-  color="#1A223F"
-  icon={true}
-  iconSvg={`<svg className="block-icon"  fill='none' viewBox='0 0 49 56' xmlns='http://www.w3.org/2000/svg'>
-      <g clipPath='url(#b)'>
-        <path
-          d='m38.489 51.477-1.1167-30.787-2.0223-8.1167 13.498 1.429v37.242l-8.2456 4.7589-2.1138-4.5259z'
-          clipRule='evenodd'
-          fill='#24386C'
-          fillRule='evenodd'
-        />
-        <path
-          d='m48.847 14-8.2457 4.7622-17.016-3.7326-19.917 8.1094-3.3183-9.139 12.122-7 12.126-7 12.123 7 12.126 7z'
-          clipRule='evenodd'
-          fill='#7589BE'
-          fillRule='evenodd'
-        />
-        <path
-          d='m0.34961 13.999 8.2457 4.7622 4.7798 14.215 16.139 12.913-4.9158 10.109-12.126-7.0004-12.123-7v-28z'
-          clipRule='evenodd'
-          fill='#B2BFE8'
-          fillRule='evenodd'
-        />
-        <path
-          d='m30.066 38.421-5.4666 8.059v9.5207l7.757-4.4756 3.9968-5.9681'
-          clipRule='evenodd'
-          fill='#24386C'
-          fillRule='evenodd'
-        />
-        <path
-          d='m24.602 36.962-7.7603-13.436 1.6715-4.4531 6.3544-3.0809 7.488 7.5343-7.7536 13.436z'
-          clipRule='evenodd'
-          fill='#7589BE'
-          fillRule='evenodd'
-        />
-        <path
-          d='m16.843 23.525 7.7569 4.4756v8.9585l-7.1741 0.3087-4.3397-5.5412 3.7569-8.2016z'
-          clipRule='evenodd'
-          fill='#B2BFE8'
-          fillRule='evenodd'
-        />
-        <path
-          d='m24.6 28 7.757-4.4752 5.2792 8.7903-6.3886 5.2784-6.6476-0.6346v-8.9589z'
-          clipRule='evenodd'
-          fill='#24386C'
-          fillRule='evenodd'
-        />
-        <path
-          d='m32.355 51.524 8.2457 4.476v-37.238l-8.0032-4.6189-7.9995-4.6189-8.0031 4.6189-7.9995 4.6189v18.479l7.9995 4.6189 8.0031 4.6193 7.757-4.4797v9.5244zm0-19.045-7.757 4.4793-7.7569-4.4793v-8.9549l7.7569-4.4792 7.757 4.4792v8.9549z'
-          clipRule='evenodd'
-          fill='#DC244C'
-          fillRule='evenodd'
-        />
-        <path d='m24.603 46.483v-9.5222l-7.7166-4.4411v9.5064l7.7166 4.4569z' fill='url(#a)' />
-      </g>
-      <defs>
-        <linearGradient
-          id='a'
-          x1='23.18'
-          x2='15.491'
-          y1='38.781'
-          y2='38.781'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop stopColor='#FF3364' offset='0' />
-          <stop stopColor='#C91540' stopOpacity='0' offset='1' />
-        </linearGradient>
-        <clipPath id='b'>
-          <rect transform='translate(.34961)'   fill='#fff' />
-        </clipPath>
-      </defs>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Qdrant](https://qdrant.tech) is an open-source vector database designed for efficient storage, management, and retrieval of high-dimensional vector embeddings. Qdrant enables fast and scalable semantic search, making it ideal for AI applications that require similarity search, recommendation systems, and contextual information retrieval.
-
-With Qdrant, you can:
-
-- **Store vector embeddings**: Efficiently manage and persist high-dimensional vectors at scale
-- **Perform semantic similarity search**: Find the most similar vectors to a query vector in real time
-- **Filter and organize data**: Use advanced filtering to narrow down search results based on metadata or payload
-- **Fetch specific points**: Retrieve vectors and their associated payloads by ID
-- **Scale seamlessly**: Handle large collections and high-throughput workloads
-
-In Sim, the Qdrant integration enables your agents to interact with Qdrant programmatically as part of their workflows. Supported operations include:
-
-- **Upsert**: Insert or update points (vectors and payloads) in a Qdrant collection
-- **Search**: Perform similarity search to find vectors most similar to a given query vector, with optional filtering and result customization
-- **Fetch**: Retrieve specific points from a collection by their IDs, with options to include payloads and vectors
-
-This integration allows your agents to leverage powerful vector search and management capabilities, enabling advanced automation scenarios such as semantic search, recommendation, and contextual retrieval. By connecting Sim with Qdrant, you can build agents that understand context, retrieve relevant information from large datasets, and deliver more intelligent and personalized responses—all without managing complex infrastructure.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Qdrant into the workflow. Can upsert, search, and fetch points. Requires API Key.
-
-
-
-## Tools
-
-### `qdrant_upsert_points`
-
-Insert or update points in a Qdrant collection
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `url` | string | Yes | Qdrant base URL |
-| `apiKey` | string | No | Qdrant API key \(optional\) |
-| `collection` | string | Yes | Collection name |
-| `points` | array | Yes | Array of points to upsert |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `status` | string | Status of the upsert operation |
-| `data` | object | Result data from the upsert operation |
-
-### `qdrant_search_vector`
-
-Search for similar vectors in a Qdrant collection
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `url` | string | Yes | Qdrant base URL |
-| `apiKey` | string | No | Qdrant API key \(optional\) |
-| `collection` | string | Yes | Collection name |
-| `vector` | array | Yes | Vector to search for |
-| `limit` | number | No | Number of results to return |
-| `filter` | object | No | Filter to apply to the search |
-| `with_payload` | boolean | No | Include payload in response |
-| `with_vector` | boolean | No | Include vector in response |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `data` | array | Vector search results with ID, score, payload, and optional vector data |
-| `status` | string | Status of the search operation |
-
-### `qdrant_fetch_points`
-
-Fetch points by ID from a Qdrant collection
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `url` | string | Yes | Qdrant base URL |
-| `apiKey` | string | No | Qdrant API key \(optional\) |
-| `collection` | string | Yes | Collection name |
-| `ids` | array | Yes | Array of point IDs to fetch |
-| `with_payload` | boolean | No | Include payload in response |
-| `with_vector` | boolean | No | Include vector in response |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `data` | array | Fetched points with ID, payload, and optional vector data |
-| `status` | string | Status of the fetch operation |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `qdrant`

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

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

apps/docs/content/docs/en/tools/schedule.mdx

@@ -1,42 +0,0 @@
----
-title: Schedule
-description: Trigger workflow execution on a schedule
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="schedule"
-  color="#7B68EE"
-  icon={true}
-  iconSvg={`<svg className="block-icon"
-      
-      xmlns='http://www.w3.org/2000/svg'
-      
-      
-      viewBox='0 0 24 24'
-      fill='none'
-      stroke='currentColor'
-      strokeWidth='2'
-      strokeLinecap='round'
-      strokeLinejoin='round'
-    >
-      <path d='M8 2v4' />
-      <path d='M16 2v4' />
-      <rect   x='3' y='4' rx='2' />
-      <path d='M3 10h18' />
-    </svg>`}
-/>
-
-## Usage Instructions
-
-Integrate Schedule into the workflow. Can trigger a workflow on a schedule configuration.
-
-
-
-
-
-## Notes
-
-- Category: `triggers`
-- Type: `schedule`

apps/docs/content/docs/en/tools/sharepoint.mdx

@@ -1,132 +0,0 @@
----
-title: Sharepoint
-description: Read and create pages
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="sharepoint"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"  fill='currentColor' viewBox='0 0 32 32' xmlns='http://www.w3.org/2000/svg'>
-      <circle fill='#036C70' cx='16.31' cy='8.90' r='8.90' />
-      <circle fill='#1A9BA1' cx='23.72' cy='17.05' r='8.15' />
-      <circle fill='#37C6D0' cx='17.42' cy='24.83' r='6.30' />
-      <path
-        fill='#000000'
-        opacity='0.1'
-        d='M17.79,8.03v15.82c0,0.55-0.34,1.04-0.85,1.25c-0.16,0.07-0.34,0.10-0.51,0.10H11.13c-0.01-0.13-0.01-0.24-0.01-0.37c0-0.12,0-0.25,0.01-0.37c0.14-2.37,1.59-4.46,3.77-5.40v-1.38c-4.85-0.77-8.15-5.32-7.39-10.17c0.01-0.03,0.01-0.07,0.02-0.10c0.04-0.25,0.09-0.50,0.16-0.74h8.74c0.74,0,1.36,0.60,1.36,1.36z'
-      />
-      <path
-        fill='#000000'
-        opacity='0.2'
-        d='M15.69,7.41H7.54c-0.82,4.84,2.43,9.43,7.27,10.25c0.15,0.02,0.29,0.05,0.44,0.06c-2.30,1.09-3.97,4.18-4.12,6.73c-0.01,0.12-0.02,0.25-0.01,0.37c0,0.13,0,0.24,0.01,0.37c0.01,0.25,0.05,0.50,0.10,0.74h4.47c0.55,0,1.04-0.34,1.25-0.85c0.07-0.16,0.10-0.34,0.10-0.51V8.77c0-0.75-0.61-1.36-1.36-1.36z'
-      />
-      <path
-        fill='#000000'
-        opacity='0.2'
-        d='M15.69,7.41H7.54c-0.82,4.84,2.43,9.43,7.27,10.26c0.10,0.02,0.20,0.03,0.30,0.05c-2.22,1.17-3.83,4.26-3.97,6.75h4.56c0.75,0,1.35-0.61,1.36-1.36V8.77c0-0.75-0.61-1.36-1.36-1.36z'
-      />
-      <path
-        fill='#000000'
-        opacity='0.2'
-        d='M14.95,7.41H7.54c-0.78,4.57,2.08,8.97,6.58,10.11c-1.84,2.43-2.27,5.61-2.58,7.22h3.82c0.75,0,1.35-0.61,1.36-1.36V8.77c0-0.75-0.61-1.36-1.36-1.36z'
-      />
-      <path
-        fill='#008789'
-        d='M1.36,7.41h13.58c0.75,0,1.36,0.61,1.36,1.36v13.58c0,0.75-0.61,1.36-1.36,1.36H1.36c-0.75,0-1.36-0.61-1.36-1.36V8.77C0,8.02,0.61,7.41,1.36,7.41z'
-      />
-      <path
-        fill='#FFFFFF'
-        d='M6.07,15.42c-0.32-0.21-0.58-0.49-0.78-0.82c-0.19-0.34-0.28-0.73-0.27-1.12c-0.02-0.53,0.16-1.05,0.50-1.46c0.36-0.41,0.82-0.71,1.34-0.87c0.59-0.19,1.21-0.29,1.83-0.28c0.82-0.03,1.63,0.08,2.41,0.34v1.71c-0.34-0.20-0.71-0.35-1.09-0.44c-0.42-0.10-0.84-0.15-1.27-0.15c-0.45-0.02-0.90,0.08-1.31,0.28c-0.31,0.14-0.52,0.44-0.52,0.79c0,0.21,0.08,0.41,0.22,0.56c0.17,0.18,0.37,0.32,0.59,0.42c0.25,0.12,0.62,0.29,1.11,0.49c0.05,0.02,0.11,0.04,0.16,0.06c0.49,0.19,0.96,0.42,1.40,0.69c0.34,0.21,0.62,0.49,0.83,0.83c0.21,0.39,0.31,0.82,0.30,1.26c0.02,0.54-0.14,1.08-0.47,1.52c-0.33,0.40-0.77,0.69-1.26,0.85c-0.58,0.18-1.19,0.27-1.80,0.26c-0.55,0-1.09-0.04-1.63-0.13c-0.45-0.07-0.90-0.20-1.32-0.39v-1.80c0.40,0.29,0.86,0.50,1.34,0.64c0.48,0.15,0.97,0.23,1.47,0.24c0.46,0.03,0.92-0.07,1.34-0.28c0.29-0.16,0.46-0.47,0.46-0.80c0-0.23-0.09-0.45-0.25-0.61c-0.20-0.20-0.44-0.36-0.69-0.48c-0.30-0.15-0.73-0.34-1.31-0.59C6.91,16.14,6.48,15.80,6.07,15.42z'
-      />
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[SharePoint](https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration) is a collaborative platform from Microsoft that enables users to build and manage internal websites, share documents, and organize team resources. It provides a powerful, flexible solution for creating digital workspaces and streamlining content management across organizations.
-
-With SharePoint, you can:
-
-- **Create team and communication sites**: Set up pages and portals to support collaboration, announcements, and content distribution
-- **Organize and share content**: Store documents, manage files, and enable version control with secure sharing capabilities
-- **Customize pages**: Add text parts to tailor each site to your team's needs
-- **Improve discoverability**: Use metadata, search, and navigation tools to help users quickly find what they need
-- **Collaborate securely**: Control access with robust permission settings and Microsoft 365 integration
-
-In Sim, the SharePoint integration empowers your agents to create and access SharePoint sites and pages as part of their workflows. This enables automated document management, knowledge sharing, and workspace creation without manual effort. Agents can generate new project pages, upload or retrieve files, and organize resources dynamically, based on workflow inputs. By connecting Sim with SharePoint, you bring structured collaboration and content management into your automation flows — giving your agents the ability to coordinate team activities, surface key information, and maintain a single source of truth across your organization.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Sharepoint into the workflow. Can read and create pages, and list sites. Requires OAuth.
-
-
-
-## Tools
-
-### `sharepoint_create_page`
-
-Create a new page in a SharePoint site
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `siteId` | string | No | The ID of the SharePoint site \(internal use\) |
-| `siteSelector` | string | No | Select the SharePoint site |
-| `pageName` | string | Yes | The name of the page to create |
-| `pageTitle` | string | No | The title of the page \(defaults to page name if not provided\) |
-| `pageContent` | string | No | The content of the page |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `page` | object | Created SharePoint page information |
-
-### `sharepoint_read_page`
-
-Read a specific page from a SharePoint site
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `siteSelector` | string | No | Select the SharePoint site |
-| `siteId` | string | No | The ID of the SharePoint site \(internal use\) |
-| `pageId` | string | No | The ID of the page to read |
-| `pageName` | string | No | The name of the page to read \(alternative to pageId\) |
-| `maxPages` | number | No | Maximum number of pages to return when listing all pages \(default: 10, max: 50\) |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `page` | object | Information about the SharePoint page |
-
-### `sharepoint_list_sites`
-
-List details of all SharePoint sites
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `siteSelector` | string | No | Select the SharePoint site |
-| `groupId` | string | No | The group ID for accessing a group team site |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `site` | object | Information about the current SharePoint site |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `sharepoint`

apps/docs/content/docs/en/tools/sms.mdx

@@ -1,53 +0,0 @@
----
-title: SMS
-description: Send SMS messages using the internal SMS service
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="sms"
-  color="#E0E0E0"
-  icon={true}
-  iconSvg={`<svg className="block-icon"  fill="#000000"   viewBox="0 0 32 32" xmlns="http://www.w3.org/2000/svg"><path d="M 2 5 L 2 25 L 7 25 L 7 30.09375 L 8.625 28.78125 L 13.34375 25 L 30 25 L 30 5 Z M 4 7 L 28 7 L 28 23 L 12.65625 23 L 12.375 23.21875 L 9 25.90625 L 9 23 L 4 23 Z M 8 12 L 8 14 L 24 14 L 24 12 Z M 8 16 L 8 18 L 20 18 L 20 16 Z"/></svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-The SMS block allows you to send text messages directly from your workflows using Sim's own SMS sending infrastructure powered by Twilio. This integration enables you to programmatically deliver notifications, alerts, and other important information to users' mobile devices without requiring any external configuration or OAuth.
-
-Our internal SMS service is designed for reliability and ease of use, making it ideal for automating communications and ensuring your messages reach recipients efficiently.
-{/* MANUAL-CONTENT-END */}
-
-## Usage Instructions
-
-Send SMS messages directly using the internal SMS service powered by Twilio. No external configuration or OAuth required. Perfect for sending notifications, alerts, or general purpose text messages from your workflows. Requires valid phone numbers with country codes.
-
-
-
-## Tools
-
-### `sms_send`
-
-Send an SMS message using the internal SMS service powered by Twilio
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `to` | string | Yes | Recipient phone number \(include country code, e.g., +1234567890\) |
-| `body` | string | Yes | SMS message content |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `success` | boolean | Whether the SMS was sent successfully |
-| `to` | string | Recipient phone number |
-| `body` | string | SMS message content |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `sms`

apps/docs/content/docs/en/tools/supabase.mdx

@@ -1,213 +0,0 @@
----
-title: Supabase
-description: Use Supabase database
----
-
-import { BlockInfoCard } from "@/components/ui/block-info-card"
-
-<BlockInfoCard 
-  type="supabase"
-  color="#1C1C1C"
-  icon={true}
-  iconSvg={`<svg className="block-icon"    viewBox='0 0 27 27' xmlns='http://www.w3.org/2000/svg'>
-      <path
-        d='M15.4057 26.2606C14.7241 27.1195 13.3394 26.649 13.3242 25.5519L13.083 9.50684H23.8724C25.8262 9.50684 26.9157 11.7636 25.7006 13.2933L15.4057 26.2606Z'
-        fill='url(#paint0_linear)'
-      />
-      <path
-        d='M15.4057 26.2606C14.7241 27.1195 13.3394 26.649 13.3242 25.5519L13.083 9.50684H23.8724C25.8262 9.50684 26.9157 11.7636 25.7006 13.2933L15.4057 26.2606Z'
-        fill='url(#paint1_linear)'
-        fillOpacity='0.2'
-      />
-      <path
-        d='M11.0167 0.443853C11.6983 -0.415083 13.0832 0.0553814 13.0982 1.15237L13.2042 17.1976H2.55005C0.596215 17.1976 -0.493259 14.9408 0.721603 13.4111L11.0167 0.443853Z'
-        fill='#3ECF8E'
-      />
-      <defs>
-        <linearGradient
-          id='paint0_linear'
-          x1='13.084'
-          y1='13.0655'
-          x2='22.6727'
-          y2='17.087'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop stopColor='#249361' />
-          <stop offset='1' stopColor='#3ECF8E' />
-        </linearGradient>
-        <linearGradient
-          id='paint1_linear'
-          x1='8.83277'
-          y1='7.24485'
-          x2='13.2057'
-          y2='15.477'
-          gradientUnits='userSpaceOnUse'
-        >
-          <stop />
-          <stop offset='1' stopOpacity='0' />
-        </linearGradient>
-      </defs>
-    </svg>`}
-/>
-
-{/* MANUAL-CONTENT-START:intro */}
-[Supabase](https://www.supabase.com/) is a powerful open-source backend-as-a-service platform that provides developers with a suite of tools to build, scale, and manage modern applications. Supabase offers a fully managed [PostgreSQL](https://www.postgresql.org/) database, robust authentication, instant RESTful and GraphQL APIs, real-time subscriptions, file storage, and edge functions—all accessible through a unified and developer-friendly interface. Its open-source nature and compatibility with popular frameworks make it a compelling alternative to Firebase, with the added benefit of SQL flexibility and transparency.
-
-**Why Supabase?**
-- **Instant APIs:** Every table and view in your database is instantly available via REST and GraphQL endpoints, making it easy to build data-driven applications without writing custom backend code.
-- **Real-time Data:** Supabase enables real-time subscriptions, allowing your apps to react instantly to changes in your database.
-- **Authentication & Authorization:** Built-in user management with support for email, OAuth, SSO, and more, plus row-level security for granular access control.
-- **Storage:** Securely upload, serve, and manage files with built-in storage that integrates seamlessly with your database.
-- **Edge Functions:** Deploy serverless functions close to your users for low-latency custom logic.
-
-**Using Supabase in Sim**
-
-Sim’s Supabase integration makes it effortless to connect your agentic workflows to your Supabase projects. With just a few configuration fields—your Project ID, Table name, and Service Role Secret—you can securely interact with your database directly from your Sim blocks. The integration abstracts away the complexity of API calls, letting you focus on building logic and automations.
-
-**Key benefits of using Supabase in Sim:**
-- **No-code/low-code database operations:** Query, insert, update, and delete rows in your Supabase tables without writing SQL or backend code.
-- **Flexible querying:** Use [PostgREST filter syntax](https://postgrest.org/en/stable/api.html#operators) to perform advanced queries, including filtering, ordering, and limiting results.
-- **Seamless integration:** Easily connect Supabase to other tools and services in your workflow, enabling powerful automations such as syncing data, triggering notifications, or enriching records.
-- **Secure and scalable:** All operations use your Supabase Service Role Secret, ensuring secure access to your data with the scalability of a managed cloud platform.
-
-Whether you’re building internal tools, automating business processes, or powering production applications, Supabase in Sim provides a fast, reliable, and developer-friendly way to manage your data and backend logic—no infrastructure management required. Simply configure your block, select the operation you need, and let Sim handle the rest.
-{/* MANUAL-CONTENT-END */}
-
-
-## Usage Instructions
-
-Integrate Supabase into the workflow. Can get many rows, get, create, update, delete, and upsert a row.
-
-
-
-## Tools
-
-### `supabase_query`
-
-Query data from a Supabase table
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `projectId` | string | Yes | Your Supabase project ID \(e.g., jdrkgepadsdopsntdlom\) |
-| `table` | string | Yes | The name of the Supabase table to query |
-| `filter` | string | No | PostgREST filter \(e.g., "id=eq.123"\) |
-| `orderBy` | string | No | Column to order by \(add DESC for descending\) |
-| `limit` | number | No | Maximum number of rows to return |
-| `apiKey` | string | Yes | Your Supabase service role secret key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `results` | array | Array of records returned from the query |
-
-### `supabase_insert`
-
-Insert data into a Supabase table
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `projectId` | string | Yes | Your Supabase project ID \(e.g., jdrkgepadsdopsntdlom\) |
-| `table` | string | Yes | The name of the Supabase table to insert data into |
-| `data` | any | Yes | The data to insert |
-| `apiKey` | string | Yes | Your Supabase service role secret key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `results` | array | Array of inserted records |
-
-### `supabase_get_row`
-
-Get a single row from a Supabase table based on filter criteria
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `projectId` | string | Yes | Your Supabase project ID \(e.g., jdrkgepadsdopsntdlom\) |
-| `table` | string | Yes | The name of the Supabase table to query |
-| `filter` | string | Yes | PostgREST filter to find the specific row \(e.g., "id=eq.123"\) |
-| `apiKey` | string | Yes | Your Supabase service role secret key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `results` | array | Array containing the row data if found, empty array if not found |
-
-### `supabase_update`
-
-Update rows in a Supabase table based on filter criteria
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `projectId` | string | Yes | Your Supabase project ID \(e.g., jdrkgepadsdopsntdlom\) |
-| `table` | string | Yes | The name of the Supabase table to update |
-| `filter` | string | Yes | PostgREST filter to identify rows to update \(e.g., "id=eq.123"\) |
-| `data` | object | Yes | Data to update in the matching rows |
-| `apiKey` | string | Yes | Your Supabase service role secret key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `results` | array | Array of updated records |
-
-### `supabase_delete`
-
-Delete rows from a Supabase table based on filter criteria
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `projectId` | string | Yes | Your Supabase project ID \(e.g., jdrkgepadsdopsntdlom\) |
-| `table` | string | Yes | The name of the Supabase table to delete from |
-| `filter` | string | Yes | PostgREST filter to identify rows to delete \(e.g., "id=eq.123"\) |
-| `apiKey` | string | Yes | Your Supabase service role secret key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `results` | array | Array of deleted records |
-
-### `supabase_upsert`
-
-Insert or update data in a Supabase table (upsert operation)
-
-#### Input
-
-| Parameter | Type | Required | Description |
-| --------- | ---- | -------- | ----------- |
-| `projectId` | string | Yes | Your Supabase project ID \(e.g., jdrkgepadsdopsntdlom\) |
-| `table` | string | Yes | The name of the Supabase table to upsert data into |
-| `data` | any | Yes | The data to upsert \(insert or update\) |
-| `apiKey` | string | Yes | Your Supabase service role secret key |
-
-#### Output
-
-| Parameter | Type | Description |
-| --------- | ---- | ----------- |
-| `message` | string | Operation status message |
-| `results` | array | Array of upserted records |
-
-
-
-## Notes
-
-- Category: `tools`
-- Type: `supabase`