Key concepts
Organization and membership
Section titled “Organization and membership”Your instance belongs to exactly one organization. A Hacker Sidekick account can use the instance only if it is a member of that organization. Someone with a valid Hacker Sidekick account who isn’t a member sees “You haven’t been given access to this server” and is sent back to the public Hacker Sidekick portal.
Membership is checked continuously, not just at sign-in. If someone is removed from the organization, they lose access to the instance within about 5 minutes, even if Desktop still holds a sign-in token for them.
Admins and standard members
Section titled “Admins and standard members”Every member is either an Admin or a Standard member. Admins can change instance configuration; standard members can look but not touch. See Roles and permissions.
Models
Section titled “Models”Your instance runs on dedicated model capacity that Hacker Sidekick provisions and maintains for you. To add a model, change one, or change which model does which job, contact Hacker Sidekick.
Roles: default, sensitive, classifier, embedding
Section titled “Roles: default, sensitive, classifier, embedding”Each model serves one or more roles:
| Role | What it’s for |
|---|---|
| Default | Ordinary requests. Required. Everything falls back to it. |
| Sensitive | Offensive-security work: exploitation, payloads, red-team tasks. Optional; falls back to default. |
| Classifier | A small, fast model that decides, per request, whether it’s default or sensitive work. Optional; falls back to default. |
| Embedding | Turns files into vectors for Desktop’s workspace search. Optional, no fallback. |
Tiers and routing
Section titled “Tiers and routing”Every chat request from Desktop lands on either the default tier or the sensitive tier. The routing policy decides how: let the classifier choose per request, or force one tier for everyone. See Model routing.
Pushed content
Section titled “Pushed content”Admins can push four things to every member’s Desktop:
- an org system prompt: standing instructions added to every agent conversation,
- a Rules of Engagement (RoE) template: the starting point for each new engagement,
- skills: playbooks the agent loads when relevant,
- MCP servers: tool servers the agent can call, reached through the instance so the credentials never leave it.
Desktop checks for changes when the member signs in and every 10 minutes after that, and keeps the last copy it received if the instance is briefly unreachable.
Usage and the change log
Section titled “Usage and the change log”The instance records every model request (who, which model, which tier, tokens, success or failure) and every configuration change an admin makes. Both are visible on Audit & Usage.
