Skip to main content

Plugin store

The in-app plugin store lets you browse, search, and install community plugins into the current session. Plugins can add new track types, view types, data adapters, and custom menu items, and some carry their own data with them.

The full catalog of white-listed plugins, each with its config snippet, is also listed on the plugin store page.

To write your own plugin, see the developer guide.

Where the install persists depends on the context:

  • web session - saved into the session and travels with the share link
  • admin server - written to config.json, persists across sessions
  • JBrowse Desktop - saved into the open session file

Some plugins (e.g. CIVIC) add their data automatically when installed. Others only register building blocks (a new track type, a new adapter) that need a matching config entry to be useful. Ask an admin if you can't edit the config yourself.

The plugin store inside the app. Open this view in JBrowse ↗

The steps behind the figure above, run against your own data.

  1. Open your genome: on the JBrowse Desktop start screen click Open new genome (or Show all available genomes to pick a hosted one).This figure uses volvox, loaded from a .2bit genome.
  2. Type your region of interest into the location box and press Enter.This figure is at ctgA:1-20000.

Open this view in JBrowse Desktop ↗

Opens JBrowse Desktop (JBrowse Desktop 5.0+) at this view and saves it as a reopenable session — swap in your own files afterwards.

Nothing happens? Paste this link into Desktop's Open JBrowse Web link... (start screen, or File → Session):

https://jbrowse.org/code/jb2/main/?config=test_data%2Fvolvox%2Fconfig.json&session=spec-%7B%22views%22%3A%5B%7B%22type%22%3A%22LinearGenomeView%22%2C%22assembly%22%3A%22volvox%22%2C%22loc%22%3A%22ctgA%3A1-20000%22%7D%5D%7D&sessionName=JBrowse+docs%3A+plugin_store

This session spec pastes after &session=spec- on any JBrowse Web instance.

{
  "views": [
    {
      "type": "LinearGenomeView",
      "assembly": "volvox",
      "loc": "ctgA:1-20000"
    }
  ]
}

Loaded against config: test_data/volvox/config.json

The same view with jbrowse-anywidget, from the config the figure loads. Swap a track's uri for your own file.

from jbrowse_anywidget import JBrowseApp, fetch_hub

config = fetch_hub("https://jbrowse.org/code/jb2/main/test_data/volvox/config.json")
app = JBrowseApp(
    assemblies=config["assemblies"],
    tracks=config.get("tracks", []),
    views=[
        {
            "type": "LinearGenomeView",
            "assembly": "volvox",
            "loc": "ctgA:1-20000"
        }
    ],
)
app  # display the widget

Hand this to a coding agent. It rebuilds the figure above headlessly, and the session file is then the thing to edit — swap an adapter uri for your own file and rerun.

cat > session.json <<'JSON'
{
  "views": [
    {
      "type": "LinearGenomeView",
      "assembly": "volvox",
      "loc": "ctgA:1-20000"
    }
  ]
}
JSON

npx @jbrowse/capture --instance https://jbrowse.org/code/jb2/main/ \
  --config https://jbrowse.org/code/jb2/main/test_data/volvox/config.json \
  --session session.json -o figure.png

Using JBrowse with AI agents covers the rest: hosted genomes to point it at, and why waiting for the render is the part that goes wrong.

Keeping a plugin for every visit

A plugin installed in a web session goes when the session does: a new session, or someone else's link, starts without it. The pin beside a plugin in the Installed plugins list keeps it instead, so that JBrowse loads it every time you open it in this browser.

  • The list is per configuration, not per site. A plugin kept on jbrowse.org/code/jb2/main/?config=demos/hg002/config.json does not load on another demo, or on another version of the app.
  • It lives in this browser and nowhere else. A session you share carries none of it, and neither does the same JBrowse opened on another machine.
  • A kept plugin that did not load this visit — switched off, or skipped after a crash — is still a row in Installed plugins, with a switch beside it.
  • An admin editing config.json is installing for every visitor instead, so the pin does not appear in admin mode.

Permanent plugins load before anything is on screen, so a plugin that crashes on load would otherwise take the app down on every visit with no way back to the menu. Two things stop that:

  • The fatal error dialog offers Reload without permanent plugins.
  • If a load never finishes, JBrowse turns the stuck plugins off before the next visit. The plugin store then shows a banner naming them, with a switch per plugin and a Turn back on and reload button once the culprit is switched off.

Adding ?safeMode to the URL turns off every permanent plugin the same way, on purpose.

See also