TinyRobot v1.0 Ships a Complete Vue 3 AI Chat Suite with Tool Approval Built In
This gives Vue 3 teams a head start on assembling AI assistants without reinventing chat UI, streaming, and session management, and it puts a safety valve on agent tool calls—users approve destructive or data-modifying actions before they run.
TinyRobot v1.0 from the OpenTiny community bundles a complete AI chat experience into a set of Vue 3 packages. The new TrChat kit wraps the entire chat page—conversation list, streaming messages, input bar, and floating-window mode—so developers can drop a working assistant into an app with one component, or keep their own logic and use only the UI pieces. Three integration paths cover using the built-in runtime, adapting an app's existing conversation logic, or reusing a Kit-managed conversation.
New capabilities focus on control and extensibility. A model selector lets users browse, search, and switch models in one panel, with settings like web search or reasoning intensity mapped to service-specific request parameters via presets. The extension panel unifies MCP servers, Skills, and custom business tools under a single management interface. Tool-call confirmation, new in v1.0, lets applications pause a tool call and ask the user to allow or deny it, with the pending state persisted so confirmation survives a page refresh.
Other additions include a message outline for long conversations, a floating-window layout for side-by-side work, an `input-prefix` slot for labeling multi-line input tasks, and a CLI that generates a chat module into an existing Vue 3 + Vite project. The release also deprecates `McpServerPicker` and `Container` in favor of the new managers.
Tool-call approval is a meaningful safety pattern for agent apps: it moves the human into the loop exactly when an action touches business data, rather than trusting the model blindly.
The package split into Chat, Components, Kit, and CLI makes the library adoptable at different levels—from a full drop-in page down to a single composable—which lowers the barrier to entry for teams with existing chat logic.
The model selector's feature mapping via presets and `mapFeatureValues` shows a practical approach to the messy reality of different model providers exposing different knobs under different names.