What happened
Mika’s GitHub release page says version 0.1.46 was released on November 18. The largest change is a plugin runtime, described as allowing the app to run plugin scripts and expose tool specifications. A plugin manifest can declare tools, permissions and a promptTransform hook. The release also adds environment-variable storage for plugins and a settings page to manage it. Prompt transformation has a timeout fallback, so the hook can fail over rather than remain stalled. The release names two built-in plugins: translate and purge-lite.
The runtime includes several implementation details that shape how plugins are handled. The release notes say plugin parameter directories are writable, tool names are deduplicated, and script output is capped. They do not specify the size of that cap or describe the permission enforcement model. Mika also adds a named custom-instruction layer called Persona, which can be bound to a conversation.
The update broadens how users can build and reuse work in the app. It adds reusable multi-step tasks with sequential execution and result reuse, as well as saved task lists that can be updated and reused with their latest results. Users can fill in missing fields for saved tasks and save tasks from a conversation. The notes also say spawn_agent can launch multiple subtasks in parallel. Separately, scheduled tasks become visible globally per device rather than being filtered by conversation.
Other additions include browsing and importing shared skills from a user-specified GitHub directory, web fetching, and search and fetching support for TinyFish. Mika adds read and write access to user-authorized device folders, per-app operation pacing options—fast, standard or human-like—and audio capabilities covering speech, playback, generation and transcription. The release says lightSteps is enabled by default to divide work between larger and smaller models. It does not state a price, minimum Android version, rollout schedule or availability restrictions.
What the archive adds
New Runtime covered Mika v0.1.45 on November 16, 2026, including its scheduling controls. This release is a new event in the same product thread: it changes scheduled-task visibility and adds a plugin runtime, rather than simply repeating the earlier update. An earlier note on Mika v0.1.13 covered startup, pacing and provider changes.
Trend signal
Mika’s plugin manifests make tools and permissions explicit surfaces that can be composed by an agent app. That supports the pattern of agent-ready software exposing capabilities: the key product boundary is a set of observable, permissioned capabilities, rather than an opaque prompt alone. The release describes declarations and runtime behavior, but does not establish how permissions are enforced in practice.
Why now
The release follows Mika v0.1.45, which included scheduling controls, by two days. In this update, scheduled tasks become visible across the device rather than being filtered by conversation, while the new plugin runtime and task-reuse features broaden what users can configure and repeat. The announcement frames these as part of one product release; it gives no explanation for the timing.
Why it matters
A plugin runtime can turn an agent app from a fixed set of built-in actions into a platform that users can extend. Declared tools and permissions give plugin authors a place to describe what an extension can do, while an environment-variable settings page offers a dedicated configuration surface. Timeouts, output limits and unique tool names are operational details that matter when scripts run inside a larger agent workflow.
The task changes point in a similar direction: saved multi-step routines can preserve work and reuse results, and parallel subtasks can split work rather than requiring one sequential interaction. Global visibility for scheduled tasks may also reduce the chance that users overlook automation because it is tied to a particular conversation. For teams considering Mika, these are useful building blocks to evaluate, not proof of production readiness. The announcement does not document permission enforcement, plugin review, task reliability or measured outcomes, so builders should test those boundaries before relying on extensions for sensitive work.
Limits and uncertainty
The release notes do not give a plugin security model, explain how declared permissions are granted or revoked, or describe whether plugins are sandboxed. They mention a script-output limit but do not state its value. The notes also do not quantify reliability for scheduled or parallel tasks, specify compatibility requirements, or provide benchmarks for lightSteps. No pricing, deployment or access terms are stated. These are release-note claims; New Runtime has not independently tested the runtime or the named plugins.
Reader takeaway
Mika v0.1.46 adds a concrete extension surface: scripts can expose declared tools and permissions, while reusable tasks and parallel subtasks make workflows more repeatable. Builders should treat those as capabilities to test, not as evidence that plugin boundaries are already safe for sensitive work. The next useful detail to look for is how the app enforces permissions and isolates plugin execution.