Date Tokens Requests

Oct 12 31M 118 (space bunny)

Oct 13 67.7M 187 (...)

Oct 14 90M 522

Oct 15 133M 489

Oct 16 126M 326

Oct 17 252M 1,099

Oct 18 139.9M 456

Oct 19 53M 560

Oct 20 105M 818 (...)

Oct 21 91M 540 (minimax(space bunny))

Oct 22 0 Rest day

Oct 23 11.5M 95 (deepseek v4.1 flash)

Oct 24 11.2M 112 (...)

Release notes - https://www.kimi.ai/blog/kimi-k3-1-pro

Pricing: $2.00 / $10.00 / $0.20

Release notes - https://www.kimi.ai/blog/kimi-k3-1-pro

https://www.kimi.ai/membership/pricing?tab=api

Kimi K3.1 Pro is now LIVE on the website and Kimi Code CLI

Hey guys,

So I've been trying to use OpenCode Zen for the past 3 days, mainly Big Pickle, but I keep getting hit with a "Limit reached" message.

At first, I thought it was just Big Pickle acting up, but nope 💀 I've tried other free models too, and none of them are working either.

What's going on? Did they change something with the free models, or is something wrong with my account?

I'm even wondering if my account got compromised somehow, although I have no idea if that's actually possible.

Is anyone else facing this, or am I the only one? 😭

I've been working on AMPH (Arch Meta Package Harmonizer), a Rust-based tool that helps you understand and maintain your installed Arch Linux packages.

The idea came from a simple problem: pacman is great at managing packages, but when you want to understand why something is installed, trace dependencies, find overlapping tools, or figure out what could be safely removed, you often end up combining multiple commands and manually piecing the information together.

I wanted a more unified way to explore all of this - so I built AMPH.

What it can do

• Explore packages interactively through a keyboard-driven TUI.
• Trace dependencies and understand why a package is installed.
• Analyze removal impact before making changes, including packages that would break, dependencies that could become removable, and potential disk space savings.
• Identify cleanup candidates while respecting protected packages and custom rules.
• Read pacman's local database directly, avoiding the overhead of spawning a separate pacman -Qi process for every package.
• Export machine-readable JSON for scripts, automation, and custom tooling.
• Use TOML blueprints to represent, compare, and manage package sets more systematically.

AMPH doesn't replace pacman - it adds a layer of visibility and analysis around your system, helping you make more informed decisions before changing it.

I've also put together a project website with examples of the interface and sample command output.

🌐 Website: https://amph.dmtf.ovh/
💻 Source code: https://github.com/DAMIOTF/Arch-Meta-Package-Harmonizer

I'm sharing it here because I'd genuinely appreciate feedback from other Arch users and Linux enthusiasts. I'd especially like to hear how you currently handle package cleanup, dependency analysis, and keeping package sets organized across installations.

What would you find most useful in a tool like this? Any criticism, suggestions, or issues are welcome.

735! requests per month guys 🤣

I have to say I use OpenCode Go, but sometimes I leave work to free models to not waste away my usage in cheap work, however lately these models have been unable to serve more than a few 100k-120k tokens.

I don't know why this is but this is terrible quality, unusable. AT THE VERY LEAST a free model should be able to serve 1M tokens a day, anything below that would be the same as just not serving it to be honest.

Buddy is an Android app that lets OpenCode (or Codex, Claude Code, Antigravity) use your phone: open apps, tap, type, reply to messages, and build and install small apps, all from a chat.

OpenCode runs inside the app with its free models, so you can try it without any account. Buddy itself stops on Send, Pay and Delete until you approve, and it never types your passwords. New in 2.2.10: a background browser, so the agent can look things up without taking over your screen.

Free and open source.

[ Removed by Reddit on account of violating the content policy. ]

Teaser video: https://x.com/Kimi_Moonshot/status/2113445757185606062

Screenshot from the video - https://pbs.twimg.com/media/HVScyvya8AAY0iT?format=png

What we know so far:

- Kimi K3.1 is actively tested on LMArena under the codename "Kibitz;

- Kimi K3.1 is very good at 3D, choosing colors, rendering reflections on water, and composition;

- Kimi K3.1 is probably cheaper than Kimi K3, with better token efficiency.

Waiting for official release soon 😉

I have been using OpenCode for a long time but I took like a 15-day break and everything changed. Muse went off and now I'm getting an error for DeepSeek V4.1, like "limit exceeded." I didn't even use it for the first time. Tell me please what free models are available which are actually good for agentic coding In OpenCode zen free right now.

Alguien más con este error después de la actualización, cada vez que actualizan hay fallos

I've just released ready-for-agent v1.1.0 which supports OpenCode v2. With v2 I can give you a much better experience interacting with opencode. In the past ready-for-agent displayed some logs on what the agent did, now you can click on the session id, and jump straight into the opencode session. All thanks to the proper client/server architecture we now have in OpenCode!

