How to report a bug

Post it on the Bugs & rough edges board at feedback.tovio.dev. You need to be signed in — guest posting is off, because an anonymous poster can never be notified when their report is fixed.

If you arrived from a report link printed by the CLI or offered by an editor extension, that link opens the portal rather than a particular board, so pick Bugs & rough edges yourself once you are there. The link carries no more than the surface you were on, the error code, the documentation page, and your TOVIO version — never a path, a repository or lane name, or anything identifying you.

What to include

• The TVO-AREA-NNN code from the end of the error message. It is the single most useful thing you can send and it reveals nothing about your repository.
• A description of what the error said, in your own words, with file paths, repository and lane names, identities, and hostnames taken out. Describe it; do not paste the block.
• The output of tovio --version.
• What you expected to happen, and what happened instead.
• Which surface you were using, and your operating system.
• Whether it happens every time or happened once.

The Surface field is required on this board and is a fixed list: CLI, VS Code, JetBrains, Desktop, Web app, Cloud / Forge, MCP / agents, SDK / bindings, Docs, Git migration, or Other. Three more fields are optional: Error code and TOVIO version are free text, and OS is a short list — Linux, macOS, Windows, or Other. Filling them in is what makes a report findable later, by us and by the next person who hits it.

What never to include

The boards are public and hosted by a third party. Describe the behaviour rather than pasting:

• repository contents, file paths, or diffs
• tokens, keys, or session strings
• identities, hostnames, or anything belonging to other people
• raw, unredacted command output — an error block usually carries at least one of the above

If you cannot describe the problem without one of those, that is a signal the issue may be security-sensitive. Stop, and read Reporting a security vulnerability instead.

Before you post

Search the board first. If someone has already reported it, upvote that post and add what is different about your case as a comment rather than filing a second one.

After you post

Your post is held for review before it appears, and so is a comment. That hold is a safety control rather than a quality filter, and Community guidelines and moderation explains it. Once approved, the post starts in Under review; What happens to your post covers where it goes from there.

A documentation problem — a page that is wrong, missing, or lost you — belongs on Docs & quickstart rather than here.

Do not report security vulnerabilities here. This board is public and operated by a third-party vendor. Read https://tovio.dev/security and use the private channel it names. Never paste repository contents, file paths, diffs, tokens, keys, or other people's data — describe the behaviour instead.