Repository navigation
v0.1.0-pilot.5
Pre-releaseKemiri v0.1.0-pilot.5
Aiki is now Kemiri, with a new home at https://kemiri.dev. This remains an early,
assisted pilot. A paired device has full backend access, including files, shell
and provider spending. Use your own accounts and repositories; this is not a sandbox.
What's new since pilot.4
- Videos play again in the installed web app. Private videos and partial
downloads no longer enter the app-shell cache. If playback fails, the viewer
shows “This video can't play here” and offers Download, Open in new tab and
Try again instead of leaving a black 0:00 player. - One name, one command:
kemiri. The oldaikicommand andAIKI_*process
settings are removed. At startup, existing server.env settings are rewritten
toKEMIRI_*, with the original saved as server.env.bak. Existing Kemiri keys
win conflicts. Rename any settings you supply through your shell or service
environment yourself before restarting. Do not rename data/config folders. - Releases now contain only
kemiri-*downloads andkemiri/source archives.
Android custom links usekemiri://. Historical task links still work;
new commits use the Kemiri-Task trailer.
Coming from pilot.2 or pilot.3?
Since those releases, HTML reports open as real pages on web and Android, follow
light/dark mode, offer Print and retain up to 20 saved versions. A built-in
html-artifacts skill helps agents make readable reports. The phone's page viewer
fills the screen and supports scrolling and zooming. Older chat history loads
again when you scroll back. MCP presets, command servers and reviewed JSON imports
add choices to the remote MCP support already present in pilot.2. After the manual
bridge upgrade, supported supervised installs offer owner-confirmed Update now
from web or Android, with health checks and automatic code rollback; no unattended
updates. The button updates your backend, not your APK.
Update while stopped
Back up config/state while stopped and repositories separately. Stop a foreground
backend with Ctrl-C. If using an installed user service, remove it with the old
command's service remove first; after updating use kemiri service install
instead of kemiri start. Do not uninstall the app or delete pairing/data folders.
Pilot.2 or pilot.3 — first install the bridge:
aiki update --version v0.1.0-pilot.4
kemiri update --version v0.1.0-pilot.5
kemiri startPilot.4 — normal standalone install (Linux glibc x64/ARM64, macOS ARM64):
kemiri update --version v0.1.0-pilot.5
kemiri startPilot.4 also installs aiki; its update command works for this binary transition,
but the old command is removed after activation. Use kemiri thereafter. Projects,
paired devices, credentials and existing installation paths stay in place.
Rollback changes code, not data; keep your backup.
Bun/source installs, Intel Macs and Linux musl (Alpine): pilot.4's embedded
updater still requires an aiki/ archive and cannot accept pilot.5's kemiri/
archive. After reaching pilot.4, use pilot.5's installer, not its embedded updater:
curl -fL https://github.com/MitzaCoder/kemiri/releases/download/v0.1.0-pilot.5/install.sh -o kemiri-install.sh
curl -fL https://github.com/MitzaCoder/kemiri/releases/download/v0.1.0-pilot.5/install.sh.sha256 -o kemiri-install.sh.sha256
# Compare: shasum -a 256 kemiri-install.sh with the downloaded checksum; read the script.
sh kemiri-install.sh --version v0.1.0-pilot.5 --no-service
kemiri startIf originally installed with --dir, pass that same absolute --dir to the new
installer. Keep custom KEMIRI_INSTALL_DIR/KEMIRI_CONFIG_DIR settings. Do not choose
a new folder. --runtime bun is supported by the new installer. On this source
fallback path, a pilot.4-written aiki launcher can remain: it selects pilot.5
and is harmless. Use kemiri; a later activation removes the owned old launcher.
Direct installed
pilot.2/3 updates to pilot.5 are not supported: go through pilot.4.
Fresh install: use the install guide
or download and review https://kemiri.dev/install.sh with the explicit pilot.5 tag.
Android: get the signed APK from the release page
and install over the old app, without uninstalling. Public application ID remains
io.github.mitzacoder.aiki; the signing key is unchanged. VersionName is
0.1.0-pilot.5, versionCode 1000005 (pilot.4: 1000004). Check the APK hash and
certificate in RELEASE-MANIFEST.json. A private/debug install may use another key.
Known limits and help
Linux is the tested host path; macOS and Windows through WSL remain experimental.
No signed/notarized Mac binary. Android needs Android 12+, a backend reachable over
HTTPS and an awake computer; the APK is not a tunnel. Real-network Android pairing
and native macOS service updates still need acceptance. There are no phone push
notifications. Review MCP permissions and command arguments before enabling tools.
Write to support@kemiri.dev with your version and redacted symptoms. Never send
credentials, pairing links or private session data. The published RELEASE-NOTES.md
adds the exact commit, signed APK hash and certificate from RELEASE-MANIFEST.json.
Published build identity
- Source commit:
c4602ec0def630d2d95d4540155512af175be788 - Android:
0.1.0-pilot.5, versionCode1000005, packageio.github.mitzacoder.aiki - APK SHA-256:
a6e8234bca599e5fa607a4cb58dbee8ddbfb943c5a91cd4b00c794c38260c4f8 - Signing certificate SHA-256:
a97bdfae948d34c2589afb4bc78acce22f079d51e6aaa2e4025f7d7d38e611e2