slancha-dogfood
Put Claude Code on Slancha. Two ways:
slancha-delegate— an MCP tool that any Claude Code session can install in one line. Your research-class subagent dispatches (file exploration, multi-source synthesis) route to Slancha's OSS models on your OpenRouter key instead of burning Anthropic quota.claude-slancha— a launcher that routes all of Claude Code's inference through a local Starlette shim → Slancha. Your dailyclaudesession runs on cheap OSS-tier models, the heavy turns automatically pin a strong tool-caller.
Status: v0.5.0. This is the consumption side of Slancha — the SaaS product lives in slancha-api. Both surfaces here are BYOK (Slancha holds no house keys): the Slancha key is yours, the OSS routes bill your OpenRouter account, and the funded Anthropic path billing is Slancha-side.
Cost honesty (read this first). Because both surfaces are BYOK on the OSS path, every dispatch lands on your OpenRouter dashboard. The convergence work (see numbers below) cut typical Claude Code turn costs ~71% on the OSS path, and the delegate's deep-research convergence rate is 100% on the validation prompt — but you should set an OpenRouter spend cap before installing. See
docs/CONSUMING_SLANCHA.md§ Cost expectations.
What you actually get (benched 2026-05-29, n≥10 each)
| surface | metric | result |
|---|---|---|
claude-slancha (ccshim) |
input cost vs unswapped default | ~71% cheaper ($1.74 → ~$0.50 per Mtok input on most turns) |
claude-slancha (ccshim) |
per-turn prefill weight | ~halved (tool-defs were 66% of a turn; MCP-strip drops ~98 unused tools) |
slancha-delegate (deep Cat C synth) |
convergence rate on Slancha | 100% (was 30% before this session's work) |
slancha-delegate (deep Cat C synth) |
mean wall-clock per dispatch | ~172s (down from ~322s baseline) |
Source: SESSION_LOG_2026_05_27_CLAUDE_SLANCHA_EMPTY_FIX.md at repo root. Method: kimi-k2.6 @ 200k budget, fixed Cat C prompt, env-controlled arms, scripts/bench_convergence.py.
Install — 5 minutes
Prerequisites
- Mac or Linux, Python 3.12+,
uv(orpipx). - Claude Code installed (
claudeon PATH). - A Slancha API key —
SLANCHA_API_KEY. - An OpenRouter API key — Slancha is BYOK; OSS-tier routes use yours. Set a spend cap on it at https://openrouter.ai/settings before continuing.
Option A — just the slancha-delegate MCP tool
This is the lighter install. Your existing Claude Code keeps using Anthropic; only research-class subagent dispatches offload to Slancha.
uv tool install slancha-dogfood # or: pipx install slancha-dogfood
claude mcp add slancha-delegate -- slancha-delegate-mcp
Then in any Claude Code session, ask it to run a research task — it should call mcp__slancha-delegate__slancha_delegate instead of spawning an Agent subagent.
Option B — full claude-slancha (CC on Slancha)
This routes all of Claude Code's inference through Slancha. Heavier setup; cheaper running cost.
uv tool install slancha-dogfood
# Run the shim in one terminal (it must stay up):
slancha-ccshim
# In another terminal:
claude-slancha
For long-running use, install the shim under launchd — see docs/CCSHIM.md.
Configuration
Both surfaces read from ~/.slancha-test/.env or env vars:
SLANCHA_API_KEY=sk-slancha-...
OPENROUTER_API_KEY=sk-or-v1-...
For the full env-knob list (model tier overrides, tool-strip allowlist, sampling temperature, convergence thresholds), see docs/CONSUMING_SLANCHA.md.
Verify it's working
# slancha-delegate (MCP) — your usage log should show successes routed to Slancha:
slancha-delegate-mcp --help # confirms the entry point exists
python -m slancha_dogfood.usage_log # after a few dispatches, shows route= / cost_usd / by_employee
# claude-slancha (shim) — health probe + a one-turn smoke test:
curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:8787/ # -> 200
claude-slancha -p "say hi"
Docs map
docs/CONSUMING_SLANCHA.md— long-form setup, every env knob, the bench numbers in full, how to override defaults per task.docs/CCSHIM.md— shim internals, the launchd plist, theSLANCHA_CC_*knobs in depth.docs/blog-claude-code-on-slancha.md— narrative example: a real CC session running on Slancha, what it cost, what it shipped.SESSION_LOG_2026_05_27_CLAUDE_SLANCHA_EMPTY_FIX.md— engineering log: the empties fix, the cost-incident diagnoses, the convergence A/B → 100%.
Development
git clone https://github.com/SlanchaAi/slancha-dogfood
cd slancha-dogfood
uv venv && source .venv/bin/activate
uv pip install -e ".[dev,ccshim]"
pytest -q # 73 tests, all green
uv run ruff check # lint
What this is not
This repo is consumption-side tooling for Slancha. It is not the Slancha product itself (that's slancha-api), not an agent framework, and not a hosted service. Non-Claude-Code clients (Cursor, Aider, …) are out of scope for now.
License
See LICENSE (or contact the maintainer — Slancha is currently private-source).
Metadata
Release files for slancha-dogfood 0.5.3
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 | |
|---|---|---|---|---|
| slancha_dogfood-0.5.3.tar.gz | 235.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| slancha_dogfood-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 291.9 kB
Release files / slancha_dogfood-0.5.3.tar.gz
| Download URL | slancha_dogfood-0.5.3.tar.gz |
|---|---|
| Size | 235.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e80aafbdc3367251a80d77a520e4d5ee953beed296e4b9112694eec4d5cfaa7d
|
|
BLAKE2b-256 checksum How to use checksums |
e9168979d4dd818d008ba7280bbc446c350c399c578f4765bbd54c6014b9783d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.8 {"installer":{"name":"uv","version":"0.11.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / slancha_dogfood-0.5.3-py3-none-any.whl
| Download URL | slancha_dogfood-0.5.3-py3-none-any.whl |
|---|---|
| Size | 56.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad4ef77a0766bb3a0415828dca16a42635d5d0ebe8ef993b89f9606e70d96305
|
|
BLAKE2b-256 checksum How to use checksums |
75adcef48634d63a0d9e0b046b8e2f78e77ad1b5fae44b3e7c146e847ce621f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.8 {"installer":{"name":"uv","version":"0.11.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for slancha-dogfood 0.5.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.