Otto

Activation Files

Otto uses activation files to validate your license and determine which products are available for each application. This page explains how activation works and how to troubleshoot common issues.

How Activation Works

When the Otto VS Code extension connects to a project, it communicates with the Otto MCP server to validate your license. The server checks:

  • Your account has an active subscription
  • The repository is associated with a registered application
  • The requested products are included in your plan

License validation happens automatically and is transparent to the user. The extension caches the validation result locally so repeated checks do not require network calls.

License Validation Flow

  1. Extension sends a license check request with your JWT and application ID
  2. The Otto server validates the JWT signature (RS256)
  3. Subscription status and product entitlements are verified
  4. A signed activation response is returned to the extension
  5. The extension caches the response for subsequent requests

Troubleshooting

License validation failed

Ensure your subscription is active in the Otto dashboard. Check that the repository is associated with an application that has the requested product enabled.

Product not available

The product you are trying to use may not be included in your current plan. Upgrade your application's product selection in the dashboard.

Offline access

Otto requires an internet connection for license validation. Cached validations expire after a short period. If you are working offline, functionality will be limited until connectivity is restored.