The questions people ask about Signoos
The questions people ask before and after they connect a repository, answered in the product's own terms. Each answer is a summary of a page on this site and links to it; when the two disagree, the page is right and this one has a bug.
What is Signoos?
Signoos is team and product management built around a live mirror of a GitHub repository you connect. You describe work in plain words; Signoos finds the code it is about, reviews every push against what was asked, and can draft a patch — while every decision that matters stays with a person on your team.
See What is Signoos, as a document · Why it is built this way
How does Signoos work?
In three steps. Connect a repository by installing the Signoos GitHub App on the repository you choose; code access is off until you turn it on, and then it is folder by folder. Delegate a task by describing the work the way you would to a colleague; Signoos finds the files it is about and binds the task to a branch. Then every push to that branch is reviewed against what was asked. The review is advice: it blocks nothing, and only a human closes work.
See The three steps, on the landing page · Getting started, in the documentation
How do I create an account and set up Signoos?
Create an account at signoos.com/register with an email and password, or with GitHub. Then create a project — one product: one repository, one team — and connect the repository through the Signoos GitHub App, choosing on GitHub’s own consent screen which repositories the installation may see. Answer the code-access question: it is off by default, and you turn it on per folder if you want localization, fix drafts and the solver to see code. Then delegate your first task. Team members are found by their public username and join by invitation.
See Create your account · The first ten minutes, in four steps
How do I sign in?
Sign in at signoos.com/login with your email and password, or with GitHub. If you have set up two-factor authentication you will be asked for a current code. If you have forgotten your password, the sign-in page links to a reset that reaches you by email. From a terminal, signoos login connects that machine to your account through your browser.
Is Signoos secure? Does it store my code or my GitHub credential?
Signoos is built on least capability, least data and least credential. It reads your repository; the one thing it can write is a finished solver patch, as a commit on a branch with a pull request — never a merge, never a force-push. Code is read only inside the folders you granted, every read path enforces the same grant, and the check fails closed. No GitHub token is stored: the App installation is exchanged for an hour-long token at the moment of use and allowed to expire. A hosted mirror of the repository exists only where you allowed code access, and it serves only the folders you granted.
Which AI models see my code?
Three AI companies and no others: OpenAI, Anthropic and Google — and only within the folders you granted. If you never grant code access and never run the solver, no repository content of yours reaches an AI provider through Signoos. Your code, tasks, reviews and tickets are never used to train or tune any model. The team leader assigns a model to each job in the AI console, and every member can read the assignments.
See AI processing: what is sent, job by job · The AI console
Does Signoos push to my repository or merge anything?
Nothing is pushed unless your team has pushing on and somebody presses the button, or a leader switched on the automatic commit, which is off by default. What reaches GitHub is a commit on the task’s own branch with a pull request beside it — never a merge, never a force-push over work that moved, and nothing at all where a leader switched pushing off. Reviews and verdicts are advice; tasks are closed by people.
Can I use Signoos from my terminal or my editor?
Yes. The terminal client is @signoos/cli: install it with npm install -g @signoos/cli, connect the machine with signoos login, and see the tasks assigned to you in the repository you have open. The editor server is @signoos/mcp, spawned by your editor after signoos setup prints the config for Cursor, Claude Code, VS Code, Codex, Kiro or Windsurf. Both are read-only by construction, and every connected machine can be revoked at signoos.com under Configurations, Devices.
See The command line: @signoos/cli · The editor server: @signoos/mcp
How do I delete my account?
Sign in, open your profile settings at signoos.com/settings/profile and use Delete account at the bottom of the page. You will be asked to type your email address to confirm and to prove your identity. The mobile app has the same control. What deletion removes, what is kept and for how long, and what to do if you cannot sign in are on the account-deletion page.
How do I get help or report a problem?
Start with the documentation, which covers setup, tasks, the solver, the AI console and both developer clients. If the answer is not there, email [email protected] — for anything: questions, problems, account matters and security reports — and include what you did, what you expected and what happened instead. Vulnerability reports follow the disclosure policy in security.txt.