@adversity/coding-tool-x 2.2.0

package/src/server/services/codex-settings-manager.js

@@ -0,0 +1,397 @@
+const fs = require('fs');
+const path = require('path');
+const os = require('os');
+const toml = require('toml');
+
+// Codex 配置文件路径
+function getConfigPath() {
+  return path.join(os.homedir(), '.codex', 'config.toml');
+}
+
+function getAuthPath() {
+  return path.join(os.homedir(), '.codex', 'auth.json');
+}
+
+// 备份文件路径
+function getConfigBackupPath() {
+  return path.join(os.homedir(), '.codex', 'config.toml.cc-tool-backup');
+}
+
+function getAuthBackupPath() {
+  return path.join(os.homedir(), '.codex', 'auth.json.cc-tool-backup');
+}
+
+// 检查配置文件是否存在
+function configExists() {
+  return fs.existsSync(getConfigPath());
+}
+
+function authExists() {
+  return fs.existsSync(getAuthPath());
+}
+
+// 检查是否已经有备份
+function hasBackup() {
+  return fs.existsSync(getConfigBackupPath()) || fs.existsSync(getAuthBackupPath());
+}
+
+// 读取 config.toml
+function readConfig() {
+  try {
+    const content = fs.readFileSync(getConfigPath(), 'utf8');
+    return toml.parse(content);
+  } catch (err) {
+    throw new Error('Failed to read config.toml: ' + err.message);
+  }
+}
+
+// 将配置对象转换为 TOML 字符串
+function configToToml(config) {
+  let content = `# Codex Configuration
+# Managed by Coding-Tool (Proxy Mode)
+
+`;
+
+  // 写入顶级字段
+  for (const [key, value] of Object.entries(config)) {
+    if (key === 'model_providers') continue; // 稍后处理
+    if (typeof value === 'string') {
+      content += `${key} = "${value}"\n`;
+    } else if (typeof value === 'boolean') {
+      content += `${key} = ${value}\n`;
+    } else if (typeof value === 'number') {
+      content += `${key} = ${value}\n`;
+    }
+  }
+
+  content += '\n';
+
+  // 写入 model_providers
+  if (config.model_providers) {
+    for (const [providerKey, providerConfig] of Object.entries(config.model_providers)) {
+      content += `[model_providers.${providerKey}]\n`;
+      for (const [key, value] of Object.entries(providerConfig)) {
+        if (typeof value === 'string') {
+          content += `${key} = "${value}"\n`;
+        } else if (typeof value === 'boolean') {
+          content += `${key} = ${value}\n`;
+        } else if (typeof value === 'number') {
+          content += `${key} = ${value}\n`;
+        }
+      }
+      content += '\n';
+    }
+  }
+
+  return content;
+}
+
+// 写入 config.toml
+function writeConfig(config) {
+  try {
+    const content = configToToml(config);
+    fs.writeFileSync(getConfigPath(), content, 'utf8');
+  } catch (err) {
+    throw new Error('Failed to write config.toml: ' + err.message);
+  }
+}
+
+// 读取 auth.json
+function readAuth() {
+  try {
+    if (!authExists()) {
+      return {};
+    }
+    const content = fs.readFileSync(getAuthPath(), 'utf8');
+    return JSON.parse(content);
+  } catch (err) {
+    throw new Error('Failed to read auth.json: ' + err.message);
+  }
+}
+
+// 写入 auth.json
+function writeAuth(auth) {
+  try {
+    const content = JSON.stringify(auth, null, 2);
+    fs.writeFileSync(getAuthPath(), content, 'utf8');
+  } catch (err) {
+    throw new Error('Failed to write auth.json: ' + err.message);
+  }
+}
+
+// 备份当前配置
+function backupSettings() {
+  try {
+    if (!configExists()) {
+      throw new Error('config.toml not found');
+    }
+
+    // 如果已经有备份，不覆盖
+    if (hasBackup()) {
+      console.log('Backup already exists, skipping backup');
+      return { success: true, alreadyExists: true };
+    }
+
+    // 备份 config.toml
+    const configContent = fs.readFileSync(getConfigPath(), 'utf8');
+    fs.writeFileSync(getConfigBackupPath(), configContent, 'utf8');
+
+    // 备份 auth.json (如果存在)
+    if (authExists()) {
+      const authContent = fs.readFileSync(getAuthPath(), 'utf8');
+      fs.writeFileSync(getAuthBackupPath(), authContent, 'utf8');
+    }
+
+    console.log('Codex settings backed up');
+    return { success: true, alreadyExists: false };
+  } catch (err) {
+    throw new Error('Failed to backup settings: ' + err.message);
+  }
+}
+
+// 恢复配置
+function restoreSettings() {
+  try {
+    if (!hasBackup()) {
+      throw new Error('No backup found');
+    }
+
+    // 恢复 config.toml
+    if (fs.existsSync(getConfigBackupPath())) {
+      const content = fs.readFileSync(getConfigBackupPath(), 'utf8');
+      fs.writeFileSync(getConfigPath(), content, 'utf8');
+      fs.unlinkSync(getConfigBackupPath());
+    }
+
+    // 恢复 auth.json
+    if (fs.existsSync(getAuthBackupPath())) {
+      const content = fs.readFileSync(getAuthBackupPath(), 'utf8');
+      fs.writeFileSync(getAuthPath(), content, 'utf8');
+      fs.unlinkSync(getAuthBackupPath());
+    }
+
+    // 清理 shell 配置文件中的环境变量（可选，不影响恢复结果）
+    removeEnvFromShell('CC_PROXY_KEY');
+
+    console.log('Codex settings restored from backup');
+    return { success: true };
+  } catch (err) {
+    throw new Error('Failed to restore settings: ' + err.message);
+  }
+}
+
+// 获取用户的 shell 配置文件路径
+function getShellConfigPath() {
+  const shell = process.env.SHELL || '';
+  if (shell.includes('zsh')) {
+    return path.join(os.homedir(), '.zshrc');
+  } else if (shell.includes('bash')) {
+    // macOS 使用 .bash_profile，Linux 使用 .bashrc
+    const bashProfile = path.join(os.homedir(), '.bash_profile');
+    const bashrc = path.join(os.homedir(), '.bashrc');
+    if (fs.existsSync(bashProfile)) {
+      return bashProfile;
+    }
+    return bashrc;
+  }
+  // 默认使用 .zshrc (macOS 默认)
+  return path.join(os.homedir(), '.zshrc');
+}
+
+// 注入环境变量到 shell 配置文件
+function injectEnvToShell(envName, envValue) {
+  const configPath = getShellConfigPath();
+  const exportLine = `export ${envName}="${envValue}"`;
+  // 使用更具体的标记，包含环境变量名，方便后续精确移除
+  const marker = `# Added by Coding-Tool for Codex [${envName}]`;
+
+  try {
+    let content = '';
+    if (fs.existsSync(configPath)) {
+      content = fs.readFileSync(configPath, 'utf8');
+    }
+
+    // 检查是否已经存在这个环境变量配置
+    const regex = new RegExp(`^export ${envName}=`, 'm');
+    const alreadyExists = regex.test(content);
+
+    if (alreadyExists) {
+      // 已存在，替换它（保留原有的标记注释）
+      content = content.replace(
+        new RegExp(`^(# Added by Coding-Tool for Codex \\[${envName}\\]\n)?export ${envName}=.*$`, 'm'),
+        `${marker}\n${exportLine}`
+      );
+    } else {
+      // 不存在，追加到文件末尾
+      content = content.trimEnd() + `\n\n${marker}\n${exportLine}\n`;
+    }
+
+    fs.writeFileSync(configPath, content, 'utf8');
+    return { success: true, path: configPath, isFirstTime: !alreadyExists };
+  } catch (err) {
+    // 不抛出错误，只是警告，因为这不是致命问题
+    console.warn(`[Codex] Failed to inject env to shell config: ${err.message}`);
+    return { success: false, error: err.message, isFirstTime: false };
+  }
+}
+
+// 从 shell 配置文件移除环境变量
+function removeEnvFromShell(envName) {
+  const configPath = getShellConfigPath();
+
+  try {
+    if (!fs.existsSync(configPath)) {
+      return { success: true };
+    }
+
+    let content = fs.readFileSync(configPath, 'utf8');
+
+    // 移除具体标记的环境变量（推荐方式）
+    content = content.replace(
+      new RegExp(`\\n?# Added by Coding-Tool for Codex \\[${envName}\\]\\nexport ${envName}=.*\\n?`, 'g'),
+      '\n'
+    );
+
+    // 如果没有标记，也尝试移除（兼容旧数据）
+    content = content.replace(
+      new RegExp(`^export ${envName}=.*\\n?`, 'gm'),
+      ''
+    );
+
+    // 清理多余的空行
+    content = content.replace(/\n\n\n+/g, '\n\n');
+
+    fs.writeFileSync(configPath, content, 'utf8');
+    return { success: true };
+  } catch (err) {
+    console.warn(`[Codex] Failed to remove env from shell config: ${err.message}`);
+    return { success: false, error: err.message };
+  }
+}
+
+// 设置代理配置
+function setProxyConfig(proxyPort) {
+  try {
+    // 先备份
+    backupSettings();
+
+    // 读取当前配置
+    const config = readConfig();
+
+    // 设置 model_provider 为 proxy
+    config.model_provider = 'cc-proxy';
+
+    // 确保 model_providers 对象存在
+    if (!config.model_providers) {
+      config.model_providers = {};
+    }
+
+    // 添加代理 provider
+    config.model_providers['cc-proxy'] = {
+      name: 'cc-proxy',
+      base_url: `http://127.0.0.1:${proxyPort}/v1`,
+      wire_api: 'responses',
+      env_key: 'CC_PROXY_KEY'
+    };
+
+    // 写入配置
+    writeConfig(config);
+
+    // 写入 auth.json
+    const auth = readAuth();
+    auth.CC_PROXY_KEY = 'PROXY_KEY';
+    writeAuth(auth);
+
+    // 注入环境变量到 shell 配置文件（解决某些系统环境变量优先级问题）
+    const shellInjectResult = injectEnvToShell('CC_PROXY_KEY', 'PROXY_KEY');
+
+    // 获取 shell 配置文件路径用于提示信息
+    const shellConfigPath = getShellConfigPath();
+    const sourceCommand = process.env.SHELL?.includes('zsh') ? 'source ~/.zshrc' : 'source ~/.bashrc';
+
+    console.log(`Codex settings updated to use proxy on port ${proxyPort}`);
+    return {
+      success: true,
+      port: proxyPort,
+      envInjected: shellInjectResult.success,
+      isFirstTime: shellInjectResult.isFirstTime,
+      shellConfigPath: shellConfigPath,
+      sourceCommand: sourceCommand
+    };
+  } catch (err) {
+    throw new Error('Failed to set proxy config: ' + err.message);
+  }
+}
+
+// 检查当前是否是代理配置
+function isProxyConfig() {
+  try {
+    if (!configExists()) {
+      return false;
+    }
+
+    const config = readConfig();
+
+    // 检查是否使用 cc-proxy provider
+    if (config.model_provider === 'cc-proxy') {
+      return true;
+    }
+
+    // 检查当前 provider 的 base_url 是否指向本地代理
+    const currentProvider = config.model_provider;
+    if (currentProvider && config.model_providers && config.model_providers[currentProvider]) {
+      const baseUrl = config.model_providers[currentProvider].base_url || '';
+      if (baseUrl.includes('127.0.0.1') && baseUrl.includes('10089')) {
+        return true;
+      }
+    }
+
+    return false;
+  } catch (err) {
+    return false;
+  }
+}
+
+// 获取当前代理端口（如果是代理配置）
+function getCurrentProxyPort() {
+  try {
+    if (!isProxyConfig()) {
+      return null;
+    }
+
+    const config = readConfig();
+    const proxyProvider = config.model_providers?.['cc-proxy'];
+    if (proxyProvider) {
+      const baseUrl = proxyProvider.base_url || '';
+      const match = baseUrl.match(/:(\d+)/);
+      return match ? parseInt(match[1]) : null;
+    }
+
+    return null;
+  } catch (err) {
+    return null;
+  }
+}
+
+module.exports = {
+  getConfigPath,
+  getAuthPath,
+  getConfigBackupPath,
+  getAuthBackupPath,
+  configExists,
+  authExists,
+  hasBackup,
+  readConfig,
+  writeConfig,
+  readAuth,
+  writeAuth,
+  backupSettings,
+  restoreSettings,
+  setProxyConfig,
+  isProxyConfig,
+  getCurrentProxyPort,
+  // 导出环境变量注入函数供其他模块使用
+  getShellConfigPath,
+  injectEnvToShell,
+  removeEnvFromShell
+};

