I just released a new round of the Kafka packages, with the biggest changes in Kafka Studio 1.4.0. Studio is a local web UI for exploring and operating a Kafka cluster, backed by the same TypeScript wire-protocol client as the rest of the workspace.

The release adds two ways to move from a broken event flow to a concrete event or command: a Kafka terminal that stays beside the UI, and a debugger for tracing events.

Kafka Studio cluster overview showing topics, partitions, broker count, and the navigation sidebar

A Kafka terminal beside the UI

Open Terminal from Studio’s top bar to dock a resizable shell below any page. You can expand or minimize it and navigate around Studio without losing the session or scrollback. It uses the actual @cookiemonsterdev/kafka-cli parser, help, formatting, completion, and confirmation checks. The active Studio profile supplies the cluster connection.

help topic list config describe --type topic orders group offsets payments-worker produce orders --key order-1 --value '{"id":1}' consume orders --tail 

Tab completes commands, flags, and live topic or group names. Ctrl+C interrupts a running command or tail. This is a Kafka command shell, not an operating-system shell. Studio enforces read-only mode on the server for terminal commands, including admin calls and producing messages.

Trace and replay event flows

The new Debugger searches JSON fields and headers across topics, then correlates records by an ID. For example: value.orderId == "123" AND headers.source == "checkout".

From a result, you can stage records for rate-limited replay, inspect compacted key history and partition routing, or decode Confluent-framed payloads with a configured Schema Registry. Repeatable produce/expect scenarios can be exported and run headlessly with kafka-studio --scenario kafka-scenario.json.

Scans are bounded and show per-partition coverage, so partial results are explicit. Replay preserves record bytes, including keys, values, headers, and tombstones; it creates new offsets and can repeat downstream side effects. Those details matter when debugging a real cluster.

More than Studio

The release chain also produced core 2.7.0, config 1.4.0, CLI 1.12.0, and docs 2.7.0. The headline user-facing work is in Studio and the documentation. The docs have improved navigation, mobile layout, and agent access.

Try it

npm install @cookiemonsterdev/kafka-studio KAFKA_BROKERS=localhost:9092 npx kafka-studio 

Studio needs a reachable Kafka broker. It runs locally and binds to 127.0.0.1 by default. If you already use the CLI, install Studio alongside it and run kafka studio.

If you try the terminal or debugger, I’d love to hear which Kafka workflow still takes too many steps. The project is open source and feedback is welcome.