Headmaster by GCAP Labs

Headmaster can connect to a hosted runtime or a local runtime. The current desktop app prioritizes the hosted service, with local operation available as a fallback. Where data is processed depends on the runtime, model, memory and tool providers you connect.

Know where the work runs

In a hosted setup, your messages and relevant context are sent to the connected runtime. In a local setup, the runtime operates on your machine, but calls to cloud models and external tools still send the data those services need. Local operation does not make cloud model requests private to your device.

Models and connected tools

A model request can include your prompt, conversation context, relevant memory and file contents provided to the agent. Tool calls send their arguments to the selected service. Review provider policies and the scope of each connection before adding sensitive material.

Permissions and review

Tool permissions depend on the engine and permission mode you select. Some modes ask for approval; others allow actions within their configured scope. Do not assume that every external action pauses for review. Start with a bounded task and verify the permission settings for its engine.

Credentials and storage

Credential handling and data storage differ between local and hosted configurations. Protect the device and runtime account, use narrowly scoped provider credentials, and revoke connections you no longer need. This page does not promise a particular encryption-at-rest implementation or that credentials always remain on your device.

Removal and retention

Uninstalling the desktop app does not necessarily remove hosted data, provider records or local app data. Review the connected services and your installation’s data location before deleting anything. Retention is specific to each provider and deployment.

Questions