Community: how to reach Signoos
Signoos is built in close conversation with the teams using it. This page is the front door: how to get help, how to tell us what to build, and how to report something that is wrong — with a person answering at the other end of each.
How to reach us
Every channel below is read by the people who build the product. We keep the list short on purpose: a channel we cannot answer well is worse than no channel.
- Email — [email protected] for anything: questions, problems, account matters, and security reports.
- In the product — feedback given from your account reaches us with the context needed to act on it.
Getting help
Start with the documentation — it covers setup, tasks, the solver, the AI console, and both developer clients, and it is maintained against the product rather than ahead of it. For the terminal client, signoos doctor checks this machine's setup and says what to fix, in words meant to be read.
If the answer is not there, write to us. Include what you did, what you expected, and what happened instead; for CLI matters, signoos --version and your platform help us reproduce it.
Feature requests and feedback
Tell us what the product should do — especially where it made you work around it. The most useful requests describe the situation rather than the feature: what you were trying to accomplish, what got in the way, and what it cost you. We read everything, and we are honest in reply: “no” and “not yet” are answers you will actually get, with the reasoning.
Note that under our terms, feedback you choose to give us may be used without obligation — feedback is not your content, and your content is never feedback.
Reporting a vulnerability
If you believe you have found a security issue in Signoos — the web application, the API, the CLI or the MCP server — tell us at [email protected]. Our disclosure policy, including what helps us act quickly and what is out of scope, is published at /.well-known/security.txt. We acknowledge reports and tell you what we find — including when we conclude an issue is not exploitable, and why.
How we work with you
- We answer. A report or a question gets a reply from a person, not a ticket number and silence.
- We say what we find. The product is built on showing its evidence, and so is the conversation around it — including “we could not reproduce this” and “this is by design, and here is why.”
- We change the page, not the story. When behaviour changes, the documentation and policies change in the same breath — the date at the top of each page says when.