Skip to content

Releases

Ouro UI for Android v0.5.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 10:00
e38acea

An agent's consequential call now asks the person on Android instead of being refused, as it does on Windows (#22). The kit also builds on AppFunctions 1.0.0 (#21), and this is the first release whose files carry a build attestation (#20).

  • OuroConfirm.install(context, actionSet) (bot.ouro.ui.actions, platform views only, so apps without ouro-hx get it) sets confirm on each consequential action that has none. An app's own confirm is never replaced. Call it from Application.onCreate.
    • What the person sees is the composed card's confirm sheet: the action's label as a question, its description, and each prepared value under its label, then Don't and Allow. Don't is the default button.
    • App on screen: the confirmation opens at once.
    • App in the background, an AppFunction call's usual case: a high-priority notification whose tap opens the confirmation. It carries no Allow and none of the values, so the person reads them first.
    • Waiting: the call suspends until the person answers or two minutes pass (OuroConfirm.DEFAULT_TIMEOUT_MS, or your own timeoutMs). Don't, Back, tapping outside, leaving the screen and the timeout all mean no, and nothing runs. The agent gets AppFunctions' denied error with the reason.
    • No notification permission, app in the background: nothing can ask, so the call is refused with OuroNeedsPerson, whose message says why and how to fix it. On Android 13 and later the app asks the person for POST_NOTIFICATIONS, which the library's manifest declares.
    • One answer for one call: each pending confirmation has a fresh 128-bit random id. The confirmation activity isn't exported, the notification's PendingIntent is immutable and single-use, and the screen reads what to show from the pending confirmation, never from the intent, so a stale or forged intent shows and answers nothing.
    • Labels: without describe, each non-null field of the input is a row, its name as words, without idempotencyKey. Pass describe for your own labels, or to keep them when R8 renames fields.
  • An action with no confirm is still refused, so nothing consequential runs that no person agreed to. A person-only action still refuses every agent with core's typed refusal.
  • AppFunctions 1.0.0. The kit builds on androidx.appfunctions 1.0.0, released on 18 November 2026, instead of 1.0.0-rc01.
  • Attestations. release.yml attests every file a release attaches: gh attestation verify ouro-hx-0.5.0.aar --repo ourostack/ouro-ui-android.
  • The sample calls OuroConfirm.install, and its agent console shows an agent's share as asking until the person answers. It adds a button to allow notifications.

Checked on: CI only. Unit tests cover the ask, answer, timeout, permission and id rules in the JVM, and the notification, the screen and its forged and stale ids in Robolectric. On an Android 17 (API 37) emulator, an agent's share through AppFunctionManager asks the person: Allow runs it, and Don't and Back refuse it. With the app sent to the launcher, a notification asks, has no Allow and none of the values, and opens the same confirmation. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue.

Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.5.0"). The Maven files are also attached below.

Ouro UI for Android v0.4.0

Choose a tag to compare

@github-actions github-actions released this 19 Nov 07:12
803227e

