The ask
On October 12 Nikolas asked whether Aria in Kremio was “just a plugin”, and whether other integrations could use the same path. Half yes: on the server, any Frappe app could already add actions through Kremio Connect’s kremio_actions hook. But the app had only four compiled-in places to show anything, and nothing generic to draw another app’s action. By October 15 the ask was explicit: a way for people to plug their ERPNext and Frappe customizations into Kremio, dynamically if possible.
The constraint
So there were three options:
- The site describes the UI, and the app draws it natively. Chosen.
- Downloaded JavaScript plugins. Ruled out by those platform rules.
- An in-app web view for Frappe app UIs. It would have overturned three earlier decisions against web views and put the app’s sign-in token next to site scripts.
That evening Nikolas approved a plan in four slices: an extension API, custom actions configured in the desk, an Apps section opened in the system browser, and later TypeScript plugins for custom builds.
Slice 1: actions that say where they go
The unit is a Kremio Connect action: a Python function, an input model and a capability (read, draft or commit). An app can now add placements to it and return typed results. From the developer guide:
@action( name="my_app_close_todo", title="Close", description="Close an open ToDo.", capability=Capability.DRAFT, input_model=CloseInput, ui=[ DocumentButton( doctype="ToDo", when="eval:doc.status == 'Open'", prefill={"todo": "doc.name"}, confirm="Close this ToDo?", ) ],)- The form comes from the input model’s JSON Schema, drawn with the app’s own field renderers. An input the app can’t draw, such as a list or a nested model, leaves the action callable without UI and logs a warning.
- Conditions and prefills run on the phone, with the same
depends_onevaluator the app already uses for forms. A button whose condition can’t be evaluated is hidden. - A placement only decides what the app shows. The action still runs as the user, checks permissions itself and writes an Action Log row.
- Results are typed: a message, a document, a new unsaved document for the person to check and save, a list, Markdown, a table or a file. Every result carries a message, so an older app shows something for a kind it doesn’t know. Nothing in the API version changed.
Slice 2: custom actions without Python
A System Manager can point a Kremio Custom Action at any whitelisted method, or an API Server Script, and place it as a button or a tile. The plan states the trade-off plainly: “Kremio can’t know what an arbitrary method does, so the capability is the admin’s word.” That’s why only System Managers create them, they stay off (The Model Context Protocol, an open standard that lets AI apps such as Claude call tools on a server. On our sites, the MCP server is how Aria, our agents and connected AI apps read ERPNext and draft in it.) unless ticked, and commit-class ones never reach MCP. ERPNext’s usual Create flows come as seven switched-off records, from Quotation to Sales Order through Purchase Order to Purchase Invoice. Slice 1’s renderer handled all of it, so the app didn’t change.
Slice 3: Apps, signed in, in the phone’s browser
The home screen lists the site’s Frappe apps, such as Frappe HR and the desk, and opens them in the system browser: SFSafariViewController on iOS, Custom Tabs on Android, never a web view. Each tap asks the site for a fresh single-use link, valid for 60 seconds, which signs the browser in and redirects to a path on the same site. Only the app’s own sign-in can get one, and signing out of Kremio ends the browser sessions it started.
Frappe’s own login_via_key has no redirect target and allows five logins an hour by default. And Frappe revokes OAuth tokens with a direct database write that runs no hooks, so Kremio Connect wraps the revocation endpoint to end those browser sessions.
What the emulator found
The live test passed: run through the app’s own code against a bench, it signed in, listed the apps, opened a link, had the same link refused the second time, and signed out. Then we tried it on an Android emulator. The app listed ERPNext, Frappe HR and the desk, and tapping Frappe HR opened Chrome. On the first try, Chrome landed on the login page.
The live test never opened a link in a client that still held an ended session’s cookie, and that’s the state a real browser is usually in.
Where it stands
All three slices went from an approved plan to merged in under a day, and reached the app’s 0.4.0 Android test build on the evening of October 16. What’s verified and what isn’t:
- Apps: checked on an Android emulator, not on a phone, and not on iOS. “Open on the web, signed in”, which uses the same links from a document, wasn’t tried on a device or an emulator.
- Slice 1’s buttons, tiles and action screen: checked through screen tests and a live suite against a bench, not on a device.
- Slice 2: Sales Order to Delivery Note checked through the app’s own code against a bench.
- Slice 4, plugins for custom builds, hasn’t started.