AI assistant for business apps

Enterprise

The assistant is for applications where users need to ask about live records and sometimes change them. It uses the app’s own registry and handler permissions, then keeps a person in the loop for writes.

The product flow

1. The user asks a question in the app.
2. The server builds a tool catalog from the composed registry and the caller’s access rules.
3. The model searches or reads through ordinary Kumiko query handlers.
4. A write becomes a proposal with the handler, declared risk, and proposed values.
5. The user runs it, opens the normal form for review, approves it for future low-risk use, or drops it.

The Assistant walkthrough shows this flow against a real service-desk example. The agent-ready guide shows the handler descriptions and risk declarations the app owns.

Why this belongs inside the app

Requirement	Kumiko Enterprise behavior
Tool visibility	The catalog is filtered for the current caller. A handler without a description stays invisible.
Write safety	Approval mode proposes writes. The default does not dispatch them directly.
Identity	Approved handlers run as the calling user, with normal access and validation.
Tenant policy	Mode, caps, provider, and approval rules can be tenant-scoped.
Audit	Executed assistant tool calls sit beside the application’s audit trail.
Data lifecycle	Conversation turns use the same personal-data and erasure model as other user-owned data.

Start with the runnable example

AI agent basic is a small service desk. The agent can search and close tickets with approval, while a high-risk purge operation can never become an unattended action.

Build your own assistant

The runtime is optional. You can build an app-owned chat surface around agent-tools, your own model client, and ordinary Kumiko handlers. Enterprise provides the maintained tool loop, approval model, caps, voice path, and persistence. A custom assistant remains responsible for its own conversation storage, provider errors, UI, policy, and security review.