## 1. Project Overview & Quickstart (remsky/AGENTS) # AGENTS Multi-harness agentic plugin marketplace for Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot, and Gemini CLI ### Repository Details - **Repository:** [remsky/AGENTS](https://github.com/remsky/AGENTS) - **GitHub Stars:** ⭐ 38,567 - **Primary Language:** Python *Note: High-volume repository documentation is actively indexed and synchronized by YakaAI.* ## 2. Official Technical Reference & Guides (remsky/docs) ## File: README.md # Website This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator. ## Installation ```sh npm ci ``` ## Local Development ```sh npm start ``` This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. ## Build ```sh npm run build ``` This command generates static content into the `build` directory and can be served using any static contents hosting service. ## Deployment Using SSH: ```sh USE_SSH=true npm run deploy ``` Not using SSH: ```sh GIT_USER= npm run deploy ``` If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch. --- ## File: docs/features/chat-features/chat-params.md --- sidebar_position: 4 title: "βš™οΈ Chat Parameters" --- Within Open WebUI, there are three levels to setting a **System Prompt** and **Advanced Parameters**: per-chat basis, per-model basis, and per-account basis. This hierarchical system allows for flexibility while maintaining structured administration and control. ## System Prompt and Advanced Parameters Hierarchy Chart | **Level** | **Definition** | **Modification Permissions** | **Override Capabilities** | | --- | --- | --- | --- | | **Per-Chat** | System prompt and advanced parameters for a specific chat instance | Users can modify, but cannot override model-specific settings | Restricted from overriding model-specific settings | | **Per-Model** | Default system prompt and advanced parameters for a specific model | Administrators can set, Users cannot modify | Admin-specific settings take precedence, User settings can be overridden | | **Per-Account** | Default system prompt and advanced parameters for a specific user account | Users can set, but may be overridden by model-specific settings | User settings can be overridden by model-specific settings | ### 1. **Per-chat basis:** - **Description**: The per-chat basis setting refers to the system prompt and advanced parameters configured for a specific chat instance. These settings are only applicable to the current conversation and do not affect future chats. - **How to set**: Users can modify the system prompt and advanced parameters for a specific chat instance within the right-hand sidebar's **Chat Controls** section in Open WebUI. - **Override capabilities**: Users are restricted from overriding the **System Prompt** or specific **Advanced Parameters** already set by an administrator on a per-model basis (**#2**). This ensures consistency and adherence to model-specific settings. Example Use Case :::tip **Per-chat basis**: Suppose a user wants to set a custom system prompt for a specific conversation. They can do so by accessing the **Chat Controls** section and modifying the **System Prompt** field. These changes will only apply to the current chat session. ::: ### 2. **Per-model basis:** - **Description**: The per-model basis setting refers to the default system prompt and advanced parameters configured for a specific model. These settings are applicable to all chat instances using that model. - **How to set**: Administrators can set the default system prompt and advanced parameters for a specific model within the **Models** section of the **Workspace** in Open WebUI. - **Override capabilities**: **User** accounts are restricted from modifying the **System Prompt** or specific **Advanced Parameters** on a per-model basis (**#3**). This restriction prevents users from inappropriately altering default settings. - **Context length preservation:** When a model's **System Prompt** or specific **Advanced Parameters** are set manually in the **Workspace** section by an Admin, said **System Prompt** or manually set **Advanced Parameters** cannot be overridden or adjusted on a per-account basis within the **General** settings or **Chat Controls** section by a **User** account. This ensures consistency and prevents excessive reloading of the model whenever a user's context length setting changes. - **Model precedence:** If a model's **System Prompt** or specific **Advanced Parameters** value is pre-set in the Workspace section by an Admin, any context length changes made by a **User** account in the **General** settings or **Chat Controls** section will be disregarded, maintaining the pre-configured value for that model. Be advised that parameters left untouched by an **Admin** account can still be manually adjusted by a **User** account on a per-account or per-chat basis. Example Use Case :::tip **Per-model basis**: Suppose an administrator wants to set a default system prompt for a specific model. They can do so by accessing the **Models** section and modifying the **System Prompt** field for the corresponding model. Any chat instances using this model will automatically use the model's system prompt and advanced parameters. ::: ### 3. **Per-account basis:** - **Description**: The per-account basis setting refers to the default system prompt and advanced parameters configured for a specific user account. Any user-specific changes can serve as a fallback in situations where lower-level settings aren't defined. - **How to set**: Users can set their own system prompt and advanced parameters for their account within the **General** section of the **Settings** menu in Open WebUI. - **Override capabilities**: Users have the ability to set their own system prompt on their account, but they must be aware that such parameters can still be overridden if an administrator has already set the **System Prompt** or specific **Advanced Parameters** on a per-model basis for the particular model being used. Example Use Case :::tip **Per-account basis**: Suppose a user wants to set their own system prompt for their account. They can do so by accessing the **Settings** menu and modifying the **System Prompt** field. ::: ## **Optimize System Prompt Settings for Maximum Flexibility** :::tip **Bonus Tips** **This tip applies for both administrators and user accounts. To achieve maximum flexibility with your system prompts, we recommend considering the following setup:** - Assign your primary System Prompt (**i.e., to give an LLM a defining character**) you want to use in your **General** settings **System Prompt** field. This sets it on a per-account level and allows it to work as the system prompt across all your LLMs without requiring adjustments within a model from the **Workspace** section. - For your secondary System Prompt (**i.e, to give an LLM a task to perform**), choose whether to place it in the **System Prompt** field within the **Chat Controls** sidebar (on a per-chat basis) or the **Models** section of the **Workspace** section (on a per-model basis) for Admins, allowing you to set them directly. This allows your account-level system prompt to work in conjunction with either the per-chat level system prompt provided by **Chat Controls**, or the per-model level system prompt provided by **Models**. - As an administrator, you should assign your LLM parameters on a per-model basis using **Models** section for optimal flexibility. For both of these secondary System Prompts, ensure to set them in a manner that maximizes flexibility and minimizes required adjustments across different per-account or per-chat instances. It is essential for both your Admin account as well as all User accounts to understand the priority order by which system prompts within **Chat Controls** and the **Models** section will be applied to the **LLM**. ::: --- ## File: docs/features/chat-features/chatshare.md --- sidebar_position: 4 title: "πŸ—¨οΈ Chat Sharing" --- ### Enabling Community Sharing To enable community sharing, follow these steps: 1. Navigate to the **Admin Panel** page as an **Admin**. 2. Click on the **Settings** tab. 3. Toggle on **Enable Community Sharing** within the **General** settings tab. :::note **Note:** Only Admins can toggle the **Enable Community Sharing** option. If this option is toggled off, users and Admins will not see the **Share to Open WebUI Community** option for sharing their chats. Community sharing must be enabled by an Admin for users to share chats to the Open WebUI community. ::: This will enable community sharing for all users on your Open WebUI instance. ### Sharing Chats To share a chat: 1. Select the chat conversation you want to share. 2. Click on the 3-dots that appear when hovering the mouse pointer above the desired chat. 3. Then click on the **Share** option. 4. Select either **Share to Open WebUI Community** (if **Enable Community Sharing** is toggled on by an **Admin**) or **Copy Link**. #### Sharing to Open WebUI Community When you select `Share to Open WebUI Community`: * A new tab will open, allowing you to upload your chat as a snapshot to the Open WebUI community website (https://openwebui.com/chats/upload). * You can control who can view your uploaded chat by choosing from the following access settings: * **Private**: Only you can access this chat. * **Public**: Anyone on the internet can view the messages displayed in the chat snapshot. * **Public, Full History**: Anyone on the internet can view the full regeneration history of your chat. :::note Note: You can change the permission level of your shared chats on the community platform at any time from your openwebui.com account. **Currently, shared chats on the community website cannot be found through search. However, future updates are planned to allow public chats to be discoverable by the public if their permission is set to `Public` or `Public, Full History`.** ::: Example of a shared chat to the community platform website: https://openwebui.com/c/iamg30/5e3c569f-905e-4d68-a96d-8a99cc65c90f #### Copying a Share Link When you select `Copy Link`, a unique share link is generated that can be shared with others. **Important Considerations:** * The shared chat will only include messages that existed at the time the link was created. Any new messages sent within the chat after the link is generated will not be included, unless the link is deleted and updated with a new link. * The generated share link acts as a static snapshot of the chat at the time the link was generated. * To view the shared chat, users must: 1. Have an account on the Open WebUI instance where the link was generated. 2. Be signed in to their account on that instance. * If a user tries to access the shared link without being signed in, they will be redirected to the login page to log in before they can view the shared chat. ### Viewing Shared Chats To view a shared chat: 1. Ensure you are signed in to an account on the Open WebUI instance where the chat was shared. 2. Click on the shared link provided to you. 3. The chat will be displayed in a read-only format. 4. If the Admin of the Open WebUI instance from which the shared link was shared has Text-to-Speech set up, there may be an audio button for messages to be read aloud to you (situational). ### Updating Shared Chats To update a shared chat: 1. Select the chat conversation you want to share. 2. Click on the 3-dots that appear when hovering the mouse pointer above the desired chat. 3. Click on the **Share** option. 4. The **Share Chat** Modal should look different if you've shared a chat before. The **Share Chat** Modal includes the following options: * **before**: Opens a new tab to view the previously shared chat from the share link. * **delete this link**: Deletes the shared link of the chat and presents the initial share chat modal. * **Share to Open WebUI Community**: Opens a new tab for https://openwebui.com/chats/upload with the chat ready to be shared as a snapshot. * **Update and Copy Link**: Updates the snapshot of the chat of the previously shared chat link and copies it to your device's clipboard. ### Deleting Shared Chats To delete a shared chat link: 1. Select the chat conversation you want to delete the shared link for. 2. Click on the 3-dots that appear when hovering the mouse pointer above the desired chat. 3. Click on the **Share** option. 4. The **Share Chat** Modal should look different if you've shared a chat before. 5. Click on **delete this link**. Once deleted, the shared link will no longer be valid, and users will not be able to view the shared chat. :::note **Note:** Chats shared to the community platform cannot be deleted. To change the access level of a chat shared to the community platform: ::: 1. Log in to your Open WebUI account on openwebui.com. 2. Click on your account username at the top right of the website. 3. Click on **Chats**. 4. Click on the chat you wish to change permission access for. 5. Scroll to the bottom of the chat and update its permission level. 6. Click the **Update Chat** button. --- ## File: docs/features/chat-features/conversation-organization.md --- sidebar_position: 4 title: "πŸ—‚οΈ Organizing Conversations" --- Open WebUI provides powerful organization features that help users manage their conversations. You can easily categorize and tag conversations, making it easier to find and retrieve them later. The two primary ways to organize conversations are through **Folders** and **Tags**. ## Organizing Conversations with Folders Folders allow you to group related conversations together for quick access and better organization. - **Creating a Folder**: You can create a new folder to store specific conversations. This is useful if you want to keep conversations of a similar topic or purpose together. - **Moving Conversations into Folders**: Conversations can be moved into folders by dragging and dropping them. This allows you to structure your workspace in a way that suits your workflow. ### Example Use Case :::tip **Organizing by Project** If you are managing multiple projects, you can create separate folders for each project and move relevant conversations into these folders. This helps keep all project-related discussions in one place. ::: ## Tagging Conversations Tags provide an additional layer of organization by allowing you to label conversations with keywords or phrases. - **Adding Tags to Conversations**: Tags can be applied to conversations based on their content or purpose. Tags are flexible and can be added or removed as needed. - **Using Tags for Searching**: Tags make it easy to locate specific conversations by using the search feature. You can filter conversations by tags to quickly find those related to specific topics. ### Example Use Case :::tip **Tagging by Topic** If you frequently discuss certain topics, such as "marketing" or "development," you can tag conversations with these terms. Later, when you search for a specific tag, all relevant conversations will be quickly accessible. ::: --- ## File: docs/features/chat-features/url-params.md --- sidebar_position: 5 title: "πŸ”— URL Parameters" --- In Open WebUI, chat sessions can be customized through various URL parameters. These parameters allow you to set specific configurations, enable features, and define model settings on a per-chat basis. This approach provides flexibility and control over individual chat sessions directly from the URL. ## URL Parameter Overview The following table lists the available URL parameters, their function, and example usage. | **Parameter** | **Description** | **Example** | |-----------------------|----------------------------------------------------------------------------------|--------------------------------------------------------| | `models` | Specifies the models to be used, as a comma-separated list. | `/?models=model1,model2` | | `model` | Specifies a single model to be used for the chat session. | `/?model=model1` | | `youtube` | Specifies a YouTube video ID to be transcribed within the chat. | `/?youtube=VIDEO_ID` | | `web-search` | Enables web search functionality if set to `true`. | `/?web-search=true` | | `tools` or `tool-ids` | Specifies a comma-separated list of tool IDs to activate in the chat. | `/?tools=tool1,tool2` | | `call` | Enables a call overlay if set to `true`. | `/?call=true` | | `q` | Sets an initial query or prompt for the chat. | `/?q=Hello%20there` | | `temporary-chat` | Marks the chat as temporary if set to `true`, for one-time sessions. | `/?temporary-chat=true` | ### 1. **Models and Model Selection** - **Description**: The `models` and `model` parameters allow you to specify which [language models](/features/workspace/models.md) should be used for a particular chat session. - **How to Set**: You can use either `models` for multiple models or `model` for a single model. - **Example**: - `/?models=model1,model2` – This initializes the chat with `model1` and `model2`. - `/?model=model1` – This sets `model1` as the sole model for the chat. ### 2. **YouTube Transcription** - **Description**: The `youtube` parameter takes a YouTube video ID, enabling the chat to transcribe the specified video. - **How to Set**: Use the YouTube video ID as the value for this parameter. - **Example**: `/?youtube=VIDEO_ID` - **Behavior**: This triggers transcription functionality within the chat for the provided YouTube video. ### 3. **Web Search** - **Description**: Enabling `web-search` allows the chat session to access [web search](/tutorials/integrations/web_search) functionality. - **How to Set**: Set this parameter to `true` to enable web search. - **Example**: `/?web-search=true` - **Behavior**: If enabled, the chat can retrieve web search results as part of its responses. ### 4. **Tool Selection** - **Description**: The `tools` or `tool-ids` parameters specify which [tools](/features/plugin/tools) to activate within the chat. - **How to Set**: Provide a comma-separated list of tool IDs as the parameter’s value. - **Example**: `/?tools=tool1,tool2` or `/?tool-ids=tool1,tool2` - **Behavior**: Each tool ID is matched and activated within the session for user interaction. ### 5. **Call Overlay** - **Description**: The `call` parameter enables a video or call overlay in the chat interface. - **How to Set**: Set the parameter to `true` to enable the call overlay. - **Example**: `/?call=true` - **Behavior**: Activates a call interface overlay, allowing features such as live transcription and video input. ### 6. **Initial Query Prompt** - **Description**: The `q` parameter allows setting an initial query or prompt for the chat. - **How to Set**: Specify the query or prompt text as the parameter value. - **Example**: `/?q=Hello%20there` - **Behavior**: The chat starts with the specified prompt, automatically submitting it as the first message. ### 7. **Temporary Chat Sessions** - **Description**: The `temporary-chat` parameter marks the chat as a temporary session. This may limit features such as saving chat history or applying persistent settings. - **How to Set**: Set this parameter to `true` for a temporary chat session. - **Example**: `/?temporary-chat=true` - **Behavior**: This initiates a disposable chat session without saving history or applying advanced configurations. Example Use Case :::tip **Temporary Chat Session** Suppose a user wants to initiate a quick chat session without saving the history. They can do so by setting `temporary-chat=true` in the URL. This provides a disposable chat environment ideal for one-time interactions. ::: ## Using Multiple Parameters Together These URL parameters can be combined to create highly customized chat sessions. For example: ```bash /chat?models=model1,model2&youtube=VIDEO_ID&web-search=true&tools=tool1,tool2&call=true&q=Hello%20there&temporary-chat=true ``` This URL will: - Initialize the chat with `model1` and `model2`. - Enable YouTube transcription, web search, and specified tools. - Display a call overlay. - Set an initial prompt of "Hello there." - Mark the chat as temporary, avoiding any history saving. --- ## File: docs/features/code-execution/artifacts.md --- sidebar_position: 1 title: "🏺 Artifacts" --- # What are Artifacts and how do I use them in Open WebUI? Artifacts in Open WebUI are an innovative feature inspired by Claude.AI's Artifacts, allowing you to interact with significant and standalone content generated by an LLM within a chat. They enable you to view, modify, build upon, or reference substantial pieces of content separately from the main conversation, making it easier to work with complex outputs and ensuring that you can revisit important information later. ## When does Open WebUI use Artifacts? Open WebUI creates an Artifact when the generated content meets specific criteria tailored to our platform: 1. **Renderable**: To be displayed as an Artifact, the content must be in a format that Open WebUI supports for rendering. This includes: * Single-page HTML websites * Scalable Vector Graphics (SVG) images * Complete webpages, which include HTML, Javascript, and CSS all in the same Artifact. Do note that HTML is required if generating a complete webpage. * ThreeJS Visualizations and other JavaScript visualization libraries such as D3.js. Other content types like Documents (Markdown or Plain Text), Code snippets, and React components are not rendered as Artifacts by Open WebUI. ## How does Open WebUI's model create Artifacts? To use artifacts in Open WebUI, a model must provide content that triggers the rendering process to create an artifact. This involves generating valid HTML, SVG code, or other supported formats for artifact rendering. When the generated content meets the criteria mentioned above, Open WebUI will display it as an interactive Artifact. ## How do I use Artifacts in Open WebUI? When Open WebUI creates an Artifact, you'll see the content displayed in a dedicated Artifacts window to the right side of the main chat. Here's how to interact with Artifacts: * **Editing and iterating**: Ask an LLM within the chat to edit or iterate on the content, and these updates will be displayed directly in the Artifact window. You can switch between versions using the version selector at the bottom left of the Artifact. Each edit creates a new version, allowing you to track changes using the version selector. * **Updates**: Open WebUI may update an existing Artifact based on your messages. The Artifact window will display the latest content. * **Actions**: Access additional actions for the Artifact, such as copying the content or opening the artifact in full screen, located in the lower right corner of the Artifact. ## Editing Artifacts 1. **Targeted Updates**: Describe what you want changed and where. For example: * "Change the color of the bar in the chart from blue to red." * "Update the title of the SVG image to 'New Title'." 2. **Full Rewrites**: Request major changes affecting most of the content for substantial restructuring or multiple section updates. For example: * "Rewrite this single-page HTML website to be a landing page instead." * "Redesign this SVG so that it's animated using ThreeJS." **Best Practices**: * Be specific about which part of the Artifact you want to change. * Reference unique identifying text around your desired change for targeted updates. * Consider whether a small update or full rewrite is more appropriate for your needs. ## Use Cases Artifacts in Open WebUI enable various teams to create high-quality work products quickly and efficiently. Here are some examples tailored to our platform: * **Designers**: * Create interactive SVG graphics for UI/UX design. * Design single-page HTML websites or landing pages. * **Developers**: Create simple HTML prototypes or generate SVG icons for projects. * **Marketers**: * Design campaign landing pages with performance metrics. * Create SVG graphics for ad creatives or social media posts. ## Examples of Projects you can create with Open WebUI's Artifacts Artifacts in Open WebUI enable various teams and individuals to create high-quality work products quickly and efficiently. Here are some examples tailored to our platform, showcasing the versatility of artifacts and inspiring you to explore their potential: 1. **Interactive Visualizations** * Components used: ThreeJS, D3.js, and SVG * Benefits: Create immersive data stories with interactive visualizations. Open WebUI's Artifacts enable you to switch between versions, making it easier to test different visualization approaches and track changes. Example Project: Build an interactive line chart using ThreeJS to visualize stock prices over time. Update the chart's colors and scales in separate versions to compare different visualization strategies. 2. **Single-Page Web Applications** * Components used: HTML, CSS, and JavaScript * Benefits: Develop single-page web applications directly within Open WebUI. Edit and iterate on the content using targeted updates and full rewrites. Example Project: Design a to-do list app with a user interface built using HTML and CSS. Use JavaScript to add interactive functionality. Update the app's layout and UI/UX using targeted updates and full rewrites. 3. **Animated SVG Graphics** * Components used: SVG and ThreeJS * Benefits: Create engaging animated SVG graphics for marketing campaigns, social media, or web design. Open WebUI's Artifacts enable you to edit and iterate on the graphics in a single window. Example Project: Design an animated SVG logo for a company brand. Use ThreeJS to add animation effects and Open WebUI's targeted updates to refine the logo's colors and design. 4. **Webpage Prototypes** * Components used: HTML, CSS, and JavaScript * Benefits: Build and test webpage prototypes directly within Open WebUI. Switch between versions to compare different design approaches and refine the prototype. Example Project: Develop a prototype for a new e-commerce website using HTML, CSS, and JavaScript. Use Open WebUI's targeted updates to refines the navigation, layout, and UI/UX. 5. **Interactive Storytelling** * Components used: HTML, CSS, and JavaScript * Benefits: Create interactive stories with scrolling effects, animations, and other interactive elements. Open WebUI's Artifacts enable you to refine the story and test different versions. Example Project: Build an interactive story about a company's history, using scrolling effects and animations to engage the reader. Use targeted updates to refine the story's narrative and Open WebUI's version selector to test different versions. --- ## File: docs/features/code-execution/mermaid.md --- sidebar_position: 3 title: "🌊 MermaidJS Rendering" --- # 🌊 MermaidJS Rendering Support in Open WebUI ## Overview Open WebUI supports rendering of visually appealing MermaidJS diagrams, flowcharts, pie charts and more, directly within the chat interface. MermaidJS is a powerful tool for visualizing complex information and ideas, and when paired with the capabilities of a large language model (LLM), it can be a powerful tool for generating and exploring new ideas. ## Using MermaidJS in Open WebUI To generate a MermaidJS diagram, simply ask an LLM within any chat to create a diagram or chart using MermaidJS. For example, you can ask the LLM to: * "Create a flowchart for a simple decision-making process for me using Mermaid. Explain how the flowchart works." * "Use Mermaid to visualize a decision tree to determine whether it's suitable to go for a walk outside." Note that for the LLM's response to be rendered correctly, it must begin with the word `mermaid` followed by the MermaidJS code. You can reference the [MermaidJS documentation](https://mermaid.js.org/intro/) to ensure the syntax is correct and provide structured prompts to the LLM to guide it towards generating better MermaidJS syntax. ## Visualizing MermaidJS Code Directly in the Chat When you request a MermaidJS visualization, the Large Language Model (LLM) will generate the necessary code. Open WebUI will automatically render the visualization directly within the chat interface, as long as the code uses valid MermaidJS syntax. If the model generates MermaidJS syntax, but the visualization does not render, it usually indicates a syntax error in the code. Don't worry – you'll be notified of any errors once the response has been fully generated. If this happens, try referencing the [MermaidJS documentation](https://mermaid.js.org/intro/) to identify the issue and revise the prompt accordingly. ## Interacting with Your Visualization Once your visualization is displayed, you can: * Zoom in and out to examine it more closely. * Copy the original MermaidJS code used to generate the visualization by clicking the copy button at the top-right corner of the display area. ### Example ```mermaid graph TD; A-->B; B-->C{Decision}; C--Yes-->D; C--No-->E; D-->F; E-->F; ``` This will generate a flowchart like the following: ```markdown startAncestor [ start ] A[A] --> B[B] B --> C[Decision] C -->| Yes | D[D] C -->| No | E[E] D --> F[F] E --> F[F] ``` Experimenting with different types of diagrams and charts can help you develop a more nuanced understanding of how to effectively leverage MermaidJS within Open WebUI. For smaller models, consider referencing the [MermaidJS documentation](https://mermaid.js.org/intro/) to provide guidance for the LLM, or have it summarize the documentation into comprehensive notes or a system prompt. By following these guidelines and exploring the capabilities of MermaidJS, you can unlock the full potential of this powerful tool in Open WebUI. --- ## File: docs/features/code-execution/python.md --- sidebar_position: 2 title: "🐍 Python Code Execution" --- # 🐍 Python Code Execution ## Overview Open WebUI allows for the client-side execution of Python code in the browser, utilizing Pyodide to run scripts within a code block in a chat. This feature enables Large Language Models (LLMs) to generate Python scripts that can be executed directly in the browser, leveraging a range of libraries supported by Pyodide. To maintain user privacy and flexibility, Open WebUI mirrors PyPI packages, avoiding direct external network requests. This approach also enables the use of Pyodide in environments without internet access. The Open WebUI frontend includes a self-contained WASM (WebAssembly) Python environment, powered by Pyodide, which can execute basic Python scripts generated by LLMs. This environment is designed for ease of use, requiring no additional setup or installation. ## Supported Libraries Pyodide code execution is configured to load only packages configured in scripts/prepare-pyodide.js and then added to "CodeBlock.svelte". The following Pyodide packages are currently supported in Open WebUI: * micropip * packaging * requests * beautifulsoup4 * numpy * pandas * matplotlib * scikit-learn * scipy * regex These libraries can be used to perform various tasks, such as data manipulation, machine learning, and web scraping. If the package you're wanting to run is not compiled inside of the Pyodide we ship with Open WebUIm, the package will not be able to be used. ## Invoking Python Code Execution To execute Python code, ask an LLM within a chat to write a Python script for you. Once the LLM has generated the code, a `Run` button will appear at the top right-hand side of the code block. Clicking this button will execute the code using Pyodide. To display the result at the bottom of a code block, ensure there is at least a single print statement within the code to display a result. ## Tips for Using Python Code Execution * When writing Python code, keep in mind that the code would be running in a Pyodide environment when executed. You can inform the LLM of this by mentioning "Pyodide environment" when asking for code. * Research the Pyodide documentation to understand the capabilities and limitations of the environment. * Experiment with different libraries and scripts to explore the possibilities of Python code execution in Open WebUI. ## Pyodide Documentation * [Pyodide Documentation](https://pyodide.org/en/stable/) ## Code Example Here is an example of a simple Python script that can be executed using Pyodide: ```python import pandas as pd # Create a sample DataFrame data = {'Name': ['John', 'Anna', 'Peter'], 'Age': [28, 24, 35]} df = pd.DataFrame(data) # Print the DataFrame print(df) ``` This script will create a sample DataFrame using pandas and print it below the code block within your chat. ## Extending the List of Supported Libraries Want to push the boundaries of what's possible? To extend the list of supported libraries, follow these steps: 1. **Fork the Pyodide repository** to create your own version. 2. **Choose new packages** from the existing list of packages within Pyodide or explore high-quality packages that Open WebUI currently lacks. 3. **Integrate the new packages** into your forked repository to unlock even more possibilities.