Skip to content

feat(adapter/junie): JetBrains Junie skill runtime #321

Closed

Description

@potiuk

Goal: Bring JetBrains Junie to feature parity with Claude Code as a skill runtime. Grounds: RFC-AI-0004 Principle 3 — Vendor neutrality.

Why Junie: JetBrains IDEs cover a large slice of the Java / Kotlin / PyCharm / IntelliJ user base — that includes most of the Apache Java-stack PMCs (Lucene/Solr, Cassandra, Camel, Beam, Flink, Kafka, Pulsar, NetBeans, …). Reaching parity means a maintainer can run framework skills from inside their JetBrains IDE without context-switching to a separate terminal CLI.

What "parity" means:

  • Skills under .claude/skills/<name>/SKILL.md are invokable from Junie
  • The tools/* bridges are reachable — Junie supports shell command execution
  • Sandbox parity: Junie runs inside the JetBrains IDE process; document threat-model considerations and the mapping to the framework's sandbox baseline (different — IDE-hosted)
  • HITL primitives: Junie has per-action confirmation natively — verify and document

Suggested approach:

  • Map SKILL.md → Junie's .junie/guidelines.md convention (Junie reads these natively as project-level agent instructions)
  • Document skill-invocation: how a maintainer triggers (e.g.) security-issue-triage from inside the JetBrains IDE
  • Validate which framework skills are well-suited to IDE-hosted execution vs better as terminal CLI flows

Reference:

Activity

  1. added
    enhancementNew feature or request
    capability:platformFramework / agent substrate skills (install, verify, doctor, override, status, setup bootstrap)
    on May 26, 2026
  2. potiuk commented on May 31, 2026

    @potiuk
    MemberAuthor

    Just work on it.. We do not assign things

  3. potiuk commented on Sep 10, 2026

    @potiuk
    MemberAuthor

    Two things that have moved since this was filed, both of which change where a contributor starts.

    The skill layout in the body is stale. This points at .claude/skills/<name>/SKILL.md. The tree now keeps sources in skills/ and exposes the harness-neutral .agents/skills/ layout — which is what the Codex adapter reads natively. A Junie adapter should target .agents/skills/, not the Claude-specific path; that also means the port inherits the universal layout instead of re-deriving one.

    Scope clarification worth keeping separate. Running Claude Code inside IntelliJ IDEA / PyCharm already works and needs nothing extra — plugin state lives in one user-scope store shared by every host of the same CLI, so a marketplace added in a terminal is already there in the IDE. That is now documented under JetBrains IDEs in marketplaces.md. This issue is specifically about Junie, JetBrains' own agent, which does not read Magpie's skills today — a genuine adapter, following docs/adapters/add-a-harness.md.

    The open question the suggested approach glosses over: mapping SKILL.md onto .junie/guidelines.md is a mapping onto project-level instructions, not onto invocable skills. Worth confirming early whether Junie can dispatch a named skill on demand, because if it only ingests guidelines as always-on context, 74 skills is not a viable shape and the port needs a different entry point.

  4. added
    family:docsDocs, MISSION.md, READMEs
    substrate:analyticsTool substrate: read-only metrics / dashboards / renderers
    substrate:action-guardTool substrate: deterministic pre-tool-use command guards
    substrate:framework-devTool substrate: build / validate / eval the framework itself
    on Oct 16, 2026
  5. Kaap10 commented on Nov 15, 2026

    @Kaap10
    Contributor

    The JetBrains Junie runtime documentation, adapter support, and test suite were merged in PR #1666 (commit 6c24f30). Closing this issue as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

capability:platformFramework / agent substrate skills (install, verify, doctor, override, status, setup bootstrap)enhancementNew feature or requestfamily:docsDocs, MISSION.md, READMEsfamily:setupsetup-* skillsfamily:toolstools/*good first issueGood for newcomerssubstrate:action-guardTool substrate: deterministic pre-tool-use command guardssubstrate:analyticsTool substrate: read-only metrics / dashboards / rendererssubstrate:framework-devTool substrate: build / validate / eval the framework itself

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions