If you're looking for Claude Code alternatives, I would first suggest looking into pi.dev or opencode for your harness. And then for models, you can choose from OpenCode Go (IMO most cost effect at this moment), OpenRouter, or direct from DeepSeek. Better if you go the Kimi route IMO and just buy a subscription from kimi.com

▲

wolttam 4 hours ago | parent | next [-]

I’m going to throw my harness in the ring: https://codeberg.org/mlow/lmcli

▲

Aeroi 5 hours ago | parent | prev | next [-]

agreed. OpenCode is a strong base, and with a couple modifications it can become a very effective harness. my sideproject mouse.dev I’ve been combining parts from OpenCode, Claude Code, and Hermes to build a cloud agent architecture that works well from mobile.

▲

CharlesW 4 hours ago | parent [-]

> OpenCode is a strong base, and with a couple modifications it can become a very effective harness.

I personally didn't find it to be competitve with Claude Code as a harness. Can I ask how you modified it to perform better?

	▲	Aeroi 4 hours ago \| parent [-]
		I haven’t run formal evals but i improved the experience for my own needs and it feels noticeably better with these modifications. -Claude-style subagents -an MCP layer for higher-level tools -Cursor-style control plane modes like Ask, Plan, Debug, and Build. The MCP layer lets the harness use things like GitHub file/code read, PR creation, web search/fetch, structured user questions, plan-mode switching, user skills, and subagents. So the improvement is mostly from better ui/ux orchestration and tool access. There's some things from hermes that are interesting as well. Most of my focus has been on applying this stack to sandboxed cloud agents so you can properly code and work from mobile devices. I can't definitively say that the stack is better or worse than Claude code, more just tuned for my use case I guess.

▲

bakugo 4 hours ago | parent | prev | next [-]

> I would first suggest looking into pi.dev

Looked into this one. Thought it was suspicious that it only had 7 open issues on github. Turns out they have a bot that auto-closes every single issue just because.

I honestly have no words.

	▲	mikeocool an hour ago \| parent \| next [-]
		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.
	▲	__cayenne__ 2 hours ago \| parent \| prev \| next [-]
		The maintainer, Mario, sometimes declares the repo is on an “issue holiday” where issues are auto closed. This particular holiday is because there is a big refactor coming up. In non holiday periods issues can be reported as normal.
	▲	skeledrew an hour ago \| parent \| prev \| next [-]
		They have a pretty decent explanation. https://github.com/badlogic/pi-mono/blob/main/CONTRIBUTING.m...
	▲	LPisGood 3 hours ago \| parent \| prev \| next [-]
		The idea is for it to he extremely minimal which strikes me as a very opinionated stance, and not opinions I agree with.
	▲	justinhj an hour ago \| parent \| prev [-]
		It's a very interesting project. Many popular open source projects are inundated with poor quality issues and prs, hence the defences they are starting to erect.

▲

aaurelions 5 hours ago | parent | prev [-]

Another very cost-effective option is Ollama Cloud. In a month of use, I only hit the 5-hour limit once, when I ran 8 agents simultaneously for 2 hours.

	▲	5 hours ago \| parent \| next [-]
		[deleted]
	▲	kopirgan an hour ago \| parent \| prev \| next [-]
		On which tier?
	▲	postatic 4 hours ago \| parent \| prev [-]
		definitely worth it - have both ollama cloud, opencode and hermes running to test them all out, working great so far.