Repository navigation
Releases: dhamidi/kit
Release list
v0.5.0
kit v0.4.0
CLI usability release
CLI basics
kit version,kit --version/-v, andkit --help/-hnow work and exit 0.
Argument parsing
Type.Boolean()schema fields are bare flags:--flagenables,--no-flagor--flag=falsenegates.Type.Number()/Type.Integer()(and union) CLI values are coerced before schema validation — no more hand-rolledType.Union([Type.Number(), Type.String()])in providers.- Schema
default:metadata is applied during parsing and shown in--helpas(default: …).
Generate
- Every component type now accepts Kit-injected
--descriptionand--filesflags; an explicit--descriptionoverrides the provider-generated one. Customparse()implementations never see these flags. kit generate ... --helpgroups options viakit: { group: 'Name' }schema metadata, inherits descriptions for nested fields, and documents the plan lifecycle (plans execute immediately unless--dry-run; usekit plan resumeafter interruptions).
Provider API
parse()is now optional — Kit falls back to its schema-derived parser.- Wrong-shaped
parse()results and exceptions fromdescribe()/create()surface as clean CLI errors naming the provider, type, and hook (setKIT_DEBUG=1for full stack traces).
Output
TableFormatteris width-aware: capped to the terminal (fallback 120 columns), with per-columnmaxWidth/flexhints and…truncation.kit component list --widedisables truncation.- New
KeyValueFormatterrenders wide records as definition lists;kit component showuses it.
REPL
- Bare
kit replstarts the interactive REPL;kit repl helpdocuments subcommands, session semantics, and examples. kit repl doauto-creates a session when needed,kit repl stopclears the remembered session, and evaluation failures exit 1 with clean stacks (no more REPL server frames).- Session ids must be 8 hex characters, so 8-character expressions like
kit.Typeno longer misparse as session ids.
v0.3.2
use-kit skill refresh
- Correct manifest behavior:
manifest applyexecutes plans by default; use--skip-plansfor deterministic scaffolding only. - Document current
generateoptions, component spec round-tripping, provider testing, plan resume, project initialization, and interactive REPL workflows. - Synchronize the bundled
kit-commandexample and built-in provider references with the current implementation. - Update the mise installation command to v0.3.2.
v0.3.0
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 --interactivefor 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