FeiZhuLulu/DeepSeek-Bot

This page introduces an external open-source repository. It is not an HDATF product.

What it does

DeepSeek-Bot (DS Bot) is a bot plugin installed into DeepSeek Harness (DSH) that adds the ability to create several bots with their own names and roles, talk with them, and hand work to them as a group. It is aimed at DSH users who want to split work among several AI bots, and the repository states that it is an independent community project separate from official DeepSeek products. Each bot is a DSH session with its own name, role, instructions and model, the bots exchange messages through the message_bot, create_bot, update_bot and ask_user tools, and a default bot called Chief manages the others. In group chats the admin bot answers by default, a mention passes the turn to another bot or a PASS marker skips a turn, and each member keeps a hidden session per group. Instead of DSH's conversation compaction, a bot writes a checkpoint through a separate call to a small model when context usage reaches 0.8. Memory is split into per-bot and team scopes and managed through the remember, forget and recall tools and a review after every turn, with limits such as 300 characters per entry and 4,000 characters for MEMORY.md, and content that looks like a secret is rejected. Web search tries the provider set in the profile, then search through the model route, then public Bing and DuckDuckGo result pages, and the bot browser in Desktop reads pages as Markdown in a read-only view separated per bot, skipping password and card fields. request_secret is described as passing a value received through a user input card only as a shell variable and keeping it out of state.json and logs, but only exact copies are masked, so encoded or split values can leak, file mode 600 has no effect on Windows, and values are sent in clear text on a page opened over http. Installation is done through Add plugin in the Plugins menu of DSH Desktop (Windows, macOS), or by assembling a configuration bundle in DSH Web with Node.js 22.19 or later and pnpm, and installing DSH and connecting the plugin are separate steps. The documentation says this is an early v0.1 release whose features, tools and storage format may change and that it was tested with dsh 0.2.1-alpha.1 on Linux, data is stored by default under .dsh/bot in the user folder, and the usage screen shows tokens only, without cost.

License

Apache-2.0 Permissive, with a patent grant. Commercial use is allowed; keep the notices and state your changes.

More in this category

• docker/docker-agent
  docker-agent is an AI agent runtime from Docker that defines agents in a YAML file and runs them with the docker agent command. The YAML lists the model, instructions, toolsets, sub-agents, fallback models, an iteration limit and skills. Tools are attached as MCP servers through the Docker MCP Gateway, local stdio or remote HTTP, alongside built-in tools such as think, todo and memory. Memory is kept in a SQLite file in the user's home folder, and RAG supports search that mixes BM25 with embeddings, plus reranking. Models come from external providers such as OpenAI, Anthropic, Gemini and Bedrock or from local models in Docker Model Runner, and the user sets the API keys. It installs as a plugin bundled with Docker Desktop 4.63 or later, or through Homebrew and release binaries. By default it asks the user before running tools with side effects, and permission rules can be applied in deny, allow, ask order. The --yolo option approves every tool automatically, sandboxed runs need Docker Sandboxes installed separately, and the working folder is mounted with write access. It also hands work to CLIs on the PATH such as claude and codex, serves a REST API with a session database, shares agents through OCI registries and evaluates by replaying saved sessions. Telemetry is on by default, and the documentation says not to assume the collected data is free of secrets or personal information.
• omnirush-ai/omnirush-gui
  OmniRush is a desktop application for asking a coding agent to work on a selected project. Prompts and project files become inputs, while edited files, command results and Git work become outputs. An Electron shell starts a local server and a bundled OpenCode engine that exposes skills and MCP tools to the selected model. MCP is a common interface through which agents call external tools. The application requires an approved OmniRush account and device sign-in before it runs prompts, and the available model catalog comes from that account. Published desktop builds target Apple Silicon macOS and Linux, not a native Windows desktop release. Free access is offered by the service itself, but its privacy policy permits collecting session traces and project uploads for model development and research partners. The desktop code is largely MIT-licensed, while the enterprise directory has separate terms, so neither local execution nor public source means private processing or unrestricted enterprise reuse.
• morluto/rea
  Gives agents tools to investigate application behavior and native binaries. Records evidence and distinguishes static inference from runtime observation.
• CopilotKit/OpenDots
  OpenDots is a self-hostable template for persistent AI agents with individual computers, spanning text, calls and Slack. Its early-stage workspace includes working-document Spaces and in-chat computer views and human review cards.
• anteloc/ldraw-nova
  ldraw-nova lets an AI agent build LEGO models from an idea and user guidance. Outputs include LDraw source, multiple views, editable glTF files and chat history.

Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.