v0.2.1

Highlights

• Added kit task, a generic provider-backed escape hatch for work that does not yet have a domain-specific provider.
• Added kit repl --interactive for a featureful command-line REPL client backed by persistent Kit REPL sessions.
• Made manifest/plan execution output stream live progress instead of buffering everything until the end.
• Improved agent progress rendering so tool calls and assistant updates show as a readable indented transcript.

User-visible changes

kit task escape hatch

You can now write manifests like:

kit task {
	name write-makefile
	file src/main.c
	file src/lib.c

	intent {
		Write a Makefile for this simple C project.
	}
}

kit task emits a normal follow-up plan, so it works with the existing manifest check, manifest plan, manifest apply, and --skip-plans review flow.

Interactive REPL client

kit repl --interactive (also kit repl -i or kit repl interactive) starts a terminal client for the existing REPL server.

It supports multiline input, top-level await, persistent VM-backed session state, history, completions, Ctrl+C handling, and dot commands such as .help, .new, .ls, .transcript, .reload, and .exit.

Clearer plan execution output

Plan execution now prints each provider event and agent update as it happens. Agent tool calls are shown as concise action lines, making long-running manifest apply and plan execution easier to follow.

More reliable agent command execution

Kit now spawns child processes through node:child_process instead of Bun's subprocess API for this path, avoiding a Bun-in-Bun hang that could leave agent steps with no output.

Release binary fixes

Compiled release binaries are now built with Bun config and dotenv autoloading disabled, so local bunfig.toml or environment files do not accidentally affect packaged executables.

Docs

The README now includes a higher-level “Working with kit” introduction that explains providers, manifests, and how Kit works with agents.

Full Changelog: v0.2.0...v0.2.1