dsh-gitea-search
针对 DeepSeek Harness，在自托管 Gitea 或 Forgejo 实例的本地镜像中进行跨仓库代码搜索。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:offzen/dsh-gitea-search#5efebe0fc2321bc68c82b1d96c9944acf865ac9aGitea Search 以 dsh-gitea-search 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Cross-repository code search for DeepSeek Harness over a local mirror of a self-hosted Gitea / Forgejo instance.
Self-hosted Gitea usually ships with the server-side code index disabled: the web UI and the API
cannot search file contents at all. This plugin mirrors every repository the token can read into a
local bare mirror, runs git grep over all of them on every branch, and exposes the results to the
model as three MCP tools (mcp__gitea_search__*). Searching and reading never touch the network.
search_gitea — file contents / file paths / commit messages, across all repositories and branchesread_gitea_file — one file from the mirror, without cloninglist_gitea_repos — what is in the mirror, optionally filtered^22.19.0 || >=24.0.0 and git (the only runtime dependencies)read:repository and read:user) for syncing a private instancedsh plugin --profile <profile> add dsh-gitea-search
--profile is required. The package declares dsh.bundle.patch, so dsh plugin add installs the
dependency, appends the bundle to the profile, and inserts the MCP client row for you — no YAML to
write. If the profile runs without configuration hot reload, restart dsh after installing; the
tools then appear as mcp__gitea_search__search_gitea, mcp__gitea_search__read_gitea_file and
mcp__gitea_search__list_gitea_repos.
The bundle starts the MCP server with npx -y dsh-gitea-search mcp (the package is distributed
prebuilt on npm, so no build permission is needed). Installing from a git checkout instead? Point
the row at node <path>/bin/mcp-server.mjs yourself — see the troubleshooting section.
The MCP client scrubs the ambient environment before it spawns the server, so values exported
in your shell do not reach it automatically. The bundle patch re-exports the variables explicitly
(!!js process.env.GITEA_* ?? ''), which means the source is the environment of the dsh process
itself — a systemd Environment= entry, or the shell that launched dsh.
| Variable | Default | Meaning |
|---|---|---|
GITEA_MIRROR_DIR | ~/.local/share/gitea-search/mirror | where the bare mirrors live |
GITEA_BASE_URL | — | Gitea/Forgejo base URL, required by sync |
GITEA_TOKEN | — | read-only API token, required by sync against a private instance |
GITEA_OWNER | all readable repos | comma-separated owners (users/orgs) to mirror |
GITEA_MAX_RESULTS | 200 | hard cap on records returned by search_gitea (max 1000) |
GITEA_MAX_SEARCH_BYTES | 131072 | total output budget for one search |
GITEA_MAX_LINE_BYTES | 2000 | per-line cap; longer lines are truncated in place with a marker |
GITEA_MAX_READ_BYTES | 60000 | per-file read cap |
GITEA_JOBS / GITEA_SYNC_JOBS | 6 | parallel repositories during search / sync |
GITEA_TIMEOUT_MS | 120000 | per git invocation timeout |
To change a value later, either export it for the dsh process, or override the row in your own
profile cordis.patch.yml by id (gitea-search) — note that an override replaces the whole
config value, so restate every key you want to keep.
export GITEA_BASE_URL=https://gitea.example.com
export GITEA_TOKEN=... # read-only token
npx -y dsh-gitea-search sync # first sync, then keep it fresh
sync enumerates every repository the token can read through the Gitea HTTP API and mirrors each
one (git clone --mirror, then git remote update --prune). The mirror is a plain directory of
bare repositories: <mirror>/<owner>/<repo>.git, or flat <mirror>/<repo>.git if you mirror a
single owner by hand. A cron entry or systemd timer keeps it fresh — examples are in
docs/MANUAL.md.
The same engine ships as a CLI: dsh-gitea-search search <pattern> [-p|-m|-E|-s|-w|-l|-c] [-r repo] [-b branch] [-A] [-n N] [--json],
plus repos, read <repo> <path> [--ref], sync [--transport https|ssh], mirror and mcp.
Run dsh-gitea-search --help for the full option list.
sync; the plugin never triggers it on its own.sync is the only networked step. The token goes to the Gitea API in an Authorization header
and to git through GIT_ASKPASS — never on a command line, never in a log (git output is
redacted before logging).git show --end-of-options, so a crafted ref
cannot be used as a git option (an arbitrary-file-write vector).failOnStartupError: true a failed MCP connection makes the row fail
to load while the harness still starts. Look for gitea-search in the dsh log. Common causes:
npx cannot reach the registry (offline host — install from a git checkout instead), or on
Windows npx may need to be written npx.cmd in the row.GITEA_MIRROR_DIR points
elsewhere — run sync once, then check dsh-gitea-search mirror.toolCallTimeoutMs: 120000. Narrow with repo, use mode: "path" or
files_only to probe first.dsh plugin --profile <profile> remove dsh-gitea-search
Remove the mirror directory and revoke the token afterwards.
Verified on a clean test machine (Node 24, Debian slim container) for each version below: bundle
installed with dsh plugin add, the profile layer resolved with no schema diagnostics, the
22-test suite green, and an MCP smoke run against a synthetic mirror (a 190 KB single-line blob and
a >64 KB CJK file) with no U+FFFD and the output guard intact.
| DSH version | Published | Install | Layer (--dump-config) | Schema diagnostics | Tests | MCP smoke |
|---|---|---|---|---|---|---|
0.2.0-rc.2 (latest, next) | 2026-09-29 | ok | ok | none | 22/22 | ok |
0.2.1-alpha.3 (alpha) | 2026-10-14 | ok | ok | none | 22/22 | ok |
0.2.1-alpha.2 | 2026-10-09 | ok | ok | none | 22/22 | ok |
0.2.1-alpha.1 | 2026-10-03 | ok | ok | none | 22/22 | ok |
The bundle declares an engines.dsh range as documentation; DSH gates installation by
peerDependencies on @deepseek-ai/dsh-*, which this configuration-only bundle does not declare,
so it installs on any 0.2.x runtime.
MIT