[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-795":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":24,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":15,"starSnapshotCount":15,"syncStatus":16,"lastSyncTime":29,"discoverSource":30},795,"chromex","GENEXIS-AI\u002Fchromex","GENEXIS-AI","A Codex-powered Chrome side-panel assistant for page context, tabs, voice, and image workflows.",null,"TypeScript",1132,116,4,3,0,2,5,58,6,19.2,"MIT License",false,"main",true,[],"2026-06-12 02:00:18","# Chromex\n\n[![CI](https:\u002F\u002Fgithub.com\u002FGENEXIS-AI\u002Fchromex\u002Factions\u002Fworkflows\u002Fci.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002FGENEXIS-AI\u002Fchromex\u002Factions\u002Fworkflows\u002Fci.yml)\n[![License: MIT](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-blue.svg)](.\u002FLICENSE)\n[![GitHub stars](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002FGENEXIS-AI\u002Fchromex?style=social)](https:\u002F\u002Fgithub.com\u002FGENEXIS-AI\u002Fchromex\u002Fstargazers)\n[![English](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Freadme-English-111827.svg)](.\u002FREADME.md)\n[![한국어](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Freadme-한국어-2563eb.svg)](.\u002Freadmes\u002FREADME.ko.md)\n[![日本語](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Freadme-日本語-dc2626.svg)](.\u002Freadmes\u002FREADME.ja.md)\n[![简体中文](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Freadme-简体中文-16a34a.svg)](.\u002Freadmes\u002FREADME.zh-CN.md)\n\nChromex is a Chrome MV3 side-panel assistant that connects Chrome to Codex through a local native bridge. It helps users work with the current page, selected tabs, uploaded files, voice input, images, and browser workflows while keeping credentials out of extension storage.\n\nPublished by **GenexisAI CHOI**.\n\n![Chromex browser side-panel assistant](.\u002Fassets\u002Fchromex-hero.png)\n\n## What It Does\n\n- Chat with the current webpage, selected open tabs, screenshots, uploaded files, PDFs, Office files, images, and browser history when requested.\n- Summarize and compare page content, YouTube videos, news articles, research pages, PDFs, and arXiv papers.\n- Edit or generate images through Codex image workflows with local output handling.\n- Use voice transcription, live voice mode, page-aware suggestions, custom profiles, and optional Codex skills.\n- Run browser-control workflows through Chrome content scripts with visible in-page activity indicators.\n\n## Install From Source\n\nUse the source checkout or [`chromex-public-source.zip`](https:\u002F\u002Fgithub.com\u002FGENEXIS-AI\u002Fchromex\u002Freleases\u002Flatest\u002Fdownload\u002Fchromex-public-source.zip):\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002FGENEXIS-AI\u002Fchromex.git\ncd chromex\nnpm install\nnpm run build\nnode scripts\u002Finstall-native-host.mjs\n```\n\nThen close every Chrome window, reopen Chrome, open `chrome:\u002F\u002Fextensions`, enable **Developer mode**, select **Load unpacked**, and choose:\n\n```text\npackages\u002Fextension\u002Fdist\n```\n\nImportant: run `npm install`, `npm run build`, and `install-native-host.mjs` from the `chromex` source folder that contains `package.json`. If Windows reports `ENOENT Could not read package.json`, you are in the wrong folder.\n\n### Windows Local Bridge Setup\n\nOn Windows, install Node.js 20 LTS or newer, then install and verify the Codex CLI first:\n\n```powershell\nnpm install -g @openai\u002Fcodex\ncodex --version\n```\n\nUse the npm install path above even if `winget install Codex -s msstore` fails. `0x8a15005e: The server certificate did not match any of the expected values` is a Windows Store \u002F TLS certificate-chain problem outside Chromex, not a Chromex install step.\n\nThen use **PowerShell** from the `chromex` source folder:\n\n```powershell\nnpm install\nnpm run build\nnode scripts\u002Finstall-native-host.mjs --browser=chrome\n```\n\nThen open `chrome:\u002F\u002Fextensions`, click **Reload** on Chromex, and press **Check connection** in the Chromex side panel.\n\nIf the side panel still says the local bridge is waiting:\n\n1. Confirm Chromex is loaded from `packages\u002Fextension\u002Fdist`.\n2. Copy the extension ID shown on the Chromex card in `chrome:\u002F\u002Fextensions`.\n3. Re-run the installer with that ID:\n\n```powershell\nnode scripts\u002Finstall-native-host.mjs \u003Cextension-id> --browser=chrome\n```\n\nThe expected public release ID is `menmlhahmendmkiicbjihgjhppkgaeom`. If Chrome shows a different ID, use the ID shown in Chrome.\n\nIf login fails with `Failed to start codex app-server`, Chromex can reach the local bridge but cannot start the Codex CLI. Re-run `codex --version`. If Windows cannot find it, set the optional Codex binary path to `%APPDATA%\\npm\\codex.cmd`, or set the folder to `%APPDATA%\\npm`. Do not put your workspace folder in the Codex binary field; the workspace folder and Codex executable path are separate settings.\n\nTo force executable detection on Windows:\n\n```powershell\nnpm install -g @openai\u002Fcodex\nwhere codex\ncodex --version\n```\n\nIf `where codex` prints `C:\\Users\\\u003Cyou>\\AppData\\Roaming\\npm\\codex.cmd`, open Chromex settings and set the optional Codex binary path to `%APPDATA%\\npm\\codex.cmd`, save, close every Chrome window, reopen Chrome, and press **Check connection**.\n\n## Runtime Boundary\n\nChromex uses this boundary:\n\n```text\nChrome Extension -> Native Messaging Host -> Local Bridge -> codex app-server\n```\n\nThe source tree is organized as:\n\n- `packages\u002Fextension`: Chrome MV3 side-panel extension\n- `packages\u002Fbridge`: local bridge daemon for Codex app-server and multimodal workflows\n- `packages\u002Fnative-host`: Chrome Native Messaging relay\n- `packages\u002Fshared`: shared types, policies, profiles, and helpers\n\n## Language Support\n\nChromex follows the browser language automatically by default. Users can also choose a language in **Settings > General > App UI language**.\n\nThe extension ships Chrome `_locales` entries for English, Korean, Japanese, Chinese, Arabic, French, German, Spanish, Portuguese, Hindi, Vietnamese, Thai, Turkish, Ukrainian, and many other Chrome-compatible locales. Model responses are instructed to follow the selected UI language unless the user asks for another language.\n\n## Security And Privacy Defaults\n\n- The extension does not store raw OpenAI API keys, OAuth tokens, or ChatGPT session tokens in Chrome extension storage.\n- Codex OAuth \u002F ChatGPT login is handled through the local Codex app-server flow.\n- API-key login is an optional local fallback and is never used automatically without user confirmation.\n- Page content, tab data, screenshots, browser history, microphone input, and browser actions are used only for user-requested workflows.\n- `history`, `tabs`, screen capture, microphone, and site access are requested only when a feature needs them.\n- Conversation history is session-only by default. Persistent local chat history is opt-in.\n- Native-host child processes and workspace hooks run with a reduced environment allowlist.\n- Generated image originals, temporary uploads, and diagnostics are handled by the local bridge.\n\nRead [SECURITY.md](.\u002FSECURITY.md) and [PRIVACY.md](.\u002FPRIVACY.md) before publishing or deploying a modified build.\n\n## Features\n\n- Persistent MV3 side panel with chat-first UX.\n- Automatic routing for page, file, image, history, voice, and browser-control requests.\n- `@` picker for selecting one or more open tabs.\n- `\u002F` picker for profile selection.\n- Attachments for images, text, PDF, DOCX, CSV, TSV, XLSX, and XLSM.\n- Read strategy policy for DOM, vision, hybrid, and site-adapter workflows.\n- Site-aware suggestions for YouTube, news, research, mail, collaboration, notes, task tools, shopping, travel, and Korean work services.\n- YouTube adapter with current timestamp context and seek actions.\n- Non-destructive image editing for uploaded images, page images, or visible screen captures.\n- Markdown rendering with code blocks, tables, links, and copy controls.\n- Optional Codex skills loaded from a user's local `.codex\u002Fskills\u002F*\u002FSKILL.md` only when enabled.\n\n## Development\n\n```bash\nnpm install\nnpm run typecheck\nnpm run test\nnpm run build\nnpm run release:audit\n```\n\nOptional browser smoke test:\n\n```bash\nnpm run smoke\n```\n\nIf no compatible browser exists, install the Playwright Chromium runtime:\n\n```bash\nnpm run smoke:install-browser\n```\n\nThe built extension is emitted to:\n\n```text\npackages\u002Fextension\u002Fdist\n```\n\n## Release Management\n\nChromex uses normal open-source release history from `0.1.1` onward. Versioning, pull request flow, and release checklist are documented in [RELEASE.md](.\u002FRELEASE.md).\n\n## Troubleshooting\n\n- **Native host missing or forbidden**: run `npm run build`, then `node scripts\u002Finstall-native-host.mjs --browser=chrome`, reload the extension in `chrome:\u002F\u002Fextensions`, and check Chromex onboarding\u002Fsystem status. If Chrome shows a different extension ID, run `node scripts\u002Finstall-native-host.mjs \u003Cextension-id> --browser=chrome`.\n- **Codex executable is not detected**: run `npm install -g @openai\u002Fcodex`, `where codex`, and `codex --version`. If needed, set the optional Codex binary path in Chromex to `%APPDATA%\\npm\\codex.cmd`, save, fully restart Chrome, and press **Check connection**.\n- **Model list does not load**: confirm the native bridge is connected, then sign in through the app-server-backed login flow.\n- **Page context is unavailable**: open Chromex from the target tab or approve the Chrome site permission prompt when the workflow requests access.\n- **Chrome still shows old UI**: run `npm run build`, reload the extension card, and confirm Chrome is loading `packages\u002Fextension\u002Fdist`.\n- **Browser smoke test fails because no browser exists**: run `npm run smoke:install-browser`, then `npm run smoke`.\n\n## License\n\nMIT. See [LICENSE](.\u002FLICENSE).\n\n## Star History\n\n\u003Ca href=\"https:\u002F\u002Fwww.star-history.com\u002F#GENEXIS-AI\u002Fchromex&Date\">\n  \u003Cpicture>\n    \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\"https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=GENEXIS-AI\u002Fchromex&type=Date&theme=dark\" \u002F>\n    \u003Csource media=\"(prefers-color-scheme: light)\" srcset=\"https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=GENEXIS-AI\u002Fchromex&type=Date\" \u002F>\n    \u003Cimg alt=\"Star History Chart\" src=\"https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=GENEXIS-AI\u002Fchromex&type=Date\" \u002F>\n  \u003C\u002Fpicture>\n\u003C\u002Fa>\n","Chromex 是一个基于 Codex 的 Chrome 侧边栏助手，能够处理页面内容、标签页、语音和图像工作流。它通过本地原生桥接技术将 Chrome 与 Codex 连接起来，提供网页聊天、截图编辑、文件上传、语音转录等功能，并支持浏览器历史记录和页面内容的总结与比较。此外，用户可以利用 Codex 的图像处理能力生成或编辑图片，并通过 Chrome 内容脚本执行浏览器控制任务。Chromex 适用于需要高效处理网页信息、多媒体内容以及进行复杂交互操作的场景，特别适合研究人员、开发者和内容创作者使用。","2026-06-11 02:39:24","CREATED_QUERY"]