CC Pocket vs WebPeek

Your agents. In your pocket. CC Pocket brings Codex and Claude to a chat UI made for your phone. Start a task, approve the next step, and review the result. Your agents run on your own computer; you can pick up the same work on another device. CHAT FIRST Each session is a room for prompts, replies, approvals, and questions. Send images, use voice input, or write with Markdown. Handle waiting approvals from the session list. CONTINUE ACROSS DEVICES Move between your phone, tablet, and Mac. Resume sessions from the CLI or app. On larger screens, keep chat, project files, and Git changes side by side. Native macOS is available; Linux and Windows desktop builds are experimental. KEEP YOUR PLACE ON WEAK NETWORKS Outgoing messages wait while you are offline and resend after reconnecting. Missed streaming updates are recovered. New requests and approvals need a connection to the Bridge Server. CREATE AND PREVIEW Generate images with Codex Imagegen and open the results in chat. Play video and audio files without leaving the app. REVIEW AND SHIP Browse project files, inspect code and image diffs, stage changes, commit, push, or revert. Keep parallel tasks separate with git worktrees. YOUR OWN MACHINES Run the Bridge Server on your Mac, Linux, or Windows computer. Connect by QR code or saved host. Tailscale supports access away from your local network, and SSH lets you manage the Bridge remotely. GET STARTED 1. Install Node.js 20.18.1 or later and Codex or Claude on your computer. 2. Run: npx @ccpocket/bridge@latest 3. Scan the QR code in CC Pocket and choose a project. A reachable Bridge Server and a configured agent account are required. CC Pocket is free to use, with optional Supporter purchases. Agent service fees are separate. CC Pocket is open source and is not affiliated with Anthropic or OpenAI. https://github.com/K9i-0/ccpocket TERMS OF USE https://www.apple.com/legal/internet-services/itunes/dev/stdeula/

WebPeek brings the four panels you already know to Safari on iPhone and iPad. Turn it on once and every page gets a small floating button; tap it and the inspector slides up over the page you are already reading. ELEMENTS • Tap the picker, then tap anything on the page to select it • A real DOM tree with syntax colouring and a breadcrumb • Edit attributes, text and outerHTML; delete nodes — all applied live • Matched CSS rules, every computed property, and a box-model diagram CONSOLE • Every console.* call captured from the very first line of the page • Uncaught errors, unhandled rejections and CSP violations, with stack traces • Expandable object trees — arrays, Maps, Sets, typed arrays, DOM nodes • An input line for running expressions, with history NETWORK • fetch, XMLHttpRequest, WebSocket, sendBeacon and EventSource, captured as they happen • Status, method, size, and a timing breakdown per request • Request and response headers, request body, response preview • Images, audio and video previewed inline • Copy as cURL, or export the whole session as a HAR file STORAGE • localStorage, sessionStorage and cookies — read, edit, add, delete • IndexedDB browser with paging, including what type each value is • Cache Storage, including what a Service Worker has cached • A usage bar for the origin BUILT FOR A PHONE • The panel lives inside the page — nothing to connect, nothing to install on a computer • Three heights, drag to resize, or a side dock on iPad • Light and dark, English, 简体中文 and 繁體中文 • Every destructive action asks first HONEST ABOUT LIMITS iOS gives Safari extensions a smaller toolbox than a desktop browser, and WebPeek says so instead of pretending. HttpOnly cookies stay invisible, pages with a strict Content-Security-Policy cannot run expressions, static files arrive without headers, and cross-origin responses only show the headers the server chose to expose. The in-app Tips screen explains each one and why. PRIVACY WebPeek reads only the page you are looking at, keeps everything on the device, and has no account, no analytics and no network calls of its own.