[Bug]: local/dsh-plugin — /loopforge and loopforge_status always throw "workingDirectory" without inject
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 75/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript, node.js
研究方向
從 local/dsh-plugin/index.js 開始,追蹤 cwdOf() 以及它在 handle() 和 tool execute() 中的呼叫位置。閱讀 DSH workingDirectory 服務 API,確認它如何解析 Agent 的目錄,接著檢查外掛程式的 inject 宣告。當 /loopforge 和 loopforge_status 都能正常運作且不再出現 workingDirectory 注入錯誤,並且報告確認新專案會回傳 {"found": false}、/loopforge start 會建立 workflow-state.json 時,即告完成。
由索引模型根據 Issue 內容生成。
描述
Component / host
Local — DeepSeek Harness (local/dsh-plugin). The bug-report form has no option for this host yet — another item worth adding, see "Related observations".
Edition
Local Portable
LoopForge version
commit dd56585276d8ecb6e0d6865f55e255194d75f85a — local/dsh-plugin = @tencent/[email protected]
What happened?
The Host bundle installs and activates (application: applied, row @tencent/loopforge-dsh resolves), but both surfaces it registers fail on every call with:
Error: cannot get property "workingDirectory" without inject
- the
loopforge_statusagent tool returns that error instead of{"found": false} /loopforge ...goes through the samecwdOf(), so it fails the same way
So the plugin is unusable on DSH 0.2.2-rc.3, even on a project where the Portable skill is installed.
Reproduction
-
Install the Portable skill into a project (see "Related observations" #1 for why
npx -y loopforge-cli@latestcannot do this today):node <repo>/local/bin/loopforge.mjs skills install dsh --project-root <project> -
Install the bundle into a DSH profile:
dsh plugin --profile <profile> add -w <repo>/local/dsh-plugin -
Restart DSH, then call the
loopforge_statustool from the agent, or type/loopforge status. -
Observe
Error: cannot get property "workingDirectory" without injectinstead of a status result.
Cause
index.js reads workingDirectory as a context property:
const service = agent?.ctx?.workingDirectory
?? agent?.ctx?.get?.('workingDirectory')
?? owner?.ctx?.workingDirectory
?? owner?.ctx?.get?.('workingDirectory')
but declares only:
export const inject = ['commands', 'tools']
In Cordis, reading an un-injected service property throws rather than returning undefined, so the DSH_PROJECT_ROOT / process.cwd() fallbacks are never reached.
Separately, the Agent contract in DSH is { readonly id: SessionId }; workingDirectory.get(session) takes a Session, which the plugin does not have here. workingDirectory.ensure(agent) is the documented way to get a session's directory from an Agent.
Suggested fix
-
Declare the service:
export const inject = ['commands', 'tools', 'workingDirectory'] -
Resolve the directory through the service API:
async function cwdOf(ctx, owner) { const agent = owner?.agent ?? owner const service = ctx.workingDirectory if (agent && typeof service?.ensure === 'function') { try { return resolve(await service.ensure(agent)) } catch {} } return resolve(process.env.DSH_PROJECT_ROOT ?? service?.defaultDirectory ?? process.cwd()) } -
awaitthe two call sites —handle()and the tool'sexecute().
Verified with this patch on DSH 0.2.2-rc.3 (macOS arm64, Node 24.19.0, Python 3.13.3): the tool returns {"found": false} on a fresh project, and /loopforge start <request> creates artifacts/<slug>/workflow-state.json through the skill's scripts/workflow_state.py.
Diagnostics
DSH 0.2.2-rc.3 (desktop runtime), profile-managed
OS macOS 15 arm64
node v24.19.0
python3 3.13.3
bundle @tencent/loopforge-dsh 0.1.0 (link: install from local dir)
error Error: cannot get property "workingDirectory" without inject
Related
- #112 / #120 — feature requests for a DSH host plugin, closed 2026-11-10. This bug is in the plugin that
landed afterwards (local/dsh-plugin), so it is not a re-report of those. - Searched
dshandloopforge-dshin existing issues: nothing covers this injection failure.
Related observations
- npm release lags the docs.
npx -y loopforge-cli@latest skills install dshfails with
argument host: invalid choice: 'dsh' (choose from codebuddy, codex, cursor, claude)on
[email protected](published 2026-09-16), whiledocs/local/usage.mdand
local/dsh-plugin/README.mdboth document that exact command.local/src/devflow_cli/targets/dsh.py
is already in the repo. Either cut a release or mark the DSH rows as "from source until the next release". - Bundle assumes a project-local skill.
SKILL_ROOT = '.dsh/skills/devflow'is hardcoded relative to
the project, but DSH also scans the user root$DSH_HOME/skills. With the skill installed globally,
/loopforgereports "Skill is not installed in this project". A project-first,
$DSH_HOME/skills/devflowfallback would support both layouts. (The skill's Python also requires a
siblingmanifest.jsonin whatever skills root it lives in — DSH ignores that file, so it is safe to
place there.) /devflowis not provided by this bundle.local/dsh-plugin/README.mdlists/devflow <request>
under "restart DSH and use", but the bundle registers only/loopforge; DSH surfaces skills through the
skill tool/catalog rather than as slash commands. Splitting that list into "provided by this bundle" vs
"provided by the skill install" would avoid the impression that both commands come from the plugin.- Issue template.
.github/ISSUE_TEMPLATE/bug_report.ymlhas no "Local — DeepSeek Harness" option
under Component / host, although DSH is a documented supported host.
- 主要語言
- Go
- 星號
- 711
- 分支
- 114
- 平均合併
- 1 天 10 小時
- 30 天內合併 PR
- 116
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
Tencent/LoopForge 的其他 Issue
-
[Bug] AI 对话切换 Claude Code 必定 400「不支持的执行器」:assistantEngineClaude 与 executorModelCatalogs 键名不一致可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 2/5 1-3 小時 新手友好度 74/100
Tencent/LoopForge#986 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 69/100
Tencent/LoopForge#969 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
Tencent/LoopForge#900 · 1 則留言 ·
維護者通常 1 天內回覆
-
[Bug]: 官方镜像未安装 wecom-cli,企业微信通知报「通知服务未安装 wecom-cli」可能已有人在做 @newexploreor 於 5 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 76/100
Tencent/LoopForge#156 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
難度 3/5 1-2 天 新手友好度 54/100
Tencent/LoopForge#994 · 1 則留言 ·
維護者通常 1 天內回覆
查看 Tencent/LoopForge 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 86/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 64/100
projectdiscovery/cdncheck#554 ·
維護者通常 1 天內回覆
-
triage needed
難度 2/5 1-3 小時 新手友好度 66/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 78/100
OpenSlides/openslides-go#342 ·
維護者通常 4 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 77/100