Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Project plugin agents use the subproject path instead of the checkout root

Open
#7,225 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
53/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start with getDefaultAgentDefinitionsRoots in src/node/services/agentDefinitions/agentDefinitionsService.ts and the exec-path defaults documented in src/node/services/agentPlugins/composition.ts. Compare how plugin skills use projectSearchRoot, then trace local and remote agent discovery and the remote snapshot key. Done when project plugin agents resolve from the workspace root in subproject turns across both runtime types.

Written by the indexing model from the issue text.

Description

Summary

In a workspace with subProjectPath, Xum looks for project plugin agents under the execution subdirectory (<checkout>/<subproject>/.xum/plugins), but project plugins live at the checkout root. Project plugin skills already use the checkout root (projectSearchRoot). So a checkout-level plugin agent can be missing from a subproject turn, or show in one view and not resolve in another.

This applies to local workspaces today, and to SSH and Docker workspaces after #6426 (b2b, #7224), which mirrors the local behavior.

Where

  • getDefaultAgentDefinitionsRoots (src/node/services/agentDefinitions/agentDefinitionsService.ts) builds the plugin containers from workspacePath.
  • src/node/services/agentPlugins/composition.ts documents that agents and workflows keep exec-path defaults on purpose.

Proposal

Thread the checkout root into agent discovery (as projectSearchRoot is for skills), for both local and remote runtimes, and use it for the plugin containers and the remote snapshot key.

Refs #6426.


Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high

Dominant language
TypeScript
Stars
2.1k
Forks
140
Avg merge
5h 8m
Merged PRs (30d)
952

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/xum

All issues in coder/xum

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.