package/src/server/services/codex-speed-test-template.json

@@ -0,0 +1,24 @@
+{
+	"model": "gpt-5-codex",
+	"instructions": "You are Codex, based on GPT-5. You are running as a coding agent in the Codex CLI on a user's computer.\n\n## General\n\n- The arguments to `shell` will be passed to execvp(). Most terminal commands should be prefixed with [\"bash\", \"-lc\"].\n- Always set the `workdir` param when using the shell function. Do not use `cd` unless absolutely necessary.\n- When searching for text or files, prefer using `rg` or `rg --files` respectively because `rg` is much faster than alternatives like `grep`. (If the `rg` command is not found, then use alternatives.)\n\n## Editing constraints\n\n- Default to ASCII when editing or creating files. Only introduce non-ASCII or other Unicode characters when there is a clear justification and the file already uses them.\n- Add succinct code comments that explain what is going on if code is not self-explanatory. You should not add comments like \"Assigns the value to the variable\", but a brief comment might be useful ahead of a complex code block that the user would otherwise have to spend time parsing out. Usage of these comments should be rare.\n- Try to use apply_patch for single file edits, but it is fine to explore other options to make the edit if it does not work well. Do not use apply_patch for changes that are auto-generated (i.e. generating package.json or running a lint or format command like gofmt) or when scripting is more efficient (such as search and replacing a string across a codebase).\n- You may be in a dirty git worktree.\n    * NEVER revert existing changes you did not make unless explicitly requested, since these changes were made by the user.\n    * If asked to make a commit or code edits and there are unrelated changes to your work or changes that you didn't make in those files, don't revert those changes.\n    * If the changes are in files you've touched recently, you should read carefully and understand how you can work with the changes rather than reverting them.\n    * If the changes are in unrelated files, just ignore them and don't revert them.\n- While you are working, you might notice unexpected changes that you didn't make. If this happens, STOP IMMEDIATELY and ask the user how they would like to proceed.\n- **NEVER** use destructive commands like `git reset --hard` or `git checkout --` unless specifically requested or approved by the user.\n\n## Plan tool\n\nWhen using the planning tool:\n- Skip using the planning tool for straightforward tasks (roughly the easiest 25%).\n- Do not make single-step plans.\n- When you made a plan, update it after having performed one of the sub-tasks that you shared on the plan.\n\n## Codex CLI harness, sandboxing, and approvals\n\nThe Codex CLI harness supports several different configurations for sandboxing and escalation approvals that the user can choose from.\n\nFilesystem sandboxing defines which files can be read or written. The options for `sandbox_mode` are:\n- **read-only**: The sandbox only permits reading files.\n- **workspace-write**: The sandbox permits reading files, and editing files in `cwd` and `writable_roots`. Editing files in other directories requires approval.\n- **danger-full-access**: No filesystem sandboxing - all commands are permitted.\n\nNetwork sandboxing defines whether network can be accessed without approval. Options for `network_access` are:\n- **restricted**: Requires approval\n- **enabled**: No approval needed\n\nApprovals are your mechanism to get user consent to run shell commands without the sandbox. Possible configuration options for `approval_policy` are\n- **untrusted**: The harness will escalate most commands for user approval, apart from a limited allowlist of safe \"read\" commands.\n- **on-failure**: The harness will allow all commands to run in the sandbox (if enabled), and failures will be escalated to the user for approval to run again without the sandbox.\n- **on-request**: Commands will be run in the sandbox by default, and you can specify in your tool call if you want to escalate a command to run without sandboxing. (Note that this mode is not always available. If it is, you'll see parameters for it in the `shell` command description.)\n- **never**: This is a non-interactive mode where you may NEVER ask the user for approval to run commands. Instead, you must always persist and work around constraints to solve the task for the user. You MUST do your utmost best to finish the task and validate your work before yielding. If this mode is paired with `danger-full-access`, take advantage of it to deliver the best outcome for the user. Further, in this mode, your default testing philosophy is overridden: Even if you don't see local patterns for testing, you may add tests and scripts to validate your work. Just remove them before yielding.\n\nWhen you are running with `approval_policy == on-request`, and sandboxing enabled, here are scenarios where you'll need to request approval:\n- You need to run a command that writes to a directory that requires it (e.g. running tests that write to /var)\n- You need to run a GUI app (e.g., open/xdg-open/osascript) to open browsers or files.\n- You are running sandboxed and need to run a command that requires network access (e.g. installing packages)\n- If you run a command that is important to solving the user's query, but it fails because of sandboxing, rerun the command with approval. ALWAYS proceed to use the `with_escalated_permissions` and `justification` parameters - do not message the user before requesting approval for the command.\n- You are about to take a potentially destructive action such as an `rm` or `git reset` that the user did not explicitly ask for\n- (for all of these, you should weigh alternative paths that do not require approval)\n\nWhen `sandbox_mode` is set to read-only, you'll need to request approval for any command that isn't a read.\n\nYou will be told what filesystem sandboxing, network sandboxing, and approval mode are active in a developer or user message. If you are not told about this, assume that you are running with workspace-write, network sandboxing enabled, and approval on-failure.\n\nAlthough they introduce friction to the user because your work is paused until the user responds, you should leverage them when necessary to accomplish important work. If the completing the task requires escalated permissions, Do not let these settings or the sandbox deter you from attempting to accomplish the user's task unless it is set to \"never\", in which case never ask for approvals.\n\nWhen requesting approval to execute a command that will require escalated privileges:\n  - Provide the `with_escalated_permissions` parameter with the boolean value true\n  - Include a short, 1 sentence explanation for why you need to enable `with_escalated_permissions` in the justification parameter\n\n## Special user requests\n\n- If the user makes a simple request (such as asking for the time) which you can fulfill by running a terminal command (such as `date`), you should do so.\n- If the user asks for a \"review\", default to a code review mindset: prioritise identifying bugs, risks, behavioural regressions, and missing tests. Findings must be the primary focus of the response - keep summaries or overviews brief and only after enumerating the issues. Present findings first (ordered by severity with file/line references), follow with open questions or assumptions, and offer a change-summary only as a secondary detail. If no findings are discovered, state that explicitly and mention any residual risks or testing gaps.\n\n## Presenting your work and final message\n\nYou are producing plain text that will later be styled by the CLI. Follow these rules exactly. Formatting should make results easy to scan, but not feel mechanical. Use judgment to decide how much structure adds value.\n\n- Default: be very concise; friendly coding teammate tone.\n- Ask only when needed; suggest ideas; mirror the user's style.\n- For substantial work, summarize clearly; follow final‑answer formatting.\n- Skip heavy formatting for simple confirmations.\n- Don't dump large files you've written; reference paths only.\n- No \"save/copy this file\" - User is on the same machine.\n- Offer logical next steps (tests, commits, build) briefly; add verify steps if you couldn't do something.\n- For code changes:\n  * Lead with a quick explanation of the change, and then give more details on the context covering where and why a change was made. Do not start this explanation with \"summary\", just jump right in.\n  * If there are natural next steps the user may want to take, suggest them at the end of your response. Do not make suggestions if there are no natural next steps.\n  * When suggesting multiple options, use numeric lists for the suggestions so the user can quickly respond with a single number.\n- The user does not command execution outputs. When asked to show the output of a command (e.g. `git show`), relay the important details in your answer or summarize the key lines so the user understands the result.\n\n### Final answer structure and style guidelines\n\n- Plain text; CLI handles styling. Use structure only when it helps scanability.\n- Headers: optional; short Title Case (1-3 words) wrapped in **…**; no blank line before the first bullet; add only if they truly help.\n- Bullets: use - ; merge related points; keep to one line when possible; 4–6 per list ordered by importance; keep phrasing consistent.\n- Monospace: backticks for commands/paths/env vars/code ids and inline examples; use for literal keyword bullets; never combine with **.\n- Code samples or multi-line snippets should be wrapped in fenced code blocks; include an info string as often as possible.\n- Structure: group related bullets; order sections general → specific → supporting; for subsections, start with a bolded keyword bullet, then items; match complexity to the task.\n- Tone: collaborative, concise, factual; present tense, active voice; self‑contained; no \"above/below\"; parallel wording.\n- Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short—wrap/reformat if long; avoid naming formatting styles in answers.\n- Adaptation: code explanations → precise, structured with code refs; simple tasks → lead with outcome; big changes → logical walkthrough + rationale + next actions; casual one-offs → plain sentences, no headers/bullets.\n- File References: When referencing files in your response, make sure to include the relevant start line and always follow the below rules:\n  * Use inline code to make file paths clickable.\n  * Each reference should have a stand alone path. Even if it's the same file.\n  * Accepted: absolute, workspace‑relative, a/ or b/ diff prefixes, or bare filename/suffix.\n  * Line/column (1‑based, optional): :line[:column] or #Lline[Ccolumn] (column defaults to 1).\n  * Do not use URIs like file://, vscode://, or https://.\n  * Do not provide range of lines\n  * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\\repo\\project\\main.rs:12:5\n",
+	"input": [
+        {"role": "system", "content": "You are a echo bot. Always say 'pong'."},
+        {
+		"type": "message",
+		"role": "user",
+		"content": [{
+			"type": "input_text",
+			"text": "ping"
+		}]
+	}],
+	"tools": [],
+	"tool_choice": "auto",
+	"parallel_tool_calls": false,
+	"reasoning": {
+		"effort": "low",
+		"summary": "auto"
+	},
+	"store": false,
+	"stream": true,
+	"prompt_cache_key": "019aa041-db00-7df0-af17-f34c7695d024"
+}

