Observe.
Start with the request and a fresh, verified view of the browser.
For the work between your ideas.
A question to research. An app to navigate. A presentation to make. Orchestrator v1.5 brings agentic planning, browser workflows, and MCP tool routing into your local AI workspace.
OPT-IN IN KIRA / LOCAL APPLE SILICON RUNTIMEExplore the work v1.5 is being developed for. Each pathway uses a compatible adapter, while KIRA’s runtime handles tools, permissions, and results.
The browser pathway works with Diagonal Browser observations, checks current targets, and carries verified results into the next decision.
Compare these two pages, note the differences, and give me a brief with source links. Ask before submitting anything.
Low, Medium, High, or Diagonal. Higher effort gives the controller more room to review a browser decision and recover from a problem.
One proposal per browser decision, with a larger allowance for steps and corrections than Low.
Maximum allowances, not speed or success promises. Up to 3,072 generated proposal tokens and a 4-minute time cap. Higher effort can take longer.
Start with the request and a fresh, verified view of the browser.
High and Diagonal compare multiple proposals against the same evidence.
Only the selected proposal reaches a tool. Its actual result informs the next step.
Diagonal thinking is an external controller that reviews proposed actions. Browser proposal ranking is not a general-purpose truth verifier; non-browser tasks currently use one proposal per decision.
Useful autonomy comes from the whole system: the model, the tool handlers, and the evidence returned by each action.
Compatible adapters run over a frozen, 4-bit Gemma 4 E4B base through MLX on Apple Silicon.
KIRA’s existing handlers check permissions and validate accepted tool blocks before execution.
Fresh browser observations and actual tool results guide the next decision and any completion claim.
Live 1 handles everyday text and native voice conversations. Orchestrator v1.5 is the separate opt-in profile for planning and tool-driven work.
Meet KIRA Live 1Orchestrator v1.5 is selectable in KIRA’s model menu. Development continues across browser workflows, connected tools, and presentations. Orchestrator V1 remains the default.
“The everyday model” describes its role in KIRA. Broader real-world reliability is still being evaluated, especially for fully autonomous presentation creation.
Explore KIRA on GitHubDiagonal controller, local development fixtures.
Diagonal controller, local development fixtures.
These small suites were used during development and involved more inference. They do not establish a general success rate, frontier capability, or reliable performance on all live websites.
The sparse architecture has an 11.804B logical parameter bound, including cloned, frozen expert layers. Around 29.6M adapter and router parameters were trainable per checkpoint. This is adapter training over a frozen base, rather than 11.804B distinct trained weights.
A dedicated presentation adapter proposes research, image, and slide actions. KIRA’s slide specialist writes and verifies the PPTX. A later image-tool continuation was selected for this branch on 11 October; a single source-backed topic produced a verified deck. That narrow trial is not a broad quality benchmark.
Compiled from the repository’s ORCHESTRATOR_V15_KIRA_PROFILE.md, the Diagonal-level experiment notes, presentation evaluations, and the active control/browser/presentation manifest. The manifest’s latest selection is used where it supersedes earlier presentation notes. Reviewed 12 October 2026.
Local inference requires a working Metal environment. Availability of a profile does not guarantee every workflow will complete.