Android now draws agent cards sent as A2UI v1.0 messages, as web, Apple and Windows do, by adapting them into Ouro's composed tree (#17).

  • OuroA2UI (bot.ouro.ui.hx.composed) ports core's A2UI adapter (a2ui.mts, core v0.19.0; unchanged in v0.20.0).
    • validateMessages checks a stream of createSurface, updateComponents, updateDataModel and deleteSurface messages against the app's catalog. Its problems come in A2UI's error format, word for word as core writes them.
    • resolveMessages gives each surface's composed tree and data model, with core's rules. A button binding stays a binding only when a field writes that exact path, and a value read from data is never followed as a binding. A button's @label goes last, a pointer through __proto__, constructor or prototype is refused, and every name is the catalog's own.
    • actionMessage wraps a person's press in A2UI's action message. messagesOf reads structuredContent.a2ui, and mcpAppToolResult writes it.
    • A surface may go at most 24 components deep, resolve to at most 5,000 nodes, and copy at most a million characters out of its data, as on Windows. Core has no such limits yet (ourostack/ouro-ui-core#100).
  • OuroComposedState.receive takes structuredContent.a2ui as well as structuredContent.ouro, and receiveA2UI returns A2UI's problems. The resolved tree must pass OuroComposed.validateTree, so every button is exactly the catalog's. A failing stream shows the same "This card can't be shown" alert. OuroComposedSurface(state, ...) takes onA2UIAction, which receives each press as A2UI's action message.
  • The sample shows the same card arriving as A2UI messages on its a2ui screen (assets/agent-card-a2ui.json).
  • README: a new "Agent cards" section covers both formats, how to wire each from a tool result, and what's still missing.

Checked on: CI only. The unit tests resolve all 13 of core's A2UI conformance cases to their expect, byte for byte, and check every tree they give against the tree validator. A Robolectric test draws an A2UI card and presses it. On an Android 17 (API 37) emulator, the sample's A2UI card is checked the way its composed card is: its buttons are the declared actions, add sends A2UI's action message and runs, share runs only on confirm, and place order hands off. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue.

Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.4.0"). The Maven files are also attached below.

Ouro UI for Android v0.3.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 12:45
8ba5196

An agent can now update a composed card it sent instead of resending the whole card, as core 0.19.0 adds. Android applies the update, and the person keeps what they entered.

  • OuroComposed.applyTreeUpdate: applies an update, all or nothing, as core's applyTreeUpdate does. It ports treeUpdateProblems too.
    • An update is { nodes?, data? }. Each node replaces the tree's one node with its id. Each data entry sets a value at a JSON pointer, and null deletes it.
    • These are refused: an id the tree lacks, an id that several template instances share, an unsafe or relative path, and a list written past its length.
    • The tree it gives is validated in full, so an update can't relabel a button or loosen its consent.
  • Reading an update: OuroComposed.read takes a tool result's structuredContent.ouro.update as Read.Update.
  • OuroComposedState and rememberOuroComposedState: they hold the card an agent sends and then updates. Call receive(result) with a tool result or update(update) with an update, and draw it with OuroComposedSurface(state, ...).
  • The person's answers stay across an update, except where the agent changed the value or the list item it sits in, as web's ComposedSurface does. The other overload, OuroComposedSurface(tree, catalog, ...), now keeps answers across a new tree or data the same way; before, it started the fields over.
  • A short alert: a tree or update that fails the checks now shows "This card can't be shown", as web does, where the surface used to draw nothing. While an update can't apply, the last card that did, with what the person entered, waits for the next one.
  • The sample: the composed screen shows the agent's update, and the emulator checks that the person's typing survives it.
  • Core 0.19.0: the pin moved from 0.18.2. Core's five tree-update conformance cases (standard/hx/composed/updates/) are vendored by tag and SHA-256, and all five pass.

Checked on: CI only. The Robolectric tests run core's claims, the composed and update cases, and the snapshots. The sample's X-ray and its composed card, with the update, run on an Android 17 (API 37) emulator. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue.

Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.3.0"). The Maven files are also attached below.

Ouro UI for Android v0.2.2

Choose a tag to compare

@github-actions github-actions released this 18 Nov 07:27
1ff3aea

A pointer in a composed tree can no longer name an object's prototype, and every name a sender chooses must be the catalog's own. This follows core 0.18.2 (ourostack/ouro-ui-core#91).

  • Pointers stay in the data:
    • validateTree refuses a field's value or a bound input whose pointer has a segment __proto__, constructor or prototype.
    • setPointer writes nothing through one.
    • The new OuroComposed.isSafePointer and isDataPointer say whether a pointer is allowed. Kotlin's maps have no prototype, but Android refuses the same trees core does.
  • Names are the catalog's own: a component, action or input field a sender names is taken only when the catalog itself has it, and a catalog may name only Ouro HX's own components. Android already worked this way; tests now pin it.
  • A2UI streams: Android reads none, so core's checks on template paths and updateDataModel don't apply here.
  • Core 0.18.2: the pin moved from 0.18.1, by tag and SHA-256.

Checked on: CI only. The Robolectric tests run core's claims, the composed cases and the snapshots. The sample's X-ray and its composed card run on an Android 17 (API 37) emulator. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue.

Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.2.2"). The Maven files are also attached below.

Ouro UI for Android v0.2.1

Choose a tag to compare

@github-actions github-actions released this 18 Nov 06:55
acdd43e

A tree whose confirm sheet would show the person anything other than what is sent is now refused, as core 0.18.1's validator says (ourostack/ouro-ui-core#88).

  • Confirm rows are checked: validateTree compares each confirm-sheet row with the rows the catalog gives for the prepared input. A tree is refused if its sheet:

    • drops or reorders a field, or changes a label;
    • changes a value, or hides the real value in raw on a field that isn't an id;
    • binds a row to a different field.

    Only an id field (one with shownAs) may show a name, with the sent id beside it. The surface still builds its rows from the catalog and the input.

  • Undeclared inputs are refused: a button input the catalog's action doesn't declare would be sent with no row on the sheet. Android checks the catalog's own keys, so a key named like a JavaScript prototype member is refused too; core's check lets those through (ourostack/ouro-ui-core#91).

  • The label resolver names only id fields: every other row shows exactly the value sent.

  • Core 0.18.1: the pin moved from 0.18.0, by tag and SHA-256.

Checked on: CI only. The Robolectric tests run core's claims, the composed cases and the snapshots. The sample's X-ray and its composed card run on an Android 17 (API 37) emulator. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue.

Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.2.1"). The Maven files are also attached below.

Ouro UI for Android v0.2.0

Choose a tag to compare

@github-actions github-actions released this 18 Nov 05:24
9334986

Android draws Ouro's composed tree: the UI an agent composes for a person, checked against your app's catalog, where every button is one of your declared actions with its consent class.

  • OuroComposedSurface: draws the tree from an MCP tool result's structuredContent.ouro (OuroComposed.read) with Ouro HX.
    • Read and write buttons press at once.
    • A consequential button opens a confirm sheet built from your catalog and the input, and presses only on confirm.
    • A person-only button calls onHandoff and never presses.
    • Fields write the data model, and a bound button sends what the person entered.
    • Nothing in it lets an agent press: an agent calls the action through its AppFunction.
  • bot.ouro.ui.hx.composed: core's composed.mts (v0.18.0) ported to Kotlin: the catalog, validateTree, JSON Pointer reads and writes, resolveButton, personPress and confirmSheet. It's tested against every tree core's conformance cases hold, and core's forged trees are rejected for the same reasons.
  • Four components from core's specs: OuroCheckbox, OuroTextField, OuroSeparator and OuroDescriptionList. Every claim their specs make is checked.
  • LocalOuroSurface: components inside an outlined OuroCard measure contrast against the card, not the page.
  • Core 0.18.0: the pin moved from 0.15.0. scripts/provenance.mjs also vendors files the dist doesn't carry (the conformance cases), by the tag's commit and SHA-256.

Limits: Android reads no A2UI messages: send Ouro's tree, not an A2UI stream. The default image loader fetches https only. A confirm sheet's rows come from your catalog, not the tree, because core's validator doesn't check them yet (ourostack/ouro-ui-core#88).

Checked on: CI only. The Robolectric tests run core's claims, the composed cases and the snapshots. The sample's X-ray and its composed card run on an Android 17 (API 37) emulator. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue; collaborators are welcome.

Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.2.0"). The Maven files are also attached below.

Ouro UI for Android v0.1.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 04:22
653bd51

The first Ouro UI kit for Android: a Compose theme and four components for people, and AppFunctions for agents, from one action declaration.

  • ouro-hx 0.1.0: OuroTheme from core's tokens (six themes, light and dark, increased contrast, reduce motion), and OuroButton, OuroBadge, OuroCard and OuroItem, rendered by hand from core's specs (vendored by SHA-256 in core-provenance.json).
  • ouro-actions 0.1.0: one path for a person's press and an agent's AppFunction call. A person-only action refuses agents with core's typed refusal. A consequential one is refused until the app's confirm asks the person.
  • Actions from core 0.15.0: core's Android generator (ouro-actions-android.mts) turns declarations into OuroActions.kt and doors.json; the kit vendors it with the specs and claims by SHA-256.

Checked on: CI only. Core's claims for all four components run in Robolectric, the snapshots cover light, dark, increased contrast and 200% text, and the sample's X-ray runs on an Android 17 (API 37) emulator. The maintainer owns no Android device, so nothing here has run on real hardware yet. If you have a device and something differs, please open an issue; collaborators are welcome.

Install: add maven { url = uri("https://ourostack.github.io/ouro-ui-android/maven") } to your repositories and implementation("bot.ouro.ui:ouro-hx:0.1.0"). The Maven files are also attached below.