$ ./claude-edge-setup.sh

termux-tools

Claude Code and a debloated browser, on your Android phone

Custom Edge Canary build · CFC browser bridge · Claude Code patching · Termux tooling

GitHub Releases

bash — termux

~ $ ./claude-edge-setup.sh --all

✓ adb · wireless paired

✓ bun · runtime ready

✓ claude-code 2.1.158 (Opus 4.8) patched

✓ cfc-bridge + extension installed

~ $ claude --version

2.1.158 (Claude Code)

~ $ edge-fix/build.sh

✓ stripped 56 trackers · re-signed APK

~ $

# Core Features

🛡

Custom Edge Canary Build

A reproducible pipeline that strips 56+ tracking permissions, analytics SDKs (OneCollector, Adjust, Tencent Matrix, KOOM), Intune MDM and telemetry endpoints from Edge Canary, then re-signs the APK.

edge-fix/build.sh — unpack, patch, sign, zipalign

patch-manifest.py — drop tracking permissions

replace-urls.list — telemetry → 127.0.0.1

📡

CFC Browser Bridge

A WebSocket bridge that wires the Edge extension to Claude Code's native Chrome host — exposing screenshots, navigation, form fill and JS-over-CDP as MCP tools inside any Claude session on Android.

claude-chrome-android — start the WS bridge

--mcp — MCP relay per session

--setup — register MCP + extension

◆

Runs the latest Claude Code (2.1.158, Opus 4.8) on bionic Android. A byte-preserving patcher edits the bun-compiled binary's vfs in place, plus sed patches for the legacy cli.js path — aligned to your CLAUDE.md.

CCINSTALL_VERSION=next — install the 4.8 binary

claude-code.sh — install + auto-patch

byte-preserving — survives bun-vfs offsets

⚙

Termux Dev Tooling

The glue that makes bionic Android a real dev box: a modular installer, x86_64 emulation via qemu, a Ghostty source build, pip-on-Termux fixes, ADB wireless automation and device-migration scripts.

x86-on-termux — run x86_64 binaries via qemu

pip-tool-install — C-ext Python CLIs on Termux

install-ghostty — GTK4 terminal, source build

# Quick Start

One installer wires up the whole stack on bionic Android — Bun, a patched Claude Code, ADB wireless, the debloated Edge build, and the CFC bridge. Requires Termux and Termux:API from F-Droid.

1. Bootstrap the installer

claude-edge-setup.sh

# One-liner bootstrap — clones the repo, then opens the menu
curl -fsSL https://raw.githubusercontent.com/tribixbite/termux-tools/main/claude-edge-setup.sh | bash

# Or clone first, then run the interactive installer
git clone https://github.com/tribixbite/termux-tools ~/git/termux-tools
cd ~/git/termux-tools
./claude-edge-setup.sh           # interactive menu
./claude-edge-setup.sh --all     # non-interactive, run every step

2. Pick what to install

Each menu option sources a self-contained module from install/modules/. Run them piecemeal or choose 9) Run all.

interactive menu

CFC Setup

  1) Install Bun (via bun-on-termux)
  2) Install Claude Code CLI            # byte-preserving patch
  3) Configure Termux permissions
  4) Setup ADB wireless
  5) Build extension (CRX)
  6) Install extension in browser
  7) Start/manage bridge
  8) Health check & diagnostics
  9) Run all (full setup)
  0) Exit

3. Connect Claude to the browser

After step 7 the bridge is live and the Edge extension is connected. Register it as an MCP server with npx claude-chrome-android --setup, then screenshots, navigation and JS-over-CDP show up as tools inside any Claude Code session.

# Command Reference

./claude-edge-setup.sh	Interactive installer menu
./claude-edge-setup.sh --all	Run every install step non-interactively
install/modules/bun.sh	Install Bun via bun-on-termux
install/modules/claude-code.sh	Install + byte-preserving patch Claude Code
install/modules/adb.sh	Pair and connect ADB over WiFi
install/modules/extension.sh	Build CRX + sideload into Edge

Full reference in docs/ — every module is self-contained and re-runnable

# How It Works

┌──────────────────────────────────────────────────────┐
│  CFC Bridge — browser automation for Claude Code     │
│                                                      │
│  Edge Canary (debloated, sideloaded extension)     │
│       │  screenshots · navigate · form-fill · CDP   │
│       │  ▲ WebSocket ▼                            │
│       ▼                                              │
│  Bridge server (claude-chrome-android)           │
│       │  FIFO tool queue · /health · /tool         │
│       │  ▲ stdio ▼                                │
│       ▼                                              │
│  Native host (Claude Code cli.js)                 │
│       │  ▲ unix socket ▼                          │
│       ▼                                              │
│  MCP relay ──▶ tools in any Claude session        │
│       mcp__cfc-bridge__screenshot, navigate, …      │
└──────────────────────────────────────────────────────┘

MV2 on Edge Android

MV3 service workers never start in sideloaded CDP targets. CFC ships as an MV2 background page, pushed via --load-extension.

Byte-preserving patches

Claude Code's bun-compiled binary is patched in place — equal-length overwrites keep the vfs offsets intact so it still runs.

# Repo Structure

termux-tools/

├── edge-fix/ Edge Canary debloat pipeline — unpack, strip trackers, re-sign the APK

├── bridge/ NPM package (claude-chrome-android) — WS bridge + MCP server for browser tools

├── edge-claude-ext/ CFC browser extension source — MV2 background + content scripts

├── install/ Modular installer — lib/common.sh + per-step modules (bun, claude-code, adb, crx)

├── scripts/ pip-tool-install, install-ghostty, migrate-termux, secure-prefs-dump, CRX build

├── x86-on-termux/ qemu-user sysroot installer to run x86_64 binaries on aarch64

├── tools/ ADB wireless connect, restore-tabs, post-update phantom-killer fixes

├── hooks/ Claude Code hooks — session lifecycle + queue automation

└── docs/ Architecture, command reference, ADB wireless guide, bridge protocol spec

# Requirements

● Termux ● Termux:API app ● Bun ● ADB (wireless) ○ Edge Canary ○ apktool / apksigner ○ Node.js 18+

● required ○ optional (for the Edge build & extras)