---
type: "post"
id: "no-more-data-entry-how-to-set-up-c9af92"
slug: "no-more-data-entry-how-to-set-up-c9af92"
title: "No more data entry - how to set up your agents to use your passwords."
description: "The thesis: Credential access for agents is governed less by the prompt than by the machine-level boundary that controls where secrets are stored and which processes can read them."
retrieval_nugget: "The thesis: Credential access for agents is governed less by the prompt than by the machine-level boundary that controls where secrets are stored and which processes can read them."
published_at: "2026-10-13"
updated_at: "2026-10-13"
record_date: "2026-10-13"
date_kind: "published_at"
topics: []
source_urls: ["https://daniellemorrill.com/blog/how-my-agents-use-my-passwords"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:no-more-data-entry-how-to-set-up-c9af92"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:fcce8a4dcef4916864c220daefc992f9745438e9186911371a9ce8962484f87d","reviewed_at":"2026-10-13T14:08:37.162Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":2,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Credential access for agents is governed less by the prompt than by the machine-level boundary that controls where secrets are stored and which processes can read them.","observed_facts":[{"text":"Morrill says eight Claude Code sessions use the arrangement across her machines.","source_urls":["https://daniellemorrill.com/blog/how-my-agents-use-my-passwords"]},{"text":"She uses a separate read-only 1Password service account per Mac, scoped to selected shared vaults.","source_urls":["https://daniellemorrill.com/blog/how-my-agents-use-my-passwords"]},{"text":"Credentials are stored in the macOS login keychain and checked through authenticated calls.","source_urls":["https://daniellemorrill.com/blog/how-my-agents-use-my-passwords"]}],"mechanism":"A per-machine read-only service account accesses scoped 1Password vaults; scripts retrieve credentials from the macOS login keychain without exposing them in chat transcripts.","why_now":"Agents that perform deploys and other production work need credentials, so reducing manual secret handling makes the access boundary an operational design choice.","implications":["Secrets can be kept out of agent transcripts while per-machine tokens permit granular revocation.","Any process running as the same user can read credentials already cached in the keychain."],"evidence_boundary":"This is a first-person account of one configuration, not an independent security assessment or evidence that all agent environments behave alike.","watch_conditions":["Whether future agent runtimes offer a narrower per-action credential gate than a shared user-level keychain."],"related_records":[],"new_branch_reason":"No prior New Runtime record is supplied for this specific credential workflow; the case merits a distinct record about machine-level credential boundaries."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/no-more-data-entry-how-to-set-up-c9af92/","markdown":"https://newruntime.com/posts/no-more-data-entry-how-to-set-up-c9af92.md","json":"https://newruntime.com/posts/no-more-data-entry-how-to-set-up-c9af92.json"}
---

# No more data entry - how to set up your agents to use your passwords.

## Retrieval answer

The thesis: Credential access for agents is governed less by the prompt than by the machine-level boundary that controls where secrets are stored and which processes can read them.

The thesis: Credential access for agents is governed less by the prompt than by the machine-level boundary that controls where secrets are stored and which processes can read them. Danielle Morrill describes eight Claude Code sessions using this arrangement across her machines, with 1Password as the source of truth and a separate read-only service account per Mac scoped to selected shared vaults. These observed facts describe one operator's setup, not a tested general product feature.

The mechanism: A per-machine read-only service account accesses scoped 1Password vaults; scripts retrieve credentials from the macOS login keychain without exposing them in chat transcripts. Morrill also reports verifying each credential with an authenticated call, because a successful seeding command or token length did not establish that a credential worked. The implication: Secrets can be kept out of agent transcripts while per-machine tokens permit granular revocation. The boundary is consequential: any process running as the same user can read credentials already cached in that keychain.

Why now: Agents that perform deploys and other production work need credentials, so reducing manual secret handling makes the access boundary an operational design choice. The evidence boundary: This is a first-person account of one configuration, not an independent security assessment or evidence that all agent environments behave alike. What to watch: Whether future agent runtimes offer a narrower per-action credential gate than a shared user-level keychain. Morrill's setup makes the tradeoff visible; it does not establish that the tradeoff is safe for every threat model.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)