transport-matters
Care for the cargo your coding agent carries.
A provider-neutral context control plane for coding agents. Sits as a reverse proxy in front of Claude, captures every /v1/messages exchange, normalises payloads into an internal representation, runs them through a deterministic curation pipeline, and optionally pauses for manual editing in a schema-aware editor.
No cert install. No system proxy settings. No sudo.
Install
uv tool install transport-matters # recommended
pipx install transport-matters # alternative
Or via the bootstrap script (installs uv first if missing):
curl -fsSL https://github.com/littleorgans/transport-matters/releases/latest/download/install.sh | bash
Quick start
# One command: starts the proxy + Claude Code together
transport-matters claude # in the current directory
transport-matters claude ~/my-project # in a specific working directory
# Proxy-only (bring your own client)
transport-matters claude --no-claude
# then in another terminal
ANTHROPIC_BASE_URL=http://localhost:8787 claude
From source
For day to day contributor work, install the local checkout as an editable uv tool:
just install-local
Then from any project directory:
transport-matters claude
If you want to run directly from source without installing a tool, run the API project explicitly:
uv run --project api transport-matters claude
From the repo root, just start is equivalent and is the preferred
source run entry point.
To validate the packaged artifact instead of the editable checkout, build and install the wheel separately before release.
Open http://localhost:8788 to see the live log, the rules UI, and the breakpoint editor.
What it does
Every /v1/messages request your agent sends gets:
- Captured — full request and response, logged to
~/.transport-matters/workspaces/{slug}/{hash}/. - Curated — a deterministic pipeline applies your rules (strip tools, truncate system parts, rewrite descriptions, drop thinking blocks).
- Paused (optional) — arm the breakpoint to edit the next request in a schema-aware editor before it forwards upstream.
All visible in a web UI at http://localhost:8788.
Why
A single Claude Code session routinely sends 285 KB payloads: 147 tools, 3 system parts, 5 message turns. Tools alone account for 67% of that. Transport Matters gives you visibility into what's being sent, a pipeline to strip and rewrite it, and a breakpoint to intervene before it hits the API.
Documentation
Full docs, architecture, and contributing guide: https://github.com/littleorgans/transport-matters
License
Apache 2.0. See LICENSE.
Metadata
Release files for transport-matters 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| transport_matters-0.3.0.tar.gz | 601.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| transport_matters-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / transport_matters-0.3.0.tar.gz
| Download URL | transport_matters-0.3.0.tar.gz |
|---|---|
| Size | 601.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb432ca31c23899e0e722750cfeacfe26eab268ebe65fd01f722625759e3ee27
|
|
BLAKE2b-256 checksum How to use checksums |
9480e90c2a711b69c56a6351257c437dcc617611030140a355ae237d01a3d9e2
|
| 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 Jun 5, 2026.
Transparency logRelease files / transport_matters-0.3.0-py3-none-any.whl
| Download URL | transport_matters-0.3.0-py3-none-any.whl |
|---|---|
| Size | 470.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e9bc2b6cdee5117d2db8ff4d624d12da1fe2e79cba5464ece87c83e1b146f075
|
|
BLAKE2b-256 checksum How to use checksums |
e969fd8cdd1f90af84f5073a0af2cb6590651c1a33e1cd984d24ec57ac13f374
|
| 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 Jun 5, 2026.
Transparency log