You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👻 Andromeda · Kiro Crew Issue Radar — I examined this issue. I will not work on it, because it is a new feature, not a bug.
What I found (default branch main at 1f66a8f):
lowkey has no DeepSeek Harness pack. The registry (packs/registry.yaml, packs/registry.json) lists bedrockify, claude-code, openclaw, hermes, kiro-cli, codex-cli, roundhouse, troika and kirocrew. No file, commit or PR in the repo refers to "deepseek".
Thus no current behaviour is wrong. The request is for a new agent pack: a new packs/deepseek-harness/ (manifest.yaml, install.sh, test.sh, resources/, as in packs/codex-cli/), new entries in both registry files, and new rows in the README pack tables.
Decisions that a maintainer must make before somebody builds it:
Is a DeepSeek Harness pack wanted in lowkey?
Model backend: Bedrock (directly, or through the bedrockify OpenAI-compatible proxy, as openclaw does), or the DeepSeek API with its own key. This decision changes the deps, the required model access and the secrets setup.
Instance type, data volume, and whether it is experimental.
My recommendation: if you want it, use bedrockify as a dependency and mark the pack experimental, the same as other recent agent packs. Also change the label from bug to enhancement. When these decisions are on the issue, a crew can do the implementation.
I recorded a pass on this issue (scope: new-feature), so other crews will not examine it again.
Activity
royosherove commentedon Oct 11, 2026
👻 Andromeda · Kiro Crew Issue Radar — I examined this issue. I will not work on it, because it is a new feature, not a bug.
What I found (default branch
mainat1f66a8f):packs/registry.yaml,packs/registry.json) listsbedrockify,claude-code,openclaw,hermes,kiro-cli,codex-cli,roundhouse,troikaandkirocrew. No file, commit or PR in the repo refers to "deepseek".packs/deepseek-harness/(manifest.yaml,install.sh,test.sh,resources/, as inpacks/codex-cli/), new entries in both registry files, and new rows in the README pack tables.Decisions that a maintainer must make before somebody builds it:
bedrockifyOpenAI-compatible proxy, asopenclawdoes), or the DeepSeek API with its own key. This decision changes the deps, the required model access and the secrets setup.experimental.My recommendation: if you want it, use
bedrockifyas a dependency and mark the packexperimental, the same as other recent agent packs. Also change the label frombugtoenhancement. When these decisions are on the issue, a crew can do the implementation.I recorded a pass on this issue (scope: new-feature), so other crews will not examine it again.