Skip to content

chore: point .env at 1Password Environment - #37

Open
remote-llm[bot] wants to merge 1 commit into
mainfrom
chore/add-env-1password
Open

remote-llm[bot] wants to merge 1 commit into
mainfrom
chore/add-env-1password

Conversation

@remote-llm

@remote-llm remote-llm Bot commented Sep 21, 2026

Copy link
Copy Markdown

TL;DR

This repo's .env now comes from a 1Password Environment instead of a file
pasted in by hand. This PR adds only the pointer — no secrets, no behaviour
change.

  1Password Environment                    this repo
  aperiodic-io/atlas
           ▲                               .env.1password
           └───────── named by ────────────┘   (committed)
           │
           ▼
     op-env run -- <cmd>     values injected at run time, nothing on disk

What it adds

File 1Password Environment
.env.1password aperiodic-io/atlas

Naming follows <github-org>/<repo>[/<app>] [stage].

Using it

op-env check              # auth + which Environment + how many vars
op-env run -- <command>   # preferred: nothing written to disk
op-env write              # only when a tool insists on a real .env file

op-env walks up from $PWD to the nearest .env.1password, so each app
directory gets its own Environment.

Tooling and setup: https://github.com/szemyd/ssh-llm-setup

🤖 Generated with Claude Code

Adds .env.1password naming the Environment that backs this repo, so
secrets are pulled with op-env instead of living in a pasted file.
No secrets and no behaviour change.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants