Skip to content


The Binder group contains the SDK packages for working with Binder specifications. This group allows developers to leverage Binder APIs to provide features such as connecting to notebooks, notebook servers, as well as notebook instances.

Table of contents


The @nteract/host-cache package contains a provider component for you to connect to a Binder instance and access its context in all child components. Examples of this package are in the source for the nteract play application.


The example below shows how to use the Host component within this package to connect to a Binder instance and display information about the connection.


import { Host } from "@mybinder/host-cache";

export default () => {
  return (
      <p>We've connected to a Binder instance within this context.</p>
        But now we need to retrieve some information about the Binder context we
        are connected to.
      <p>So let's use the "Host.Consumer" component!</p>
        {host =>
          host ? (
              Endpoint: {host.endpoint}
              Token: {host.token}
          ) : null


The @nteract/rx-binder package provides a set of functions for connecting to a remote instance provided by Binder. This package allows you to connect to a remote compute instance from your nteract application to execute code.

See an example of this package in the source code for the nteract play app.


This content is still in development. For more information, reach out to the community on GitHub.


const { binder } = require("rx-binder");

binder({ repo: "nteract/vdom" }).subscribe(msg => console.log(msg));
> { phase: 'built',
  imageName: '',
  message: 'Found built image, launching...\n' }
{ phase: 'launching', message: 'Launching server...\n' }
{ phase: 'ready',
  message: 'server running at\n',
  url: '',
  token: 'tocwpFakeToken' }