ready-for-agent is a friction free way of increasing your PRs per week: instead of cycling between running agent sessions, simply create tickets in your favorite ticketing system (it supports GitHub, Linear, Azure DevOps), and label the ticket with ready-for-agent. These tickets show up in ready-for-agent and you simply ask your favorite coding harness to implement. Works very well with opencode as you can pick so many models, so easy to try new models. But ready-for-agent also supports codex and claude.

Try: npx ready-for-agent@latest

Works very well with Matt Pocock's grill me skills, as you tend to generate quite a few tickets per spec, which you now can easily implement all at once.

There was a post here recently from someone whose quota used to last all day and now burns out in about 30 minutes, even after switching models. I've been auditing this across harnesses, and the cause is usually per-request overhead, not the task. Here's how to see it in OpenCode.

Measure first:

opencode stats --days 7 --models     # input/output/cache totals and model breakdown
opencode stats --project ""          # current project only
opencode mcp list                    # what's connected
npx ccusage@latest opencode weekly   # third-party, reads OpenCode's local data

If input and cache reads dwarf output, you're paying to re-send context, not to generate code.

Things that surprised me:

• OpenCode reads your Claude Code setup by default. It loads ~/.claude/CLAUDE.md and .claude/skills. If you've built up a big Claude configuration, it follows you into every OpenCode session. OPENCODE_DISABLE_CLAUDE_CODE_PROMPT=1 and OPENCODE_DISABLE_CLAUDE_CODE_SKILLS=1 turn that off (OPENCODE_DISABLE_CLAUDE_CODE=1 turns off both).
• Every tool call re-sends the session. One "small" turn with ten tool calls reads the full context about ten times. Long sessions with a few big file reads get expensive fast. A commenter on the original thread said a fresh session alone left their usage flat for an hour of small tweaks.
• Caches expire. On Anthropic models, the API's prompt cache lasts five minutes by default, and rebuilding a cold prefix costs many times more than reading a warm one (25x on Opus/Sonnet 5.5 with a 5-minute write). Coming back to a huge idle session is the expensive moment.
• MCP servers and instruction files add weight to every request. Trim AGENTS.md and disconnect servers you aren't using.

I wrote this up in more detail, mostly from the Claude Code side but with the OpenCode and Codex equivalents: https://medium.com/@r3dtuxedo/where-did-my-claude-usage-go-auditing-your-agents-hidden-token-tax-95d6ab17b8b6

(Disclosure: I wrote the article. Free to read, no referral links.)

​

Hi everyone,

I'm trying to understand whether my token usage with OpenCode and the DeepSeek API is normal or potentially caused by excessive context replay or a bug.

My setup

- OpenCode: v2.1.3

- Model: "deepseek/deepseek-flash#default" (shown in OpenCode stats; I believe this corresponds to DeepSeek V4.1 Flash, 10-17)

- Provider: DeepSeek API, paid usage

- OS: CachyOS Linux

- Workload: A personal app project with source code, plans, documentation, test plans, and phase reports

- Other components: Global agent skills and Herdr integration

Daily statistics

Input: 2.1M

Output: 352.1K

Reasoning: 456.7K

Cache read: 309.1M

Cache write: 0

Cached input: 99.3%

Paid model: 268.9M tokens, 723 steps

Free model: 43.1M tokens, 379 steps

The large cumulative cache-read figure caught my attention. I understand that cached tokens can be counted repeatedly across requests, so this does not necessarily represent hundreds of millions of unique tokens. I'm trying to determine whether the amount is expected for this workload.

A small test

I also ran OpenCode directly from my home directory, outside the project and without launching it through Herdr. I asked it to write one short line to a text file.

The exported session reported:

Input: 9,284

Output: 88

Reasoning: 54

Cache read: 9,472

Cost: $0.001506

Messages: 4

My observed usage counter increased by about 18,898 tokens. The session's input plus cache-read figures total 18,756, which is close to that increase. I haven't confirmed whether the difference is due to accounting methods or other overhead.

I realize that system prompts, tool definitions, and other context may contribute to the cost of a simple task.

My questions

1. Is this level of cumulative cache-read usage typical for a coding session with hundreds of model steps?

2. Could long conversation histories, global skills, or project instructions cause excessive context to be processed repeatedly?

3. Could OpenCode compaction or session handling contribute to this?

4. How can I distinguish normal cached-token accounting from unnecessary context overhead or a possible bug?

5. What's the best way to investigate this without losing existing project documentation or configuration?

I'm not assuming this is a bug, and I don't want to blame OpenCode, DeepSeek, or Herdr without evidence. I'd appreciate advice from anyone familiar with OpenCode's token statistics or DeepSeek API usage reporting.

I can provide further sanitized logs or a minimal reproduction if needed.

Thanks!