Which board to post on

The five boards, what belongs on each, and the one that is internal to the project.

Written By Dustin

Last updated About 3 hours ago

There are five boards. Three are public, one is limited to design partners, and one is internal to the project.

Feature requestsSomething TOVIO does not do, or does in a way that costs you work.
Bugs & rough edgesSomething broken, wrong, or confusing enough to count as broken.
Docs & quickstartA page that is wrong, missing, or lost you — including the getting-started path.
Design partnersSegmented: visible only to design partners. See The design partner program.
Team captureInternal to the project. Not visible outside it, and not somewhere you can post.

If you pick the wrong one

It is not worth fixing twice. Leave the post where it is and say so in a comment rather than deleting it and filing it again somewhere else — a duplicate costs more than a misfiled post. Choosing well only ever saved a step.

The one choice that cannot be undone is posting a security issue on any of them. That has its own article, and the rule has no exceptions.

The fields

Surface is required on the three public boards: CLI, VS Code, JetBrains, Desktop, Web app, Cloud / Forge, MCP / agents, SDK / bindings, Docs, Git migration, or Other. Error code, TOVIO version, and OS are optional and worth filling in on anything that looks like a bug.

Tags

Tags are applied during triage rather than by you. Most name the area a post touches — permissions, secrets and sealing, agents, MCP, locking, conflicts, sync, Git migration, install, performance, error messages, onboarding, pricing, enterprise, accessibility, cloud — and a few are process tags such as needs-adr, quick-win, and design-partner. You do not need to guess them; describing the problem well is enough.

What Team capture is, since it is named here

It is where the project records wants heard somewhere other than the boards — in a call, an email, a conversation — so they are not lost. It holds paraphrased wants only: no company names, no quotes, no contact records. Nothing is ever moved from it onto a public board. It is named in this article because the workspace configuration is published in the project repository, and it would be strange to list four boards when there are five.

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.