No. It is designed primarily as a self-hosted application you run on your infrastructure or workstation. You control networking, TLS, and who can reach the service.

No. Core features work over the web UI and HTTP API. MCP and integration with the rich skill ecosystem on the Claude community are optional when you want assistants or a skill runtime to consume packaged capabilities. We fully support that path: follow the user manual to install the skills you prefer, use the product’s built-in security checks to validate them, and execute with confidence.

No — it amplifies what your team can do. Think of it as a capable assistant that drafts and suggests; your team reviews, decides, and owns the outcome.

Sensitive data flows depend on your configuration: local execution, which models you call, and which external services you enable. Run data-protection assessments before processing regulated data. With this product’s design, interactions are auditable and can be reviewed in a visual way—helping security teams verify behavior instead of working blind.

Many automation tasks touch the desktop, filesystem, or internal APIs. Keeping execution close to the environment reduces latency and can simplify compliance—at the cost of you maintaining the runtime.

Yes—see the Visual Studio Marketplace listing or download a VSIX. The Automation Skill Builder app must still run locally; extensions only embed the UI. A Microsoft Office add-in remains under evaluation.

Vision stacks often download models on first use. Expect a longer cold start; subsequent runs are typically faster. See the manual for warmup and skip flags.

Community users can ask questions in the public forum — response times vary. If your team needs reliable support with a guaranteed response, check out our professional plan.

See the user manual for OS support and optional Python / Node.js prerequisites.