Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DeepClaude – Claude Code agent loop with DeepSeek V4 Pro

github.com

Post reply on HN
Print view View original

171–180 of 322 posts

Re: DeepClaude – Claude Code agent loop with DeepSeek V4 Pro

#171

Post by spaceman_2020 »

adonese wrote: post #136
faangguyindia wrote: post #100

Earlier quoted context omitted.

those who use deepseek v4, what level of output you get? Codex 5.3 or GPT 5.4? is flash version on level of gpt 5.4 mini

I tried it on a non trivial, but also well documented and self contained task. It did amazingly well. I used deepseek v4 pro via deepseek platform. The model is very fast and also it is super cheap. I burned only 0.06 USD (I reckon how the same task would have cost me had I used e.g., amp). PS. mentioning amp because i used to use it and I pay directly for token. I topped up 5 usd so I will be going to use it and see…

have you used it for non coding tasks via MCP, like Figma/Paper for design or Ableton MVP for sound design?

The token cost makes it tempting to use for token-heavy tasks like this

Re: DeepClaude – Claude Code agent loop with DeepSeek V4 Pro

#172

Post by oarsinsync »

altmanaltman wrote: post #123
mikeocool wrote: post #107

Earlier quoted context omitted.

Their process is outlined here: https://github.com/badlogic/pi-mono/blob/main/CONTRIBUTING.m... > Maintainers review auto-closed issues daily and reopen worthwhile ones. Issues that do not meet the quality bar below will not be reopened or receive a reply. Seems like not an unreasonable way to deal with the problem of large numbers of low quality issues being submitted.

But how is it any different from keeping them open? Like if they are going to sort through all the issues eventually (like they claim), why not just close the ones that are not worthy when they get to them instead of closing all by default? Is it just so that the project doesnt have open issues on its github page? But they are open issues in reality because the maintainer will eventually go through them? Nothing is "…

> But how is it any different from keeping them open?

If all open issues are actionable items, that makes expected workload a lot easier to handle.

If most open issues are actually in "needs triage / needs review" state, you lose the signal from the noise.

The issue tracker for a project exists primarily as a tool for maintainers, not for outsiders. Yes, the maintainers could change their workflow to create a new view that only shows triaged tickets.

Or, they could ensure the default 'open' view serves their needs.

Re: DeepClaude – Claude Code agent loop with DeepSeek V4 Pro

#173

Post by spirit23 »

Tanxsinxlnx wrote: post #170
spirit23 wrote: post #110

Earlier quoted context omitted.

So I created https://getaivo.dev , one can use model in the coding agent directly. Just `aivo claude -m deepseek-v4-pro`

does it support aws bedrock provider support,does i can use any model in this

Currently no, but it can be added

Re: DeepClaude – Claude Code agent loop with DeepSeek V4 Pro

#174

Post by woctordho »

yard2010 wrote: post #125
varenc wrote: post #119

Earlier quoted context omitted.

The more interesting part of deepclaude is the local proxy it runs to switch models mid-session and do combined cost tracking. Though these features seem quite buried in the LLM-generated readme. Looking at the history, it appears they were added later, and the readme wasn't restructured to highlight this. Also, the author checked in their apparently effective social media advertising plan: https://github.com/aattara…

How come such slop is allowed here, what value do these vibe coded zero shot "projects" add? Why not just post the prompt?

For the same reason that GitHub has a releases page for uploading binaries.

Re: DeepClaude – Claude Code agent loop with DeepSeek V4 Pro

#176

Post by vanchor3 »

oarsinsync wrote: post #172
altmanaltman wrote: post #123

Earlier quoted context omitted.

But how is it any different from keeping them open? Like if they are going to sort through all the issues eventually (like they claim), why not just close the ones that are not worthy when they get to them instead of closing all by default? Is it just so that the project doesnt have open issues on its github page? But they are open issues in reality because the maintainer will eventually go through them? Nothing is "…

> But how is it any different from keeping them open? If all open issues are actionable items, that makes expected workload a lot easier to handle. If most open issues are actually in "needs triage / needs review" state, you lose the signal from the noise. The issue tracker for a project exists primarily as a tool for maintainers, not for outsiders. Yes, the maintainers could change their workflow to create a new vie…

Somehow going through closed issues just to reopen them sounds like more effort than just using the built in label system which is made for this purpose, but maybe that's just me.

Re: DeepClaude – Claude Code agent loop with DeepSeek V4 Pro

#179

Post by torginus »

zozbot234 wrote: post #141
adonese wrote: post #136

Earlier quoted context omitted.

I tried it on a non trivial, but also well documented and self contained task. It did amazingly well. I used deepseek v4 pro via deepseek platform. The model is very fast and also it is super cheap. I burned only 0.06 USD (I reckon how the same task would have cost me had I used e.g., amp). PS. mentioning amp because i used to use it and I pay directly for token. I topped up 5 usd so I will be going to use it and see…

> But my impression so far is even when model subsidization is done, those open source models are quite viable alternatives. My understanding is that DeepSeek V4 Pro is going to be uniquely good at working on consumer platforms with SSD offload, due to its extremely lean KV cache. Even if you only have a slow consumer platform, you should be able to just let it grind on a huge batch of tasks in parallel entirely unat…

Good. It's hard to overstate how nervous most executives are about relying on cloud-based providers.

AI currently works basically by sending your entire codebase and workflow, and internal communication over the internet to some third party provider, and your only protection is some legal document say they pinky promise they won't train on your data.

And said promise is made by people whose entire business model relies on being able to slurp up all the licensed content on the internet and ignore said licensing, on the defense of being too big to fail.

Re: DeepClaude – Claude Code agent loop with DeepSeek V4 Pro

#180

Post by syntex »

Not sure you can replace Claude with DeepSeek V4 that easily and have same results.

From what I see while building my own agentic system in Elixir, the problem is in training for your specific harness/contracts. Claude/GPT-style models seem to be trained around very specific contracts used by the harness like tool call formats, planning structure, patching, reading files, recovering from errors, and knowing when to stop.

In practice, you either need a very strong general model that can infer and follow those contracts (expensive), or a weaker model that has been fine-tuned / trained specifically on your own agent contracts. Otherwise, the whole thing becomes flaky very quickly. And I suspect with Deepseek V4 you may get last options.

Post reply on HN