Frequently Asked Questions

YAAA is a local-first, AI-assisted automation app for building applets and reusable workflows you can inspect, edit, and run on your own machine. It is built around an OAuth AI companion that can inspect applets and editor state through app-owned controls, with work underway to operate every applet plus the Code, GUI, and PDF editors through human-approved commands.

The AI companion connects to Claude through Anthropic and to OpenAI through OAuth or provider credentials you control. It is designed to help inspect applets, read editor state, propose changes, and drive app-owned commands with previews, confirmations, and audit evidence instead of uncontrolled background actions.

No cloud account is required for local-first applet authoring and running local automations. You only connect a provider account or credential when you want the AI companion to use an external AI provider, and those connections are optional.

Yes. YAAA is designed so applets and automation workspaces run locally by default, with optional cloud or provider connections only when you configure them.

YAAA is local-first: user-created applets and automation workspaces run on your machine by default. Optional integrations and AI provider connections are used only when you configure them.

Applets are manifest-first automations you author with an applet.json file and a Lua, Python, or C# entrypoint. Plugins extend the app itself as sealed, signed packages; the Code Editor, GUI Designer, and PDF Editor appear as modular editor tiles only when their plugins are installed and authorized.

Protected applet and plugin packages are encrypted with AES-256-GCM and signed with Ed25519, then denied if they are tampered with or unauthorized. Premium plugins can require a signed entitlement so only the authenticated users designated by the developer can decrypt, install, and run them.

YAAA is designed for local work, so applet authoring and local runs do not depend on a constant cloud connection. Features that require external services, provider credentials, licensing checks, or connected integrations need connectivity when you use them.

You can author applets in Lua, Python, or C#. The language is declared in the applet manifest, the workspace scaffold creates the matching entrypoint, and capabilities are requested through the manifest and permission flow.

Create an applet workspace, choose Lua, Python, or C#, then define the applet manifest and entrypoint. From there you can run it locally, add a GUI, or package it for authorized users.

YAAA does not claim any automation tool is risk-free. Its security model starts with local-first execution, capability-gated sandbox permissions, and protected packages that must verify before they run. Security still depends on your device, connected providers, and the permissions you grant.

Licensing and entitlements decide which protected plugins and applets a user can install, decrypt, and run. A package that is missing the required entitlement, belongs to the wrong user, or fails verification is denied.