Kite CLI v0.1.4 fixes a small behavior with an outsized effect on event-driven pipelines: standard output now flushes after each event.

Why a flush matters

A terminal can appear to print output immediately while a downstream process waits behind a buffer. That difference is easy to miss during interactive testing and obvious when a real event stream is piped into another command, parser, or agent adapter.

With v0.1.4, each emitted event becomes available to the next process promptly instead of waiting for the output buffer to fill.

The Unix contract

Kite’s usefulness depends on ordinary composition. An event stream should behave like a stream, not like a batch file that happens to arrive over time. This release tightens that contract without adding another configuration surface.

The immutable change record and release assets are available in the Kite CLI v0.1.4 release.

Primary signals