nastech-app 1.0.0

package/NasTechapp.md

@@ -0,0 +1,383 @@
+# NasTech Expo App — Agent Safety Guide
+
+> **Read this entire file before touching anything in `NasTech/`.**
+> Every rule below was learned from a real build failure. Violating any one
+> of them will silently break EAS cloud builds even if the app runs fine locally.
+
+---
+
+## 1. What this project is
+
+The `NasTech/` directory is an **Expo SDK 55** React Native app that lives inside
+the larger `nastech-ai/NasTech-Agent` monorepo. It is built and distributed as an
+Android APK (and iOS IPA) via **EAS Build** (Expo Application Services).
+
+```
+nastech-ai/NasTech-Agent/   ← git root
+├── NasTech/                ← THIS project (Expo app)
+│   ├── app.config.js
+│   ├── eas.json
+│   ├── package.json
+│   ├── .easignore
+│   ├── plugins/
+│   │   └── withEinkCompatibility.js
+│   └── sources/
+│       ├── app/            ← expo-router file-based routes
+│       ├── assets/
+│       │   └── images/     ← ALL app icons and splash images live here
+│       └── ...
+├── .gitignore              ← REPO ROOT gitignore — rules here affect EAS
+├── .github/
+│   └── workflows/
+│       └── eas-build-android.yml
+└── ...
+```
+
+---
+
+## 2. How EAS builds work (critical mental model)
+
+EAS CLI does **not** archive from the `NasTech/` directory alone. It reads the
+nearest `.git` folder (which is at the repo root), then archives the **entire
+git repository** respecting both `.gitignore` and `.easignore`.
+
+The archive is extracted on the EAS server to:
+```
+/home/expo/workingdir/build/
+```
+So the Expo project root on EAS is:
+```
+/home/expo/workingdir/build/NasTech/
+```
+
+**Consequence:** Any `.gitignore` pattern in the repo root that matches a path
+inside `NasTech/` will cause those files to be **silently absent** on the EAS
+server — even if the files are committed to git and visible in GitHub.
+
+---
+
+## 3. The `.gitignore` trap — NEVER add broad patterns
+
+The repo-root `.gitignore` already contains patterns. If you add a new pattern,
+check whether it could accidentally match something inside `NasTech/`.
+
+**WRONG** — matches `NasTech/sources/assets/images/` and strips images from EAS:
+```
+images/
+```
+
+**CORRECT** — anchored to repo root only, does not affect NasTech:
+```
+/images/
+```
+
+**Rule:** When adding a gitignore pattern that refers to a generic directory
+name (e.g. `data/`, `logs/`, `tmp/`, `images/`, `assets/`), **always anchor
+it with a leading `/`** unless you explicitly want it to apply at every depth.
+
+---
+
+## 4. Image and asset paths in `app.config.js` — RELATIVE ONLY
+
+`app.config.js` configures all app icons, splash screens, and favicons.
+
+**WRONG — absolute path via `path.resolve`:**
+```js
+// Breaks on EAS because __dirname resolves differently on their servers
+icon: path.resolve(__dirname, 'sources/assets/images/icon.png'),
+```
+
+**CORRECT — relative path from project root:**
+```js
+icon: './sources/assets/images/icon.png',
+```
+
+Expo's config system resolves `./...` paths from the project root
+(`NasTech/`) on every platform. Relative paths are portable; absolute paths
+built with `path.resolve(__dirname, ...)` are fragile and will break if the
+project is ever evaluated from a different working directory.
+
+**All image-referencing fields that must use relative paths:**
+- `expo.icon`
+- `expo.android.adaptiveIcon.foregroundImage`
+- `expo.android.adaptiveIcon.monochromeImage`
+- `expo.web.favicon`
+- Inside `plugins` arrays: `expo-notifications` icon, `expo-splash-screen`
+  image references
+
+**Do NOT add `const path = require('node:path')` or use `__dirname`** for
+asset paths. It is fine to use `path` for non-asset logic (e.g. git commands).
+
+---
+
+## 5. `withEinkCompatibility.js` — the lazy-require rule
+
+`NasTech/plugins/withEinkCompatibility.js` is a config plugin. It **must**
+lazy-require `expo/config-plugins` **inside the plugin function body**, not at
+the top of the file:
+
+**WRONG — top-level require:**
+```js
+const { withAndroidManifest } = require('expo/config-plugins'); // ← breaks EAS
+const withEinkCompatibility = (config, options = {}) => { ... };
+```
+
+**CORRECT — lazy require inside function:**
+```js
+const withEinkCompatibility = (config, options = {}) => {
+  const { withAndroidManifest } = require('expo/config-plugins'); // ← safe
+  ...
+};
+```
+
+**Why:** EAS evaluates `app.config.js` (and therefore loads all plugins listed
+in it) **before** running `pnpm install`. If `expo/config-plugins` is required
+at module load time, the require fails because `node_modules` doesn't exist yet.
+Lazy-requiring it inside the function body defers the require until `expo prebuild`
+actually runs the plugin, at which point `node_modules` is present.
+
+---
+
+## 6. `.easignore` — what is excluded from the EAS archive
+
+`NasTech/.easignore` tells EAS which files/directories to strip before uploading.
+Current contents:
+```
+node_modules/
+.node_modules_bak/
+android/
+ios/
+.git/
+*.keystore
+credentials.json
+__tests__/
+coverage/
+.expo/
+dist/
+build/
+```
+
+**Do not add `sources/` or `sources/assets/` or `images/` to `.easignore`.**
+Those paths contain app source code and required image assets.
+
+---
+
+## 7. Package manager — pnpm v10
+
+The project uses `pnpm@10.11.0` (set in `package.json` `packageManager` field).
+
+```json
+"packageManager": "pnpm@10.11.0"
+```
+
+**pnpm v10 changed default behavior:** it no longer runs build scripts for
+packages that are not explicitly allow-listed. If you add a native module that
+requires a build step (e.g. `esbuild`, packages with `install.js` scripts), you
+must add it to `pnpm.onlyBuiltDependencies` in `package.json`:
+
+```json
+"pnpm": {
+  "overrides": { "react": "19.2.0" },
+  "onlyBuiltDependencies": ["esbuild", "@shopify/react-native-skia", "your-new-package"]
+}
+```
+
+Run `pnpm install` after any change to `package.json`.
+
+---
+
+## 8. Expo SDK 55 — package version discipline
+
+All `expo-*` packages must be pinned to `~55.x.x`. Do **not** upgrade any
+individual `expo-*` package to a higher major version without upgrading the
+entire SDK.
+
+Before adding or upgrading any package, run:
+```bash
+cd NasTech && npx expo install --check
+```
+This validates that all Expo-managed packages are on the correct SDK 55 range.
+
+**Do not run `expo upgrade`** unless intentionally migrating the entire SDK.
+
+---
+
+## 9. Local prebuild verification — run this before every push
+
+After any change to `app.config.js`, `plugins/`, or `NasTech/package.json`:
+
+```bash
+cd NasTech
+npx expo prebuild --platform android --clean
+```
+
+A successful run ends with:
+```
+✅ E-ink compatibility plugin applied successfully
+✔ Finished prebuild
+```
+
+If prebuild fails locally, **do not push**. Fix it first.
+
+---
+
+## 10. How to push changes (git CLI is blocked in the Replit main agent)
+
+Changes must be pushed via the **GitHub REST API** using the
+`GITHUB_PERSONAL_ACCESS_TOKEN` secret. The repo is `nastech-ai/NasTech-Agent`.
+
+**Step-by-step:**
+
+1. Get the current file SHA from GitHub (needed for updates):
+```bash
+curl -s -H "Authorization: Bearer $GITHUB_PERSONAL_ACCESS_TOKEN" \
+  "https://api.github.com/repos/nastech-ai/NasTech-Agent/contents/NasTech/app.config.js" \
+  | python3 -c "import sys,json; print(json.load(sys.stdin)['sha'])"
+```
+
+2. Base64-encode the new file content:
+```bash
+BASE64=$(base64 -w 0 NasTech/app.config.js)
+```
+
+3. Push via PUT:
+```bash
+curl -s -X PUT \
+  -H "Authorization: Bearer $GITHUB_PERSONAL_ACCESS_TOKEN" \
+  -H "Content-Type: application/json" \
+  "https://api.github.com/repos/nastech-ai/NasTech-Agent/contents/NasTech/app.config.js" \
+  -d "{\"message\": \"fix: describe change here\", \"content\": \"$BASE64\", \"sha\": \"<SHA_FROM_STEP_1>\"}" \
+  | python3 -c "import sys,json; d=json.load(sys.stdin); print('commit:', d.get('commit',{}).get('sha','ERROR'))"
+```
+
+A successful push prints a commit SHA.
+
+---
+
+## 11. EAS build — triggering and monitoring
+
+Builds are triggered via the GitHub Actions workflow at
+`.github/workflows/eas-build-android.yml`.
+
+**Trigger a new build:**
+```bash
+curl -s -X POST \
+  -H "Authorization: Bearer $GITHUB_PERSONAL_ACCESS_TOKEN" \
+  -H "Accept: application/vnd.github+json" \
+  "https://api.github.com/repos/nastech-ai/NasTech-Agent/actions/workflows/eas-build-android.yml/dispatches" \
+  -d '{"ref":"main"}'
+```
+
+**Check status:**
+```bash
+curl -s -H "Authorization: Bearer $GITHUB_PERSONAL_ACCESS_TOKEN" \
+  "https://api.github.com/repos/nastech-ai/NasTech-Agent/actions/runs?per_page=5" \
+  | python3 -c "
+import sys,json
+runs = json.load(sys.stdin).get('workflow_runs',[])
+for r in runs:
+    print(r['id'], r['status'], r['conclusion'] or 'pending', r['head_sha'][:8], r['name'])
+"
+```
+
+**Get logs of a failed run** (replace RUN_ID):
+```bash
+curl -s -H "Authorization: Bearer $GITHUB_PERSONAL_ACCESS_TOKEN" \
+  "https://api.github.com/repos/nastech-ai/NasTech-Agent/actions/runs/RUN_ID/logs" \
+  -L -o /tmp/eas_logs.zip
+
+python3 -c "
+import zipfile
+with zipfile.ZipFile('/tmp/eas_logs.zip') as z:
+    content = z.read('EAS Android preview build/7_Build Android APK.txt').decode('utf-8', errors='replace')
+    for i, line in enumerate(content.split('\n')):
+        if any(x in line for x in ['Error', 'ENOENT', 'failed', '✖']):
+            print(f'line {i}: {line}')
+"
+```
+
+**EAS account:** `nastechai2` · **projectId:** `0a7f820d-0e70-4fb9-aba7-0701324e0975`
+**Build profiles:** `preview` (default), `production`, `development`
+
+**Free plan limit:** The `nastechai2` account has a monthly EAS build quota.
+If a build fails with *"This account has used its Android builds from the Free plan
+this month"*, this is a quota error — **not a code error**. The quota resets on
+the 1st of each month. No code changes are needed.
+
+---
+
+## 12. EAS binary log format
+
+EAS build logs downloaded from the EAS dashboard are in a proprietary binary
+format (not gzip, zlib, lzma, bz2, or zstd). **Do not attempt to decompress
+them.** The only readable logs come from:
+- GitHub Actions step logs (method above)
+- Text pasted directly from the EAS build dashboard UI
+
+---
+
+## 13. Build profiles (`eas.json`)
+
+| Profile | Distribution | Channel | APK type |
+|---|---|---|---|
+| `preview` | internal (sideload) | preview | signed APK |
+| `production` | store | production | signed AAB |
+| `development` | internal | development | debug with dev client |
+
+The `SHARP_IGNORE_GLOBAL_LIBVIPS=1` env var is set in every profile — do not
+remove it; it prevents sharp (image processing) from conflicting with the EAS
+build image's system libvips.
+
+---
+
+## 14. `sources/assets/images/` — the canonical image directory
+
+All app icon and splash image files live at:
+```
+NasTech/sources/assets/images/
+```
+
+| File | Purpose |
+|---|---|
+| `icon.png` | Main app icon (1024×1024 RGBA PNG) |
+| `icon-adaptive.png` | Android adaptive icon foreground (1024×1024 RGBA PNG) |
+| `icon-monochrome.png` | Android monochrome/themed icon (1024×1024 RGBA PNG) |
+| `icon-notification.png` | Android notification icon |
+| `icon-openclaw.png` | Alt brand icon |
+| `splash-android-light.png` | Android light-mode splash |
+| `splash-android-dark.png` | Android dark-mode splash |
+| `favicon.png` | Web favicon |
+| `transparent.png` | Transparent placeholder |
+| `logotype.png` | Text logotype |
+
+These files ARE tracked in git and ARE in GitHub. If a new EAS build reports
+them missing, the most likely cause is a new `.gitignore` pattern at the repo
+root that matches `images/` without a leading `/`. Fix: anchor it as `/images/`.
+
+---
+
+## 15. Forbidden actions checklist
+
+Before pushing any change, verify you have NOT done any of the following:
+
+- [ ] Added `path.resolve(__dirname, ...)` to any image path in `app.config.js`
+- [ ] Added `require('expo/config-plugins')` at the top level of any plugin file
+- [ ] Added an un-anchored pattern like `images/` or `assets/` to the root `.gitignore`
+- [ ] Added `sources/`, `sources/assets/`, or any image directory to `.easignore`
+- [ ] Upgraded an `expo-*` package beyond SDK 55 range (`~55.x.x`)
+- [ ] Changed `packageManager` away from `pnpm@10.11.0`
+- [ ] Added a native module that requires a build script without listing it in
+      `pnpm.onlyBuiltDependencies`
+- [ ] Skipped running `npx expo prebuild --platform android --clean` after config changes
+
+---
+
+## 16. Quick-start checklist for any new change
+
+1. **Read** this file
+2. Make your change
+3. Run `cd NasTech && npx expo prebuild --platform android --clean`
+4. Confirm it ends with `✔ Finished prebuild`
+5. Push via GitHub REST API (section 10)
+6. Trigger EAS build (section 11)
+7. Monitor GitHub Actions for the step-level result

