docs: refresh README layout, add badges, tables, and richer sections

Author: tonyHu08

README.md

@@ -1,63 +1,81 @@
 # Codex Bridge Desktop
 
+Control your local Codex threads from Telegram. Keep working while away from your Mac. 🚀
+
+![App Icon](./apps/desktop/electron/assets/cab-brand-icon.png)
+
+![GitHub release](https://img.shields.io/github/v/release/tonyHu08/CodeX_Bridge?display_name=tag&sort=semver)
+![macOS](https://img.shields.io/badge/platform-macOS-111827)
+![License](https://img.shields.io/github/license/tonyHu08/CodeX_Bridge)
+![Stars](https://img.shields.io/github/stars/tonyHu08/CodeX_Bridge?style=social)
+
 [English](#english) | [中文](#中文)
 
+Quick links: [Download](https://github.com/tonyHu08/CodeX_Bridge/releases) · [Commands](./docs/COMMANDS.md) · [Troubleshooting](./docs/TROUBLESHOOTING.md) · [Report issue](https://github.com/tonyHu08/CodeX_Bridge/issues)
+
+---
+
 ## English
 
-Control your local Codex threads from Telegram in under 2 minutes.
+### What is this?
 
-Codex Bridge is built for the exact pain point many people hit today: Codex is powerful on desktop, but your work stalls the moment you step away from your machine. This project keeps your real Codex thread alive on your phone, with status, approvals, and results in one chat.
+Codex is great on desktop, but it is not remote-first: your work stalls the moment you step away from your machine.
 
-![App Icon](./apps/desktop/electron/assets/cab-brand-icon.png)
+**Codex Bridge** keeps your real Codex thread alive on your phone, with:
 
-### Real screenshots
+- ✅ Thread-aware remote control (`/threads`, `/bind`, `/current`)
+- 🔒 Safe remote execution (approvals: `/approve` / `/deny`)
+- 📊 Status + limits (`/status`, `/usage`)
+- 🧰 Menu bar controls (online state + remote switch)
+- 🌏 Bilingual UX (English + Chinese)
 
-![Desktop app home](./docs/assets/readme/desktop-home.png)
-![Telegram remote control](./docs/assets/readme/telegram-threads.png)
+### Real screenshots
 
-### Why people star this project
+| Desktop app home | Telegram remote control |
+| --- | --- |
+| ![Desktop app home](./docs/assets/readme/desktop-home.png) | ![Telegram remote control](./docs/assets/readme/telegram-threads.png) |
 
-- No CLI in the main path.
-- Remote control is thread-aware (`/threads`, `/bind`, `/current`).
-- Safe remote execution with approval commands (`/approve`, `/deny`).
-- Menu bar quick controls for online state and remote switch.
-- Built-in bilingual UX (English + Chinese).
+### Features ✨
 
-### Recent stability fixes
+- **Remote chat with context**: keep using the same local Codex thread from Telegram.
+- **Approvals**: when Codex wants to run commands or change files, you can approve/deny from Telegram.
+- **Queue + cancel**: long runs can be cancelled with `/cancel`.
+- **Usage**: check your remaining limits with `/usage` (alias: `/limits`).
 
-- `/threads` is now resilient: if `thread/list` is slow/unavailable, it degrades to the Codex sidebar cache so Telegram still gets a fast reply.
-- Reduced “stuck waiting” cases caused by Keychain prompts/hangs (best-effort Keychain access with short timeouts).
+Notes:
 
-### What you can do
+- Photo input is **experimental** and depends on your Codex App / App Server version.
+- Per-thread “busy status” is **not** reliably observable from Codex today (we only know tasks started by this bridge).
 
-- Send text input from Telegram to the bound Codex thread.
-- Send photos as image input (experimental; depends on your Codex App / App Server version).
-- Watch execution state + final response in the same Telegram chat.
-- Query Codex limits with `/usage` (alias: `/limits`).
-- Cancel long runs with `/cancel`.
-- Run official hosted mode (recommended) or switch to self-hosted mode.
+### 2-minute setup (local mode, recommended for open-source)
 
-### 2-minute setup (official hosted path)
+1. Download the latest desktop build from [Releases](https://github.com/tonyHu08/CodeX_Bridge/releases) and open it.
+2. In the onboarding wizard:
+   1. **Environment check** (Codex CLI + App Server).
+   2. **Configure Telegram bot** (paste a BotFather token).
+   3. **Pair your phone** (QR / deep link).
+3. In Telegram:
+   1. Send `/threads`
+   2. Tap a thread button (or `/bind <index>`)
+4. Send your first remote prompt.
 
-1. Download the latest desktop build from [Releases](https://github.com/tonyHu08/CodeX_Bridge/releases).
-2. Open the app and finish the 3-step onboarding:
-   1. Codex environment check.
-   2. Phone pairing (QR / deep link).
-   3. In Telegram, send `/threads` and bind one thread.
-3. Send your first remote message directly in Telegram.
+### Command cheat sheet 🧩
 
-No BotFather token is required in official hosted mode.
+| Command | What it does |
+| --- | --- |
+| `/threads` | List recent threads and bind quickly |
+| `/bind latest` | Bind the latest thread |
+| `/bind <index|threadId>` | Bind a specific thread |
+| `/current` | Show snapshot of the current bound thread |
+| `/status` | Show bridge status |
+| `/usage` / `/limits` | Show Codex rate limits remaining |
+| `/cancel` | Cancel the current task |
+| `/unbind` | Clear current binding |
 
-### Command cheat sheet
+### Recent stability fixes 🛠️
 
-- `/threads` list recent threads and bind quickly.
-- `/bind latest` bind latest thread.
-- `/bind <index|threadId>` bind target thread.
-- `/current` show snapshot of current bound thread.
-- `/status` show bridge status.
-- `/usage` or `/limits` show Codex limits.
-- `/cancel` stop running task.
-- `/unbind` clear current binding.
+- `/threads` is now resilient: if `thread/list` is slow/unavailable, it degrades to the Codex sidebar cache so Telegram still gets a fast reply.
+- Reduced “stuck waiting” cases caused by Keychain prompts/hangs (best-effort Keychain access with short timeouts).
 
 ### Visual flow
 
@@ -75,24 +93,13 @@ flowchart LR
 ```mermaid
 flowchart TB
     U["Telegram user"] --> T["Telegram bot"]
-    T --> R["Bridge relay (hosted/local)"]
+    T --> R["Bridge relay (local on your Mac)"]
     R --> A["Desktop agent"]
     A --> C["Codex App Server JSON-RPC"]
     C --> TH["Selected Codex thread"]
     TH --> C --> A --> R --> T --> U
 ```
 
-### Screenshots and media
-
-More screenshots:
-
-- `docs/assets/readme/`
-
-- [Press kit](./assets/press-kit/README.md)
-- [Launch playbook](./docs/LAUNCH_PLAYBOOK.md)
-- [Launch posts (copy-ready)](./docs/LAUNCH_POSTS.md)
-- [User stories](./docs/USER_STORIES.md)
-
 ### Docs
 
 - [Commands](./docs/COMMANDS.md)
@@ -110,65 +117,76 @@ More screenshots:
 ```bash
 npm install
 npm run setup
-npm run dev:relay
-npm run build:desktop
-npm run start:desktop
-```
-
-```bash
-npm run typecheck
 npm run build
+npm run start:desktop
 ```
 
 ---
 
 ## 中文
 
-把本机 Codex 远程装进 Telegram，2 分钟内就能发出第一条远程指令。
+### 这是什么？
 
-Codex Bridge 解决的是一个非常实际的问题：你离开电脑后，Codex 对话就中断。这个项目让你在手机上继续操作同一个 thread，保持上下文、审批和结果回包的一致性。
+Codex 在桌面端很强，但它不是“随时随地继续工作”的工具：你一离开电脑，对话就中断。
 
-### 核心价值
+**Codex Bridge** 把你的本机 Codex thread 连接到 Telegram，让你在手机上继续推进同一条对话，上下文、审批和回包都保持一致：
 
-- 主路径不依赖命令行。
-- 不是普通“消息转发”，而是 thread 级远程控制。
-- 支持远程审批和状态追踪。
-- 菜单栏可直接查看状态、开关远程。
-- 桌面端和 Telegram 双语体验（中/英）。
+- ✅ thread 级远程控制（`/threads`、`/bind`、`/current`）
+- 🔒 远程审批（`/approve` / `/deny`）
+- 📊 状态与用量（`/status`、`/usage`）
+- 🧰 菜单栏快速开关（在线状态 + 远程开关）
+- 🌏 双语体验（中 / 英）
 
-### 已支持能力
+### 真机截图
 
-- Telegram 文本/图片输入转发到绑定 thread。
-- `/threads` 查看并快速绑定会话。
-- `/usage` / `/limits` 查看 Codex 用量。
-- `/cancel` 终止长任务。
-- 官方托管模式（推荐）与本地自托管模式可切换。
+| 电脑端主页 | Telegram 远程控制 |
+| --- | --- |
+| ![Desktop app home](./docs/assets/readme/desktop-home.png) | ![Telegram remote control](./docs/assets/readme/telegram-threads.png) |
 
-### 快速开始（官方托管）
+### 功能亮点 ✨
 
-1. 在 [Releases](https://github.com/tonyHu08/CodeX_Bridge/releases) 下载并打开桌面 App。
-2. 按向导完成三步：
-   1. Codex 环境检测。
-   2. 手机配对（扫码或 deep link）。
-   3. Telegram 发送 `/threads` 并绑定线程。
-3. 直接在 Telegram 发送消息开始远程操作。
+- **带上下文的远程续聊**：不是消息转发，是继续你本机的真实 thread。
+- **审批**：需要执行命令/修改文件时，可在 Telegram 一键同意/拒绝。
+- **队列与终止**：长任务可以用 `/cancel` 主动停止。
+- **用量**：`/usage`（别名 `/limits`）查看剩余额度。
+
+说明：
 
-说明：官方托管模式下，不需要手动去 BotFather 创建 Token。
+- 图片输入属于**实验能力**，是否可用取决于你的 Codex App / App Server 版本。
+- 每个 thread 的“是否正在运行”目前无法从 Codex 稳定获取（桥接只能知道自己触发的任务）。
 
-### 常用命令
+### 2 分钟上手（开源推荐：本机模式）
 
-- `/threads`：查看最近线程并快速绑定
-- `/bind latest`：绑定最新线程
-- `/bind <编号|threadId>`：绑定指定线程
-- `/current`：查看当前线程快照
-- `/status`：查看桥接状态
-- `/usage` 或 `/limits`：查看用量
-- `/cancel`：终止当前任务
-- `/unbind`：解除当前绑定
+1. 在 [Releases](https://github.com/tonyHu08/CodeX_Bridge/releases) 下载并打开桌面 App。
+2. 按向导完成：
+   1. **环境检测**（Codex CLI + App Server）
+   2. **配置 Telegram 机器人**（粘贴 BotFather token）
+   3. **手机配对**（扫码或 deep link）
+3. Telegram 里：
+   1. 发送 `/threads`
+   2. 点选 thread（或 `/bind <编号>`）
+4. 开始发消息远程操作。
+
+### 常用命令 🧩
+
+| 命令 | 作用 |
+| --- | --- |
+| `/threads` | 查看最近会话并快速绑定 |
+| `/bind latest` | 绑定最新会话 |
+| `/bind <编号|threadId>` | 绑定指定会话 |
+| `/current` | 查看当前会话快照 |
+| `/status` | 查看桥接状态 |
+| `/usage` / `/limits` | 查看剩余用量与重置时间 |
+| `/cancel` | 终止当前任务 |
+| `/unbind` | 解除绑定 |
+
+### 最近稳定性修复 🛠️
+
+- `/threads` 更稳：`thread/list` 超时会降级到 Codex 侧边栏缓存，确保 Telegram 仍能快速拿到列表。
+- 降低 Keychain 造成的“卡住/无回包”风险（Keychain 访问改为短超时 best-effort）。
 
 ### 相关文档
 
-- [发布增长手册](./docs/LAUNCH_PLAYBOOK.md)
-- [首发文案模板（可直接复制）](./docs/LAUNCH_POSTS.md)
-- [用户故事脚本](./docs/USER_STORIES.md)
-- [媒体素材包](./assets/press-kit/README.md)
+- [命令说明](./docs/COMMANDS.md)
+- [故障排查](./docs/TROUBLESHOOTING.md)
+- [隐私与边界](./docs/PRIVACY.md)