A module's version is <tenant>.<generation>.<AppSite build count>, and every module publishes it at /version.json. An update is available when AppSite's generation is higher, or its build count is higher in the same generation. A module served from AppSite itself is always current; your own custom apps have no AppSite version; a version that cannot be read is shown as unknown, with the reason.

/billing shows the numbers tenantUsageSummary reports — the same ones as the AI module's Usage page — and the server's own verdict for the AI module. The extension counts nothing itself.

The command palette also has Ask the CLI…, CLI: Doctor, CLI: Tools on This Computer and CLI: Open appsite Terminal.

• Your open folder (Local mode only). With My CLI, the model may be given your open folder, read-only: by the appsite CLI itself (ask --read, secret files denied) — or, when your CLI is older than that, by the editor, which picks at most 8 files (28 KB) matching your question's words, removes obvious secrets, and tells the model exactly which ones. The line under your question says what was read ("Read 2 files of my-sdk: runner.mjs, README.md"), or that no folder is open. Never in cloud mode. Turn it off with appsite.cli.readWorkspace.
• Only what the chip under the box shows is sent: the selection, or the open file when nothing is selected, capped at appsite.ai.maxContextKb. Turn it off with the checkbox or appsite.ai.includeContext.
• Obvious secrets are removed first (private keys; Google, Anthropic, GitHub, AWS and Slack keys; JWTs; password = "…" style values). Files that exist to hold secrets (.env*, *.pem, id_rsa*, service-account JSON, .npmrc, *.tfvars) are never attached whole. This is a safety net, not a guarantee — check the chip.
• Code is attached to the question it was sent with; earlier turns resend only the words, and only the last 4 exchanges.
• Your AppSite records (appsite.ai.searchRecords). When a question names a kind of record, the extension asks Google's Firestore (firestore.googleapis.com) for that kind, with your own sign-in — the database's rules decide, exactly as in the AI module, and a collection you may not read is reported as not allowed, never worked around. Only the tenant you are working in, only rows marked with that tenant, at most 200 records from each of at most 6 collections, at most 24,000 characters attached. Where your tenant's records live is read from AppSite's registry (your tenant's entry, else its public copy). Collections that hold credentials are never asked for; fields named like passwords, tokens or keys are dropped; card- and SIN-shaped numbers are removed. What is attached goes with that one question — to AppSite AI (counted against your tenant's tokens) in CLI runner mode, or to the AI tool on this computer in Local mode. The line under each question says what was looked at. A tenant whose records live in its own Google project cannot be read from VS Code yet: nothing is attached and the chat says so.
• Your folder (Local mode, appsite.cli.readWorkspace). The appsite CLI hands Claude Code read-only file tools (Read, Grep, Glob) for that one folder — nothing that writes or runs commands, nothing outside it, and .env*, *.pem/*.key, id_rsa*, service-account and *credentials*.json, credentials, .npmrc/.netrc/.pypirc, .git-credentials, .pgpass, .htpasswd and *.tfvars are denied. What it reads is sent to Anthropic under your own Claude plan, as part of that question. A secret kept in an ordinary file could still be read — this is a safety net, not a guarantee. When Claude Code cannot answer and another tool does (agy, Copilot), the folder is not read, and the answer's footer says so. The folder is never offered in Restricted Mode, and needs an appsite CLI that knows --read (an older one answers without the folder, and the chat says so).
• Your session's refresh token is kept in VS Code's secret storage (your OS keychain), never in settings or files. /logout deletes it from this computer.
• A sign-in the extension did not start is ignored. Your ID token is only ever sent to Google's own sign-in and database addresses (securetoken.googleapis.com, firestore.googleapis.com) and to AppSite's Cloud Functions / Cloud Run addresses.

AppSite keeps a registry of installations. The installer registers when it finishes, and the extension registers when VS Code starts, every 30 minutes, and when you sign in.

• Sent: a random id made on this computer (not derived from it), the extension and editor versions, your OS family and CPU, whether the editor is remote or web — and, only when you are signed in, your ID token, from which the server takes your tenant and email.
• Not sent: IP address, hostname, user name, paths, workspace or file names, anything you typed. Registration carries none of your questions or code.
• Your control: the appsite.ai.registerInstall setting, VS Code's own telemetry switch, or --no-register on the installer.
• Revoke: /revoke in the chat, AppSite AI: Revoke This Installation's Registration, or the installer's --revoke <id>. The record is erased and the extension never registers again until you turn it back on.
• Administrators: a tenant's owner or admin sees and can revoke that tenant's signed-in installations; AppSite platform staff can act on any (AI module → Connections → Installations). A revoked extension signs out and refuses cloud answers until it is reinstated. Every action is audited.

• Status (2026-10-12): the deployed appsiteAiProxy predates the allowance and role gate (built, not yet deployed), so today it does not refuse on allowance or role. The extension does not enforce either itself.
• Version numbers read <tenant>.<type>.<changes>: the first number is the publisher (0 is Appsations, Inc.; AppSite's own modules use 1), the middle is the type of release, and the last counts changes.
• Develop: open the vscode/ folder of the AI module's repository and press F5 to run an Extension Development Host. npm test runs the extension's tests; the extension has no dependencies and no build step.
• Release: npm run package builds the .vsix; npm run release:site re-packages and publishes it to the AI module's downloads together with its manifest (size + SHA-256) and the three double-click installers; node scripts/release-site.mjs does the same without re-packaging (use it when only the installer or launchers changed — vsce does not build byte-identical files).