aattaran/deepclaude
Use Claude Code's autonomous agent loop with DeepSeek V4 Pro, OpenRouter, or any Anthropic-compatible backend. Same UX, 17x cheaper.
View Origin LinkProduct Positioning & Context
Use Claude Code's autonomous agent loop with DeepSeek V4 Pro, OpenRouter, or any Anthropic-compatible backend. Same UX, 17x cheaper.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is aattaran/deepclaude?
aattaran/deepclaude is a digital product or tool described as: Use Claude Code's autonomous agent loop with DeepSeek V4 Pro, OpenRouter, or any Anthropic-compatible backend. Same UX, 17x cheaper.
Where did aattaran/deepclaude originate?
Data for aattaran/deepclaude was aggregated directly from the GitHub Open Source community ecosystem, representing raw developer and early-adopter sentiment.
When was aattaran/deepclaude publicly launched?
The initial public indexing or launch date for aattaran/deepclaude within our tracked developer communities was recorded on May 3, 2026.
How popular is aattaran/deepclaude?
aattaran/deepclaude has achieved measurable traction, logging over 1,874 traction score and facilitating 106 recorded discussions or engagements.
Are there active development issues for aattaran/deepclaude?
Yes, we are currently tracking open architectural debates and bug reports for this project on GitHub. There are currently 5 active high-priority issues logged recently.
Is aattaran/deepclaude recognized by media or academic researchers?
Yes. It has been covered by media outlets like Github.com. This indicates the concept has reached a level of mainstream or scientific viability beyond just developer forums.
Are there open-source alternatives related to aattaran/deepclaude?
Yes, the GitHub ecosystem contains correlated projects. For example, a repository named Gitlawb/openclaude shares highly similar architectural descriptions and topics.
How does the creator describe aattaran/deepclaude?
The original author or development team describes the product as follows: "Use Claude Code's autonomous agent loop with DeepSeek V4 Pro, OpenRouter, or any Anthropic-compatible backend. Same UX, 17x cheaper."
Active Developer Issues (GitHub)
Logged: May 5, 2026
Logged: May 4, 2026
Logged: May 4, 2026
Logged: May 4, 2026
Logged: May 4, 2026
Community Voice & Feedback
That `{"backends":{}, "total_cost":0}` output means **zero `/v1/messages` requests reached the proxy** — even though `/deepseek` switched the mode, no actual model calls came through.
Most likely cause: a port-extraction bug in the wrapper that was just fixed in PR #26. Old code did `head -1`/`Select-Object -First 1` on the proxy's port file, which grabbed the proxy's banner line instead of the port number. Claude Code then pointed at a wrong port (or no port), so all model calls bypassed the proxy and went straight to `api.anthropic.com`.
**Try:**
1. `git pull` (or wait for PR #26 to merge to `main`)
2. Relaunch — wrapper now matches numeric-only line for the port
3. Run `/proxy-status` and a math question, then `/proxy-status` again — should see request count incrementing
Re: the screenshot — it's the official Claude Code CLI in a terminal, no extension. The slash-command UI is built into Claude Code itself.
Most likely cause: a port-extraction bug in the wrapper that was just fixed in PR #26. Old code did `head -1`/`Select-Object -First 1` on the proxy's port file, which grabbed the proxy's banner line instead of the port number. Claude Code then pointed at a wrong port (or no port), so all model calls bypassed the proxy and went straight to `api.anthropic.com`.
**Try:**
1. `git pull` (or wait for PR #26 to merge to `main`)
2. Relaunch — wrapper now matches numeric-only line for the port
3. Run `/proxy-status` and a math question, then `/proxy-status` again — should see request count incrementing
Re: the screenshot — it's the official Claude Code CLI in a terminal, no extension. The slash-command UI is built into Claude Code itself.
deepllm
👍 **deepcloe** — keeps the "deep" brand, drops the "Claude" trademark risk
---
_Generated by [Claude Code](https://claude.ai/code)_
---
_Generated by [Claude Code](https://claude.ai/code)_
👍 **cheapcode** — same Claude Code UX, fraction of the cost
---
_Generated by [Claude Code](https://claude.ai/code)_
---
_Generated by [Claude Code](https://claude.ai/code)_
👍 **modelswap** — swaps the model, works for any agent not just Claude Code
---
_Generated by [Claude Code](https://claude.ai/code)_
---
_Generated by [Claude Code](https://claude.ai/code)_
👍 **codeswap** — swaps the model backend inside Claude Code (or any coding agent)
---
_Generated by [Claude Code](https://claude.ai/code)_
---
_Generated by [Claude Code](https://claude.ai/code)_
Thanks for the report — this is a real bug, and there are two separate issues at play.
## Root cause
**In the current version**, running `deepclaude` (default mode) sets `ANTHROPIC_BASE_URL` directly to the upstream backend (e.g. `https://api.deepseek.com/anthropic`) and launches Claude Code. The local proxy on `:3200` is **not** in the request path — it only starts in `--remote` mode. That's why `/_proxy/cost` shows empty: nothing flows through it.
**"Still uses Claude tokens"** — if you're logged in to a Claude Max/Pro subscription via `claude login`, the subscription auth can override the API key env var. Claude Code ends up sending requests to DeepSeek's URL but authenticated with your Anthropic OAuth token, which DeepSeek rejects, and then falls back to Anthropic.
## Fix (in the next push)
The fix routes all modes — not just `--remote` — through the local proxy. That means:
- Cost tracking works in normal `deepclaude` mode
- `/switch` works mid-session in all modes
- The prox...
## Root cause
**In the current version**, running `deepclaude` (default mode) sets `ANTHROPIC_BASE_URL` directly to the upstream backend (e.g. `https://api.deepseek.com/anthropic`) and launches Claude Code. The local proxy on `:3200` is **not** in the request path — it only starts in `--remote` mode. That's why `/_proxy/cost` shows empty: nothing flows through it.
**"Still uses Claude tokens"** — if you're logged in to a Claude Max/Pro subscription via `claude login`, the subscription auth can override the API key env var. Claude Code ends up sending requests to DeepSeek's URL but authenticated with your Anthropic OAuth token, which DeepSeek rejects, and then falls back to Anthropic.
## Fix (in the next push)
The fix routes all modes — not just `--remote` — through the local proxy. That means:
- Cost tracking works in normal `deepclaude` mode
- `/switch` works mid-session in all modes
- The prox...
Yeah, same. Does not work. still uses the Claude tokens
What information can I provide to help you troubleshoot?
Discovery Source
GitHub Open Source Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.
SaaS Metrics