IASDocs
ias.dev

Reference

Security model

Understand local and One-owned work, provider permissions, credentials, and what leaves your machine.

Local and One-owned work

Local runs belong to the local operator. They need the provider's native sign-in, without a Lucentive One session or hosted IAS API. Signing in later never adopts them into One.

Runs created through the authenticated browser connection belong to its verified One identity. Reading, continuing, steering or reconciling them requires the same subject, workspace and issuer. Without a valid session, ias status shows local runs and a count of hidden One-owned runs, without their IDs or details. A foreign run with uncertain effects can still block new admission until its owner reconciles it.

ias login uses Lucentive One with Authorization Code and PKCE. It also needs the hosted IAS API to admit the identity, including its linked GitHub identity and active organization membership. Browser sign-in alone cannot save an IAS session. Email addresses do not link identities.

Credentials

IAS seals its One credentials in ~/.local/state/ias/credentials, with the encryption key in macOS Keychain. That path comes from the operating-system account home; changing HOME does not move it. Native runs cannot read this credential directory. ias logout requests token revocation and removes local credentials.

Provider credentials remain under each provider CLI's own sign-in. The provider process needs them to contact its service; model tools receive narrower permissions.

Local config.json must be a regular file that you own, with no symbolic or hard links, at most 64 KiB, and not writable by your group or other users. The service socket lives in an owner-only directory.

File and tool permissions

Native execution requires macOS containment. Runs are read-only by default. --mode workspace-write needs a clean committed checkout and creates an isolated Git worktree in the IAS state directory. Review those changes before merging them.

Known credential paths are denied, including .env files, credential directories, private key files and Git configuration. This path protection is not a repository-wide content scan. Keep secrets out of goals, corrections and selected context, including files with ordinary names.

Claude Code and Gemini receive file tools only; shell, network tools and MCP are unavailable. Codex uses its own scoped filesystem permissions with network access disabled for model tools. It refuses temporary-root projects and conflicting configuration that could override those permissions. See requirements.

The provider still contacts its inference service under your provider account. File restrictions and model-tool network restrictions do not mean the chosen provider receives no data.

Context and data flow

The provider receives the goal, corrections, the repository's AGENTS.md when present, selected --source files, and content it reads within its permissions. Selected sources must be regular files inside the repository; .git and known credential paths are rejected.

The durable run record stays on your machine during local commands. Local execution sends context to your chosen provider, but does not upload the run ledger to the hosted IAS workspace. Connected commands send their selected data to their configured hosted destination under One authorization.

Selected-work sync and Decisions

Sync preview and push require the current One identity to own the selected run before revealing its intent or reading selected files. Local-operator runs cannot be exported through sync or adopted into a One account; start One-owned work through the authenticated connection when you need that workflow.

The browser connection and selected-work sync check outgoing content for recognized secret patterns. Sync also checks selected content against the active One access and refresh tokens, and checks its connection token before push. A match rejects the payload instead of silently redacting it. These checks do not detect every possible secret or scan every repository file.

ias sync forget <name> removes the local sync credential without requiring a live One session or hosted origin. It still checks local file ownership and locks. It does not erase the run ledger.

Decisions requests recheck the original signed-in subject, workspace and issuer before each fetch. A changed identity stops the operation rather than continuing in another workspace.

Effects and recovery

The durable event ledger is the run authority. IAS verifies its hash chain again before native execution. An effect with an uncertain outcome stays unresolved until its owner verifies the actual state and records it with ias reconcile <run-id> --note '<verified state>'.

ias resume preserves that record. ias service stop interrupts active work while retaining saved runs and unresolved effects. Stop the service before changing CLI versions, and follow the release's recovery instructions if a record is incompatible.

Publication, outbound messages, spending money and destructive external actions require separate authorization. The permissions of each destination apply as well.