Trueseek AI
  • Getting Started
    • Get started with Trueseek
    • Trueseek vs Other AI Platforms
  • AI Agents
    • AI Agents Overview
    • AI Agents Examples
    • Dynamic Context
    • Interactive blocks
    • OpenAPI
    • Integrations
  • Plugins
    • Build a Trueseek plugin
    • Server Plugin
    • Plugin Server Side vs Client Side
    • OAuth for Plugin
    • How to Use Trueseek Plugin
  • System Prompt
    • Set up System Instruction
  • Prompts
    • Prompt library
    • Prompt Examples
    • Automatic Prompt Caching
    • Message Syntax
  • Chat Management
    • Organize chats
    • Share/Export a Chat
    • Pin Chats
  • Upload and Chat with Files
    • Chat with Documents
    • Chat with Videos
  • Text-to-speech
    • Set up Text-to-speech
    • Create Custom voice
  • General Settings
    • General Settings
    • Customize app appearance
    • Keyboard shortcuts
  • Support
    • Frequently Asked Questions
    • Report Error/Bugs
Powered by GitBook
On this page
  1. Plugins

Plugin Server Side vs Client Side

Server vs. Client Plugins: Key Differences

Server Plugins

  • What are they? Server plugins run on the server side and keep sensitive data like API keys, credentials, and the plugin’s code hidden from the user. Only the plugin’s output is visible to the user.

  • How do they work?

    • When these plugins are used, HTTP requests are sent from the server rather than the user’s device.

    • The system decides when to use the plugin based on the functionality and context of the request.

  • When to use them?

    • Use them when you need to keep API keys and other sensitive data hidden.

    • They are best when plugins require HTTP Action implementations.

    • Server plugins are more convenient for users since they do not need to configure anything.

Client Plugins

  • What are they? Client plugins run directly on the user’s browser. The user has full visibility of the plugin’s code, API keys, and other settings, which they must provide in order to use the plugin.

  • How do they work?

    • For plugins using JavaScript, the code is executed in a sandboxed environment within the user’s device.

    • If the plugin sends HTTP requests, those requests will be made directly from the user’s device, potentially leading to CORS issues.

  • When to use them?

    • Use client plugins for tasks that require running on the user’s device, like rendering charts or running JavaScript.

    • They are suitable if you want to allow users to use their own API keys.

Can a plugin run both on the server and client side?

  • No, plugins cannot run simultaneously on both the server and client side. However, you can create two separate versions of the same plugin—one for the server side and one for the client side. Note that this could result in two plugins with the same name, which might confuse users.

Let me know if you need more details!

PreviousServer PluginNextOAuth for Plugin

Last updated 4 months ago