How to use anime-find
DeepSeek Harness plugin for in-conversation multi-source anime search. Aggregates results from Mikan
This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.
This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.
Quick start
anime-find
— source: plugin_wiki.wiki_content
Install & verify
dsh plugin --profile web add @cocofhu/anime-find
Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.
— source: plugins.install
Key points
- 聚合 Mikan、AniBT 和 AnimeGarden
- 在对话流中展示番剧封面、标题、评分、格式和资源数量
- 根据 Asia/Shanghai 时区识别当前新番季度
- 支持「还有吗」「换一批」等追问并分页展示更多结果
- 点击卡片后按字幕组和集数浏览资源,并可查看 Bangumi 介绍、评分和短评
— source: plugin_wiki.readme_en (fallback readme_raw)
FAQ
What should I say in the conversation to trigger the anime search?
Any anime-related questions will cause the Agent to call the anime_find_search tool and output clickable cards in the reply; saying "what are some good anime lately" "this season" "any more" will automatically expand according to the current quarter (Asia/Shanghai timezone). Saying "search Mushoku Tensei" will search by title.
What can I see after clicking on a card?
A resource list grouped by subtitle team, containing episode numbers, magnet links and .torrent file addresses; if the card has a Bangumi ID, the details will also fetch the introduction, rating, genre tags and up to 5 short reviews, all done on the Host side as a proxy and not written to the tool body for the Agent.
Can the streaming Tab be used by default? Do I need to prepare my own rules?
It is enabled by default with a built-in pilot rule xfdm (static parsing only, no content hosting). If that site is unavailable, you can disable it in settings or paste custom rule JSON; the rule must be statically parseable and contain at least these eight fields: name/baseURL/searchURL/searchList/searchName/searchResult/chapterRoads/chapterResult.
Do I need to restart dsh web after installation?
Yes. After installing/updating the plugin, you need to restart dsh web and force refresh the browser; this is because the HLS player (hls.min.js) is explicitly registered by the Host and can only be loaded by ToolView after refreshing.
Do I need to restart after changing the config? Where is the file stored?
No, it takes effect upon saving. The config is written to anime-find.json in the Harness user directory (default $DSH_HOME/anime-find.json, or ~/.dsh/anime-find.json if DSH_HOME is not set). Version and installation source are read-only fields and will not be written to this file.
What should I do when prompted "The player cannot load this episode"?
This is due to no playable address being parsed for that episode or source site restrictions. You can switch to other sources in the same tab, or open the source site page directly to watch; when rule parsing is limited, the streaming Tab will automatically hide but will not affect the introduction and resource browsing.
Will data be sent to the model or uploaded to the cloud?
No. Search requests are sent by the plugin to the corresponding source sites (Mikan/AniBT/AnimeGarden), and Bangumi introductions/short reviews are requested by the Host as a proxy and only rendered to the UI, not written to the tool body for the Agent; the config file only exists locally.
How do I update to the latest version?
Manually click "Check for Updates" in the "Version & Update" section of the plugin settings page. When a new version is found, follow the prompts to execute "dsh plugin --profile web update anime-find" in the terminal, then restart dsh web and force refresh the browser; it will not check automatically, nor use pre-release/draft Releases. This command will not be displayed for local link/file installations.
— source: plugin_wiki.faq_json
Compatibility
- DSH: >= 0.1.0-rc.6(peerDependency 写 *;开发时使用 @deepseek-ai/dsh-tools ^0.1.0-rc.6)
- Node: >=22(package.json#engines.node)
— source: plugin_wiki.compatibility_json
Pitfalls
Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.
— source: general rule