Repository navigation
v0.1.0-pilot.3
Pre-releaseAiki v0.1.0-pilot.3
An early, assisted pilot: run coding agents on your own computer, then 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.2
- Fixed “Could not start MCP sign-in” with Notion on local installs, on both
localhostand127.0.0.1. Sign-in errors now explain the reason more clearly. - Copy sign-in link lets you finish MCP sign-in in another browser. If it
cannot return to the initiating app, copy its callback URL and paste it there. - The bottom-left corner now shows your backend version and an update available
notice. Open it for Settings → About and release notes. Updates stay manual.
Install or update
See the install guide
for prerequisites and reviewed download steps.
curl -fL https://github.com/MitzaCoder/aiki/releases/download/v0.1.0-pilot.3/install.sh -o install.sh
# Read install.sh before running it.
sh install.sh --version v0.1.0-pilot.3 --no-service
aiki startIn another terminal, run aiki open, then aiki pair. Keep the one-time pairing
URL/code private; connect a provider and choose a project. The short installer is
curl -fsSL https://aikilabs.dev/install.sh | sh; it checks the release installer's
checksum. Download and read it first if you prefer.
From pilot.2: stop Aiki and back up state/config and repositories, then run:
aiki update
aiki startPilot.2 already follows its saved pilot channel, which includes later pilots and
stable releases. No --version is needed unless you deliberately switched channels
or want an exact tag. Nothing updates or restarts automatically. For a user
service, stop with aiki service remove and start with aiki service install
instead; for foreground use, stop with Ctrl-C. A code rollback does not undo
database migrations. If you added the AIKI_ALLOWED_ORIGINS workaround for Notion,
you can keep or remove its local-origin entries after upgrading. Preserve any
other trusted origins you still need.
From pilot.1: use aiki update --version v0.1.0-pilot.3 once while stopped to
acquire pilot-channel support, then start Aiki. That first update may use Bun.
Android: install the new APK
over the old one; do not uninstall. It uses the same owner signing key and package
io.github.mitzacoder.aiki, versionName 0.1.0-pilot.3, versionCode 1000003
(pilot.2 was 1000002). Check its checksum and the certificate fingerprint in
RELEASE-MANIFEST.json against the owner's invitation. Private/debug installations
may have a different key. Settings → About and licences has dependency notices.
Known limits
- Linux is the tested host path. macOS and Windows through WSL are experimental.
Linux binaries require glibc; macOS x64 and Linux musl use the Bun fallback.
macOS binaries are not signed/notarized. - Android needs Android 12+, your own backend reachable over HTTPS and a computer
that stays awake. The APK supplies no tunnel. Keep authentication on and approve
the matching pairing code in an already paired browser. - No phone push notifications in this pilot. No Google account or Firebase setup
is needed for ordinary foreground use. - MCP tools run with your backend's authority. Review permissions and approval
arguments. Notion requires an account before consent. Remote/source backends
still need an explicitly trusted callback origin.
Expect rough edges. Send redacted symptoms and version details, never credentials,
pairing links or session data. The owner adds exact source/APK/certificate details
to the draft's RELEASE-NOTES.md before publication.
Exact release identity
- tag:
v0.1.0-pilot.3 - commit:
20b0e10752a934ceaec0831034293944417cbc8e - package:
io.github.mitzacoder.aiki - versionName:
0.1.0-pilot.3 - versionCode:
1000003 - apkSHA256:
85c079c1be0f8b30cbbabad220e962664c48d5554373d86167807645e1c68a84 - certificateSHA256:
a97bdfae948d34c2589afb4bc78acce22f079d51e6aaa2e4025f7d7d38e611e2