Repository navigation
v0.1.0-pilot.4
Pre-releaseKemiri v0.1.0-pilot.4
The first Kemiri release, previously called Aiki. This is still an early, assisted
pilot: run coding agents on your own computer and follow their work in a browser
or Android. Use your own repositories and provider accounts. A paired device has
full backend access, including shell, files and provider spending. This is not a
sandbox or a shared hosting service.
What's new since pilot.3
- The Kemiri name. The app and command are now Kemiri. The old
aikicommand
andAIKI_*settings still work. Existing installation folders, credentials,
pairings, projects and settings stay in place. Do not rename or delete them. - HTML artifacts open as pages, on web and Android, with a source view when
needed. Pages follow your theme, offer Print and can open in a separate web tab.
Android's page fills the viewer and supports scrolling, panning and zooming. - Artifact history. Saving the same filename on a task updates one card with
previous/next version controls. Up to 20 snapshots are retained; downloads use
the selected version. Existing cards remain available as version 1. - A bundled
html-artifactsskill gives agents report, proof index, dashboard
and slide templates. It loads only when needed; your own design instructions
take precedence. Project settings can optionally block page connections and
forms. That switch is not a guarantee of an offline page: permitted images,
media, CDN requests and external links can still send data. - Older conversation history loads again when you scroll back.
- Owner-confirmed backend updates, from web or Android after this first manual
upgrade. Review the version and notes, then confirm. The backend waits for running
tool calls, not whole agent turns; Cancel is available before restart. An unhealthy
new backend automatically restores the previous code. No unattended updates. - More MCP choices. Search developer-service presets, run command-based MCP
servers and review JSON imports before adding them. Presets explain sign-in and
permissions; they do not connect or enable tools automatically. - Roomier MCP/artifact dialogs and quieter update notices. The temporary
top-level-only board task filter has been removed.
How friends update
From pilot.3 (also pilot.2 or pilot.1): back up state/config while stopped and
back up repositories separately. Stop the foreground backend with Ctrl-C, then:
aiki update --version v0.1.0-pilot.4
kemiri startaiki start still works too. For an installed user service, stop it first with
aiki service remove, run the update above, then use kemiri service install
instead of kemiri start. The old installed updater deliberately downloads
compatible aiki-* assets; this release also publishes canonical kemiri-* assets.
No re-pairing, folder move or uninstall is needed. Pilot.3 lacks the new updater
API/supervisor, so use this stopped CLI update once before trying Update now.
A code rollback does not undo database migrations; keep your backup.
Fresh install: see the install guide.
curl -fL https://github.com/MitzaCoder/kemiri/releases/download/v0.1.0-pilot.4/install.sh -o install.sh
# Read install.sh and verify the release checksum before running it.
sh install.sh --version v0.1.0-pilot.4 --no-service
kemiri startIn another terminal run kemiri open, then kemiri pair. Keep the one-time pairing
URL/code private. The website bootstrap is at https://kemiri.dev/install.sh
until the Kemiri domain cutover; download/read it first and keep the explicit
--version v0.1.0-pilot.4 argument.
Android: install the new APK
over the old one; do not uninstall. The package remains io.github.mitzacoder.aiki
and the owner signing key is unchanged. VersionName is 0.1.0-pilot.4, versionCode
1000004 (pilot.3 was 1000003). Compare checksums and the certificate fingerprint
in RELEASE-MANIFEST.json with the owner's invitation. Private/debug installations
may use a different key. The APK is not updated by the backend update button.
Known limits
- Linux is the tested host path. macOS and Windows through WSL are experimental;
native macOS service update acceptance is still needed. Linux binaries need
glibc; unsupported binary platforms use the private-Bun fallback. macOS binaries
are not signed/notarized. - Android needs Android 12+, a backend reachable over HTTPS and an awake computer.
The APK supplies no tunnel. Keep authentication on and approve matching pairing
codes in an already paired browser. A real-network pairing check is still needed
before inviting phone use; local preparation does not certify it. - No phone push notifications in this pilot. Ordinary foreground use needs no
Google account or Firebase setup. - MCP tools have your backend's authority. Review imports, permissions and command
arguments. Preset sign-in may need a vendor account or registered OAuth app.
Send redacted symptoms and version details, never credentials, pairing links or
session data. Before publication the owner appends the exact source commit, APK
hash and signing certificate to the draft's RELEASE-NOTES.md.
Exact release identity
- tag:
v0.1.0-pilot.4 - commit:
4e3f658c2b3dd4d832b451d7f96381540849a9ab - package:
io.github.mitzacoder.aiki - versionName:
0.1.0-pilot.4 - versionCode:
1000004 - apkSHA256:
1d1a9d04c18cc55ee5b2587543d0a56cd47a59c0ad22770b51ba5390d80c91fc - certificateSHA256:
a97bdfae948d34c2589afb4bc78acce22f079d51e6aaa2e4025f7d7d38e611e2