FKTeams

Lazy cat OIDC login has been integrated. ##Functional characteristics - Multi-agent collaboration: Support team mode, depth mode, roundtable mode and custom mode, and use agents with different roles to collaborate to complete complex tasks. - Web workbench: Provides session switching, real-time streaming output, approval interruption, historical recovery and parallel sub-task status display. - Skills and MCP: Install and manage skills, support access to MCP services in the form of HTTP, SSE, and stdio. - File and sharing: Built-in file management, upload and download, search, preview, batch download and password sharing links. - Timed tasks: Support natural language creation of background tasks and view execution results and historical products. ###Daily usage 1. Create independent tasks by 'New Session', use the sidebar to switch historical sessions, and restore different contexts. 2. Ask the team mode directly in the input box, or use agent switch/`@ agent name` to point tasks to specific roles. 3. Click File Management to upload documents, code, pictures or data files, and then quote these files in the conversation to continue processing. 4. Maintain models, skills, MCP services, custom agents, channels, and long-term memory settings in System Configuration. 5. Click 'Timing Tasks' to view the list of existing tasks, filter by status, and enter the details to view the latest results and historical output. The current version of the Web interface does not have an entry for directly creating tasks. 6. If you need to use '/v1' for external clients, you still need to write the 'api_keys' of '[openai_api]' in the 'config/config.toml' of the application data, and then use 'https://fkteams. Your box name.heiyu.space/v1' as the OpenAI Base URL; there is no separate 'OpenAI Compatible API' configuration page in the existing Web configuration window. See the configuration method below. 7. If you need to use 'roundtable discussion', you need to prepare '[roundtable]' and '[[roundtable.members]]' separately in the 'config/config.toml' of the application data; each member's 'model' must reference the named model already defined in '[models]' and cannot be run directly by just a 'default' model card in the interface. See configuration below. ### `/v1` Default Key and Modification Location Open the application data of the application, and then you need to modify the config.toml file under the config folder. The modification location and example are as follows: ```toml [openai_api] api_keys = ["sk-your-own-key"] ``` After the modification is completed, restarting the application will take effect. ### `Roundtable Discussion` Configuration Example If you want to enable Roundtable Discussion, please also open the application data of this application and edit config/config.toml. Here is a minimum available example: ```toml [[models]] name = "planner" provider = "openai" base_url = "https://api.openai.comv1" api_key = "your_xaapi_key" model = "gpt-5.4" [[models]] name = "reviewer" provider = "openai" base_url = "https://api.openai.comv1" api_key = "your_xaapi_key" model = "gpt-5.4" [roundtable] max_iterations = 2 [[roundtable.members]] index = 0 name = "Plan Planner" desc = "Dissolve the problem first and propose an implementation plan" model = "planner" [[roundtable.members]] index = 1 name = "Result Reviewer" desc = "Supplementary risks, limitations and improvement recommendations" model = "reviewer" ``` Description: - Models in [[[roundtable.members]] must refer to existing names in [[models]] - Even if two members use the same model service, it is recommended to use different names to distinguish roles - After the modifications are completed, restarting the application will take effect