package/src/server/services/codex-statistics-service.js

@@ -0,0 +1,255 @@
+const fs = require('fs');
+const path = require('path');
+const os = require('os');
+
+/**
+ * Codex 统计服务 - 数据采集和存储
+ *
+ * 文件结构：
+ * ~/.claude/cc-tool/
+ *   ├── codex-statistics.json         # Codex 总体统计
+ *   └── codex-daily-stats/
+ *       ├── 2025-12-05.json           # 每日汇总统计
+ *       └── ...
+ */
+
+// 获取基础目录
+function getBaseDir() {
+  const dir = path.join(os.homedir(), '.claude', 'cc-tool');
+  if (!fs.existsSync(dir)) {
+    fs.mkdirSync(dir, { recursive: true });
+  }
+  return dir;
+}
+
+// 获取每日统计目录
+function getDailyStatsDir() {
+  const dir = path.join(getBaseDir(), 'codex-daily-stats');
+  if (!fs.existsSync(dir)) {
+    fs.mkdirSync(dir, { recursive: true });
+  }
+  return dir;
+}
+
+// 获取统计文件路径
+function getStatisticsFilePath() {
+  return path.join(getBaseDir(), 'codex-statistics.json');
+}
+
+// 获取每日统计文件路径
+function getDailyStatsFilePath(date) {
+  return path.join(getDailyStatsDir(), `${date}.json`);
+}
+
+// 初始化统计对象
+function initStatsObject() {
+  return {
+    requests: 0,
+    tokens: {
+      input: 0,
+      output: 0,
+      reasoning: 0,
+      cached: 0,
+      total: 0
+    },
+    cost: 0
+  };
+}
+
+// 加载总体统计
+function loadStatistics() {
+  const filePath = getStatisticsFilePath();
+  try {
+    if (fs.existsSync(filePath)) {
+      const data = fs.readFileSync(filePath, 'utf8');
+      return JSON.parse(data);
+    }
+  } catch (err) {
+    console.error('[Codex Statistics] Failed to load statistics:', err);
+  }
+
+  return {
+    version: '1.0',
+    lastUpdated: new Date().toISOString(),
+    global: {
+      totalRequests: 0,
+      totalTokens: 0,
+      totalCost: 0
+    },
+    byChannel: {},
+    byModel: {}
+  };
+}
+
+// 保存总体统计
+function saveStatistics(stats) {
+  const filePath = getStatisticsFilePath();
+  stats.lastUpdated = new Date().toISOString();
+
+  try {
+    fs.writeFileSync(filePath, JSON.stringify(stats, null, 2), 'utf8');
+  } catch (err) {
+    console.error('[Codex Statistics] Failed to save statistics:', err);
+  }
+}
+
+// 加载每日统计
+function loadDailyStats(date) {
+  const filePath = getDailyStatsFilePath(date);
+  try {
+    if (fs.existsSync(filePath)) {
+      const data = fs.readFileSync(filePath, 'utf8');
+      return JSON.parse(data);
+    }
+  } catch (err) {
+    console.error('[Codex Statistics] Failed to load daily stats:', err);
+  }
+
+  return {
+    date: date,
+    summary: {
+      requests: 0,
+      tokens: 0,
+      cost: 0
+    },
+    byChannel: {},
+    byModel: {}
+  };
+}
+
+// 保存每日统计
+function saveDailyStats(date, stats) {
+  const filePath = getDailyStatsFilePath(date);
+
+  try {
+    fs.writeFileSync(filePath, JSON.stringify(stats, null, 2), 'utf8');
+  } catch (err) {
+    console.error('[Codex Statistics] Failed to save daily stats:', err);
+  }
+}
+
+// 更新统计数据
+function updateStats(stats, tokens, cost) {
+  stats.requests += 1;
+  if (stats.tokens) {
+    stats.tokens.input += tokens.input || 0;
+    stats.tokens.output += tokens.output || 0;
+    stats.tokens.reasoning += tokens.reasoning || 0;
+    stats.tokens.cached += tokens.cached || 0;
+    stats.tokens.total += tokens.total || 0;
+  }
+  stats.cost += cost || 0;
+}
+
+/**
+ * 记录一次请求
+ * @param {Object} requestData - 请求数据
+ */
+function recordRequest(requestData) {
+  try {
+    const {
+      timestamp = new Date().toISOString(),
+      channel,
+      channelId,
+      model,
+      tokens = {},
+      cost = 0
+    } = requestData;
+
+    // 计算 total tokens
+    const totalTokens = (tokens.input || 0) + (tokens.output || 0) + (tokens.reasoning || 0);
+    tokens.total = totalTokens;
+
+    // 1. 更新总体统计
+    const globalStats = loadStatistics();
+
+    globalStats.global.totalRequests += 1;
+    globalStats.global.totalTokens += totalTokens;
+    globalStats.global.totalCost += cost || 0;
+
+    // 按渠道统计
+    if (channelId) {
+      if (!globalStats.byChannel[channelId]) {
+        globalStats.byChannel[channelId] = {
+          name: channel || channelId,
+          ...initStatsObject(),
+          firstUsed: timestamp,
+          lastUsed: timestamp
+        };
+      }
+      updateStats(globalStats.byChannel[channelId], tokens, cost);
+      globalStats.byChannel[channelId].lastUsed = timestamp;
+    }
+
+    // 按模型统计
+    if (model) {
+      if (!globalStats.byModel[model]) {
+        globalStats.byModel[model] = initStatsObject();
+      }
+      updateStats(globalStats.byModel[model], tokens, cost);
+    }
+
+    saveStatistics(globalStats);
+
+    // 2. 更新每日统计
+    const date = new Date(timestamp).toISOString().split('T')[0];
+    const dailyStats = loadDailyStats(date);
+
+    dailyStats.summary.requests += 1;
+    dailyStats.summary.tokens += totalTokens;
+    dailyStats.summary.cost += cost || 0;
+
+    // 每日 - 按渠道统计
+    if (channelId) {
+      if (!dailyStats.byChannel[channelId]) {
+        dailyStats.byChannel[channelId] = {
+          name: channel || channelId,
+          ...initStatsObject()
+        };
+      }
+      updateStats(dailyStats.byChannel[channelId], tokens, cost);
+    }
+
+    // 每日 - 按模型统计
+    if (model) {
+      if (!dailyStats.byModel[model]) {
+        dailyStats.byModel[model] = initStatsObject();
+      }
+      updateStats(dailyStats.byModel[model], tokens, cost);
+    }
+
+    saveDailyStats(date, dailyStats);
+
+  } catch (err) {
+    console.error('[Codex Statistics] Failed to record request:', err);
+  }
+}
+
+/**
+ * 获取总体统计
+ */
+function getStatistics() {
+  return loadStatistics();
+}
+
+/**
+ * 获取每日统计
+ */
+function getDailyStatistics(date) {
+  return loadDailyStats(date);
+}
+
+/**
+ * 获取今日统计
+ */
+function getTodayStatistics() {
+  const today = new Date().toISOString().split('T')[0];
+  return loadDailyStats(today);
+}
+
+module.exports = {
+  recordRequest,
+  getStatistics,
+  getDailyStatistics,
+  getTodayStatistics
+};