How do I share what Junie produced?

Add Comma as an MCP server in the JetBrains AI settings and put the publish rule in `.junie/guidelines.md`. Junie then publishes finished documents and replies with a URL rather than leaving them in the tool window.

Where does Junie read project instructions from?

`.junie/guidelines.md` in the project. It is loaded for every task in that project, which makes it the right home for a standing rule about where finished work goes.

Does this work across the JetBrains IDEs?

Yes — the MCP configuration is at the IDE level, so IntelliJ, PyCharm, GoLand, RubyMine and the rest all pick it up the same way.

Why not attach the document to the issue tracker?

You can, and for tracking that is correct. But an attachment has no anchored comment thread and no revision history, so review feedback ends up as a list of 'in section 3 you said…' comments instead of marks on the sentence.

What scope does the token need?

`reports:write`, plus `comments:read` if Junie should read feedback back on a later run.

Share what Junie produced

Junie does its best work on the tasks that end in prose: work out what this twelve-year-old Spring service actually does on startup, plan the Kotlin migration, review the module boundaries and say which ones are lying.

The output arrives in a tool window docked inside the IDE. The architect who needs to approve the module boundaries may well be in a different IDE, or in no IDE at all.

Attach the server, then write the guideline

Comma is a remote MCP server — an endpoint and a Bearer token from API tokens, registered in the JetBrains AI settings. The shape is the one in MCP setup.

Then make it standing, in .junie/guidelines.md:

When a task's deliverable is a document — a migration plan, an architecture
review, an investigation — publish it to Comma as an HTML report and reply with
the URL. Update the recorded report id rather than creating a new report.

Because guidelines are per project and committed, everyone on the repo inherits the behaviour without a setup conversation.

The enterprise-Java case for this

Long-lived JVM codebases produce exactly the documents that outlive the person who asked for them: the reason a module boundary is where it is, the risk register for a framework upgrade. A tool window is not a place for those. A URL with revision history is.

It renders, in a sandboxed iframe — call graphs, tables, stack traces intact.
The reader needs no IDE. Not IntelliJ, not a licence, not the repo.
Comments anchor to the claim, so the objection sits on the boundary being argued about — see commenting on HTML.
Revisions stack on one URL, so the link in the ticket ages well.

Share what Junie produced

Attach the server, then write the guideline

The enterprise-Java case for this

Worth knowing

Try it

Related