fix(cli): a link to a nested agent lands on the wrong file in Kilo and OpenCode builds
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 83/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start with the agent link resolvers in cli/src/contexts/tools/domain/profiles/kilo/build.ts and cli/src/contexts/tools/domain/profiles/opencode/build.ts, then compare their path handling with the generic flat strategy's flatAgentPath. Add a failing test for a nested agent on each tool, then update the resolvers to match the flat path rule. Done when both tests confirm links point to the flattened agent files.
Written by the indexing model from the issue text.
Description
Description
In Kilo and OpenCode builds, a link from one agent's text to an agent nested under agents/<folder>/ resolves to a path that keeps the folder, while the agent file itself is written flattened. The link lands on a file that does not exist.
Affected file(s)
cli/src/contexts/tools/domain/profiles/kilo/build.ts, cli/src/contexts/tools/domain/profiles/opencode/build.ts (their own agent link resolvers)
Expected behaviour
A link to a nested agent resolves to the file the build writes, through the same rule as the generic flat strategy's flatAgentPath.
Observed behaviour
The generic flat strategy was aligned in #1158 (agent writer, command naming an agent, markdown link). The Kilo and OpenCode agent transforms still resolve links through their own resolvers, which do not drop the folder.
AI tool
Other: Kilo, OpenCode.
OS
macOS, Linux, Windows.
Additional context
No shipped plugin nests agents today, so no user is affected yet. The fix is a test with a nested agent on each of the two tools, red first.
- Dominant language
- TypeScript
- Stars
- 481
- Forks
- 45
- Avg merge
- 23h 18m
- Merged PRs (30d)
- 106
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ai-driven-dev/framework
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ai-driven-dev/framework#1162 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ai-driven-dev/framework#1147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ai-driven-dev/framework#1118 ·
Maintainers usually reply within 1 day
-
docs(framework): explain how a contributor without push access opens a pull requestMay be free again @sadhana-s-codez claimed this 9 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ai-driven-dev/framework#1117 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ai-driven-dev/framework#1112 · 1 comment ·
Maintainers usually reply within 1 day
All issues in ai-driven-dev/framework
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
shoelace-style/webawesome#2979 ·
Maintainers usually reply within 1 day
-
Chip source filter and denial markers miss Storage rows when a Storage activity source is pickedOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
omdsh-dev/DSH-better-sidebar#1141 ·
Maintainers usually reply within 2 days