What the editor and desktop surfaces send

TOVIO's governance rule is that the software does not report to anyone unless you act. This article says what that means concretely on each surface, because a rule is only worth as much as its implementation.

The editor extensions

Neither extension makes a network request. They spawn the tovio binary and parse its output — that is their entire input and output. Any traffic you see comes from the CLI doing what you asked it to do, such as a sync.

There is exactly one outbound thing, and it is a browser link: Send Feedback…. It opens a page in your browser, only when you invoke it, and the URL carries only three fields:

• from — which surface you are on, vscode or the JetBrains equivalent
• code — an error code, and only if it matches the exact TVO-AREA-NNN shape; anything else is dropped rather than forwarded
• v — the extension version, omitted when blank

The title, cause, context, and any file paths from an error envelope never leave the editor. The link points at a TOVIO-owned address, never directly at a third-party portal, so where it forwards is a decision the project can change without shipping a new extension.

The desktop app

Its interface runs under a content-security policy whose connect-src permits only its own origin and the local inter-process channel. It cannot open a network connection at all — not to TOVIO, not to anyone. Everything it does goes through the engine embedded in the same process.

Its browser layer is also granted no filesystem, dialog, shell, process, or HTTP capability. Choosing a folder or a certificate happens inside a trusted native command, not by handing a path string from the web layer to the host.

No update check either

The desktop app does not currently check for updates. There is no periodic call, no version ping, and no setting to disable because nothing is running. See the update article for what exists and what does not.

What the CLI sends

Only what you ask it to: sync, push, pull, clone, fetch, and the Forge commands talk to a relay or Forge you configured. Opportunistic auto-sync can piggyback on a commit or a land, which is a convenience rather than a surprise — suppress it for one command with --no-sync, or persistently with TOVIO_NO_SYNC.

When you do report something

The feedback boards are public and third-party hosted. Send the TVO-* code, your version, your OS, and a description of the behaviour. Never repository contents, file paths, diffs, tokens, keys, or anyone else's data — paths in particular are metadata that often disclose more than the content would. If you cannot describe the problem without one of those, treat it as potentially security-sensitive and use the private channel at tovio.dev/security instead.