Agent Login
Pick the route that matches the task. Each route ends at its own finish line.
A missing prerequisite ends the route as a named block.
Rules for every route
- Read access before any authenticated operation. It
decides who may use which credential and how to confirm the agent's identity.
- Setup or credential work does not continue into an application login
unasked, except onboarding's own proof login. A login that the user or a
calling workflow, such as verify, asks for counts as a request.
- Machine setup and other administration need an explicit user request. That
covers vault creation, service-account grants, token storage and rotation,
and host configuration. A login or credential task creates no tokens, changes
no grants, and reads personal credentials only as access approves.
- Keep values inside the consumer. Keep them out of chat, agent tool arguments,
logs, source code, project files such as tracked
.env files and fixtures,
and verification artifacts. Apply the user's capture policy.
- Send a credential only to exact approved destinations, including identity
providers and redirects. Use an encrypted transport for remote destinations,
such as HTTPS for web origins. Plain HTTP is allowed only for approved
loopback test origins.
- A login approval covers credential use, not later application actions.
- Report provider authentication, delivery, and login as separate results. Each
needs its own proof.
Machine or account setup
Use this route to provision unattended agent access, repair a runtime that
prompts for Touch ID, onboard an application account, or check login readiness.
- For the vault, service account, and each runtime's token, follow
machine setup. It is done when each affected
runtime authenticates as the designated identity.
- To onboard an application account, follow
onboard an account.
Onboarding includes its proof login. It is done when that login is verified
or a missing prerequisite other than the login itself is named.
Credential use, storage, or item management
Use this route when a command, API, test harness, or subprocess needs a
credential, when a value must be saved, or when items in the designated
writable agent vault must be created, updated, archived, or deleted. After
access, follow
secrets for programs.
It is done when one of these is true:
- The consumer authenticates or accepts the privately delivered credential.
Product and test results belong to the work that asked for the credential;
use verify for product assertions.
- The requested item state, such as saved fields or an archived or deleted
item, checks out in the designated vault under the scoped service account.
- The missing prerequisite is named, such as a missing runtime token or missing
scope.
UI login
Use this route to sign into an application in a browser or device session.
Reuse an existing authenticated session when its account and role fit the
requested work. Preserve user-established sessions. Reuse does not prove
automatic login; a login assertion starts from its required signed-out state.
- Choose a credential-aware consumer that resolves fields privately into the
actual browser or device session. Honor host routing. The bundled
agent-login command supports only 1Password and existing local Chromium
CDP tabs; follow browser login to
use it. Native T3/Codex browser and simulator adapters are not implemented.
An approved project consumer can supply another supported path. Ordinary
typing tools take literal values and cannot do private delivery. If delivery
is unavailable, report the missing integration and continue after user
sign-in.
- Treat filling or submission as delivery results. Use the original session to
confirm authenticated state and the intended account and role.
It is done when the original session shows the intended account and role and
stays open for the requested work. Use verify for product
assertions.
1---2name: agent-login3description: Use when signing into applications, setting up or diagnosing agent credential access, or supplying and managing approved credentials for authentication.4metadata:5 source: https://skillmd.com/skills/sreejithraman/agent-login6---78# Agent Login910Pick the route that matches the task. Each route ends at its own finish line.11A missing prerequisite ends the route as a named block.1213## Rules for every route1415- Read [access](references/access.md) before any authenticated operation. It16 decides who may use which credential and how to confirm the agent's identity.17- Setup or credential work does not continue into an application login18 unasked, except onboarding's own proof login. A login that the user or a19 calling workflow, such as verify, asks for counts as a request.20- Machine setup and other administration need an explicit user request. That21 covers vault creation, service-account grants, token storage and rotation,22 and host configuration. A login or credential task creates no tokens, changes23 no grants, and reads personal credentials only as access approves.24- Keep values inside the consumer. Keep them out of chat, agent tool arguments,25 logs, source code, project files such as tracked `.env` files and fixtures,26 and verification artifacts. Apply the user's capture policy.27- Send a credential only to exact approved destinations, including identity28 providers and redirects. Use an encrypted transport for remote destinations,29 such as HTTPS for web origins. Plain HTTP is allowed only for approved30 loopback test origins.31- A login approval covers credential use, not later application actions.32- Report provider authentication, delivery, and login as separate results. Each33 needs its own proof.3435## Machine or account setup3637Use this route to provision unattended agent access, repair a runtime that38prompts for Touch ID, onboard an application account, or check login readiness.3940- For the vault, service account, and each runtime's token, follow41 [machine setup](references/machine-setup.md). It is done when each affected42 runtime authenticates as the designated identity.43- To onboard an application account, follow44 [onboard an account](references/browser-login.md#onboard-an-account).45 Onboarding includes its proof login. It is done when that login is verified46 or a missing prerequisite other than the login itself is named.4748## Credential use, storage, or item management4950Use this route when a command, API, test harness, or subprocess needs a51credential, when a value must be saved, or when items in the designated52writable agent vault must be created, updated, archived, or deleted. After53[access](references/access.md), follow54[secrets for programs](references/secrets-for-programs.md).5556It is done when one of these is true:5758- The consumer authenticates or accepts the privately delivered credential.59 Product and test results belong to the work that asked for the credential;60 use [verify](../verify/SKILL.md) for product assertions.61- The requested item state, such as saved fields or an archived or deleted62 item, checks out in the designated vault under the scoped service account.63- The missing prerequisite is named, such as a missing runtime token or missing64 scope.6566## UI login6768Use this route to sign into an application in a browser or device session.6970Reuse an existing authenticated session when its account and role fit the71requested work. Preserve user-established sessions. Reuse does not prove72automatic login; a login assertion starts from its required signed-out state.73741. Choose a credential-aware consumer that resolves fields privately into the75 actual browser or device session. Honor host routing. The bundled76 `agent-login` command supports only 1Password and existing local Chromium77 CDP tabs; follow [browser login](references/browser-login.md#fill-a-tab) to78 use it. Native T3/Codex browser and simulator adapters are not implemented.79 An approved project consumer can supply another supported path. Ordinary80 typing tools take literal values and cannot do private delivery. If delivery81 is unavailable, report the missing integration and continue after user82 sign-in.832. Treat filling or submission as delivery results. Use the original session to84 confirm authenticated state and the intended account and role.8586It is done when the original session shows the intended account and role and87stays open for the requested work. Use [verify](../verify/SKILL.md) for product88assertions.