DepTime

[DepTime]

An API time machine for Python libraries, built for coding agents.

When an agent hits ImportError, AttributeError or "unexpected keyword argument" in a fast-moving library, one call to DepTime says what changed, in which release, and what to use instead. Answers are computed from static diffs of every indexed release, not from docs or model memory.

Free, open source (MIT), and local: your code and errors never leave your machine.

[How DepTime works. Built nightly on GitHub: new PyPI releases are read statically and diffed release to release; packages are never imported or run. The only thing that crosses to your machine is one file, index.sqlite.xz. Answered on your machine: deptime mcp answers your agent locally, and your code and errors stay there.]

Every night, GitHub Actions reads each new release's public API with griffe, which parses the source without running it, diffs it against the previous release, and publishes the result as one file, index.sqlite.xz, on this repo's Releases. On your machine, deptime mcp checks that file's sha256 and schema before swapping it in, then answers every question locally in milliseconds. The full design is in docs/04-architecture.md, and the decisions are in docs/adr/.

TypeError: Client.__init__() got an unexpected keyword argument 'proxies'

{  "symbol": "httpx.Client.__init__(proxies)",  "issue": "param_removed",  "installed_version": "0.28.1",  "last_version_with": "0.27.2",  "first_version_without": "0.28.0",  "deprecated_in": "0.26.0",  "replacements": [    {"target": "proxy", "confidence": 0.8, "source": "deprecation_message"},    {"target": "mounts", "confidence": 0.79, "source": "deprecation_message"}  ],  "pin_to_restore": "httpx<=0.27.2",  "confidence": "high"}

That's the real explain_error answer from the published index, trimmed. The full answer also quotes the deprecation message DepTime found in httpx's own source, and adds a one-sentence explanation for your agent to pass on.

Status: alpha. The prebuilt index is rebuilt twice a day. Known gaps are tracked in BACKLOG.md.

How well it works

Each check's right answers were written down before DepTime first ran on it (bench/). Judge DepTime by the first run: the fixes since then were designed from its misses, so the later numbers are flattering.

Across all 237 real tracebacks in the benchmark, including the ones fixes were designed from, DepTime names the right package, name and release for 97.9%, and a right replacement is among its first three for 66.7%. CI re-scores them and both holdouts on every code change and every published index, and fails on a drop of more than 2 points (or a false-positive rate up by more than 1).

Install

Requires uv.

# Claude Code. Cursor, Codex, VS Code and Claude Desktop take the same# command (uvx deptime mcp) in their MCP config.claude mcp add deptime -- uvx deptime mcp

On first launch DepTime downloads its prebuilt index (one file from this repo's GitHub Releases) in the background, then checks for a newer one at most once a day. Set DEPTIME_OFFLINE=1 to never touch the network. Each index carries a signed record of the CI run that built it; deptime index pull --verify checks it (SECURITY.md).

Claude Code users can also install the plugin in integrations/claude-code with /plugin marketplace add cschmertz/deptime, then /plugin install deptime@deptime. It adds a skill and a local hook that suggests DepTime when a Python version-change error appears in a command's output.

First launch timing out? uvx installs DepTime the first time a client starts it. On macOS with an x86_64 uv (an Intel Mac, or Intel Homebrew on Apple silicon), one dependency, cryptography, has no prebuilt wheel and is compiled, which can take longer than a client waits for a server to start. Run uvx deptime --help once beforehand.

Client compatibility

Checked 2026-11-05 with deptime 0.1.4 (details):

Tools

Every answer carries evidence and a confidence level. If a package isn't covered, DepTime says so instead of guessing. The contracts are in docs/03-product-spec.md.

CLI

uvx deptime explain --installed httpx==0.28.1 < traceback.txtuvx deptime history httpx Client.__init__uvx deptime check httpx 0.28.1 'httpx.Client:proxies,proxy'uvx deptime diff httpx 0.27.2 0.28.1uvx deptime diff pydantic 2024-06-01              # everything since a dateuvx deptime index status | pull

Hosting (optional)

Local mode covers coding agents. For web clients that only accept a URL, run deptime serve (MCP at /mcp, JSON at /v1/*) on any container host. The repo includes a Dockerfile and fly.toml, and the server applies anonymous rate limits. See docs/05-self-hosting.md.

Prior art and credits

• griffe does the static analysis.
• since-cutoff diffs your pinned dependencies against a model's training cutoff, locally and on demand. DepTime differs by shipping a prebuilt cross-version index and starting from a traceback.
• Context7 and Ref serve version-specific docs. DepTime answers symbol-level "when and what replaced it" questions.

Contributing

The most useful contributions are wrong-answer reports, which become benchmark cases. See CONTRIBUTING.md. Development setup:

uv sync && uv run pytest# build a small local index from real PyPI wheelsuv run deptime ingest httpx --versions 0.27.2 0.28.1

Docs

Product spec · Architecture · Self-hosting · Risks & spikes · Privacy & security · Changelog

License

MIT