The loopback boundary

Agentissimo keeps code execution local. The daemon’s server binds loopback only — 127.0.0.1 and ::1 — and never 0.0.0.0. Your code, keys, and agent processes stay on your machine. The hosted backend handles account auth and coordination, but it does not execute agents or hold model keys.

Two layers

1. The bind. Both the dev server and the packaged server bind loopback addresses only. An outside host cannot reach the port at all.
2. The guard. Endpoints that supervise child processes or touch worktrees additionally check the caller’s address and reject any non-loopback caller with HTTP 403 — defense in depth on top of the bind.

The desktop shell holds the same line: it points its window at the loopback URL and rejects navigation anywhere else.

What this means

• Nothing from the local daemon is served to the network.
• An account is required for the hosted backend, but there is no remote build and no remote execution.
• The agent CLIs run as local processes under the supervisor, on your machine.

Telemetry

Agentissimo collects no telemetry by default. An opted-in account may sync aggregated skill-usage counts (day, catalog, skill, harness, count) to the backend — no code, keys, prompts, or model responses are included. See the privacy policy.