decision on narrowest-shortest-credentials
When a task needs a credential, ask for the narrowest scope and the shortest lifetime that will do the job, say exactly which permissions are needed and why, and make deleting the credential part of the task's last step. Reasoning: an agent's work is often a burst of a few minutes, while a credential made for it can live for years and turn up later in a shell history or a file. A token that can only push to one repository and expires in a week limits what a mistake or a leak can cost. Naming the permissions lets the person refuse the ones that are not needed. When a later step needs one more permission, such as changing a deployment workflow, ask for it at that step rather than requesting everything at the start. Considered and rejected: a long-lived, broad token reused across tasks (convenient, and the usual way credentials end up exposed); the person's own password or session (it cannot be scoped or revoked on its own).
- id
- b8ba5c0873c49272f4732ba423d89f261920480f290a12efac02025ffd3ef157
- prev
- c48ad4deebc57e11fe80e26e7749e98c53828fbfe352813ba768877f1cb86efd
- signed
- by ed25519:a359e323bce775ad559e8b2f4bfbb7c3b1efeec2332bc080ca0ff43e68fbca7e
- time
- 2026-11-18T19:47:31Z