package/README.md

@@ -0,0 +1,75 @@
+# NasTech App
+
+A React Native / Expo mobile application for interacting with a self-hosted **NasTech Agent** backend.
+Built on top of the open-source the original open-source app project, fully rebranded and wired to the NasTech system.
+
+## Architecture
+
+| Layer | Description |
+|-------|-------------|
+| **Mobile UI** | React Native + Expo (iOS / Android / macOS via Tauri) |
+| **API bridge** | `sources/sync/nastechApi.ts` — REST + WebSocket client |
+| **Wire types** | `sources/wire/index.ts` → NasTech-owned schemas in `sources/nastech-wire/` |
+| **Server config** | `sources/sync/serverConfig.ts` — default `http://127.0.0.1:9119` |
+| **Auth** | Bearer token via `Authorization: Bearer <session-token>` |
+
+## Wiring to NasTech Backend
+
+The app connects to the NasTech Agent dashboard backend (`nastech_cli/web_server.py`):
+
+```
+NasTech App ──HTTP/WS──► http://127.0.0.1:9119
+                          ├── GET  /api/status          (server probe)
+                          ├── GET  /api/sessions         (session list)
+                          ├── GET  /api/sessions/:id/messages
+                          ├── DELETE /api/sessions/:id
+                          └── WS   /api/events?channel=… (real-time)
+```
+
+### Auth modes
+- **Insecure** (local): `python3 -m nastech_cli.main dashboard --insecure` — no token required
+- **Secure**: pass `Authorization: Bearer <session-token>` — set the token in-app via Settings → Server
+
+## Getting Started
+
+```bash
+cd NasTech
+pnpm install
+pnpm start            # Expo dev server
+pnpm ios              # Run on iOS simulator
+pnpm android          # Run on Android emulator
+pnpm web              # Run in browser
+```
+
+Set the server URL (defaults to `http://127.0.0.1:9119`):
+- In-app: Settings → Server
+- Env: `EXPO_PUBLIC_NASTECH_SERVER_URL=http://your-server:9119`
+
+## Key Source Files
+
+| File | Purpose |
+|------|---------|
+| `sources/sync/nastechApi.ts` | NasTech REST + WebSocket API client |
+| `sources/sync/serverConfig.ts` | Server URL + log URL storage |
+| `sources/wire/index.ts` | Wire type re-exports |
+| `sources/hooks/useNasTechAction.ts` | Error-handling async action hook |
+| `sources/sync/apiSocket.ts` | Real-time socket connection |
+| `sources/utils/errors.ts` | NasTechError type |
+
+## App Config
+
+| Variant | Bundle ID | Name |
+|---------|-----------|------|
+| development | `com.nastech.app.dev` | NasTech (dev) |
+| preview | `com.nastech.app.preview` | NasTech (preview) |
+| production | `com.nastech.app` | NasTech |
+
+## Notes
+
+- Encryption key derivation strings (the upstream crypto salts, etc.) in
+  `sources/sync/encryption/` are **intentionally left unchanged** — they are
+  cryptographic key derivation salts and must remain stable to avoid breaking
+  decryption of existing data.
+- Wire protocol schemas are fully owned in `sources/nastech-wire/` with no external wire dependency.
+- Test fixture data in `sources/sync/__testdata__/` may still reference original
+  paths — these are static replay traces and do not affect runtime behavior.

