Skip to content

Working in a managed install

When Desktop is connected to your instance, it works the way you’re used to, with a few differences.

Every request the agent makes goes to your instance’s dedicated models, as your administrators have set them up. You don’t pick a tier. Your instance decides per request whether it’s ordinary work (default tier) or offensive-security work (sensitive tier), or your organization sends everything to one tier. See Model routing if you’re curious how.

Workspace indexing and web search also go through your instance.

Skills your administrators publish show up in the Skills view with an org badge. The agent can load them like any other skill. You can’t edit or delete them in Desktop; ask an administrator if one needs changing. Your own skills and the Hacker Sidekick built-in skills are still there.

MCP tool servers your organization publishes appear in the MCP view with an org badge. They’re reached through your instance, so the server address and credentials never touch your machine. You can’t edit or remove them, but you can switch one off locally if you don’t want the agent using it.

Your organization decides whether you may also add your own MCP servers. If it doesn’t allow them, the option to add a server is hidden and any personal servers you added before are disconnected. They come back if the policy changes.

Calls to org MCP tools are recorded in your organization’s change log by tool name only. The arguments you pass and the results that come back aren’t recorded.

If your organization pushes a system prompt, the agent receives it as Organization instructions that apply to all work on the instance. It’s added after your own custom instructions from Settings, so you can still add your own preferences, but the organization’s instructions take precedence where they conflict.

If your organization pushes an RoE template:

  • Desktop treats it as your RoE when deciding whether one is present.
  • Creating a new engagement RoE starts from your organization’s template instead of a blank page. Fill in the engagement-specific details as usual.
  • No plans, upgrades or top-ups. The plan badge, usage meter, upgrade and top-up prompts are hidden. Your organization pays for usage under its contract. If a run is paused because your access was refused, Desktop tells you to contact your admin; once access is restored you can resume where it left off.
  • There’s no per-person monthly token cap.
  • You can have up to 30 requests in flight at once. Past that, extra requests are refused with “Too many concurrent requests” until earlier ones finish. Normal use, including parallel sub-agents, rarely reaches this.
  • You can start up to 600 requests a minute. That’s far above normal use; it exists to stop a runaway script or loop.

Desktop refreshes your organization’s policy, skills and MCP servers when you sign in and every 10 minutes. If a refresh fails because of a network problem, Desktop keeps using the last copy it received. Model requests still need the instance to be reachable.

If your access is revoked, the next refresh clears the organization’s policy, skills and MCP servers from Desktop.

If you’re removed from the organization, the instance stops accepting your requests within about 5 minutes and the status bar shows <your organization> rejected this account. You stay signed in. To go back to the standard Hacker Sidekick service, choose Use my personal account in Settings → Enterprise (beta) (and clear any manual instance address you set).