Start Development

The main project repository is at exokitxr/exokit. You can clone it the regular way:

git clone

Note: Exokit Engine and Exokit Browser both run off of the same codebase.

Install and build

All of the Exokit depedencies and native code can be build with npm install:

npm install

Linux dependencies

Linux additionally requires that you install some local dependencies. For debian/ubuntu they are:

apt-get install -y \
build-essential wget python libglfw3-dev libglew-dev libfreetype6-dev libfontconfig1-dev uuid-dev libxcursor-dev libxinerama-dev libxi-dev libasound2-dev libexpat1-dev


  1. Exokit’s bindings code is a native module build using the binding.gyp recipe.
  2. Exokit downloads and uses several prebuilt dependencies. They have been pre-compiled for all supported architectures and uploaded to npm. They self-extract themselves based off detected architecture.

Run Exokit Engine

Exokit Engine is just a node module, so you can run it with node.

From the exokit git clone directory, do:

node .

This will start the Exokit Engine CLI.

[x] // enter code here

Here, you can enter:

  • A URL, which will trigger navigation
  • <dom> elements
  • dom = <assignment> expressions
  • Commands to run in the context of the window

Note: This is the same experience as you get with the Exokit installer when running Exokit Engine CLI.


Exokit has a logging mode enabled by the -l flag:

exokit -l

The logs go in $HOME/.exokit/log.txt. For window that generally means C:\username\.exokit\log.txt.


You can use the regular Node debugging tools to debug Exokit Engine.

To start Exokit in inspector mode from the exokit git clone directory:

node --inspect .

After the above you should be able to use chrome://inspect in the Chrome browser to connect to the node running Exokit Engine. You can use this to:

  1. Inspect values from the browser
  2. Set deugging breakpoints
  3. Capture heap snapshots
  4. Capture CPU profiles of live sites

Wait for attach

You may also be interested in starting Exokit Engine so that it doesn’t run until you get a chance to attach the inspector. For that you can use:

node --inspect-brk .


See something? Please do file an issue!

Pull Requests are very much welcome as well.


  • <SkImage.h> not found, or a missing header: this means a prebuilt dependency did not extract. Clear your npm/yarn cache, rm -Rf node_modules and npm install again.