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

Composition inspector: list a trusted remote checkout's plugin skills and agents

Open
  • Is something wrong?
#7,284 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ThomasK33 is already working on this.

Since Oct 26, 2026.

  • #7592 by @ThomasK33 — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
desktop, devtools

Research direction

Start in src/node/services/agentPlugins/composition.ts at buildWorkspaceComposition, then read how projectPluginContainerPaths applies the trust gate and how getRemoteProjectPluginSnapshot reads remote plugin data. Add coverage for a trusted remote project whose plugin skill appears and an untrusted one whose skill does not; done when both cases pass and the inspector lists the trusted remote plugins.

Written by the indexing model from the issue text.

Description

Follow-up from #6426. The composition inspector (buildWorkspaceComposition in src/node/services/agentPlugins/composition.ts) does not list the plugin skills and agents of a trusted SSH or Docker checkout, which turns now load from the cached remote snapshot (#7281 skills, C3 agents). The inspector shows what a turn would load, so it underreports for remote projects.

Fix direction: build the inspector's remote roots with the same trust gate (projectPluginContainerPaths) and read them through getRemoteProjectPluginSnapshot (no extra round trip once warm), with a test that a trusted remote checkout's plugin skill appears and an untrusted one does not.

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.