A boundary
you can understand.

Local inference never sends project content to a hosted model provider.

Stays on your hardware

The workspace and local model run on the computer or private server you choose.

  • Selected project files and instructions
  • Recorded decisions and generated outputs
  • Model inference over that project content

Requires your permission

Web research and external connectors are separate capabilities. Both are off by default.

  • Web requests can expose queries to outside services.
  • Connectors send the data needed for the action you allow.
  • Review the destination and scope before enabling either.

Roles define access

An agent’s job does not give it unrestricted access. Read, write, and request permissions are explicit.

  • Read only the selected project context.
  • Write only where the role is permitted.
  • Request only the roles its policy allows.

Local work.
Separate outside access.

A source citation helps you check an answer. A permission boundary helps you control what the agent can reach. You need both.

Your computer or private server
Project filesLocal modelYour output

Outside your boundary

Web researchOff by default
External connectorsOff by default

Permissions, in plain language.

PermissionWhat it controlsWhat to review
ReadWhich project material a role may use.Include only the files needed for its task.
WriteWhere a role may create or change outputs.Keep source files and draft outputs distinct.
RequestWhich other agent roles it may ask to act.Review the permissions of those roles too.
External accessOptional web research and connector actions.Check the destination and data leaving your boundary.

The website and your
workspace are separate.

This marketing website does not access your self-hosted project files. Website account creation uses the hosting platform’s sign-in to verify your identity, then requires a valid invitation. It stores your account identity, display name, and invitation redemption record.

The site saves your theme preference in this browser. It includes no advertising or analytics scripts. The hosting service processes requests and authentication under its own policies.

Account and inquiry records remain until the site owner deletes them. Use the contact form to request access, correction, or deletion. Submitting a request does not delete records automatically; verification may be needed before account changes. Short-lived, hashed request counters help limit abuse and are removed when expired entries are next cleaned up.

When you submit the contact form, your name, email, message, submission time, and receipt reference are stored in this website’s hosted database for the site owner to review. This is separate from local model inference. Do not include confidential files, passwords, or private client material.

Source material

Sample source material for this product walkthrough.