컨텍스트 드리프트를 감지하고, 파일 중복 읽기를 방지하며, 토큰 분석 보고서를 제공하여 Claude Code의 컨텍스트를 깨끗하게 유지합니다.
다른 이름 Anuj7411/sipcode
- 스타
- 46
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 1.7.1
- 마지막 커밋
- 2026년 10월 16일
- 라이선스
- MIT
Sipcode MCP란?
Sipcode은(는) MCP server입니다. 컨텍스트 드리프트를 감지하고, 파일 중복 읽기를 방지하며, 토큰 분석 보고서를 제공하여 Claude Code의 컨텍스트를 깨끗하게 유지합니다.
프로젝트 README에서 생성된 요약
Sipcode MCP server 정보
Sipcode는 컨텍스트 부패를 자동으로 감지하고 파일 중복 읽기를 방지하여 Claude Code의 컨텍스트 창을 깨끗하게 유지할 수 있도록 돕습니다. 이 CLI 도구는 개발자와 AI 에이전트 사이의 계층 역할을 수행하며, 토큰 낭비를 줄이고 답변 품질을 향상시킵니다. Claude Code 또는 OpenAI Codex를 사용하면서 비용과 컨텍스트 상태를 로컬에서 관리하고자 하는 개발자를 위해 설계되었습니다.
사용자는 npm을 통해 도구를 설치하며, drift, proxy, benchmark와 같은 특정 명령어를 사용하여 세션을 관리할 수 있습니다. 서버는 일반적인 사용 중에 네트워크 호출을 전혀 하지 않으므로 데이터가 로컬 머신에 안전하게 유지됩니다. 또한 today 및 forecast와 같은 도구를 통해 토큰 사용량과 예상 비용을 추적하는 상세한 분석 기능을 제공합니다. Codex 사용자의 경우, 로컬 세션 로그를 읽어 비용 분석 및 사용량 제한 모니터링 기능을 특화하여 제공합니다.
활용 사례
- 1컨텍스트 상태 모니터링현재 AI 세션이 비대해지고 있는지 또는 평소 사용 패턴에서 벗어나고 있는지 확인합니다.
- 2토큰 비용 절감파일 중복 읽기를 식별하고 방지하여 모델로 전송되는 토큰 수를 줄입니다.
- 3지출 및 예측 추적토큰 사용량의 일일 요약을 확인하고 월말 예상 비용을 파악합니다.
- 4Codex 사용량 제한 관리OpenAI Codex 플랜의 잔여량을 분석하고 제한에 도달할 시점을 예측합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Sipcode MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Sipcode MCP 설치
$ claude mcp add sipcode -- npx -y sipcodeCursor에 Sipcode MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"sipcode": {
"command": "npx",
"args": [
"-y",
"sipcode"
]
}
}
}VS Code에 Sipcode MCP 설치
.vscode/mcp.json
{
"servers": {
"sipcode": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sipcode"
]
}
}
}VS Code CLI에 Sipcode MCP 설치
$ code --add-mcp '{"name":"sipcode","type":"stdio","command":"npx","args":["-y","sipcode"]}'Claude Desktop에 Sipcode MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"sipcode": {
"command": "npx",
"args": [
"-y",
"sipcode"
]
}
}
}Codex에 Sipcode MCP 설치
$ codex mcp add sipcode -- npx -y sipcodeCodex config.toml에 Sipcode MCP 설치
~/.codex/config.toml
[mcp_servers.sipcode] command = "npx" args = ["-y", "sipcode"]
Gemini CLI에 Sipcode MCP 설치
$ gemini mcp add -s user sipcode npx -- -y sipcodeGemini settings.json에 Sipcode MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"sipcode": {
"command": "npx",
"args": [
"-y",
"sipcode"
]
}
}
}자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
GitHub에서 보기Install in 30 seconds
npm i -g sipcode
sipcode init
That is it. Your next Claude Code session will use Sipcode automatically. Verify a few minutes later:
sipcode drift
If the output reads no drift, context health stable, Sipcode is doing its job.
Already installed? Keep it fresh. Sipcode makes zero network calls, so it can't pop an "update available" notice. Build a weekly habit: run
sipcode update(ornpm i -g sipcode@latest) to pull the latest fixes. Full details in Updating Sipcode.
What is Sipcode?
Sipcode is a free command-line tool that sits between you and Claude Code. It does three things:
- It watches Claude Code's context window and warns you when it starts to bloat (we call this "context rot")
- It catches duplicate file reads and other waste before they reach Claude, so you pay less for the same answers
- It gives you receipts. Every saving is measurable in your terminal.
It is open source under the MIT license. It makes zero network calls during normal use. Your data never leaves your laptop.
How Sipcode compares
| Sipcode | Tool A | Tool B | Tool C | |
|---|---|---|---|---|
| Approach | Live PreToolUse hook | Cross-session memory store | Static methodology | RAG retrieval server |
| Caps verbose tool output | ✓ | ✗ | docs only | ✗ |
| Dedups same-session re-reads | ✓ | ✗ | docs only | ✗ |
| Mid-session install support | ✓ Verified Warm-Fill | n/a | n/a | n/a |
| Zero false-dedup by construction | ✓ | n/a | n/a | n/a |
| Reproducible benchmark on locked corpus | ✓ 62.6% median (20 synthetic tasks) | ✗ | ✗ | ✗ |
| Self-introspection MCP tools | ✓ 16 tools | ✗ | ✗ | partial |
| Agents covered | Claude Code (all features); OpenAI Codex (spend analytics and usage limits, no hook) | not compared | not compared | not compared |
| Zero network calls in normal use | ✓ | ✓ | n/a | ✗ |
| MIT licensed | ✓ | ✓ | ✓ | ✓ |
Sipcode is complementary to memory tools that persist context across sessions (Tool A in the table). Sipcode keeps each individual session clean. They solve different problems. Run both for maximum effect.
Full feature-by-feature comparison with tool names revealed: anuj7411.github.io/sipcode/compare
Why you probably want it
If you use Claude Code for real work, you have already felt this:
- Long sessions get expensive fast. A two-hour session on Claude Max can burn through your daily plan
- Quality drops as the context window fills. Claude starts re-reading files, repeating itself, losing the thread of what you asked
- You cannot tell what is bloat and what is signal
Sipcode measures the bloat, then removes the parts Claude does not need. Run sipcode benchmark on any machine and you will see the same 62.6% median reduction on the locked 20-task corpus. That corpus is synthetic: scripted pairs of Claude Code transcripts (without and with Sipcode), not recordings of live sessions. It shows what Sipcode's mechanisms remove from a modeled session. Your own number depends on your workload, and sipcode impact measures it on your real sessions.
The two-minute tour
After installing, here are the five commands that show you what Sipcode is doing.
1. sipcode drift
Tells you if your current Claude Code session is drifting from your normal usage pattern. Bloated context, repeated reads, stale signals are all flagged here.
✓ Sipcode drift: no drift, context health stable vs your recent baseline.
By default it checks your most recent session, across Claude Code and Codex. --session <id> checks a specific one, --here limits it to sessions from the folder you are in, and --agent claude-code or --agent codex picks the tool.
2. sipcode proxy --stats
Shows what Sipcode caught in the current session, broken down by rewriter.
Sipcode proxy, rewrite stats
total rewrites: 144
est. tokens saved: ~288,685 (heuristic)
signal kept: 67% (med), weighted across all rewrites
3. sipcode benchmark
Runs the locked 20-task corpus and produces a reproducible savings number. Anyone, anywhere can run this and get 62.6%. The transcripts are scripted, not recorded from live sessions, so read it as a model of Sipcode's mechanisms rather than a measured bill (see METHODOLOGY).
62.6% median savings on a locked 20-task corpus
range 37.4% to 80.6% 3,567,170 tokens $22.48
4. sipcode today
Daily spend summary. Tokens used, sessions, output ratio, comparison to your 30-day median.
spend so far $1.20 across 4 sessions
tokens so far 943.8K output ratio 3.7%
5. sipcode forecast
Month-end projection based on your last 14 days.
projected month-end $17,674 (range $14,139 to $21,208)
Codex
Sipcode also reads OpenAI Codex CLI session logs (~/.codex/sessions and ~/.codex/archived_sessions, or the folder CODEX_HOME points to). For Codex this is spend analytics and usage limits: Sipcode reports what your Codex sessions used, where the tokens went, and how close you are to your plan's limits. It does not change what Codex does.
Commands that read Codex: stats, today, forecast, trend, impact, why, receipt, drift, regress and limits (Codex only), plus the session tools in the MCP server (they take an optional agent input: "claude-code" or "codex") and get_codex_limits.
-
--agent codexshows Codex only.--agent claude-codeshows Claude Code only. -
With no
--agentflag and both tools installed,stats,today,forecast,trendandimpactprint one section per tool.stats,todayandforecastend with one combined line, in this shape:Both tools: <total tokens> tokens · ~$<Claude Code> + ~$<Codex> -
why,receiptanddriftreport on the most recent session across both tools. When the other tool has a recent session too, a one-line hint names it and the flag that shows it. -
--hereworks for Codex too: it matches the working folder Codex recorded for each session. -
--jsoncovers one tool per call. Without--agentit covers Claude Code and prints a note on stderr when Codex logs exist too. Add--agent codexfor Codex JSON. -
With no
--agentflag on a machine with Cursor and Codex, Sipcode shows Codex (it does not read Cursor's session logs).
How Codex tokens are counted. Sipcode reads Codex's per-request usage records, or, in logs from older Codex versions, the change in the running total Codex logs after each request. Cached input is part of Codex's input count, so Sipcode never bills cached tokens twice. A request copied into a resumed or forked session file is counted once. On the maintainer's machine, Sipcode's per-file totals equal Codex's own final total_token_usage on all 15 real session logs, and an independent counter that shares no code with Sipcode (scripts/verify-counts.mjs) cross-checks every period command against the same logs.
Prices. Codex models are priced from OpenAI's API price table (developers.openai.com/api/docs/pricing, and each Codex model's page under developers.openai.com/api/docs/models, as of 2026-10-09), including the long-context rate for prompts over 272,000 input tokens. A model with no known price is shown as unpriced: its tokens are still counted, a line under the cost says how many were left out of it, and it is never shown as $0.
Not supported for Codex yet: writing rules to AGENTS.md (rules, and the rules step of init), registering the MCP server in Codex, the proxy and hooks (proxy, hygiene), estimate and benchmark. rules --agent codex and estimate --agent codex stop with error E009 instead of showing Claude Code data.
Compressed Codex logs. Codex compresses older session logs to .jsonl.zst. Sipcode reads them exactly like plain logs on Node.js 22.15 or newer. On an older Node.js it skips them, and every report starts with a warning that says how many it could not read and that reading them needs Node.js 22.15 or newer. A damaged or unreadable log gets the same kind of warning. With --json the warning is a note on stderr and the JSON is unchanged.
Codex limits: sipcode limits
Codex writes your plan's usage-limit readings into its own logs after each request. sipcode limits reads them, with zero network calls, and answers three questions: when will I hit my limit, what used it, and did it shrink.
Example output of sipcode limits --since all (the tokens-per-1% history here goes back further than the default 90 days):
sipcode limits · Codex · plan: go · as of 2h ago (your last Codex request)
Weekly limit 62% used resets Wed 14 Oct 14:00 at this pace: runs out Tue 13 Oct ~18:00
30-day limit 22% used resets Mon 2 Nov at this pace: lasts until reset
What used your weekly limit (since Wed 7 Oct)
0199a1b2-c3d4-7a11 sipcode 31% 3.1M tokens
0199a0f7-11aa-7b02 my-app 17% 1.4M tokens
codex-auto-review (9 requests) 6%
unattributed (no Codex requests on this computer) 8%
Tokens per 1% of your weekly limit (gpt-5.4)
Mar 28: 425K Apr 1: 357K Apr 13: 77K
Possible limit cut around Apr 13: 5.1x fewer tokens per 1%.
Limits cover your whole account. Codex use on other devices or in the cloud
is not in these logs and can look like a cut.
- Every limit window the logs report (5-hour, weekly, 30-day): percent used, reset time, and when it runs out at this pace. The pace is the percent used divided by the time since the period started, counted up to now, so the estimate moves later while you are not using Codex. "as of" is your last Codex request: the percent is only as fresh as that.
- What used it: the current period's top 5 sessions and projects (folder name only), plus Codex's automatic reviews as one line. Each rise in the percent is shared by the requests made since the previous rise, in proportion to their tokens. A rise with no request on this computer shows as
unattributed, because limits are shared with your other devices and Codex cloud. - Did it shrink: how many tokens 1% of the limit bought in each finished period with at least 20% used, compared only within one model (a period counts when 90% or more of its tokens came from one model). Periods that started on the same day also show their start time (
Jul 5 16:39).Possible limit cutappears when a period bought at most half the median of at least two earlier periods. It always says "possible": Codex use on another device raises the percent without local tokens. - Options:
--json;--since <window>(default90d), how far back the tokens-per-1% history goes;--herenarrows only the "what used it" list to sessions from the current folder (limits are account-wide). sipcode todayadds one line for the Codex limit closest to running out, when Codex has logged limit readings.today --jsonis unchanged.- MCP:
get_codex_limits(optionalsince) returns the same JSON assipcode limits --json. - Claude Code's logs do not record limits, so
limits --agent claude-codestops with error E009.
Did it get worse after an update? sipcode regress
sipcode regress checks your own Claude Code and Codex logs for regressions that arrive with an update, and names the version that brought each one. Each version is compared with your other versions, so no outside baseline is needed, and nothing leaves your machine.
Example output (one machine's logs; your numbers will differ):
sipcode regress · local only, no network
Claude Code: 27,671 interactive requests in 42 sessions (710 subagent and Agent SDK requests left out of the comparison), 2026-05-04 to 2026-10-12, versions 2.1.121 to 2.1.295
Known-regression windows your logs cover: R1, R4, R5
Codex: 930 requests in 15 sessions, 2026-03-28 to 2026-10-08, versions 0.118.0 to 0.162.0, 3 version/model groups with enough limit data
No regressions detected in your logs.
| Check | What it looks for | Confirmed regression it catches |
|---|---|---|
warm-cache-miss |
back-to-back requests (under 5 minutes apart) that re-write most of the context | R2: --resume prompt-cache miss (2.1.69 to 2.1.89) |
post-idle-cold |
the cache staying cold for the next requests after a break of an hour or more | R3: thinking history cleared after an idle hour (2.1.85 to 2.1.100) |
ttl-5m |
main-conversation cache written with the 5-minute TTL instead of 1 hour | R4: 1-hour cache TTL downgraded to 5 minutes (fixed in 2.1.129) |
uncached-input |
large uncached input on requests right after a tool result | R1: Fable 5.1 tool context re-sent uncached (2.1.257 to 2.1.259) |
hourly-rebuild |
the whole prompt cache rebuilt about every hour | R5: OAuth refresh rebuilt the cache hourly (fixed in 2.1.248) |
codex-limit-burn |
a Codex version using more of your limit per token than your other versions on the same plan and window | none in the catalog |
- A finding outside the known catalog is a signal worth reporting, not proof of a bug. A Codex finding could also be a limit change on your plan at the same time, and Codex on your other devices or in the cloud shares the same limit.
- Subagent and Agent SDK requests are left out: their cache policy differs by design.
--bug-reportadds a block to paste into a GitHub issue: token counts, versions, dates and short session ids only. Review it before posting.--jsonfor scripts,--agent claude-codeor--agent codexfor one tool,--min-n <n>for the minimum requests per version a check needs (default 20).- If no logs can be read (for example a sandbox blocks the folders), it prints "Nothing to analyse ... This is NOT a clean result." and exits with code 2. With too little data it says "Not enough data to compare versions yet". When one tool was compared and the other was read but had too little data, it names that tool ("Not enough data to compare Codex versions yet"), so a missing finding for it is not a clean result.
- An independent counter that shares no code with Sipcode (
scripts/verify-counts.mjs) recomputes the coverage, every check's table and the findings ofregress --jsonfrom the same logs.
Use Sipcode inside Codex
The Sipcode plugin lets you ask Codex about your own usage in plain words, in the ChatGPT desktop app or in the Codex CLI. Each answer comes from the sipcode command on your computer, reading your local logs.
Step 1. Install Sipcode once (Node.js 20 or newer), in a terminal:
npm i -g sipcode
The plugin runs this installed sipcode. It does not use npx, because Codex's sandbox usually blocks downloads.
Step 2. Add the plugin. Follow the path that matches how you use Codex.
If you use Codex only in the ChatGPT desktop app (typing codex in a terminal says it is not recognized):
-
Open a terminal (PowerShell on Windows, Terminal on macOS) and run these two commands:
npx -y @openai/codex plugin marketplace add Anuj7411/sipcode npx -y @openai/codex plugin add sipcode@sipcodenpxruns OpenAI's Codex CLI (npm package@openai/codex) without installing it; the first run downloads it, which can take a minute. The first command adds this repository as a plugin marketplace namedsipcode, the second installs the Sipcode plugin from it. Both write to~/.codex, the folder the desktop app reads its plugins from. -
Quit the ChatGPT desktop app completely and open it again.
-
Open Plugins and check that Sipcode is there (pick the
sipcodemarketplace as the source if the list does not show it). If it is not marked as installed, install it from there. -
Start a new chat.
OpenAI's docs do not describe a button in the desktop app for adding a marketplace from GitHub on a personal account, which is why this path uses the CLI command once. You do not need to keep the CLI installed.
If you have the Codex CLI (codex --version works):
- Run
codex plugin marketplace add Anuj7411/sipcode. - Run
codex plugin add sipcode@sipcode, or open/pluginsin Codex, choose thesipcodemarketplace and install Sipcode. - Start a new Codex session. If you also use the desktop app, quit and reopen it.
Step 3. Ask:
| Ask | Sipcode runs |
|---|---|
| "How much did I spend on Codex this month?" | sipcode forecast --agent codex --json (also today and stats) |
| "How close am I to my Codex limit? Did it shrink?" | sipcode limits (its terminal output, for local times) |
| "Why was my last Codex session so expensive?" | sipcode why --agent codex --json |
| "Did Codex or Claude Code get worse after an update?" | sipcode regress --bug-report |
- If Codex's sandbox blocks
~/.codexor~/.claude, the plugin asks for permission to run the command with read access instead of reporting an empty result. - Dollar figures are at API prices; on a ChatGPT plan you are not billed per token.
- Answers show numbers the way the
sipcodeterminal output does: dollars to the cent, whole percents, and times in your local time zone, never raw JSON values. - The plugin is instructions only (four skills): no hooks, no MCP server, no network calls.
- Ask in a new, short chat. Codex re-sends the whole conversation with every request, so the same question asked at the end of a long work chat uses far more of your limit than in a fresh one. Each answer runs one Sipcode command, with no extra checks first.
- To update the plugin later, run
npx -y @openai/codex plugin marketplace upgrade sipcode(orcodex plugin marketplace upgrade sipcode), then restart the desktop app and start a new chat (a chat keeps the skill instructions it started with). Update thesipcodecommand itself withnpm i -g sipcode@latest.
How to install (more detail)
Sipcode works on Mac, Linux, and Windows. You need Node.js 20 or newer, and Node.js 22.15 or newer to read the session logs Codex compresses (.jsonl.zst).
Step 1. Install Node.js
Skip this step if you already have Node.js. Otherwise:
- Mac:
brew install node - Linux: open nodejs.org/en/download, choose the LTS version, Linux and nvm, and run the commands shown there. (The
nodejspackage in Ubuntu's and Debian's own repositories is often older than Node 20.) - Windows: Download from nodejs.org
Verify it worked:
node --version
You should see v20.0.0 or higher.
Step 2. Install Sipcode globally
npm i -g sipcode
This downloads Sipcode from npm and makes the sipcode command available everywhere.
If you see permission errors on Mac or Linux, try:
sudo npm i -g sipcode
Verify it installed:
sipcode --version
You should see 1.7.2 or higher.
Step 3. Run sipcode init to wire it into Claude Code
sipcode init
This command does four things:
- Creates a small
.sipcode/manifest.mdfile in your current project so Claude knows what your project is about - Adds a small block to your
CLAUDE.md(or creates one) with rules that keep Claude's replies terse - Installs the Sipcode hook into Claude Code, which is the thing that actually saves tokens
- Marks the date so
sipcode impactcan show you before-and-after savings later
You will see a checklist as it runs. Each step shows a checkmark when it completes.
The two questions it asks (and what to pick):
1. Manifest budget. How lean to keep the project summary Sipcode injects.
- tighten (recommended): auto-trims low-signal sections so the summary stays lean, and never blocks you.
- strict: hard-caps the manifest at 2k tokens and refuses if it would go over.
- off: no cap, the manifest can grow to any size.
2. Output compression rules. How terse Claude's replies are in this project.
- default (recommended): diff-style edits, no "here's what I did" preamble.
- strict: telegraphic, clipped replies, for power users who want maximum brevity.
- verbose: extra context and explanation, good while you are still learning the tool.
- skip: don't install reply rules at all.
Not sure? Take the recommended option in each. You can change either choice later: run sipcode rules --mode <default|strict|verbose> for the reply style, or re-run sipcode manifest to regenerate the summary.
Step 4. Open a new Claude Code session
Sipcode picks up automatically on the next tool call Claude makes. No restart needed in most cases. To be safe, you can close any existing Claude Code window and open a fresh one.
Now Claude Code will be using Sipcode in the background.
Step 5. After about an hour of work, check it
sipcode drift
sipcode proxy --stats
If drift says "no drift" and proxy --stats shows a few dozen rewrites with savings, everything is working.
Updating Sipcode
Sipcode never checks for updates on its own. That would require a network call, and zero network calls in normal use is a guaranteed property of the codebase (a test fails the build otherwise). Updating is always a manual, explicit step.
To update to the latest version:
npm i -g sipcode@latest
Or use the built-in helper:
sipcode update # prints your current version + the update command
sipcode update --run # runs the update in place for you
After updating, confirm with sipcode --version and see what changed in the CHANGELOG. The MCP config never needs re-pasting; Claude asks the server for its tools on every reconnect, so new tools appear automatically.
Release cadence: patch releases ship whenever a fix or improvement is ready, often within a day or two of a reported issue. Since Sipcode can't notify you (zero network calls), a good habit is to run sipcode update about once a week. It's a one-second check, and --run upgrades you on the spot if something's new. Watch or star the repo to catch releases too.
Sipcode MCP 질문
Sipcode MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add sipcode -- npx -y sipcode를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Sipcode MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Sipcode를 어떻게 설치하나요?
npm i -g sipcode를 실행한 후 sipcode init을 입력하세요. 이후 Claude Code 세션부터 자동으로 적용됩니다.
Sipcode가 네트워크 호출을 하거나 데이터를 외부로 전송하나요?
아니요. 일반적인 사용 환경에서 네트워크 호출을 전혀 수행하지 않으며, 데이터는 사용자의 노트북을 절대 벗어나지 않습니다.
Claude Code 세션의 컨텍스트가 비대해지고 있는지 어떻게 확인하나요?
sipcode drift를 실행하세요. 베이스라인과 비교하여 비대해진 컨텍스트, 반복된 읽기, 오래된 신호를 찾아냅니다.
Sipcode로 OpenAI Codex 사용량을 추적할 수 있나요?
네. Codex CLI 세션 로그를 읽어 비용 분석 및 사용량 제한을 확인합니다. 단, Codex의 동작을 직접 수정하지는 않습니다.
Sipcode 벤치마크의 절감 효과는 어느 정도인가요?
고정된 20개 작업 코퍼스 벤치마크 결과, 어떤 환경에서든 재현 가능한 중앙값 62.6%의 토큰 감소율을 보여줍니다.