MPL-2.0 Go LLM gateway with DeepSeek best compatibility: install via npx/Docker, point coding agents at its OpenAI/Anthropic-compatible endpoint, and manage routing from the local web UI.
DSH integration
Compatible
Author-claimed
Safety audit
Unaudited
Last verified
2026-08-21
License
MPL-2.0
01What can it help you accomplish?
Give coding agents a unified model endpoint with DeepSeek best compatibility
OpenAI- and Anthropic-compatible endpoints (http://localhost:12580/tingly/openai/v1 and /tingly/anthropic) with protocol translation, Thinking-workflow reasoning support, cache-hit optimization, vision proxy and web search for DeepSeek
Developers running DeepSeek models in coding agents who want one local endpoint with broad protocol compatibility
Wire coding agents to the gateway with one click
One-click configuration for Claude Code and OpenCode (manual guides in-app for Xcode and others), with transparent proxying for SDKs and CLI tools
Teams using coding agents or custom AI tools that need a quick, low-friction model endpoint setup
Control AI agents remotely from IM apps
Remote task execution and monitoring through Telegram, DingTalk, Feishu, Lark, Weixin, WeCom, Slack and Discord bots configured in the web UI's Remote section
Builders who want to run and check on agents from a phone or share agent access across a team
02How to install into DeepSeek Harness
Prerequisites
- Node.js LTS with npx for the recommended install path (the README provides install steps via nvm for macOS/Linux and winget or nodejs.org for Windows); or Docker for the container paths
- Go 1.26+ only applies to building from source (source build is documented under the Contributing Guide)
Installation steps
- 01
Run `npx tingly-box@latest` (or `npx -y tingly-box@latest`) — installs and runs the binary, auto-restarts, migrates and opens the Web UI when run without args
$ npx tingly-box@latest
- 02
If you hit network issues, use the bundled binary: `npx -y tingly-box-bundle@latest` (CN npm mirrors are supported, e.g. `npx --registry=https://registry.npmmirror.com -y tingly-box-bundle@latest`)
$ npx -y tingly-box-bundle@latest
- 03
Or run from Docker: `mkdir tingly-data` then `docker run -d --name tingly-box -p 12580:12580 -v `pwd`/tingly-data:/home/tingly/.tingly-box ghcr.io/tingly-dev/tingly-box`
- 04
Or use Docker Compose for an isolated environment: `docker-compose up -d` (Web UI at http://localhost:12581; `docker-compose down` to stop)
- 05
Open the Web UI at http://localhost:12580 and configure providers, routes and agent integrations there
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
Runs as a standalone local LLM gateway beside DSH (not installed inside the harness): agents connect to its OpenAI/Anthropic-compatible endpoints, while the repo is tagged as a dsh plugin and the README documents DeepSeek best compatibility
Agent-first model gateway
model providers (API keys and OAuth providers like Claude.ai / Codex)→unified OpenAI/Anthropic-compatible endpoint for agents with automatic protocol translation; adds typically < 1ms of overhead
proxies requests to remote model providers (network egress); stores per-user configuration and usage data locallySmart routing engine
models, tokens and custom policies→requests routed across models and tokens based on cost, speed, or custom policies — beyond simple load balancing
Visual control plane (Web UI)
browser on http://localhost:12580→manage providers, routes, aliases, models and remote bots at a glance — no config files needed; includes client-side usage analytics (token consumption, latency, cost estimates)
writes configuration locally instead of config filesLocal stdio MCP web tools
an MCP client→local stdio MCP server exposing `web_search` / `web_fetch` tools
fetches web content over the network when called
04Who is it for? When not to use it?
Good for
- Developers running DeepSeek models in coding agents who want one local endpoint with broad protocol compatibility
- Teams using coding agents or custom AI tools that need a quick, low-friction model endpoint setup
- Builders who want to run and check on agents from a phone or share agent access across a team
Not for
- Known issues have been recorded in a public fault record; the maintainers ask users to update to the latest version to resolve them, so staying on the latest release is effectively required.
05Compatibility, maintenance and safety notes
- Known issues have been recorded in a public fault record; the maintainers ask users to update to the latest version to resolve them, so staying on the latest release is effectively required.
- The gateway serves local agents but forwards requests to remote model providers, so it needs network access and valid API keys or OAuth authorizations for the providers you route to.
- The recommended install path requires Node.js LTS with npx; container paths require Docker, and Docker Compose uses port 12581 to avoid conflicting with a host install on 12580.
MPL-2.0 · actively maintained (latest release v0.260819.0, 2026-08-19)
06Frequently asked questions
How does Tingly Box work with DeepSeek Harness?
Tingly Box runs as a standalone local gateway beside your harness rather than installing inside it: agents connect to its OpenAI/Anthropic-compatible endpoints (http://localhost:12580/tingly/openai/v1 or /tingly/anthropic). The repo is tagged as a dsh plugin, and the README documents DeepSeek best compatibility — protocol adaptation, Thinking reasoning, cache optimization, vision proxy, web search and 1M context.
What do I need before installing?
Node.js LTS with npx for the recommended `npx tingly-box@latest` install, or Docker / Docker Compose for the container paths. Go 1.26+ is only required if you build from source.
Where do requests and data go?
The gateway runs locally on port 12580 and proxies requests to the model providers you configure via API keys or OAuth (Claude.ai, Codex, etc.). Configuration and per-user usage data are stored locally; a Guardrails doc covers policy-based safety checks and protected credential masking.
Is there MCP support?
Yes — Tingly Box ships a local stdio MCP server for `web_search` / `web_fetch`, documented in docs/mcp-web-tools.md.
What are the limitations?
Known issues are tracked in a public fault record and the maintainers ask you to update to the latest version to resolve them. You also need network access plus valid API keys or OAuth authorizations for the providers you route to.
07Related DSH workflows
openviking
by volcengine
Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
colleague-skill
by titanwings
Turn memories and knowledge into warm, reusable agent skills — a skill generator for digital companions in the AI persona era.
archify
by tt-a1i
Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self-contained HTML with motion and crisp export.
learn-harness-engineering
by walkinglabs
Harness engineering beginner tutorial, from 0 to 1
08Data and sources
DeepSeek is optimized for mainstream agent workflows, offering broad compatibility across protocol adapters, agent clien…
Tingly Box **serves agents, coordinates AI models, optimizes context, and routes requests** for maximum efficiency — wit…
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-08-21. Found an error? Submit a correction.