enso-release

A deployment and Android-release command for the Enso project. It builds and publishes the web application and creates a new APK, the installable package used by Android devices.

In plain words
What is it for?
Use it to merge and deploy changes, build the frontend, update qualifying documentation, publish an APK, and restart the required services.
Why use it?
Releasing the web and mobile versions involves several linked steps and version checks. This coordinates the deployment and makes the new mobile version available for over-the-air updates.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/proxy2021/enso/enso-release
Clone the repo
git clone --depth 1 https://github.com/Proxy2021/Enso

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 919 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00919
Opus 5 $0.00000 $0.00460
Sonnet 5 $0.00000 $0.00184
Haiku 4.5 $0.00000 $0.00092

Measured yesterday against content hash 2614a833fc43, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

enso-release scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -s http://localhost:3001/api/version | python3 -m json.tool

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s http://localhost:3001/api/version | python3 -m json.tool
.claude/commands/enso-release.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploy Enso (merge, build, commit, push, restart) then build and publish a new Android APK release for OTA client updates.

⛔ If you are running inside the Enso gateway — do NOT run this command. It restarts the gateway and would kill your session.

How the Mobile Update Pipeline Works

  1. package.json holds version (semver) and versionCode (integer) — single source of truth
  2. android/app/build.gradle reads both from package.json at build time
  3. Server exposes /api/version (version info + apkAvailable) and /api/apk (download)
  4. Mobile client checks /api/version every 30 minutes via version-check.ts
  5. If serverVersionCode > installedVersionCode, an UpdateBanner appears
  6. User taps Update → AppUpdaterPlugin.installApk() downloads APK → triggers system installer

Steps

Phase 1 — Deploy (same as /enso-deploy)

  1. Merge worktree to main: If on a worktree branch, merge into main. If already on main, skip.

  2. Build web frontend: Run npm run build to produce the production bundle.

  3. Assess & update docs: Review recent commits. Only update docs for major features (see /enso-deploy for criteria). Skip for minor changes.

  4. Commit any uncommitted changes (doc updates, build artifacts).

  5. Push: git push to remote.

Phase 2 — Version Bump

  1. Bump version in package.json:

    • Increment versionCode by 1 (e.g. 57 → 58)
    • Bump the patch component of version (e.g. "0.2.55" → "0.2.56")
    • Use a targeted edit — only change the version lines, don't touch anything else
  2. Commit version bump: chore: bump version to <version> (versionCode <code>)

Phase 3 — Build Android APK

  1. Set up environment (needed for Gradle):
    export JAVA_HOME="/opt/homebrew/opt/openjdk@21/libexec/openjdk.jdk/Contents/Home"
    export ANDROID_HOME="/opt/homebrew/share/android-commandlinetools"
    
    Verify Java is available: $JAVA_HOME/bin/java -version If not found, install: brew install openjdk@21

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 87 lines · 0 tokens per session scan C 2614a833fc43

Subscribe to this mod's changes

enso-release is a command published in the GitHub repository Proxy2021/Enso (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 919 tokens. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.