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

Server Plugin

Types of Plugins: Server vs. Client

Plugins can be divided into two types:

  1. Server Plugins

    • These plugins run on the server side.

    • Users cannot see the plugin’s code, API keys, credentials, or any sensitive data. Only the output of the plugin is visible to users.

    • The system decides when to use these plugins based on the plugin's functionality and the context in which it’s being used.

    • Server plugins can only run HTTP Actions.

  2. Client Plugins

    • These plugins run locally in the user’s browser.

    • The user is responsible for providing necessary settings like API keys, credentials, and other configurations.

    • The user can view and edit the source code of client plugins.

Key Differences Between Server and Client Plugins

Server Plugins

Client Plugins

✅ Run on the server side and are hidden from the user.

✅ Run locally on the user’s browser.

✅ Sensitive data (like API keys) is not visible to the user.

✅ The user provides API keys and settings.

✅ The system determines when to use the plugin based on context.

✅ The user can view and modify the plugin code.

✅ Only support HTTP Action implementation.

✅ Support both HTTP and JavaScript-based implementations.

Creating Server Plugins

  • Creating a server plugin is similar to creating a client plugin, with the key difference being that server plugins must use HTTP Actions for their implementation.

  • When a server plugin runs, HTTP requests are sent from the server side, meaning users do not see the sensitive data or settings used by the plugin.

By default, most plugins are client-side plugins, but server plugins are an option for advanced use cases, where sensitive data needs to be kept private or where only HTTP-based actions are required.

Let me know if you need more details or help with anything else!

PreviousBuild a Trueseek pluginNextPlugin Server Side vs Client Side

Last updated 4 months ago