Polyglot repo: python/ is the authoritative full-featured implementation
(CodexLLM + ClaudeLLM + FallbackLLM + CLI); ts/ is a phase-1 CodexLLM SDK
targeted at your-app. Both share docs/drivers-contract.md as the
cross-language subprocess contract.
You are implementing subllm: a Python library that runs LLM requests
(summarize / search-and-summarize) through flat-rate coding subscriptions via the
genuine official clients — codex exec and interactive claude driven over
tmux. No per-token API. No proxy.
docs/superpowers/specs/2026-06-02-subllm-v1-design.md— the approved design spec. This is authoritative.docs/superpowers/plans/2026-06-02-subllm-v1.md— the ordered implementation plan. Execute it step by step.docs/research/research_subscription-summarization_2026-06-02.md— background, sourcing, and the gotchas (codex context pollution; claude 2026-06-15 billing split; JSONL completion detection).
Client-native execution only. NEVER build or use a subscription-to-API HTTP proxy (token wrapped behind an OpenAI-compatible endpoint) — ban risk. subllm only drives the real official CLIs as subprocesses.
base.py,errors.py,preflight.py(RegionGuard),DryRunLLM, pyproject/uv, tests scaffoldCodexLLMend-to-end (ship first)- minimal CLI
ClaudeLLMvia adapted tmux driverFallbackLLM+ drivers-contract docs
Tooling: uv for venv/deps. Tests use stub codex/tmux binaries on PATH — no
real subscription calls in tests. The one exception is the opt-in live smoke
suite (tests/test_integration.py), skipped unless SUBLLM_LIVE=1; run it with
SUBLLM_LIVE=1 uv run pytest -m integration to verify the clients against the
real subscriptions.