package/Stores.md

@@ -0,0 +1,85 @@
+# App Store & Google Play Store Information
+
+## App Name
+NasTech
+
+## Subtitle / Short Description
+Claude Code on the go
+
+## Categories
+- **App Store Primary**: Developer Tools
+- **App Store Secondary**: Productivity
+- **Google Play**: Productivity > Developer Tools
+
+## Keywords
+claude, code, ai, programming, developer, tools, encrypted, secure, coding, assistant, mobile, sync, offline, notifications, privacy
+
+## App Description / Full Description
+
+NasTech is the secure mobile companion for Claude Code that lets you continue your AI coding sessions anywhere (not affiliated with Anthropic). Built by developers who needed to check on Claude's progress during coffee breaks, this app brings the full Claude Code experience to your phone with military-grade encryption.
+
+**Important**: This app requires Claude Code to be installed on your computer. NasTech is a companion app that connects to your existing Claude Code setup.
+
+**Key Features:**
+
+• Continue Claude Code sessions seamlessly between desktop and mobile
+• Push notifications for permission requests and task completion
+• Access conversation history even when your terminal is offline
+• End-to-end encryption - your code stays private
+• Real-time streaming of Claude's responses
+• Zero-knowledge architecture - we can't read your data
+
+**How It Works:**
+1. Install the nastech CLI on your computer
+2. Scan a QR code to securely pair your devices
+3. Use 'nastech' instead of 'claude' to start encrypted sessions
+4. Switch between desktop and mobile instantly
+
+Perfect for developers who:
+- Want to monitor long-running tasks on the go
+- Need secure access to proprietary code discussions
+- Value privacy and open-source transparency
+- Work from coffee shops, trains, or anywhere
+
+NasTech uses the same encryption as Signal (TweetNaCl) and is completely open source. Your encryption keys never leave your device, and all data is encrypted before transmission.
+
+Built by Bay Area engineers who believe the best tools come from scratching your own itch. We needed a way to securely check on our AI coding assistant while away from our desks - so we built it and shared it with the community.
+
+Your code. Your privacy. Your Claude Code companion.
+
+## Promotional Text
+**App Store (170 chars)**: Securely continue your Claude Code sessions on mobile. End-to-end encrypted, open source, with push notifications for completed tasks. Your AI coding assistant, anywhere.
+
+**Google Play (80 chars)**: Secure mobile Claude Code companion. Encrypted, open source, with notifications.
+
+## What's New (for updates)
+- Initial release
+- End-to-end encryption for all messages
+- Push notifications for permissions and task completion
+- Offline access to conversation history
+- Real-time sync with desktop sessions
+
+## URLs
+
+### Privacy Policy
+https://github.com/nastech-ai/nastech/blob/main/PRIVACY.md
+
+### Support / Contact
+https://github.com/nastech-ai/nastech/issues
+
+### Website / Marketing
+https://github.com/nastech-ai/nastech
+
+## Additional Google Play Requirements
+
+### Content Rating
+Everyone
+
+### Target Audience
+Developers and software engineers
+
+### Contains Ads
+No
+
+### In-App Purchases
+No

