Keiko turns your repository, your documents and your models into one calm place to work: chat with the models you configure, understand a codebase, generate reviewable tests, investigate bugs, and keep a memory of what was learned along the way. Everything runs on your machine, and every action stays inside the authority you grant.

What you get

• A workspace that understands your repository — inspect, search and reason over real code, not snippets.
• Your own models — bring the endpoints you already trust; Keiko never ships or hides credentials.
• A coding workbench — plan and edit inside a verified sandbox, under an autonomy mode you choose. It can take an issue all the way to a pull request in one governed run.
• Tests, investigations, verification — reviewable outcomes with honest state: no green over a broken gateway, and every refusal names its reason.
• Memory that learns from experience — decisions and findings persist locally and sharpen future answers.
• Evidence you can show an auditor — counts, hashes and statuses; never your content.

Download

The desktop packages install in one step and include everything — runtime and coding sidecar bundled, nothing else to install.

Download the latest release →

| Platform | Package | | --------------------- | -------------------------------------------------------- | | macOS (Apple Silicon) | keiko-macos-arm64.zip | | macOS (Intel) | keiko-macos-x64.zip | | Windows x64 | keiko-windows-x64-setup.exe or keiko-windows-x64.zip | | Linux x64 | keiko-linux-x64.zip |

Keiko is an open-source project and does not yet buy Apple and Microsoft code-signing certificates, so macOS and Windows ask once before the first launch: on macOS System Settings → Privacy & Security → Open Anyway, on Windows SmartScreen More info → Run anyway. Every release states this plainly. Keiko then opens at http://127.0.0.1:1983.

Install with npm

npm install -g @oscharko-dev/keiko

keiko init && keiko start

Run it inside a project with a package.json. The UI opens at http://127.0.0.1:1983 — keiko stop shuts it down, keiko start --port <n> picks another port. Requires Node.js >=24.18.0 <25 || >=26.3.0 <27; the desktop packages bring their own runtime. The coding sidecar ships with the desktop packages and with repository checkouts — the npm install reports it honestly as unavailable rather than pretending.

Honest limits

• The CLI, the UI and the SDK share one product. Surface coverage is intentionally not identical. keiko gen-tests and keiko investigate print a reviewable report but do not persist an evidence manifest.
• The UI can create a local runtime config during first-run setup. To list models, Keiko calls the gateway model list endpoint you configured — credentials stay in your local config.
• Keiko serves loopback only: keiko start and the UI validate a loopback host value, and the server always binds 127.0.0.1. keiko start --port <n> sets the Port to bind (default: 1983).

What's in 1.1

1.1 folds every reviewed customer-facing change since 1.0.5 into one minor bump. The published surface is unchanged from 1.0 — nothing was added, removed or renamed — so 1.x remains the supported line under the same promise.

• The activity log is now a strict machine-reconstruction contract: every record is validated against a versioned registry, support exports refuse unsafe filesystem targets and never silently overwrite, and support analysis explicitly classifies legacy, corrupt, truncated or incomplete evidence.
• The Coding Workbench moves to OpenCode 2 and keeps per-conversation task history so a run's steps stay visible across restarts.
• Voice conversations with the Digital Twin are turn-based, with a simpler audio setup.
• Publishing a stable release is a single unattended button: when the current dev version is already published, the release automation prepares and requests the next reviewed version by itself instead of asking for a manual bump step.
• Chat and workbench polish: the Chat History New button no longer flashes enabled during load, and the workbench composer chip row is removed.

What's in 1.0

1.0 is the first stable major. The published surface is unchanged from 0.3.17 — nothing was added, removed or renamed — so what changes is the promise around it: 1.x is the supported line, and a breaking change to it requires a new major release.

• Updates are production-ready on Windows, macOS and Linux, and a failed update preserves the complete current install.
• The Coding Workbench takes an issue to a pull request in one governed run, and an approved changeset edit now lands instead of expiring beneath the decision.
• Linux x64 joins macOS and Windows as a downloadable package, with its coding runtime shipping qualified and generated code reaching the network only through the gateway boundary.
• Windows installs through a native bootstrap, with the setup executable's digest bound into the published manifest.
• Every Git outcome can be reconstructed from the activity log alone.
• Grounded retrieval is bounded on large workspaces, and local knowledge retrieval runs on a fast approximate-nearest-neighbour index.
• Security: Next.js 16.3.3 closes two critical advisories.

Principles

• Human-controlled by design. You select the task, the autonomy mode and the authority envelope; hard limits fail closed.
• Local-first. Your repositories, memory and evidence live on your machine, and Keiko serves loopback only.
• Evidence over trust. Manifests and audit exports carry counts, scopes and hashes — never raw content.
• Honest state. No silent failure, no green over broken.

Learn more

• oscharko.dev — the product page
• Documentation — architecture decisions, design system, troubleshooting
• Operator runbook — the full operator reference
• Contributing — the quality bar and how changes land
• Security policy — reporting and boundaries
• Report a finding — structured, account-free intake

License

Apache 2.0 — © Oliver Scharkowski