@codedroid/mcp 0.1.1 → 0.1.2

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "codedroid",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Your Android phone, through CodeDroid: read the screen, tap and type, hand CodeDroid a whole task, run adb, and verify app changes on the device.",
   "author": {
     "name": "CodeDroid"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "codedroid",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Drive your Android phone through CodeDroid, with MCP tools and device testing skills.",
   "author": {
     "name": "CodeDroid"

package/{LICENSE.aura-mcp-connect → LICENSE}

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 Dinesh Kumar C
+Copyright (c) 2026 CodeDroid
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -1,264 +1,80 @@
 # CodeDroid MCP
 
-Connect Claude Code, Codex, Gemini CLI, and other MCP clients to your Android phone.
+Let Claude Code, Codex, Gemini CLI, or any MCP client use your Android phone.
+Read the screen, interact with apps, take screenshots, and test what you build
+through [CodeDroid](https://get.codedroid.com). Your phone and computer can be on different networks.
 
-CodeDroid MCP provides tools for reading the screen, interacting with apps, taking screenshots,
-and running tasks through the [CodeDroid Android app](https://get.codedroid.com). The phone and
-computer can be on different networks. The optional `adb` tool requires a separate USB or
-wireless debugging connection.
+## Get started
 
-## Requirements
+You'll need **Node.js 20+** and **CodeDroid on your Android phone**, signed in with
+its accessibility service enabled. Both devices need internet access.
 
-- Node.js 20 or later on your computer.
-- CodeDroid installed on your phone, signed in, with its accessibility service enabled.
-- An internet connection on both devices.
+### 1. Install for your coding client
 
-To use the optional `adb` tool, install [Android platform-tools](https://developer.android.com/tools/releases/platform-tools)
-on your computer and connect the phone over USB or wireless debugging.
-
-## Installation
-
-Choose your coding client below. Each plugin or extension includes the MCP server and two
-skills: `codedroid-phone` for interacting with the phone, and `test-on-device` for building,
-installing, and testing Android apps.
-
-### Claude Code
-
-Run these commands in Claude Code:
+**Claude Code** — run inside Claude Code:
 
 ```text
 /plugin marketplace add codedroid-team/codedroid-mcp
 /plugin install codedroid@codedroid
 ```
 
-### Codex
-
-Run these commands in your terminal with a current version of the Codex CLI:
+**Codex** — run in your terminal:
 
 ```bash
 codex plugin marketplace add codedroid-team/codedroid-mcp
 codex plugin add codedroid@codedroid
 ```
 
-### Gemini CLI
+**Gemini CLI** — run in your terminal:
 
 ```bash
 gemini extensions install https://github.com/codedroid-team/codedroid-mcp
 ```
 
-Restart your coding client after installation, then pair your phone.
+Each installation includes the MCP server and skills for phone control and Android app testing.
+Restart your coding client after installing.
 
-For a standalone MCP server or another client, see [MCP configuration](#mcp-configuration).
+Using another client? See [manual MCP setup](docs/reference.md#mcp-configuration).
 
-## Pair your phone
+### 2. Pair your phone
 
-1. On the phone, open **CodeDroid → Settings → Computers → Pair a computer**.
-2. Run the command shown on the phone in your computer's terminal. For example:
+1. Open **CodeDroid → Settings → Computers → Pair a computer** on your phone.
+2. Run the command shown there in your computer's terminal. For example:
 
    ```bash
    npx -y @codedroid/mcp pair ABCD-EFGH
    ```
 
-3. Tap **Allow** on the phone when prompted.
+3. Tap **Allow** on your phone when prompted.
 
-Pairing codes expire after 10 minutes and can only be used once. Development builds include
-`--server=<url>` in the pairing command; use the command exactly as displayed.
+Use the command exactly as shown. Pairing codes expire after 10 minutes and work once.
 
-To verify the connection, ask your coding agent:
+### 3. Ask your agent
 
 > Read the screen on my phone and describe what is open.
 
-Or check from your terminal:
-
-```bash
-npx -y @codedroid/mcp status
-npx -y @codedroid/mcp call get_screen
-```
-
-## Usage
-
-Ask your coding agent to work with the paired phone. For example:
-
-- "Open Android Settings and check the Android version."
-- "Open my app, navigate to the sign-in screen, and take a screenshot."
-- "Install this APK, launch the app, and check logcat for crashes." (Requires `adb`.)
-
-The agent can interact with the phone one step at a time or use `run_task` to delegate a goal
-to CodeDroid's agent. `run_task` returns a task ID. Use `get_task` to wait for completion and
-read progress, or `cancel_task` to stop the task.
-
-### Tools
-
-| Tool | Description |
-| --- | --- |
-| `get_screen` | Read the current app and screen as numbered accessibility elements; optionally include a screenshot. |
-| `take_screenshot` | Capture a JPEG screenshot. |
-| `tap`, `long_press` | Interact with an element by node, text, resource ID, content description, or screen coordinates. |
-| `type_text` | Enter text in the focused field; optionally clear it first or press Enter afterward. |
-| `swipe` | Swipe or scroll between screen coordinates. |
-| `press_key` | Press Back, Home, Enter, or Recents. |
-| `open_app`, `list_apps` | Launch an app by package name or list installed apps. |
-| `wait_for` | Wait for text to appear or disappear, or for an app to open. |
-| `clipboard` | Read or update the clipboard. |
-| `device_info` | Inspect the device model, Android version, user, screen, lock state, and CodeDroid readiness. |
-| `run_task`, `get_task`, `cancel_task` | Start, monitor, or cancel a task run by CodeDroid's agent. |
-| `adb` | Run local adb commands against the connected phone. |
-| `codedroid_status` | Check the phone connection and get instructions for resolving connection problems. |
-
-Screen interaction tools return an `after` observation with the current app, keyboard state,
-screen changes, and visible elements. Phone tool errors include an error code, message, and
-hint for recovery.
-
-## Manage access
-
-Paired computers appear in **Settings → Computers** on the phone.
-
-- **Remove** revokes a computer's access. Pair again to reconnect it.
-- **Stop** disconnects the active computer and blocks it for one minute.
-- **Allow computers to connect** turns computer access on or off.
-
-CodeDroid displays the computer's name and a Stop button while it acts on the phone.
-
-## MCP configuration
-
-Use these options when you want the MCP server without a plugin or extension. Configure one
-installation method per client to avoid registering the tools twice.
-
-### Standalone Claude Code server
-
-```bash
-claude mcp add codedroid -- npx -y @codedroid/mcp
-npx -y @codedroid/mcp skill install
-```
-
-The optional second command installs the two skills in `~/.claude/skills`.
-
-### Standalone Codex server
-
-```bash
-codex mcp add codedroid -- npx -y @codedroid/mcp
-npx -y @codedroid/mcp skill install --codex
-```
-
-The optional second command installs the skills in `~/.codex/skills`. For calls longer than Codex's
-60-second default timeout, such as APK installation, set `tool_timeout_sec` in
-`~/.codex/config.toml`:
-
-```toml
-[mcp_servers.codedroid]
-command = "npx"
-args = ["-y", "@codedroid/mcp"]
-tool_timeout_sec = 300
-```
-
-### Standalone Gemini CLI server
-
-```bash
-gemini mcp add --scope user --timeout 300000 codedroid npx -y @codedroid/mcp
-```
-
-### Other MCP clients
+Then try:
 
-Add this server configuration to your client's MCP settings:
+- “Open Android Settings and check the Android version.”
+- “Open my app, navigate to sign-in, and take a screenshot.”
+- “Install this APK, launch it, and check for crashes.”*
 
-```json
-{
-  "mcpServers": {
-    "codedroid": {
-      "command": "npx",
-      "args": ["-y", "@codedroid/mcp"]
-    }
-  }
-}
-```
-
-Clients that support Streamable HTTP can also connect to `http://127.0.0.1:4826/mcp` while the
-CodeDroid MCP daemon is running.
+*Installing APKs and using `adb` also requires Android platform-tools and a USB or wireless
+debugging connection. See [adb setup](docs/reference.md#adb-setup).
 
-### Environment variables
+## Need help?
 
-| Variable | Description |
-| --- | --- |
-| `CODEDROID_SERIAL` | Select an adb device when several are connected. `ANDROID_SERIAL` is also supported. |
-| `CODEDROID_MCP_PORT` | Set the local daemon port. Default: `4826`. |
-| `CODEDROID_MCP_ADB=0` | Disable the `adb` tool. |
-| `CODEDROID_MCP_CLIENT` | Set the client name shown on the phone. |
-| `ADB` | Set the path to the adb executable. |
-| `CODEDROID_DEBUG=1` | Include stack traces in diagnostic output. |
-
-## CLI reference
+Check your connection:
 
 ```bash
-npx -y @codedroid/mcp pair ABCD-EFGH
-npx -y @codedroid/mcp connect
 npx -y @codedroid/mcp status
-npx -y @codedroid/mcp call get_screen
-npx -y @codedroid/mcp call tap '{"text": "Display"}'
-npx -y @codedroid/mcp stop
 ```
 
-`connect` reconnects a paired computer. `stop` shuts down the local daemon.
-
-## Troubleshooting
-
-Run `npx -y @codedroid/mcp status` or call `codedroid_status` from your agent to diagnose a
-connection problem.
-
-| Problem | Action |
-| --- | --- |
-| Computer is not paired, or pairing was removed | Create a new code in **Settings → Computers → Pair a computer** and run the displayed command. |
-| Phone is not connected | Open CodeDroid, check its internet connection and sign-in, and enable **Allow computers to connect**. |
-| Connection is awaiting approval | Tap **Allow** on the phone. |
-| Connection was denied | Wait one minute, run `npx -y @codedroid/mcp connect`, then tap **Allow**. |
-| Connection was stopped on the phone | Wait one minute before reconnecting. |
-| adb cannot find the phone | Connect it over USB, or run `adb pair <ip:port>` followed by `adb connect <ip:port>` for wireless debugging. |
-
-Force-stopping or running instrumentation against `com.codedroid.app` disables its accessibility
-service. Re-enable it in Android Accessibility settings afterward. Clearing the app's data also
-signs it out. UiAutomator tests and `uiautomator dump` temporarily suspend CodeDroid's
-accessibility access while they run.
-
-## Architecture
-
-```text
-MCP client → stdio bridge → local daemon → CodeDroid relay → Android app
-                              └── local adb
-```
-
-All clients on a computer share a local daemon and its connection to the paired phone. The
-phone and daemon each open an outbound WebSocket to the CodeDroid server. The phone reconnects
-after a restart or network change. MCP screen interactions are serialized on the phone.
-
-Calls interrupted by a connection loss are not automatically replayed: an action may have
-completed before its response was lost. Read the screen before deciding whether to retry.
-
-Pairing credentials are stored in `~/.codedroid/host.json`, readable only by your user account.
-Daemon logs are written to `~/.codedroid/daemon.log`.
-
-## Development
-
-From the package directory:
-
-```bash
-npm install
-npm test
-claude mcp add codedroid -- node "$PWD/src/index.js"
-```
-
-The npm tests run without a phone, relay server, or adb. In the monorepo, the Android app's MCP
-JVM tests also verify the bridge against the app's server implementation and export the tool
-fixture used by the skill tests. Install the package's npm dependencies before running those
-contract tests from `CodeDroid-app/`:
-
-```bash
-./gradlew :app:testDebugUnitTest --tests 'com.codedroid.app.mcp.*'
-```
+Manage or revoke computer access in **CodeDroid → Settings → Computers**.
 
-These tests export `test/fixtures/phone-tools.json` and run `test/phone-contract.mjs` against
-the app's MCP server through a test relay.
+See the [reference guide](docs/reference.md) for tools, manual setup, configuration,
+[troubleshooting](docs/reference.md#troubleshooting), and development.
 
-## Attribution
+## License
 
-Parts of the bridge are derived from
-[aura-mcp-connect](https://github.com/Dinesh210805/aura-android-use/tree/main/aura-mcp-connect)
-(MIT, Copyright (c) 2026 Dinesh Kumar C). See [LICENSE.aura-mcp-connect](LICENSE.aura-mcp-connect).
+[MIT](LICENSE) © 2026 CodeDroid

package/docs/reference.md

@@ -0,0 +1,188 @@
+# CodeDroid MCP reference
+
+[Back to setup](../README.md)
+
+## Tools
+
+The agent can interact with the phone one step at a time or use `run_task` to delegate a goal
+to CodeDroid's agent. `run_task` returns a task ID. Use `get_task` to wait for completion and
+read progress, or `cancel_task` to stop the task.
+
+| Tool | Description |
+| --- | --- |
+| `get_screen` | Read the current app and screen as numbered accessibility elements; optionally include a screenshot. |
+| `take_screenshot` | Capture a JPEG screenshot. |
+| `tap`, `long_press` | Interact with an element by node, text, resource ID, content description, or screen coordinates. |
+| `type_text` | Enter text in the focused field; optionally clear it first or press Enter afterward. |
+| `swipe` | Swipe or scroll between screen coordinates. |
+| `press_key` | Press Back, Home, Enter, or Recents. |
+| `open_app`, `list_apps` | Launch an app by package name or list installed apps. |
+| `wait_for` | Wait for text to appear or disappear, or for an app to open. |
+| `clipboard` | Read or update the clipboard. |
+| `device_info` | Inspect the device model, Android version, user, screen, lock state, and CodeDroid readiness. |
+| `run_task`, `get_task`, `cancel_task` | Start, monitor, or cancel a task run by CodeDroid's agent. |
+| `adb` | Run local adb commands against the connected phone. |
+| `codedroid_status` | Check the phone connection and get instructions for resolving connection problems. |
+
+Screen interaction tools return an `after` observation with the current app, keyboard state,
+screen changes, and visible elements. Phone tool errors include an error code, message, and
+hint for recovery.
+
+## Manage access
+
+Paired computers appear in **Settings → Computers** on the phone.
+
+- **Remove** revokes a computer's access. Pair again to reconnect it.
+- **Stop** disconnects the active computer and blocks it for one minute.
+- **Allow computers to connect** turns computer access on or off.
+
+CodeDroid displays the computer's name and a Stop button while it acts on the phone.
+
+## adb setup
+
+The optional `adb` tool requires [Android platform-tools](https://developer.android.com/tools/releases/platform-tools)
+on your computer and a USB or wireless debugging connection to your phone.
+
+For USB, enable **USB debugging** in the phone's Developer options, connect the cable, and
+accept the debugging prompt on the phone. Run `adb devices` to check the connection.
+For wireless debugging, see [troubleshooting](#troubleshooting).
+
+## MCP configuration
+
+Use these options when you want the MCP server without a plugin or extension. Configure one
+installation method per client to avoid registering the tools twice.
+
+### Standalone Claude Code server
+
+```bash
+claude mcp add codedroid -- npx -y @codedroid/mcp
+npx -y @codedroid/mcp skill install
+```
+
+The optional second command installs the two skills in `~/.claude/skills`.
+
+### Standalone Codex server
+
+```bash
+codex mcp add codedroid -- npx -y @codedroid/mcp
+npx -y @codedroid/mcp skill install --codex
+```
+
+The optional second command installs the skills in `~/.codex/skills`. For calls longer than Codex's
+60-second default timeout, such as APK installation, set `tool_timeout_sec` in
+`~/.codex/config.toml`:
+
+```toml
+[mcp_servers.codedroid]
+command = "npx"
+args = ["-y", "@codedroid/mcp"]
+tool_timeout_sec = 300
+```
+
+### Standalone Gemini CLI server
+
+```bash
+gemini mcp add --scope user --timeout 300000 codedroid npx -y @codedroid/mcp
+```
+
+### Other MCP clients
+
+Add this server configuration to your client's MCP settings:
+
+```json
+{
+  "mcpServers": {
+    "codedroid": {
+      "command": "npx",
+      "args": ["-y", "@codedroid/mcp"]
+    }
+  }
+}
+```
+
+Clients that support Streamable HTTP can also connect to `http://127.0.0.1:4826/mcp`.
+After pairing, run `npx -y @codedroid/mcp connect` to start the shared daemon before connecting
+an HTTP client.
+
+### Environment variables
+
+| Variable | Description |
+| --- | --- |
+| `CODEDROID_SERIAL` | Select an adb device when several are connected. `ANDROID_SERIAL` is also supported. |
+| `CODEDROID_MCP_PORT` | Set the local daemon port. Default: `4826`. |
+| `CODEDROID_MCP_ADB=0` | Disable the `adb` tool. |
+| `CODEDROID_MCP_CLIENT` | Set the client name shown on the phone. |
+| `ADB` | Set the path to the adb executable. |
+| `CODEDROID_DEBUG=1` | Include stack traces in diagnostic output. |
+
+## CLI reference
+
+```bash
+npx -y @codedroid/mcp pair ABCD-EFGH
+npx -y @codedroid/mcp connect
+npx -y @codedroid/mcp status
+npx -y @codedroid/mcp call get_screen
+npx -y @codedroid/mcp call tap '{"text": "Display"}'
+npx -y @codedroid/mcp stop
+```
+
+`connect` reconnects a paired computer. `stop` shuts down the local daemon.
+
+## Troubleshooting
+
+Run `npx -y @codedroid/mcp status` or call `codedroid_status` from your agent to diagnose a
+connection problem.
+
+| Problem | Action |
+| --- | --- |
+| Computer is not paired, or pairing was removed | Create a new code in **Settings → Computers → Pair a computer** and run the displayed command. |
+| Phone is not connected | Open CodeDroid, check its internet connection and sign-in, and enable **Allow computers to connect**. |
+| Connection is awaiting approval | Tap **Allow** on the phone. |
+| Connection was denied | Wait one minute, run `npx -y @codedroid/mcp connect`, then tap **Allow**. |
+| Connection was stopped on the phone | Wait one minute before reconnecting. |
+| adb cannot find the phone | Connect it over USB, or run `adb pair <ip:port>` followed by `adb connect <ip:port>` for wireless debugging. |
+
+Force-stopping or running instrumentation against `com.codedroid.app` disables its accessibility
+service. Re-enable it in Android Accessibility settings afterward. Clearing the app's data also
+signs it out. UiAutomator tests and `uiautomator dump` temporarily suspend CodeDroid's
+accessibility access while they run.
+
+## Architecture
+
+```text
+MCP client → stdio bridge → local daemon → CodeDroid relay → Android app
+                              └── local adb
+```
+
+All clients on a computer share a local daemon and its connection to the paired phone. The
+phone and daemon each open an outbound WebSocket to the CodeDroid server. The phone reconnects
+after a restart or network change. MCP screen interactions are serialized on the phone.
+
+Calls interrupted by a connection loss are not automatically replayed: an action may have
+completed before its response was lost. Read the screen before deciding whether to retry.
+
+Pairing credentials are stored in `~/.codedroid/host.json`, readable only by your user account.
+Daemon logs are written to `~/.codedroid/daemon.log`.
+
+## Development
+
+From the package directory:
+
+```bash
+npm install
+npm test
+claude mcp add codedroid -- node "$PWD/src/index.js"
+```
+
+The npm tests run without a phone, relay server, or adb. In the monorepo, the Android app's MCP
+JVM tests also verify the bridge against the app's server implementation and export the tool
+fixture used by the skill tests. Install the package's npm dependencies before running those
+contract tests from `CodeDroid-app/`:
+
+```bash
+./gradlew :app:testDebugUnitTest --tests 'com.codedroid.app.mcp.*'
+```
+
+These tests export `test/fixtures/phone-tools.json` and run `test/phone-contract.mjs` against
+the app's MCP server through a test relay.
+

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "codedroid",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Drive your Android phone through CodeDroid, with MCP tools and device testing skills.",
   "mcpServers": {
     "codedroid": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codedroid/mcp",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "MCP server for controlling Android devices through CodeDroid from Claude Code, Codex, Gemini CLI, and other MCP clients.",
   "type": "module",
   "main": "src/index.js",
@@ -16,7 +16,8 @@
     "gemini-extension.json",
     ".mcp.json",
     "README.md",
-    "LICENSE.aura-mcp-connect"
+    "docs",
+    "LICENSE"
   ],
   "engines": {
     "node": ">=20"
@@ -42,5 +43,6 @@
   "repository": {
     "type": "git",
     "url": "git+https://github.com/codedroid-team/codedroid-mcp.git"
-  }
+  },
+  "license": "MIT"
 }

package/src/adb-tool.js

@@ -2,10 +2,8 @@
  * adb — a single generic MCP tool that runs an adb command against a phone
  * attached to THIS computer (USB, or Wireless Debugging).
  *
- * Forked from aura-mcp-connect's `aura-adb` (MIT, Copyright (c) 2026 Dinesh Kumar C;
- * see LICENSE.aura-mcp-connect). Changed: on by default, since the user is a developer
- * (CODEDROID_MCP_ADB=0 turns it off); marked destructive so clients ask before running
- * it; a per-call timeout.
+ * Enabled by default (CODEDROID_MCP_ADB=0 turns it off), with a per-call timeout.
+ * Marked destructive so clients ask before running it.
  *
  * It never touches the connection to CodeDroid: it shells out to this machine's
  * own `adb`, exactly like a developer typing `adb install app.apk` themselves.

package/src/daemon.js

@@ -3,9 +3,7 @@
  * CodeDroid on the phone (through the CodeDroid server's relay) and serves MCP over
  * Streamable HTTP on localhost.
  *
- * Forked from aura-mcp-connect (MIT, Copyright (c) 2026 Dinesh Kumar C; see
- * LICENSE.aura-mcp-connect): the link is a WebSocket relay instead of WebRTC, and the adb tool is
- * on by default.
+ * The phone connection uses a WebSocket relay. The adb tool is enabled by default.
  *
  * Every MCP client (Claude Code, Claude Desktop, Cursor, VS Code windows…)
  * connects to http://127.0.0.1:<port>/mcp and gets its own MCP session; tool

package/src/index.js

@@ -21,8 +21,6 @@
  * leaves out the adb tool. CODEDROID_SERIAL picks the adb tool's device when several are attached.
  *
  * All log output goes to stderr — stdout is reserved for MCP JSON-RPC frames.
- *
- * Forked from aura-mcp-connect (MIT, Copyright (c) 2026 Dinesh Kumar C; see LICENSE.aura-mcp-connect).
  */
 import { VERSION } from "./version.js";
 

package/src/proxy-core.js

@@ -2,10 +2,9 @@
  * proxy-core — builds an MCP Server that transparently forwards requests to a
  * backend MCP Client (the single phone connection).
  *
- * Forked from aura-mcp-connect (MIT, Copyright (c) 2026 Dinesh Kumar C; see
- * LICENSE.aura-mcp-connect). Changed: a session still opens when the phone cannot be
- * reached, serving the local tools (adb, codedroid_status) and saying why in its
- * instructions, and tools/list keeps trying the phone.
+ * A session still opens when the phone cannot be reached, serving the local tools
+ * (adb, codedroid_status) and saying why in its instructions. tools/list keeps
+ * trying the phone.
  *
  * Used twice:
  *   - daemon: one proxy Server per HTTP client session → phone client

package/src/skill.js

@@ -7,9 +7,6 @@
  *   or any directory (--dir).
  * - Change together: the skills name tools, so a renamed tool means editing them
  *   (test/skill.test.mjs checks every name they use exists).
- *
- * Forked from aura-mcp-connect's skill.js (MIT, Copyright (c) 2026 Dinesh Kumar C; see
- * LICENSE.aura-mcp-connect).
  */
 import fs from "fs";
 import os from "os";

package/src/stdio-shim.js

@@ -5,9 +5,6 @@
  *
  *   IDE ── stdio ── this shim ── HTTP ── daemon ── relay ── CodeDroid on the phone
  *
- * Forked from aura-mcp-connect (MIT, Copyright (c) 2026 Dinesh Kumar C; see
- * LICENSE.aura-mcp-connect).
- *
  * Any number of shims (one per IDE/window) share the one phone connection.
  */
 import { spawn } from "child_process";

package/src/version.js

@@ -1,2 +1,2 @@
 /** The bridge's version, sent to the phone in its hello and shown by `--version`. */
-export const VERSION = "0.1.1";
+export const VERSION = "0.1.2";