@tarunspandit/codexflow 0.29.0

package/FAQ.md

@@ -0,0 +1,327 @@
+# CodexFlow FAQ
+
+## Which ChatGPT account should I use?
+
+Use a ChatGPT account with Apps / Developer Mode access. OpenAI currently lists Developer Mode for Pro, Plus, Business, Enterprise, and Education accounts on web.
+
+Current testing shows free and Go accounts do not expose the app flow needed for CodexFlow.
+
+codexflow does not unlock Developer Mode, unlock models, bypass account limits, or provide account access. It connects to the ChatGPT app surface your account already has.
+
+Account access and model tool support are separate. An eligible account can have Apps / Developer Mode, while a specific model surface may still be unable to call connectors or MCP tools directly. If CodexFlow actions are unavailable in that chat, use another tool-capable ChatGPT surface or the Pro context fallback for that session.
+
+## How is CodexFlow different from generic workspace bridges?
+
+They can look similar at the transport layer because both use a local MCP-style bridge and a workspace root.
+
+codexflow is more focused: it is built around one clear product loop for ChatGPT users:
+
+```text
+install -> run codexflow -> paste the copied Server URL -> choose a project per ChatGPT conversation
+```
+
+The main differences are:
+
+- CodexFlow is ChatGPT Developer Mode first, not a generic workspace bridge.
+- Bash, write/edit, tool mode, Codex session reads, and handoff execution are separate safety controls.
+- Durable context is repo-backed through `AGENTS.md` and `.ai-bridge/*`, so important project memory stays reviewable in files.
+- The normal workflow emphasizes compact cards, diffs, `show_changes`, smoke tests, and handoff status files.
+- CodexFlow keeps a strict boundary: no model proxying, account pooling, third-party Pro site scraping, quota bypassing, or OS sandbox claims.
+
+codexflow connects ChatGPT to a user-approved local repository over MCP. Repository access, command permissions, and change review remain explicit.
+
+## What does Repository Analysis understand?
+
+Repository Analysis builds a local repository map from bounded, inspectable evidence:
+
+- project and package manifests
+- source/test/config/documentation paths
+- common declarations, imports, includes, and internal module relationships
+- Git changes and existing project verification scripts
+
+It supports TypeScript/JavaScript, Python, Go, Rust, Swift, Java, C#, C, and C++ declaration patterns. Unsupported languages still participate in safe inventory and lexical search.
+
+Relationships are labeled `exact`, `strong`, or `inferred`. The repository map does not replace a compiler or language server. CodexFlow does not require a language server, daemon, embedding service, or vector database.
+
+Analysis is process-local and cached by a bounded workspace fingerprint. Direct CodexFlow writes, edits, and patches invalidate that cache. If limits are reached, results say `partial` and retain normal tree/search/read/review fallback behavior.
+
+Set `CODEXFLOW_ANALYSIS=0` to disable this layer while keeping the standard file, search, Git, and review tools available.
+
+Terminal users can inspect the same facts without ChatGPT:
+
+```bash
+codexflow inspect --json
+codexflow review --json
+```
+
+## What is the `codexflow` supertool?
+
+Note: this FAQ follows GitHub `main`. Check the npm badge/version before assuming a `main` feature is in `codexflow@latest`.
+
+`codexflow` is a stable wrapper tool for advanced setups. It accepts:
+
+```json
+{ "action": "search", "args": { "query": "needle", "path": "src" } }
+```
+
+Call it with `action=list_actions` to see what the current server mode actually allows. It cannot call tools that are hidden by `--tool-mode`, `--no-bash`, or non-workspace write mode.
+
+Use explicit tools such as `read`, `search`, `edit`, `bash`, and `show_changes` for normal work. Use the supertool when ChatGPT connector caching, custom workflows, or stable wrapper-style integrations matter more than separate visible tool descriptors.
+
+## What is the recommended install path?
+
+Install globally once:
+
+```bash
+npm install -g @tarunspandit/codexflow
+```
+
+Then run one command from anywhere:
+
+```bash
+codexflow
+```
+
+CodexFlow discovers local Codex project folders automatically and starts the broker and tunnel.
+
+`npx codexflow@latest` still works as a no-install fallback, but the global install is easier for normal users.
+
+## What do I enable in ChatGPT?
+
+Open ChatGPT and go to:
+
+```text
+Settings
+-> Security and login
+-> Developer mode: on
+-> Enforce CSP in developer mode: on
+
+Settings
+-> Plugins
+-> Create
+```
+
+When creating the plugin:
+
+```text
+Name: CodexFlow
+Description: Local workspace bridge for ChatGPT coding
+Connection: Server URL
+Server URL: paste the URL copied by CodexFlow
+Authentication: No Authentication / None
+```
+
+The copied Server URL already includes the private CodexFlow token.
+
+## Should CSP stay enabled?
+
+Yes. Keep Enforce CSP in developer mode enabled.
+
+codexflow widgets are built for the CSP-enabled path. They do not need unrestricted network access, external fonts, remote scripts, iframes, or third-party images.
+
+## Does CodexFlow bypass rate limits?
+
+No.
+
+codexflow does not bypass, avoid, increase, pool, resell, or modify ChatGPT, Codex, OpenAI, or third-party model limits. Every request still runs through the user's own ChatGPT session and whatever limits that account has.
+
+The useful part is that Codex and ChatGPT are different product surfaces. If one workflow is unavailable and another product surface you already have access to is still available, CodexFlow lets you work against the same local repo without changing either product's limits.
+
+## Can CodexFlow use GPT-5.5?
+
+Only if your ChatGPT account already exposes that exact model, or a similar stronger model, in the ChatGPT web product surface you are using, and that model surface can call Developer Mode apps.
+
+Some GPT-5.5 Pro or other model surfaces may not expose app actions in a given chat. If CodexFlow actions are unavailable there, CodexFlow cannot make that request reach the local server. CodexFlow does not provide, proxy, resell, or unlock models. It gives compatible ChatGPT sessions local repo tools.
+
+For models that cannot call tools, generate a repo context bundle instead:
+
+```bash
+codexflow pro-bundle --root /path/to/repo --copy
+```
+
+## What can ChatGPT see through CodexFlow?
+
+ChatGPT can see explicit workspace context exposed by tools:
+
+- `AGENTS.md`
+- `.ai-bridge` plans and status files
+- git status
+- git diff
+- selected source files
+- file tree and search results
+
+It cannot read hidden Codex runtime memory or anything outside the allowed workspace unless you explicitly allow that root.
+
+## What can ChatGPT edit?
+
+In normal coding mode, ChatGPT can write and exact-edit files inside the configured workspace.
+
+Safety defaults block common sensitive paths:
+
+- `.env`
+- private keys
+- `.git`
+- `node_modules`
+- generated build/cache folders
+- symlink escapes
+- paths outside the workspace
+
+Use handoff mode if you want ChatGPT to write a plan only and let Codex execute locally. In handoff mode, generic `write` and `edit` tools are not advertised to ChatGPT.
+
+Use `CODEXFLOW_WRITE_MODE=off` when you want direct `write` and `edit` tools removed from the advertised MCP tool list while still allowing bounded handoff/context files.
+
+## Can CodexFlow bind bash to a specific session id?
+
+codexflow cannot attach to, read, or execute inside a specific Codex app conversation or terminal session.
+
+The MCP `bash` tool runs from the CodexFlow server process you started for the configured workspace. MCP session ids are HTTP transport state between ChatGPT and CodexFlow; they are not Codex conversation ids.
+
+What CodexFlow can do is require a matching local bash session label before it runs shell commands:
+
+```bash
+codexflow --bash-session main --require-bash-session
+```
+
+Then `bash` calls must include `session_id: "main"`. This helps avoid accidental shell execution in the wrong CodexFlow terminal, but it is not remote control of an existing Codex app chat.
+
+codexflow can list local Codex session ids and titles when you explicitly opt in:
+
+```bash
+codexflow --codex-sessions metadata
+```
+
+This reads local Codex JSONL history under `~/.codex/sessions` and `~/.codex/archived_sessions` and returns metadata plus `codex resume <session-id>` commands. Use `--codex-sessions read` only if you also want bounded transcript reads. It does not attach to a live Codex app conversation.
+
+If you do not want ChatGPT to trigger shell commands while you work in Codex, start CodexFlow with bash disabled:
+
+```bash
+codexflow --no-bash
+```
+
+This removes the `bash` MCP tool from the advertised tool list. ChatGPT can still use non-bash CodexFlow tools such as workspace open, read, search, and show_changes. Direct `write`/`edit` are advertised only in workspace write mode.
+
+If you only want ChatGPT to plan and leave execution to Codex or another local agent:
+
+```bash
+codexflow --mode handoff --no-bash
+```
+
+## Which tunnel should I choose?
+
+Use this rule:
+
+```text
+Fast demo:              Cloudflare quick tunnel
+Recommended stable URL: ngrok free dev domain
+Custom domain:          Cloudflare named tunnel
+Tailnet users:           Tailscale Funnel
+No public tunnel:       local-only mode, only for clients that can reach localhost
+```
+
+Cloudflare quick tunnel URLs change on restart. If you put a quick-mode URL into ChatGPT, you must edit the ChatGPT app Server URL every time you restart the tunnel.
+
+For most users, the better path is a free ngrok dev domain. Create a free ngrok account, find your assigned dev domain under Universal Gateway -> Domains, and save that hostname during `codexflow`.
+
+If you own a domain, use Cloudflare named tunnels and route DNS to a hostname like `codexflow.example.com`.
+
+## Why does ChatGPT show “Something went wrong” when I create a connector?
+
+Usually ChatGPT could not reach the public MCP URL. A generated `trycloudflare.com` URL is not proof that `cloudflared` stayed connected.
+
+Run the connection test:
+
+```bash
+codexflow connection-test --root /path/to/repo
+```
+
+This keeps `read`, `tree`, `search`, and `load_skill`, but disables file writes,
+bash, and tool cards. In ChatGPT, create the development plugin under
+`Settings -> Plugins`, paste the complete Server URL, and choose
+`No Authentication`.
+
+The terminal output separates the failure boundary:
+
+- No `POST /mcp received`: the request did not reach CodexFlow. Check the ChatGPT
+  Plugins page and the tunnel.
+- `POST /mcp -> 401`: paste the complete URL, including `codexflow_token`.
+- `POST /mcp -> 2xx`: ChatGPT reached CodexFlow and the MCP endpoint responded.
+
+Keep CodexFlow running while testing. A Cloudflare quick-tunnel URL changes on
+every restart. If Cloudflare returns `530` / `Error 1033`, check DNS or
+proxy-client DNS handling on the machine running `cloudflared`.
+
+ChatGPT now manages development apps under Plugins. The browser error
+`Failed to execute 'removeChild' on 'Node'` occurs in the ChatGPT page, before
+codexflow can handle an MCP request. Remove or recreate the stale plugin entry
+from the Plugins page, then retry with the current URL. CodexFlow cannot repair
+that browser-side entry.
+
+Official references:
+
+- OpenAI: connect an MCP server to ChatGPT: https://developers.openai.com/apps-sdk/deploy/connect-chatgpt
+- OpenAI: MCP server authentication: https://developers.openai.com/apps-sdk/build/auth
+- ngrok dev domains: https://ngrok.com/docs/universal-gateway/domains
+- Cloudflare Tunnel routing: https://developers.cloudflare.com/tunnel/routing/
+- Cloudflare Tunnel DNS records: https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/dns/
+
+## Can I use the same ChatGPT app URL every day?
+
+Yes, if you use a stable hostname.
+
+Recommended simple path:
+
+```bash
+codexflow
+# choose ngrok
+# enter your ngrok free dev domain
+```
+
+After that:
+
+```bash
+codexflow
+```
+
+The same hostname and CodexFlow token are reused for that workspace.
+
+## What if I want to work in two repos at once?
+
+Run one CodexFlow process. Open two ChatGPT conversations and choose a different project in each picker. Both chats share the same broker and tunnel while keeping independent project bindings.
+
+## Where are the current docs?
+
+Use the [CodexFlow website](https://tarunspandit.github.io/codexflow/), the [GitHub repository](https://github.com/tarunspandit/codexflow), or the documentation shipped in the npm package.
+
+## Is CodexFlow production safe?
+
+codexflow is a local developer bridge, not an OS sandbox.
+
+Use it with repos you trust. Keep token auth enabled for public tunnels. Keep safe bash on unless you know why you need full bash. Read [SECURITY.md](SECURITY.md) before exposing it through a public tunnel.
+
+## Where are saved settings stored?
+
+codexflow stores local state under `~/.codexflow` by default. On Windows that is usually `C:\Users\<you>\.codexflow`.
+
+Workspace profiles are JSON files saved under:
+
+```text
+~/.codexflow/profiles/
+```
+
+Current runtime connection files are saved under:
+
+```text
+~/.codexflow/runtime/
+```
+
+Set `CODEXFLOW_HOME` to move this directory.
+
+Use:
+
+```bash
+codexflow settings
+codexflow settings list
+codexflow settings delete --yes
+```
+
+Saved tokens are redacted when profiles are displayed.

package/FAQ_ZH.md

@@ -0,0 +1,279 @@
+# CodexFlow 中文 FAQ
+
+## 我应该用什么 ChatGPT 账号？
+
+使用能访问 Apps / Developer Mode 的 ChatGPT 账号。OpenAI 当前文档列出的 web 端 Developer Mode 账号范围包括 Pro、Plus、Business、Enterprise 和 Education。
+
+当前测试显示，Free / Go 账号不暴露 CodexFlow 需要的 App 创建流程。
+
+codexflow 不解锁 Developer Mode，不解锁模型，不绕过账号限制，也不提供账号访问。它只连接你自己的 ChatGPT App 界面和你自己的本地仓库。
+
+## 推荐安装方式是什么？
+
+注意：这个 FAQ 跟随 GitHub `main`。假设某个 `main` 功能已经进入 `codexflow@latest` 前，请先看 npm badge/version。
+
+全局安装一次：
+
+```bash
+npm install -g @tarunspandit/codexflow
+```
+
+然后从任何目录运行唯一命令：
+
+```bash
+codexflow
+```
+
+CodexFlow 会自动发现本机 Codex 使用过的项目，并启动 broker 和 tunnel。
+
+`npx codexflow@latest` 仍然可用，但普通用户更容易理解全局安装。
+
+## ChatGPT 里要打开什么设置？
+
+在 ChatGPT 中打开：
+
+```text
+Settings
+-> Security and login
+-> Developer mode: on
+-> Enforce CSP in developer mode: on
+
+Settings
+-> Plugins
+-> Create
+```
+
+创建 Plugin 时填写：
+
+```text
+Name: CodexFlow
+Description: Local workspace bridge for ChatGPT coding
+Connection: Server URL
+Server URL: 粘贴 CodexFlow 复制的 URL
+Authentication: No Authentication / None
+```
+
+复制的 Server URL 已经包含私有 CodexFlow token。
+
+## CSP 要保持开启吗？
+
+要保持开启。
+
+codexflow 的小组件按 CSP 开启的路径构建。它不需要远程脚本、外部字体、iframe、第三方图片或任意外部请求。
+
+## CodexFlow 会绕过速率限制吗？
+
+不会。
+
+codexflow 不绕过、不提升、不合并、不转售、不修改 ChatGPT、Codex、OpenAI 或第三方模型限制。所有请求仍然通过你自己的 ChatGPT 会话，并受该账号当前限制约束。
+
+它的价值在于 ChatGPT 和 Codex 是不同产品界面。某个工作流暂时不可用时，如果另一个你本来就有权限的界面仍可用，CodexFlow 可以让它继续操作同一个本地仓库。
+
+## CodexFlow 可以使用 GPT-5.5 吗？
+
+前提是你的 ChatGPT 账号已经在 Web 产品里提供这个模型或同级更强模型，并且该模型界面可以调用 Developer Mode Apps。
+
+codexflow 不提供、不代理、不转售、也不解锁模型。它只给兼容的 ChatGPT 会话提供本地仓库工具。
+
+如果某个模型不能直接调用工具，用上下文包回退：
+
+```bash
+codexflow pro-bundle --root /path/to/repo --copy
+```
+
+然后把生成的 `.ai-bridge/pro-context.md` 粘贴给该模型，让它做规划，再用本地执行器执行。
+
+## 为什么 Pro 账号也可能连不上某个模型？
+
+账号权限和模型工具能力是两回事。
+
+Plus / Pro 可以暴露 Apps / Developer Mode，但某个具体模型界面仍然可能不能调用连接器或 MCP 工具。遇到这种情况时，用 `codexflow pro-bundle --copy` 导出上下文，再把计划交给本地代理执行。
+
+## ChatGPT 能通过 CodexFlow 看到什么？
+
+ChatGPT 能看到工具显式暴露的工作区内容：
+
+- `AGENTS.md`
+- `.ai-bridge` 计划、状态、执行记录
+- git status
+- git diff
+- 文件树和搜索结果
+- 你让它读取的源码文件
+
+它不能读取 Codex 的隐藏运行时记忆，也不能读取工作区外的文件，除非你明确允许额外 root。
+
+## ChatGPT 可以编辑什么？
+
+Normal coding 模式下，ChatGPT 可以在配置的工作区内写入和精确编辑文件。
+
+默认会阻止：
+
+- `.env`
+- 私钥
+- `.git`
+- `node_modules`
+- 生成目录和缓存目录
+- symlink 逃逸
+- 工作区外路径
+
+如果你只想让 ChatGPT 规划，不想让它直接改源码，用 handoff 模式。
+
+## CodexFlow 能把 bash 绑定到某个会话 id 吗？
+
+codexflow 不能附加到、读取或复用某一个 Codex App 聊天会话或终端会话。
+
+MCP 的 `bash` 工具是在你启动的 CodexFlow 本地服务器进程里，针对配置的 workspace root 执行。MCP session id 只是 ChatGPT 和 CodexFlow HTTP 服务器之间的传输状态，不是 Codex 会话 id。
+
+但 CodexFlow 可以要求 bash 调用带上匹配的本地 session 标签：
+
+```bash
+codexflow --bash-session main --require-bash-session
+```
+
+之后 `bash` 调用必须包含 `session_id: "main"`。这能避免误触发到错误的 CodexFlow 终端，但不是远程控制某个已有的 Codex App 聊天。
+
+如果你显式开启，CodexFlow 可以列出本地 Codex session id 和标题：
+
+```bash
+codexflow --tool-mode full --codex-sessions metadata
+```
+
+它会读取 `~/.codex/sessions` 和 `~/.codex/archived_sessions` 下的本地 Codex JSONL 历史，返回 metadata 和 `codex resume <session-id>` 命令。只有需要有限长度 transcript 读取时才使用 `--codex-sessions read`。它不会附加到正在运行的 Codex App 聊天。
+
+如果你正在 Codex 里工作，不希望 ChatGPT 触发 shell 命令，可以关闭 bash：
+
+```bash
+codexflow --no-bash
+```
+
+如果只想让 ChatGPT 写计划，由 Codex 或其他本地 agent 执行：
+
+```bash
+codexflow --mode handoff --no-bash
+```
+
+## 选择哪种 tunnel？
+
+按这个规则选：
+
+```text
+快速 demo：          Cloudflare quick tunnel
+推荐稳定 URL：       ngrok free dev domain
+自定义域名：          Cloudflare named tunnel
+Tailnet 用户：        Tailscale Funnel
+无公网 URL：          local-only，只适合能访问 localhost 的 MCP 客户端
+```
+
+Cloudflare quick tunnel 每次重启 URL 都变。把 quick URL 填到 ChatGPT 后，每次重启都要改 ChatGPT App 的 Server URL。
+
+大多数用户建议用 ngrok free dev domain。创建免费 ngrok 账号，在 Universal Gateway -> Domains 找到分配给你的 dev domain，并在 `codexflow` 里保存。
+
+如果你有自己的域名，用 Cloudflare named tunnel，把 DNS 路由到例如 `codexflow.example.com` 的主机名。
+
+## ChatGPT 创建 connector 时显示 “Something went wrong” 怎么办？
+
+通常是 ChatGPT 无法访问公网 MCP URL。生成 `trycloudflare.com` URL 不代表 `cloudflared` 一直连通。
+
+运行连接测试：
+
+```bash
+codexflow connection-test --root /path/to/repo
+```
+
+这个模式保留 `read`、`tree`、`search` 和 `load_skill`，关闭文件写入、bash
+和 tool cards，并记录请求是否到达本地 MCP endpoint。在 ChatGPT 的
+`Settings -> Plugins` 创建 development plugin，粘贴完整 Server URL，
+Authentication 选择 `No Authentication`。
+
+- 没有 `POST /mcp received`：请求没有到达 CodexFlow，检查 ChatGPT Plugins 页面和 tunnel。
+- `POST /mcp -> 401`：请粘贴包含 `codexflow_token` 的完整 URL。
+- `POST /mcp -> 2xx`：ChatGPT 已到达 CodexFlow，MCP endpoint 也已响应。
+
+测试期间保持 CodexFlow 运行。Cloudflare quick tunnel 每次重启都会更换 URL。
+如果 Cloudflare 返回 `530` / `Error 1033`，检查运行 `cloudflared` 的机器上的
+DNS 或代理客户端 DNS 设置。
+
+ChatGPT 现在在 Plugins 中管理 development app。浏览器错误
+`Failed to execute 'removeChild' on 'Node'` 发生在 ChatGPT 页面中，早于任何
+codexflow MCP 请求。请在 Plugins 页面删除或重建旧条目，再使用当前 URL 重试；
+codexflow 无法修复浏览器端的旧条目。
+
+## 能每天使用同一个 ChatGPT App URL 吗？
+
+可以，前提是使用稳定 hostname。
+
+推荐简单路径：
+
+```bash
+codexflow
+# 选择 ngrok
+# 输入你的 ngrok free dev domain
+```
+
+之后：
+
+```bash
+codexflow
+```
+
+同一个 hostname 和 CodexFlow token 会被当前工作区复用。
+
+## quick mode 为什么每次都要改 URL？
+
+Cloudflare quick tunnel 是一次性的临时地址。每次重新启动 tunnel，Cloudflare 会分配一个新的 `trycloudflare.com` URL。
+
+如果你不想改 ChatGPT 设置，用 ngrok free dev domain 或 Cloudflare named tunnel。
+
+## 同时处理两个仓库怎么办？
+
+只运行一个 CodexFlow。打开两个 ChatGPT 对话，在各自的项目选择器中选择不同仓库；它们共享同一个 broker/tunnel，但项目绑定彼此独立。
+
+## 最新文档在哪里？
+
+请使用 [CodexFlow 网站](https://tarunspandit.github.io/codexflow/zh.html)、[GitHub 仓库](https://github.com/tarunspandit/codexflow) 或 npm 包内附带的文档。
+
+## CodexFlow 是否违反服务条款？
+
+codexflow 使用 ChatGPT 的官方 Developer Mode / MCP App 接入路径，让你自己的 ChatGPT 会话连接到你自己的本地工具。
+
+它不绕过限制，不抓取隐藏接口，不共享账号，不转售模型，不伪造请求来源，也不把第三方模型包装成别的模型。
+
+用户仍然需要遵守 ChatGPT、Codex、OpenAI 和任何第三方服务的条款。
+
+## CodexFlow 生产环境安全吗？
+
+codexflow 是本地开发桥，不是操作系统级沙箱。
+
+只在你信任的仓库里使用。公网 tunnel 保持 token auth 开启。保持 safe bash，除非你明确知道为什么需要 full bash。公网暴露前先读 [SECURITY.md](SECURITY.md)。
+
+## 保存的设置在哪里？
+
+工作区配置保存在：
+
+```text
+~/.codexflow/profiles/
+```
+
+管理命令：
+
+```bash
+codexflow settings
+codexflow settings list
+codexflow settings delete --yes
+```
+
+显示设置时，保存的 token 会被打码。
+
+## CodexFlow 能帮助 ChatGPT 维持上下文吗？
+
+可以帮助，但方式是显式文件和上下文包，不是隐藏记忆。
+
+推荐使用：
+
+- `AGENTS.md` 写项目规则。
+- `.ai-bridge/decisions.md` 写关键决策。
+- `.ai-bridge/current-plan.md` 写当前计划。
+- `.ai-bridge/agent-status.md` 写本地执行结果。
+- `codexflow pro-bundle --copy` 给不能调用工具的模型生成上下文包。
+
+这样 ChatGPT 断线、换模型或换会话后，仍然可以通过文件恢复上下文。

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 CodexFlow contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/NOTICE

@@ -0,0 +1,9 @@
+CodexFlow trademark notice
+
+CodexFlow is an independent open-source project. It is not affiliated with,
+endorsed by, sponsored by, or otherwise officially connected with OpenAI.
+
+Codex, ChatGPT, OpenAI, and related names and marks are the property of their
+respective owner. References in this software and its documentation are used
+only to describe compatibility, interoperability, and the source of optional
+local project metadata.