package/TERMS.md

@@ -0,0 +1,83 @@
+# Terms of Use
+
+Last updated: January 2025
+
+## Acceptance of Terms
+
+By downloading, installing, or using NasTech, you agree to be bound by these Terms of Use. If you do not agree to these terms, do not use NasTech.
+
+## About NasTech
+
+NasTech is a free, open-source mobile client for AI code assistance, released under the MIT License. The software is provided as-is by the open-source community without any warranties or guarantees.
+
+## License
+
+NasTech is licensed under the MIT License. This means you are free to:
+
+- Use the software for any purpose, including commercial use
+- Modify the source code
+- Distribute copies of the software
+- Distribute modified versions
+
+The full MIT License text is available in the source code repository.
+
+## Acceptable Use
+
+You agree to use NasTech responsibly and in compliance with all applicable laws. You must not:
+
+- Use NasTech for any illegal or unauthorized purpose
+- Attempt to harm, disable, or impair the functionality of NasTech
+- Use NasTech to generate harmful, offensive, or inappropriate content
+- Violate the terms of service of any AI services you connect to through NasTech
+- Attempt to reverse engineer security features or encryption protocols
+
+## Third-Party Services
+
+NasTech may connect to third-party AI services (such as Claude, OpenAI, etc.). You acknowledge that:
+
+- You are responsible for complying with their terms of service
+- You need valid API keys and accounts with these services
+- NasTech is not responsible for the availability or performance of third-party services
+- Costs associated with API usage are your responsibility
+
+## Independence and Disclaimers
+
+**NasTech is an independent, community-driven project.** We are not affiliated with, endorsed by, or connected to Anthropic, Claude, OpenAI, or any other AI service providers. NasTech is a third-party client that works with publicly available APIs.
+
+## Limitation of Liability
+
+**IMPORTANT:** NasTech is provided "AS IS" without warranty of any kind. The developers, contributors, and distributors of NasTech shall not be liable for:
+
+- Any direct, indirect, incidental, or consequential damages
+- Data loss or corruption
+- Lost profits or business interruption
+- Any claims arising from your use of NasTech
+
+## Privacy
+
+NasTech respects your privacy. The app:
+
+- Does not collect personal information without your consent
+- Stores API keys locally on your device
+- Does not share your data with third parties (except when connecting to AI services you configure)
+- May use crash reporting and analytics tools as disclosed in the Privacy Policy
+
+## Changes to Terms
+
+We reserve the right to update these Terms of Use at any time. Continued use of NasTech after changes constitutes acceptance of the new terms.
+
+## Governing Law
+
+These terms shall be governed by and construed in accordance with applicable laws, without regard to conflict of law principles.
+
+## Contact
+
+For questions about these Terms of Use, please visit our GitHub repository or contact the maintainers through the project's official channels.
+
+## Severability
+
+If any provision of these Terms is found to be unenforceable or invalid, that provision will be limited or eliminated to the minimum extent necessary so that these Terms will otherwise remain in full force and effect.
+
+## Entire Agreement
+
+These Terms of Use constitute the entire agreement between you and the NasTech project regarding the use of the software, superseding any prior agreements or understandings.