clawdex-mobile 2.0.1 → 4.0.0

package/apps/mobile/src/theme.ts

@@ -1,4 +1,4 @@
-import { Platform, StyleSheet } from 'react-native';
+import { Platform } from 'react-native';
 
 export const colors = {
   // Backgrounds
@@ -68,17 +68,11 @@ export const radius = {
   full: 999,
 };
 
-export const shadow = StyleSheet.create({
-  sm: Platform.select({
-    ios: {
-      shadowColor: '#000',
-      shadowOffset: { width: 0, height: 2 },
-      shadowOpacity: 0.3,
-      shadowRadius: 6,
-    },
-    default: { elevation: 3 },
-  }) as object,
-});
+export const shadow = {
+  sm: {
+    boxShadow: '0px 2px 6px rgba(0, 0, 0, 0.3)',
+  },
+} as const;
 
 export const typography = {
   largeTitle: {

package/bin/clawdex.js

@@ -10,13 +10,14 @@ function printUsage() {
   console.log(`Usage: clawdex <command> [options]
 
 Commands:
-  init [--no-start] [--platform <mobile|ios|android>]
-      Run interactive onboarding and secure setup.
-      By default, this also starts bridge + Expo at the end.
-      Use --no-start to skip auto-launch.
+  init [--no-start]
+      Run interactive bridge onboarding and secure setup.
+      By default, this also starts the secure bridge in the foreground.
+      Use --no-start to configure only.
 
   stop
-      Stop bridge + Expo services for this project.
+      Stop bridge services for this project.
+      Also stops a local Expo dev process if one was started from this checkout.
 
   upgrade [--version <latest|x.y.z>] [--restart]
   update  [--version <latest|x.y.z>] [--restart]
@@ -146,7 +147,7 @@ function runUpgrade(args) {
 
   console.log(`Current clawdex-mobile version: ${previousVersion}`);
   if (!options.noStop) {
-    console.log("Stopping running bridge/Expo services before upgrade...");
+    console.log("Stopping running local services before upgrade...");
     const stopResult = runScript("stop-services.sh", [], { exitOnComplete: false });
     if (!stopResult.ok) {
       console.error("error: failed to stop services before upgrade.");

package/docs/codex-app-server-cli-gap-tracker.md

@@ -1,6 +1,6 @@
 # Codex App-Server + CLI Gap Tracker
 
-Last updated: February 24, 2026
+Last updated: March 20, 2026
 
 ## Scope
 This tracker compares `clawdex-mobile` against current Codex app-server + CLI capabilities and records what still needs to be added.
@@ -49,12 +49,21 @@ Status: In progress (first implementation pass completed)
 ## Remaining Gaps (Beyond Gap 1)
 
 ### Gap 2: Slash Command Coverage in Mobile
-- Many Codex CLI slash commands are not exposed as first-class actions in mobile UX.
-- Mobile currently has partial command shortcuts and multiple unsupported command branches.
+- Status: In progress
+- Mobile now supports `/agent` thread switching, sub-agent transcript cards, and nested sub-agent rows in the drawer so spawned workers are visible in the main conversation model instead of being hidden behind generic tool-call traces.
+- Mobile still does not expose the full Codex desktop slash-command surface as dedicated UI actions.
+- Agent management remains lightweight:
+  - no dedicated create/configure sub-agent surface beyond `/agent`
+  - no richer per-agent live status/dashboard view
 
 ### Gap 3: Account/Auth UX
-- No dedicated mobile flow for login state, logout, account details, or rate limits.
-- Auth refresh is still operationally env-driven in bridge, not user-driven in app.
+- Status: In progress
+- Mobile Settings now exposes read-only account state via `account/read`, including ChatGPT email + plan type when available.
+- Remaining:
+  - no dedicated standalone account screen outside Settings
+  - login/logout is not user-driven in mobile UI yet
+  - auth refresh is still operationally env-driven in bridge, not user-driven in app
+  - no API-key entry flow in mobile UI
 
 ### Gap 4: MCP + Tooling UX
 - No end-to-end UI for MCP server status, reload, OAuth login, or remote skills list/export.

package/docs/privacy-policy.md

@@ -0,0 +1,54 @@
+# Privacy Policy
+
+Last updated: March 6, 2026
+
+## Overview
+
+Clawdex Mobile is a companion app for connecting to a bridge service that you run on your own machine. The app is designed for trusted private networking, such as LAN, VPN, or Tailscale. It is not a public multi-tenant shell service.
+
+## Information Processed
+
+Clawdex Mobile can process:
+
+- Chat prompts and assistant responses
+- Bridge connection details you enter in the app
+- Terminal command text and command output returned by your bridge
+- Git repository status, diffs, commit messages, and related metadata
+- File or image attachments you choose to send
+- Voice input audio used for speech-to-text features
+
+## How Information Is Used
+
+The app uses this information to:
+
+- connect your phone to your self-hosted bridge
+- display and continue assistant threads
+- execute approved terminal and Git workflows on infrastructure you control
+- upload user-selected files and images to your own workflow
+- support optional voice-to-text input
+
+## Storage and Retention
+
+Clawdex Mobile does not define a separate cloud retention layer for your project data. Data is generally stored by services and infrastructure you control, including your local bridge, repository, logs, caches, and any model providers or integrations that you configure.
+
+## Sharing
+
+Clawdex Mobile does not include advertising SDKs. Data may be transmitted to third-party model or infrastructure providers only when you configure and use those services as part of your own setup.
+
+## Security
+
+Security depends on how you configure your bridge and network. The app is intended for trusted-network use. You are responsible for protecting bridge tokens, provider credentials, repository access, and device access.
+
+## Your Responsibility
+
+You are responsible for:
+
+- operating the bridge only on systems you own or are authorized to control
+- securing your network path and credentials
+- reviewing commands, approvals, and repository actions before execution
+
+## Contact
+
+For support, use the project support channel:
+
+https://github.com/Mohit-Patil/clawdex-mobile/issues

package/docs/setup-and-operations.md

@@ -6,11 +6,12 @@ This guide is the detailed companion to the top-level `README.md`.
 
 After `clawdex init`, expected sequence:
 
-1. Bridge health passes (`Bridge health check passed.`)
-2. Expo starts (`Starting Expo (mobile) in background...`)
-3. You may briefly see a spinner (`Waiting for Expo output - ...`)
-4. Expo output begins (`expo start --host lan`, QR block, `Metro waiting on exp://...`)
-5. Press Enter to detach onboarding while Expo + bridge keep running
+1. Secure config is written or reused
+2. The bridge starts in the foreground
+3. A pairing QR is printed for the mobile app
+4. Bridge logs stay attached until you stop the process
+
+Published npm releases bundle prebuilt bridge binaries for `darwin-arm64`, `linux-x64`, and `win32-x64`. On those hosts, normal bridge startup does not require a Rust compile. Intel Macs fall back to a local Rust build.
 
 ## Manual Secure Setup (No Wizard)
 
@@ -37,7 +38,13 @@ Creates/updates:
 npm run secure:bridge
 ```
 
-### 4) Start Expo
+### 4) Pair from the mobile app
+
+Open the installed mobile app on your phone, then scan the bridge QR. If needed, enter the bridge URL manually (for example `http://100.x.y.z:8787` or `http://192.168.x.y:8787`). The chosen bridge URL is stored on-device and can be changed later in Settings.
+
+## Local Mobile Development Only
+
+If you are developing the mobile app from this repo, start Expo separately:
 
 ```bash
 npm run mobile
@@ -45,15 +52,12 @@ npm run mobile
 
 `npm run mobile` uses `scripts/start-expo.sh`, which sets `REACT_NATIVE_PACKAGER_HOSTNAME` from your secure config so QR resolution is predictable.
 
-On first app launch, onboarding will ask for your bridge URL (for example `http://100.x.y.z:8787` or `http://192.168.x.y:8787`). This URL is stored on-device and can be changed later in Settings.
-
 ## Advanced Knobs
 
 Optional environment variables:
 
 - `CLAWDEX_SETUP_VERBOSE=true` — show full installer output
-- `BRIDGE_HEALTH_WAIT_SECS=300` — max wait for bridge `/health`
-- `EXPO_OUTPUT_WAIT_SECS=90` — spinner timeout before streaming Expo logs
+- `CLAWDEX_BRIDGE_FORCE_SOURCE_BUILD=true` — ignore a bundled bridge binary and build from local Rust sources instead
 - `EXPO_AUTO_REPAIR=true` — auto-repair React Native runtime on `npm run mobile`
 - `EXPO_CLEAR_CACHE=true` — force `expo start --clear` via `npm run mobile`
 
@@ -65,7 +69,8 @@ npm run teardown
 
 Can:
 
-- stop Expo + bridge
+- stop the bridge
+- also stop local Expo if you started it from this repo
 - remove generated artifacts (`.env.secure`, `.bridge.log`, `.expo.log`, pid files)
 - optionally reset `apps/mobile/.env` from `.env.example`
 - optionally run `tailscale down`
@@ -94,7 +99,7 @@ npm run teardown -- --yes
 
 | Variable | Purpose |
 |---|---|
-| `EXPO_PUBLIC_HOST_BRIDGE_TOKEN` | token sent by mobile client |
+| `EXPO_PUBLIC_HOST_BRIDGE_TOKEN` | token used by local mobile dev builds |
 | `EXPO_PUBLIC_ALLOW_QUERY_TOKEN_AUTH` | query-token behavior for WebSocket auth fallback |
 | `EXPO_PUBLIC_ALLOW_INSECURE_REMOTE_BRIDGE` | suppress insecure-HTTP warning |
 | `EXPO_PUBLIC_PRIVACY_POLICY_URL` | in-app Privacy link |
@@ -140,9 +145,10 @@ Expected response contains `"status":"ok"`.
 ### Choosing Start Directory
 
 1. Open sidebar
-2. Under `Start Directory`, pick:
-   - `Bridge default workspace`, or
-   - a discovered workspace path from existing chats
+2. Under `Start Directory`, pick either:
+   - `Bridge default workspace`
+   - a discovered workspace path from existing Codex chats
+   - any folder on the bridge host via the built-in folder browser or manual path entry
 
 Behavior:
 

package/docs/terms-of-service.md

@@ -0,0 +1,33 @@
+# Terms of Service
+
+Last updated: March 6, 2026
+
+## Overview
+
+Clawdex Mobile is a companion client for interacting with a bridge service and repository environment that you control. By using the app, you agree to use it only with systems, repositories, and infrastructure that you own or are explicitly authorized to access.
+
+## Acceptable Use
+
+You may not use Clawdex Mobile to access, control, or modify machines, repositories, or services without authorization. You are responsible for all actions initiated through the app, including approvals, terminal commands, Git actions, and file transfers.
+
+## Credentials and Access
+
+You must keep bridge tokens, provider credentials, repository credentials, and device access secure. If you believe credentials have been exposed, you should rotate them immediately and stop using the affected bridge until it is secured.
+
+## Operational Risk
+
+Clawdex Mobile can initiate workflows that change files, repositories, and machine state on your host environment. You are responsible for reviewing and approving actions before execution and for maintaining backups or recovery procedures appropriate to your environment.
+
+## Availability
+
+The app depends on your bridge, network, repositories, model providers, and related services. Functionality may be unavailable if those dependencies are unavailable or misconfigured.
+
+## No Warranty
+
+The software is provided on an as-is basis. You assume responsibility for how it is configured and used in your environment.
+
+## Contact
+
+For support, use the project support channel:
+
+https://github.com/Mohit-Patil/clawdex-mobile/issues

package/docs/troubleshooting.md

@@ -1,23 +1,16 @@
 # Troubleshooting
 
-## Onboarding looks stuck before Expo logs appear
+## Bridge startup seems slow
 
-- Expo startup can be slow on first launch.
-- You should see: `Waiting for Expo output ...`
-- Increase timeout if needed:
-
-```bash
-EXPO_OUTPUT_WAIT_SECS=180 clawdex init
-```
-
-- If Expo never emits logs:
-
-```bash
-tail -n 120 .expo.log
-```
+- `clawdex init` no longer starts Expo for the shipped app.
+- Published npm installs should use a bundled bridge binary on `darwin-arm64`, `linux-x64`, and `win32-x64`.
+- If startup is still compiling Rust, you are usually on a source checkout, an unsupported host, or a package without bundled bridge binaries.
+- The slow parts are usually npm dependency install/repair or the first Rust bridge build on source-based setups.
+- If you want to skip the interactive wizard after initial setup, use `npm run secure:bridge`.
 
 ## Expo starts but QR/network is wrong
 
+- This only applies when you are developing the mobile app locally from the repo.
 - Re-run `npm run secure:setup`
 - Confirm `.env.secure` has correct `BRIDGE_HOST`
 - Restart `npm run mobile`
@@ -38,13 +31,14 @@ npm run stop:services
 
 ## Bridge auth errors (`401`, invalid token)
 
-- Ensure `BRIDGE_AUTH_TOKEN` in `.env.secure` matches `EXPO_PUBLIC_HOST_BRIDGE_TOKEN` in `apps/mobile/.env`
-- Restart bridge + Expo after token changes
+- For the shipped mobile app, rescan the bridge QR or update the stored token in Settings.
+- For a local dev build, also ensure `BRIDGE_AUTH_TOKEN` in `.env.secure` matches `EXPO_PUBLIC_HOST_BRIDGE_TOKEN` in `apps/mobile/.env`.
+- Restart the bridge after token changes.
 
 ## Tailscale issues
 
 - Verify host and phone are on the same Tailscale network
-- Check host IP (`tailscale ip -4`) and mobile `.env` URL
+- Check host IP (`tailscale ip -4`) and the bridge URL saved in the mobile app
 
 ## `codex` not found
 
@@ -53,6 +47,8 @@ npm run stop:services
 
 ## Bridge build fails with `linker 'cc' not found`
 
+This only applies when the bridge is building from Rust source instead of using a bundled binary.
+
 Install C build tools:
 
 ```bash
@@ -106,7 +102,7 @@ npm run start -- --clear
 
 ## Plan mode errors (`RPC-32600` invalid `collaborationMode`)
 
-- Restart Expo and reload app bundle
+- Restart the app and reconnect to the bridge
 - Ensure bridge/mobile revisions match
 - Run API test if needed:
 
@@ -118,4 +114,4 @@ npm run -w apps/mobile test -- --runInBand src/api/__tests__/client.test.ts
 
 - Ensure revision supports `turn/interrupt`
 - If run already finished, stop button disappears by design
-- Pull latest, restart bridge, reload Expo bundle
+- Pull latest, restart bridge, then retry from the mobile app

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clawdex-mobile",
-  "version": "2.0.1",
+  "version": "4.0.0",
   "homepage": "https://github.com/Mohit-Patil/clawdex-mobile#readme",
   "repository": {
     "type": "git",
@@ -21,11 +21,12 @@
     "ios": "./scripts/start-expo.sh ios",
     "android": "./scripts/start-expo.sh android",
     "bridge": "BRIDGE_WORKDIR=$(pwd) npm run -w @codex/rust-bridge dev",
+    "bridge:package:stage-current": "node ./scripts/bridge-binary.js stage-current",
     "setup:wizard": "./scripts/setup-wizard.sh",
     "stop:services": "./scripts/stop-services.sh",
     "secure:setup": "./scripts/setup-secure-dev.sh",
-    "secure:bridge": "./scripts/start-bridge-secure.sh",
-    "secure:bridge:dev": "BRIDGE_RUN_MODE=dev ./scripts/start-bridge-secure.sh",
+    "secure:bridge": "node ./scripts/start-bridge-secure.js",
+    "secure:bridge:dev": "node ./scripts/start-bridge-secure.js --dev",
     "bridge:ts": "BRIDGE_WORKDIR=$(pwd) npm run -w @codex/mac-bridge dev",
     "version:sync": "node scripts/sync-versions.js",
     "build": "npm run --workspaces build",
@@ -36,9 +37,9 @@
   },
   "dependencies": {
     "@types/react": "~19.2.10",
+    "expo": "^55.0.8",
     "react": "19.2.0",
     "react-dom": "19.2.0",
-    "react-native": "0.83.2",
-    "expo": "^55.0.2"
+    "react-native": "0.83.2"
   }
 }

package/scripts/bridge-binary.js

@@ -0,0 +1,194 @@
+#!/usr/bin/env node
+"use strict";
+
+const fs = require("node:fs");
+const os = require("node:os");
+const path = require("node:path");
+
+const SUPPORTED_RUNTIME_TARGETS = {
+  "darwin-arm64": {
+    platform: "darwin",
+    arch: "arm64",
+    rustTarget: "aarch64-apple-darwin",
+    binaryName: "codex-rust-bridge",
+  },
+  "linux-x64": {
+    platform: "linux",
+    arch: "x64",
+    rustTarget: "x86_64-unknown-linux-gnu",
+    binaryName: "codex-rust-bridge",
+  },
+  "win32-x64": {
+    platform: "win32",
+    arch: "x64",
+    rustTarget: "x86_64-pc-windows-msvc",
+    binaryName: "codex-rust-bridge.exe",
+  },
+};
+
+function repoRoot() {
+  return path.resolve(__dirname, "..");
+}
+
+function resolveRuntimeTarget(platform = os.platform(), arch = os.arch()) {
+  for (const [target, metadata] of Object.entries(SUPPORTED_RUNTIME_TARGETS)) {
+    if (metadata.platform === platform && metadata.arch === arch) {
+      return target;
+    }
+  }
+  return null;
+}
+
+function binaryNameForTarget(target) {
+  const metadata = SUPPORTED_RUNTIME_TARGETS[target];
+  if (!metadata) {
+    throw new Error(`Unsupported bridge target '${target}'.`);
+  }
+  return metadata.binaryName;
+}
+
+function packagedBinaryPath(rootDir = repoRoot(), target = resolveRuntimeTarget()) {
+  if (!target) {
+    return null;
+  }
+  return path.join(rootDir, "vendor", "bridge-binaries", target, binaryNameForTarget(target));
+}
+
+function builtBinaryPath(rootDir = repoRoot(), platform = os.platform()) {
+  const binaryName = platform === "win32" ? "codex-rust-bridge.exe" : "codex-rust-bridge";
+  return path.join(rootDir, "services", "rust-bridge", "target", "release", binaryName);
+}
+
+function ensureExecutable(filePath) {
+  if (process.platform !== "win32") {
+    fs.chmodSync(filePath, 0o755);
+  }
+}
+
+function stageBinary({ rootDir = repoRoot(), from, target = resolveRuntimeTarget() }) {
+  if (!from) {
+    throw new Error("--from is required.");
+  }
+  if (!target) {
+    throw new Error("No supported runtime target for this host. Pass --target explicitly.");
+  }
+
+  const destination = packagedBinaryPath(rootDir, target);
+  if (!destination) {
+    throw new Error(`Unable to compute packaged path for target '${target}'.`);
+  }
+
+  fs.mkdirSync(path.dirname(destination), { recursive: true });
+  fs.copyFileSync(from, destination);
+  ensureExecutable(destination);
+  return destination;
+}
+
+function parseArgs(argv) {
+  const positional = [];
+  const flags = {};
+
+  for (let index = 0; index < argv.length; index += 1) {
+    const value = argv[index];
+    if (!value.startsWith("--")) {
+      positional.push(value);
+      continue;
+    }
+
+    const key = value.slice(2);
+    const next = argv[index + 1];
+    if (!next || next.startsWith("--")) {
+      flags[key] = true;
+      continue;
+    }
+    flags[key] = next;
+    index += 1;
+  }
+
+  return { positional, flags };
+}
+
+function main() {
+  const { positional, flags } = parseArgs(process.argv.slice(2));
+  const command = positional[0];
+  const rootDir = flags.root ? path.resolve(flags.root) : repoRoot();
+
+  switch (command) {
+    case "current-target": {
+      const target = resolveRuntimeTarget();
+      if (!target) {
+        process.exit(1);
+      }
+      console.log(target);
+      return;
+    }
+    case "has-current-packaged": {
+      const filePath = packagedBinaryPath(rootDir);
+      if (filePath && fs.existsSync(filePath)) {
+        console.log(filePath);
+        return;
+      }
+      process.exit(1);
+      return;
+    }
+    case "current-packaged-path": {
+      const target = flags.target || resolveRuntimeTarget();
+      const filePath = packagedBinaryPath(rootDir, target);
+      if (!filePath) {
+        process.exit(1);
+      }
+      console.log(filePath);
+      return;
+    }
+    case "current-built-path": {
+      console.log(builtBinaryPath(rootDir));
+      return;
+    }
+    case "stage-current": {
+      const destination = stageBinary({
+        rootDir,
+        from: builtBinaryPath(rootDir),
+        target: flags.target || resolveRuntimeTarget(),
+      });
+      console.log(destination);
+      return;
+    }
+    case "stage": {
+      const destination = stageBinary({
+        rootDir,
+        from: flags.from ? path.resolve(flags.from) : "",
+        target: flags.target || resolveRuntimeTarget(),
+      });
+      console.log(destination);
+      return;
+    }
+    default:
+      console.error("Usage:");
+      console.error("  node scripts/bridge-binary.js current-target");
+      console.error("  node scripts/bridge-binary.js has-current-packaged");
+      console.error("  node scripts/bridge-binary.js current-packaged-path [--target <target>]");
+      console.error("  node scripts/bridge-binary.js current-built-path");
+      console.error("  node scripts/bridge-binary.js stage-current [--target <target>]");
+      console.error("  node scripts/bridge-binary.js stage --from <binary> [--target <target>]");
+      process.exit(1);
+  }
+}
+
+module.exports = {
+  SUPPORTED_RUNTIME_TARGETS,
+  binaryNameForTarget,
+  builtBinaryPath,
+  ensureExecutable,
+  packagedBinaryPath,
+  resolveRuntimeTarget,
+  stageBinary,
+};
+
+if (require.main === module) {
+  try {
+    main();
+  } catch (error) {
+    console.error(error instanceof Error ? error.message : String(error));
+    process.exit(1);
+  }
+}