Support
viewbus is a one-person project, so there's no ticket queue and no response-time promise. Everything below reaches me.
Bug reports and feature requests
Open an issue on GitHub. Feature requests are ranked by 👍 reactions and the most-wanted ones show up on the home page, so upvoting an existing one helps more than opening a duplicate.
Feedback from inside the app
viewbus has a feedback dialog built in. It reaches me directly, and it's the easiest route if you'd rather not post in public or don't have a GitHub account — including anything security-sensitive. You can optionally attach your local log file; logs carry no credentials and no message bodies.
In the app: Settings → Send feedback.
Before you file
A few things that usually answer the question faster than I can:
- The changelog — the fix may already have shipped. Check you're on the current version.
- The common questions on the home page.
- MCP setup and the local API reference, if you're wiring viewbus into something else.
When reporting a bug, the viewbus version, your OS, and what you were doing when it broke are usually enough. Never paste a connection string, an access token, or a real message body into a public issue — if the report needs one of those to make sense, use the in-app dialog instead.