Install, connect, control, prove.

Mikie is a semantic context compiler, bounded control runtime, and content-free evidence system for coding agents.

Product boundary

The customer product is the compiled native relay plus its authenticated hosted authority and web account. The editable Python MCP in the source repository is a contributor and research surface; it is not the customer installer and it exposes a different catalog.

The relay serves stdio MCP from the repository you explicitly connect. The hosted service resolves identity, repository authority, entitlement, quota, operation leases, Evidence ingestion, and Meter projections. Neither a model nor a caller can select a different tenant or arbitrary server path.

Install from npm

The public npm package installs the matching native relay for Windows x64, macOS Apple Silicon or Intel, and Linux x64.

For one temporary MCP process:

npx -y @getmikie/cli mcp

For authentication, repository binding, receipt hooks, updates through npm, and Mikie Control:

npm install --global @getmikie/cli
mikie login
mikie connect .
mikie privacy review

The npm launcher contains no relay, pricing, receipt, or model logic. It executes the exact-version native platform package and inherits stdio. Unsupported tuples and missing binaries fail before process creation.

Set up a coding client

From the connected repository, use the release-owned setup adapter:

mikie setup codex
mikie doctor

mikie setup claude
mikie doctor

Setup backs up the existing client configuration, writes only Mikie-owned keys, preserves unrelated MCP servers, and verifies the result. A generic stdio descriptor is available for compatible clients, but a named third-party client is not advertised as supported until its exact integration has saved release evidence.

The exact eight-tool contract

The installed customer relay exposes exactly eight read-only tools. Internal hosted, write, record, benchmark, evaluator, and contributor tools are rejected even if a modified client asks for them.

MCP initialization and tools/list must match this exact ordered catalog. A configured entry alone is not runtime proof; mikie doctor checks initialization, authorization, repository binding, encrypted-outbox readability, and the tool list.

Run Mikie Control

Control runs one immutable, repository-scoped request through the Codex App Server, one Mikie context retrieval, one model-produced patch, deterministic verification outside the model, and at most one precise repair.

mikie control run --request C:\absolute\path\control-request.json --json

The request file freezes the repository, allowed paths, commands, verifier, model, reasoning effort, timeout, and private temporary root. Repository drift, forbidden tools, out-of-scope changes, App Server loss, missing usage, or failed Evidence persistence terminate the attempt. JSON output reports content-free terminal facts and hashes, never prompts, context, patch bodies, verifier output, or credentials.

Evidence and Meter

Eligible provider usage is normalized into canonical content-free Evidence, encrypted in the local outbox before upload, signed by the device, authenticated by the hosted service, and appended to the PostgreSQL ledger. Meter, Shadow, finance, engineering, and receipt views are projections of that ledger.

Exact, calculated, estimated, bounded, and unavailable values remain distinct. Unpriced observations do not become zero. Subscription fees do not become per-turn spend. Planning-only Shadow output does not become realized savings, and Control availability does not become a provider-backed performance claim.

Privacy and consent

Ordinary Evidence forbids source code, raw prompts, model or tool outputs, commands, secrets, credentials, environment values, and raw repository paths. Repository content is processed only inside an authorized, operation-scoped request; it is not an ordinary telemetry payload.

Enhanced Meter telemetry is a separate explicit consent path with retention, export, withdrawal, and deletion controls under Account → Privacy. Core MCP access and billing state do not depend on granting enhanced consent.

Native account downloads

Account installers appear only after the exact platform and client row clears signing, lifecycle, update, rollback, and clean-machine proof.

Until a support-matrix row is advertised, the account page keeps that installer hidden and points to npm. npm package proof does not stand in for Authenticode, Apple notarization, installer repair, secure update, rollback, or clean-machine lifecycle proof.

Troubleshooting and lifecycle

Start with the shortest authoritative check:

mikie doctor

If authentication has expired, run mikie login and then mikie doctor. Use mikie device revoke, mikie logout, and mikie uninstall for normal device and configuration lifecycle work. Do not delete credential lock files or manually edit the keyring vault.