A plugin has three parts: a capability manifest, backend logic, and a frontend UI. Develop locally, validate in a sandbox, sign and package, then publish with one click.
Write a manifest with the SDK, declaring inputs, outputs, permissions, and the human-facing UI (form / preview).
Implement the capability logic to run in a sandbox; I/O follows one contract (input file + result file), with error normalization handled by the SDK.
The host renders forms and previews from the schema with zero UI code; rich interfaces run as sandboxed embeds.
Run on the local development platform for real: the same input produces byte-identical results, and the AI tool and human UI behave the same.
Sign and package as .tueopkg, submit for review, and publish to the capability marketplace for procurement, licensing, and metering.
No more claiming "I did it" — in real repositories AI reads code, edits files, runs tests, and produces MRs, yielding real diffs and branches.
Tool family: read files (including image, PDF, and spreadsheet parsing), precise replacement, run shell, code search, directory browsing, and web search and scraping.
Real-time event streaming for long sessions, permission and approval prompts, and folder-trust confirmations — every action is confirmable and auditable.
Invokes work orders, knowledge, attachments, and other business capabilities via MCP — business data enters the engine through a single path, and credentials are never passed down.
Pure text models can still see and hear: images are described by a vision model, audio runs through a built-in runtime, and model routing is decided server-side.
Subagents run in parallel or nested by task complexity, and spawning one requires confirmation before it runs — enforced, not left to prompt conventions.
Identity boundaries, credentials never leaving the server, and a traceable patch ledger with provenance — a coding core private customers can trust.
@tueo/plugin-sdk is the single source of truth for capabilities across the four-layer architecture. One TypeScript definition yields types, validation, and documentation at once.
Backends run in a sandbox with network isolation, credential injection, and full audit; without a network grant, execution is fully offline.
Capability manifests are Ed25519-signed with three trust tiers — official, partner, and community; tampering fails verification and blocks installation.
One capability contract: AI employees call it as a tool, business users use it as a UI — no need for two codebases.
Review, publishing, versioning, permission declarations, and install consent — publishing brings a capability under enterprise procurement governance.
Publish to the Capabilities marketplace, where tenants procure, license, and meter it — managing capabilities as assets.
17 layouts plus 4 design languages; one DSL produces an HTML preview and an editable .pptx (preview equals export); existing PPTs inherit colors and fonts with one click.
AI handles extraction; a rules engine handles deterministic validation (format, dates, quantities); green-yellow-red review preview — human review for under <1% of cases.