cctape
A local proxy for Claude Code that archives every request and response, with a web UI for browsing sessions, searching transcripts, inspecting raw API traffic, tracking token usage and cost, and an MCP server for Claude to inspect past sessions.
Features
- Find any past conversation. Full-text search across every session you've ever run, with ranked results and highlighted snippets.
- See what Claude costs you. Token and dollar spend broken down by session, account, and model, plus a live chart of how close you are to your 5-hour and weekly rate limits.
- Let Claude search its own history. A built-in MCP server so the agent can look up what you discussed last week instead of re-deriving context you already paid for.
Quick start
Run cctape with uv:
uvx cctape
On first run, your browser opens to a setup page at http://127.0.0.1:5555/setup with the one env var you need to copy. After that, run claude as usual — sessions appear in the UI as they happen.
Pass --no-browser to skip the auto-open.
Configuration
Shell
Add to ~/.zshrc (or ~/.bashrc):
export ANTHROPIC_BASE_URL=http://127.0.0.1:5555/proxy
Claude Code VS Code extension
Add to user settings:
"claudeCode.environmentVariables": [
{"name": "ANTHROPIC_BASE_URL", "value": "http://127.0.0.1:5555/proxy"}
]
MCP server
Register the MCP server with the claude CLI so Claude Code can search its own archive:
claude mcp add --transport http cctape http://127.0.0.1:5555/mcp
This exposes search_transcripts and get_session_window to the agent.
Flags and environment variables
--host/--port— bind address (defaults:127.0.0.1,5555)--no-browser— don't auto-open the browser on first runCCTAPE_DB— database path (default:~/.cctape/cctape.db)
Running it as a service
cctape is a regular HTTP server; run it under whatever supervisor you like (launchd, systemd, tmux, etc.). Once it's up on 127.0.0.1:5555 and your ANTHROPIC_BASE_URL points at /proxy, it just stays out of the way.
Development
Clone the repo and run the frontend + backend separately during development.
Build the frontend once (output is served by the backend from backend/src/cctape/static/):
cd frontend && npm install && npm run build
Start the backend with reload:
cd backend && uv run uvicorn --reload --reload-dir src --factory --port=5555 cctape:create_app
--reload-dir src scopes the file watcher to backend source; without it uvicorn walks the whole repo (including frontend/node_modules and .venv) on every poll and pegs a CPU core.
Open http://127.0.0.1:5555.
The frontend can also run on its own dev server with HMR:
cd frontend && npm run dev
Pre-commit hooks run ruff, pyright, pytest, eslint, and tsc.
Metadata
Release files for cctape 0.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cctape-0.3.5.tar.gz | 1.4 MB | With provenance | Details for cctape-0.3.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cctape-0.3.5-py3-none-any.whl | Python 3 | none | any | Details for cctape-0.3.5-py3-none-any.whl |
Total release size: 2.7 MB
Release files / cctape-0.3.5.tar.gz
| Download URL | cctape-0.3.5.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a633a879555f30b900a08cfb15a3ce925a5004b862727963ea13212deca7315
|
|
BLAKE2b-256 checksum How to use checksums |
7431c4ecd3507e74999e31e19e404791036d20809c41a89b298c38d9996ae6c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 1, 2026.
Transparency logRelease files / cctape-0.3.5-py3-none-any.whl
| Download URL | cctape-0.3.5-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11db48eaa324d617f23748eb46935815bbbed7d63a379c05ab8536b3bd33d094
|
|
BLAKE2b-256 checksum How to use checksums |
86e0abce6dcc64e1e3be207337d94a3f6de9b19c2fa9afa3dfee7f326794eb68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 1, 2026.
Transparency logSecurity for cctape 0.3.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cctape-0.3.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.