Skip to content
Browse documentation
Controlled alphaValidatedClaude Code / Cursor · In development

Argos developer documentation

Security Model

Understand the trusted-host boundary and authority Argos does not grant.

Separate credentials

Browser OAuth authenticates a human. Agents use scoped execution credentials. Tracking grants no authority. Agents cannot approve REVIEW or submit verification.

Organization and project isolation

Existing membership, authorization and RLS boundaries remain authoritative. Adapter identity is descriptive, not authorization.

Trusted-host model

Argos controls supported operations through installed boundaries and rereads repository state. It assumes the host, runtime, dependencies and criteria are trusted. This is not malicious-host isolation.