mimo-throughput

Real-time LLM performance monitoring plugin for MiMoCode. Tracks TTFT, TPS, latency, token usage and cost per model with a TUI sidebar display.

Features

• TTFT (Time To First Token) per model
• TPS (Tokens Per Second) per model
• Latency tracking
• Token usage breakdown (input, output, reasoning, cache)
• Cost estimation per model
• Recent requests display

Installation

MiMoCode separates server config (mimocode.json) and TUI config (tui.json). Both need the plugin listed:

# Server config: .mimocode/mimocode.json
{
  "plugin": ["mimo-throughput"]
}

# TUI config: .mimocode/tui.json
{
  "$schema": "https://opencode.ai/tui.json",
  "plugin": ["mimo-throughput"]
}

Display

The plugin adds a collapsible "Throughput" section to the MiMoCode TUI sidebar showing:

▼ Throughput  5 reqs  $0.0012
  mimo-auto  120ms  45.2/s  2.1s  ↑1.2k ↓3.4k
  Recent
  mimo-auto  80ms  52.1/s  1.8s  ↑800 ↓2.1k

Relationship with opencode-throughput

This project is a fork of opencode-throughput by Howardzhangdqs, adapted for MiMoCode.

What changed

| | opencode-throughput | mimo-throughput | |---|---|---| | Target | OpenCode | MiMoCode | | Plugin API | @opencode-ai/plugin | @mimo-ai/plugin | | Package name | opencode-throughput | mimo-throughput |

What's the same

The core logic is identical — both use the same TUI rendering (SolidJS + @opentui), event system (message.updated, message.part.updated), and slot registration (sidebar_content). MiMoCode's plugin API is a superset of OpenCode's, so the code works without modification.

Why a separate package?

MiMoCode and OpenCode share the same plugin architecture but have different peerDependencies. Publishing as mimo-throughput with @mimo-ai/plugin as the peer dependency ensures clean installs without version conflicts.

License

MIT — original work by Howardzhangdqs